Hyper-V does not support memory overcommit. Nor does VMware recommend using that feature in a production environment.
Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php -----Original Message----- From: Steve Moffat [mailto:[EMAIL PROTECTED] On Behalf Of NTSysAdmin Sent: Monday, December 08, 2008 8:47 AM To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types Strange I tried both. On a pair of Dell 1950's with 16gig of memory sharing an Openfiler San, (Powervault sc220s). At most I had 6 W2K3 VMs with 2 GB memory running on the HyperV. With ESXi I ran out of space on the LUN after 13 W2K3 VM's. Performance was fine on both. The benefit of being able to upgrade to get VMotion was also a mitigating fact. S -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 9:41 AM To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types Really? We did a basic test on one of our servers, the free ESX against Hyper-V and the general consensus was that the Hyper-V one is quicker. Besides we love all things MS here. Saying that I haven't run any definitive tests against the two, but the MS offering certainly did feel quicker when the chaps here sat in front of the VMs. Olly -----Original Message----- From: Steve Moffat [mailto:[EMAIL PROTECTED] On Behalf Of NTSysAdmin Sent: 08 December 2008 13:35 To: NT System Admin Issues Subject: RE: VMWARE to Hyper-V and HAL types You should have stuck with VMWare....ESXi (Also Free), is far superior to HyperV Beta...And I'm a Microsoft guy...HyperV won't catch up for a good few years yet. If you think HyperV is fast, ESXi will blow you away. S -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 9:29 AM To: NT System Admin Issues Subject: VMWARE to Hyper-V and HAL types Hi chaps, I'm looking at moving our VMWare based VMs to our new Hyper-V based servers. New VMs are working a treat, and certainly Hyper-V seems far more responsive than our VMWare based setup. However existing VMWare based VMs are proving an issue. While the VM's have been imported to Hyper-V without any problems it would appear that the HAL of the VMWare VMs have all been set to 'Standard PC' at some point during the installation of the guest OS (all Windows 2003). In order to install the Hyper-V tools we need to be running a ACPI based HAL. My question is this; is there a way in Windows 2003 to move from a Standard PC based HAL to an ACPI based HAL ? I know that MS don't support it (at least from what i can see on the web), but is there a way to hack a solution to it ? The only option we have at the moment is to re-install the guest OS's but that would mean a lot of work and possibly re-config of the apps running on them. Olly ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
