Comments on: Hyper-V, not in my datacenter (part 2: Guest OS and Memory overcommit) http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/ Your P.I. on virtualization Tue, 24 Aug 2010 15:28:38 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Dominique http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-982 Dominique Thu, 24 Jun 2010 08:37:33 +0000 http://www.gabesvirtualworld.com/?p=104#comment-982 Great article for people that want to understand memory-overcommitment and transparant pagesharing! Great article for people that want to understand memory-overcommitment and transparant pagesharing!

]]> By: George http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-825 George Tue, 16 Mar 2010 19:34:12 +0000 http://www.gabesvirtualworld.com/?p=104#comment-825 Ah ok that's cool, thanks for the explanation. I was about to post that I didn't understand. So there's a difference in architecture design btw the two?<br>George Ah ok that's cool, thanks for the explanation. I was about to post that I didn't understand. So there's a difference in architecture design btw the two?
George

]]> By: buy r4i http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-808 buy r4i Mon, 25 Jan 2010 18:46:47 +0000 http://www.gabesvirtualworld.com/?p=104#comment-808 Both ESX and Hyper-V are based on a hypervisor running on bare metal but uses 2 different architectures. The main difference as Andrew states is that once ESX is up and running the RHEL based servcie console can actually be unavailable and the VM’s on the ESX host will still run even though they will be unmanageable.<br><br>In Hyper-V the VM’s or child partitions are dependant on both the parent partition and the hypervisor. If the parent partition is not available and working then the guest VM’s will not work at all. Both ESX and Hyper-V are based on a hypervisor running on bare metal but uses 2 different architectures. The main difference as Andrew states is that once ESX is up and running the RHEL based servcie console can actually be unavailable and the VM’s on the ESX host will still run even though they will be unmanageable.

In Hyper-V the VM’s or child partitions are dependant on both the parent partition and the hypervisor. If the parent partition is not available and working then the guest VM’s will not work at all.

]]> By: Gabrie van Zanten http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-810 Gabrie van Zanten Thu, 17 Dec 2009 00:27:31 +0000 http://www.gabesvirtualworld.com/?p=104#comment-810 Hi, no I don't ignore the cost of ESX licensing. But you can't just say ESX costs (for example) $1000 and Hyper-V is free. If you can run 40 VMs on 1 ESX host and only 10 VMs on that same host when it is running Hyper-V, then you need more on hardware with Hyper-V. So yes the license cost of ESX is more, but don't your care on the total cost too?<br><br>Please, for good discussion, also supply your e-mail address when entering new comment.<br>Gabe Hi, no I don't ignore the cost of ESX licensing. But you can't just say ESX costs (for example) $1000 and Hyper-V is free. If you can run 40 VMs on 1 ESX host and only 10 VMs on that same host when it is running Hyper-V, then you need more on hardware with Hyper-V. So yes the license cost of ESX is more, but don't your care on the total cost too?

Please, for good discussion, also supply your e-mail address when entering new comment.
Gabe

]]> By: Kukulkan http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-809 Kukulkan Thu, 17 Dec 2009 00:17:43 +0000 http://www.gabesvirtualworld.com/?p=104#comment-809 The biggest hole in your review is ignoring the cost of ESX licensing. The biggest hole in your review is ignoring the cost of ESX licensing.

]]> By: penman96 http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-811 penman96 Thu, 10 Dec 2009 20:51:01 +0000 http://www.gabesvirtualworld.com/?p=104#comment-811 What the memory over-commitment table tells me is that 3 or 4 of these ESX host servers may start disk paging if there is a utilization spike. DRS wouldn't help either, as DRS isn't memory overcommitment aware. As you correctly said at first, memory overcommitment in production is a risky idea. VMware best practice discourages it too - even if their marketing materials do not. ESX 15 has a 25% memory overcommitment. <br><br>Not in my datacenter ;-) What the memory over-commitment table tells me is that 3 or 4 of these ESX host servers may start disk paging if there is a utilization spike. DRS wouldn't help either, as DRS isn't memory overcommitment aware. As you correctly said at first, memory overcommitment in production is a risky idea. VMware best practice discourages it too – even if their marketing materials do not. ESX 15 has a 25% memory overcommitment.

Not in my datacenter ;-)

]]> By: Data Centres http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-812 Data Centres Thu, 10 Dec 2009 13:10:36 +0000 http://www.gabesvirtualworld.com/?p=104#comment-812 Fantastic post. From last couple of month I need information about The guest OS support of Hyper-V. And finally I got all information. The post is very informative. Fantastic post. From last couple of month I need information about The guest OS support of Hyper-V. And finally I got all information. The post is very informative.

]]> By: Miquel Àngel http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-178 Miquel Àngel Thu, 28 May 2009 14:36:16 +0000 http://www.gabesvirtualworld.com/?p=104#comment-178 We are in the same problem we have in our CPD 90% microsoft products but when we wont virtualize we did it with ESXi because we still have windows NT in some servers....microsoft rules! We are in the same problem we have in our CPD 90% microsoft products but when we wont virtualize we did it with ESXi because we still have windows NT in some servers….microsoft rules!

]]> By: Mike La Spina http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-177 Mike La Spina Fri, 27 Feb 2009 17:06:51 +0000 http://www.gabesvirtualworld.com/?p=104#comment-177 Hi Gabe, It does become evident that Microsoft has failed to get the concept of "Sharing Resources" in order to maximize utilization of the hardware layer. I view Microsoft as an infant with attitude in the world of virtualization services. Regards, Mike Hi Gabe,

It does become evident that Microsoft has failed to get the concept of “Sharing Resources” in order to maximize utilization of the hardware layer. I view Microsoft as an infant with attitude in the world of virtualization services.

Regards,

Mike

]]> By: Gabe http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-2-guest-os-and-memory-overcommit/comment-page-1/#comment-176 Gabe Wed, 28 Jan 2009 22:06:08 +0000 http://www.gabesvirtualworld.com/?p=104#comment-176 @Bridget: To be honest, I'm not always very consequent in these kind of things. I did mean Gigabytes of memory, so GB it is then :-) And I'm honored to be quoted :-) Please remember there is a lot of confusion about what "overcommit" really is. Think it is essential to explain this to your audience. Regards Gabrie @Bridget: To be honest, I’m not always very consequent in these kind of things. I did mean Gigabytes of memory, so GB it is then :-)

And I’m honored to be quoted :-)

Please remember there is a lot of confusion about what “overcommit” really is. Think it is essential to explain this to your audience.

Regards
Gabrie

]]>