Guest Schmeg Posted July 14, 2008 Posted July 14, 2008 I have a Windows 2008 Stanard 32-bit terminal server. I need to run a Windows 2003 Standard 32-bit terminal server on it as a virtual machine. Our applications are not 64-bit compatible and do not have near term plans to support it. I know Windows 2008 Standard has a memory limit of 4G. With the virtual machine scenario, I am limited to splitting the 4G or could I physically put 8G in the box and split 4G for the host OS and 4g for the guest OS ?
Guest Jeff Pitsch Posted July 14, 2008 Posted July 14, 2008 Re: Windows 2008 TS Memory What are you using for virtualization? Keep in mind that Virtual Server will give you lousy performance and Hyper-v is only supported on 64-bit. Of course this will all depend on how many users you are planningo n the server but in your configuration, yes it will work with PAE switch on the host OS, you will get very few users on the system before it performance is an issue. Jeff Pitsch Microsoft MVP - Terminal Services "Schmeg" <sschmeg@yahoo.com> wrote in message news:%23MrEpMb5IHA.2064@TK2MSFTNGP02.phx.gbl... >I have a Windows 2008 Stanard 32-bit terminal server. > > I need to run a Windows 2003 Standard 32-bit terminal server on it as a > virtual machine. > > Our applications are not 64-bit compatible and do not have near term plans > to support it. > > I know Windows 2008 Standard has a memory limit of 4G. > > With the virtual machine scenario, I am limited to splitting the 4G or > could I physically put 8G in the box and split 4G for the host OS and 4g > for the guest OS ? > > > > >
Guest Schmeg Posted July 14, 2008 Posted July 14, 2008 Re: Windows 2008 TS Memory Thanks for the feedback. My original plan was to use Hyper-V from the Windows 2008 32-bit standard host as I wasn't aware Hyper-V was only supported on 64-bit. Knowing that, I would likely pursue the VMWare product. What do you consider as "very few users on the system before it is a performance issue" and what would make it the performance hog - the virtualization or other reasons? Thanks "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message news:OdAk4Wb5IHA.2064@TK2MSFTNGP02.phx.gbl... > What are you using for virtualization? Keep in mind that Virtual Server > will give you lousy performance and Hyper-v is only supported on 64-bit. > Of course this will all depend on how many users you are planningo n the > server but in your configuration, yes it will work with PAE switch on the > host OS, you will get very few users on the system before it performance > is an issue. > > Jeff Pitsch > Microsoft MVP - Terminal Services > > > "Schmeg" <sschmeg@yahoo.com> wrote in message > news:%23MrEpMb5IHA.2064@TK2MSFTNGP02.phx.gbl... >>I have a Windows 2008 Stanard 32-bit terminal server. >> >> I need to run a Windows 2003 Standard 32-bit terminal server on it as a >> virtual machine. >> >> Our applications are not 64-bit compatible and do not have near term >> plans to support it. >> >> I know Windows 2008 Standard has a memory limit of 4G. >> >> With the virtual machine scenario, I am limited to splitting the 4G or >> could I physically put 8G in the box and split 4G for the host OS and 4g >> for the guest OS ? >> >> >> >> >> > >
Guest Jeff Pitsch Posted July 14, 2008 Posted July 14, 2008 Re: Windows 2008 TS Memory I would recommend first of all researching your options before following through on any plan. What VMWare product? Keep in mind that anhything that runs on top of Windows (barring Hyper-V of course) is going through a few hops just to get to the hardware. for instance, VMWare ESX, virtual iron, go through one layer of virtualization and run their own specialized kernels design specifically for virtualization. Windows has none of this and you are going through at least two layers of virtualization to gain hardware access. I would highly, highly recommend that you become much more familiar with virtualization before you delve into this area. I dont' want to sound mean or anything but you didn't even know that hyper-v is 64-bit only and that was your game plan. I cannot stress enough that learning about new technology before you jump into it, especially with virtualization is critical. As for how many users, it's hard to say. Way to many variables but may anywhere from 5 - 20 quite easily less, possibly more. I truthfully can't think of an organization, at least ones I've dealt with, that would put anything less than ESX, Virtual Iron, XEN, or possibly Hyper-v into a production environment. Jeff Pitsch Microsoft MVP - Terminal Services "Schmeg" <sschmeg@yahoo.com> wrote in message news:epRbSUc5IHA.4268@TK2MSFTNGP02.phx.gbl... > Thanks for the feedback. > > My original plan was to use Hyper-V from the Windows 2008 32-bit standard > host as I wasn't aware Hyper-V was only supported on 64-bit. Knowing that, > I would likely pursue the VMWare product. > > What do you consider as "very few users on the system before it is a > performance issue" and what would make it the performance hog - the > virtualization or other reasons? > > Thanks > > > "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message > news:OdAk4Wb5IHA.2064@TK2MSFTNGP02.phx.gbl... >> What are you using for virtualization? Keep in mind that Virtual Server >> will give you lousy performance and Hyper-v is only supported on 64-bit. >> Of course this will all depend on how many users you are planningo n the >> server but in your configuration, yes it will work with PAE switch on the >> host OS, you will get very few users on the system before it performance >> is an issue. >> >> Jeff Pitsch >> Microsoft MVP - Terminal Services >> >> >> "Schmeg" <sschmeg@yahoo.com> wrote in message >> news:%23MrEpMb5IHA.2064@TK2MSFTNGP02.phx.gbl... >>>I have a Windows 2008 Stanard 32-bit terminal server. >>> >>> I need to run a Windows 2003 Standard 32-bit terminal server on it as a >>> virtual machine. >>> >>> Our applications are not 64-bit compatible and do not have near term >>> plans to support it. >>> >>> I know Windows 2008 Standard has a memory limit of 4G. >>> >>> With the virtual machine scenario, I am limited to splitting the 4G or >>> could I physically put 8G in the box and split 4G for the host OS and 4g >>> for the guest OS ? >>> >>> >>> >>> >>> >> >> > >
Guest jphallett Posted July 15, 2008 Posted July 15, 2008 Re: Windows 2008 TS Memory On Jul 14, 9:11 am, "Schmeg" <ssch...@yahoo.com> wrote: > I have a Windows 2008 Stanard 32-bit terminal server. > > I need to run a Windows 2003 Standard 32-bit terminal server on it as a > virtual machine. > > Our applications are not 64-bit compatible and do not have near term plans > to support it. > > I know Windows 2008 Standard has a memory limit of 4G. > > With the virtual machine scenario, I am limited to splitting the 4G or could > I physically put 8G in the box and split 4G for the host OS and 4g for the > guest OS ? I'm not a Windows server 2008 expert and I do not have a running 2008 machine yet. Everything I have read if you are running Standard 32-bit it will only recognize a maximum of 4 GB of ram so you would have to split it with VMWare. I currently run 2003 standard with 2 dual core processors and 4 GB of ram with VMware Server running another server on it. I split the ram between the physical and virtual machines. I have no issues with performance. The servers are running the same software just different versions. Just my 2 cents :-)
Recommended Posts