Comments on: Hyper-V, not in my datacenter (part 1 – Hardware) http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/ Your P.I. on virtualization Tue, 07 Feb 2012 11:19:00 +0000 hourly 1 By: Gabrie van Zanten http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-721 Gabrie van Zanten Sat, 02 Jan 2010 16:52:01 +0000 http://www.gabesvirtualworld.com/?p=103#comment-721 Hi<br>Thanks for posting your comment. Let me first say that this Hyper-V series is writen more than a year ago and is talking about Hyper-V version 1. <br><br>When talking about a limited list of NICs for Hyper-V, I'm talking about usage in datacenter. In a datacenter I want VLAN support and Teaming in some form. This teaming doesn't have to be etherchannel, but can be any form of teaming, as long as failure of a nic is picked up immediately. <br><br>Now, take your list of NICs that you think Hyper-V supports (and does) and strike all the NICs of which the vendor has not yet written a driver that supports VLANs AND supports teaming. When talking about this with Microsoft at the time of writing, there was a list of 12 (twelve) nics that could offer this support. <br><br>That is how I came to my conclusion that although the list of 'supported' NICs seems to be much longer for Hyper-V, it turns out the be much smaller when looking at real life usage in the datacenter.<br><br>Regards<br>Gabrie Hi
Thanks for posting your comment. Let me first say that this Hyper-V series is writen more than a year ago and is talking about Hyper-V version 1.

When talking about a limited list of NICs for Hyper-V, I'm talking about usage in datacenter. In a datacenter I want VLAN support and Teaming in some form. This teaming doesn't have to be etherchannel, but can be any form of teaming, as long as failure of a nic is picked up immediately.

Now, take your list of NICs that you think Hyper-V supports (and does) and strike all the NICs of which the vendor has not yet written a driver that supports VLANs AND supports teaming. When talking about this with Microsoft at the time of writing, there was a list of 12 (twelve) nics that could offer this support.

That is how I came to my conclusion that although the list of 'supported' NICs seems to be much longer for Hyper-V, it turns out the be much smaller when looking at real life usage in the datacenter.

Regards
Gabrie

]]> By: Gabrie van Zanten http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-484 Gabrie van Zanten Sat, 02 Jan 2010 09:52:01 +0000 http://www.gabesvirtualworld.com/?p=103#comment-484 Hi<br>Thanks for posting your comment. Let me first say that this Hyper-V series is writen more than a year ago and is talking about Hyper-V version 1. <br><br>When talking about a limited list of NICs for Hyper-V, I'm talking about usage in datacenter. In a datacenter I want VLAN support and Teaming in some form. This teaming doesn't have to be etherchannel, but can be any form of teaming, as long as failure of a nic is picked up immediately. <br><br>Now, take your list of NICs that you think Hyper-V supports (and does) and strike all the NICs of which the vendor has not yet written a driver that supports VLANs AND supports teaming. When talking about this with Microsoft at the time of writing, there was a list of 12 (twelve) nics that could offer this support. <br><br>That is how I came to my conclusion that although the list of 'supported' NICs seems to be much longer for Hyper-V, it turns out the be much smaller when looking at real life usage in the datacenter.<br><br>Regards<br>Gabrie Hi
Thanks for posting your comment. Let me first say that this Hyper-V series is writen more than a year ago and is talking about Hyper-V version 1.

When talking about a limited list of NICs for Hyper-V, I'm talking about usage in datacenter. In a datacenter I want VLAN support and Teaming in some form. This teaming doesn't have to be etherchannel, but can be any form of teaming, as long as failure of a nic is picked up immediately.

Now, take your list of NICs that you think Hyper-V supports (and does) and strike all the NICs of which the vendor has not yet written a driver that supports VLANs AND supports teaming. When talking about this with Microsoft at the time of writing, there was a list of 12 (twelve) nics that could offer this support.

That is how I came to my conclusion that although the list of 'supported' NICs seems to be much longer for Hyper-V, it turns out the be much smaller when looking at real life usage in the datacenter.

Regards
Gabrie

]]> By: John Wagner http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-720 John Wagner Fri, 01 Jan 2010 04:15:17 +0000 http://www.gabesvirtualworld.com/?p=103#comment-720 You mentioned a limited number of nics supported with Hyper-V? I'd like to see where you got that from? Actual more nics are supported on hyper-v than on vmware. NOW before you get upset over this continue reading, this is because Hyper-V does NOT SUPPORT NIC TEAMING! Hyper-V requires the hardware vendor of the nic to provide the software to do the teaming or failover or loadbalancing.. Vmware doesn't require this but does it through vmware.. Hence the reason they have a smaller list of compatible nics.. Not the other way around as you state it.. I think this is a HUGE HUGE HUGE shortcoming of hyper-v that Vmware should really hammer on but they don't.. I've called microsoft to task on this on their blogs on numerous occasions. I've spoken to members of microsofts hyper-v team and told them they need to fix this but they don't care... <br>Another point, microsoft does have a hardware compatibility list.. (HAL) and you can check it over to see what is compatible and what is not. But this is really not a point to choose microsoft or vmware over the other. Both run on most hardware.. (If they didn't they wouldn't be very good now would they?) <br>Thats my two cents worth.. otherwise your article is very interesting..<br><br>thanks for taking time to read ALL of my comments.. ;-) You mentioned a limited number of nics supported with Hyper-V? I'd like to see where you got that from? Actual more nics are supported on hyper-v than on vmware. NOW before you get upset over this continue reading, this is because Hyper-V does NOT SUPPORT NIC TEAMING! Hyper-V requires the hardware vendor of the nic to provide the software to do the teaming or failover or loadbalancing.. Vmware doesn't require this but does it through vmware.. Hence the reason they have a smaller list of compatible nics.. Not the other way around as you state it.. I think this is a HUGE HUGE HUGE shortcoming of hyper-v that Vmware should really hammer on but they don't.. I've called microsoft to task on this on their blogs on numerous occasions. I've spoken to members of microsofts hyper-v team and told them they need to fix this but they don't care…
Another point, microsoft does have a hardware compatibility list.. (HAL) and you can check it over to see what is compatible and what is not. But this is really not a point to choose microsoft or vmware over the other. Both run on most hardware.. (If they didn't they wouldn't be very good now would they?)
Thats my two cents worth.. otherwise your article is very interesting..

thanks for taking time to read ALL of my comments.. ;-)

]]> By: John Wagner http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-486 John Wagner Thu, 31 Dec 2009 21:15:17 +0000 http://www.gabesvirtualworld.com/?p=103#comment-486 You mentioned a limited number of nics supported with Hyper-V? I'd like to see where you got that from? Actual more nics are supported on hyper-v than on vmware. NOW before you get upset over this continue reading, this is because Hyper-V does NOT SUPPORT NIC TEAMING! Hyper-V requires the hardware vendor of the nic to provide the software to do the teaming or failover or loadbalancing.. Vmware doesn't require this but does it through vmware.. Hence the reason they have a smaller list of compatible nics.. Not the other way around as you state it.. I think this is a HUGE HUGE HUGE shortcoming of hyper-v that Vmware should really hammer on but they don't.. I've called microsoft to task on this on their blogs on numerous occasions. I've spoken to members of microsofts hyper-v team and told them they need to fix this but they don't care... <br>Another point, microsoft does have a hardware compatibility list.. (HAL) and you can check it over to see what is compatible and what is not. But this is really not a point to choose microsoft or vmware over the other. Both run on most hardware.. (If they didn't they wouldn't be very good now would they?) <br>Thats my two cents worth.. otherwise your article is very interesting..<br><br>thanks for taking time to read ALL of my comments.. ;-) You mentioned a limited number of nics supported with Hyper-V? I'd like to see where you got that from? Actual more nics are supported on hyper-v than on vmware. NOW before you get upset over this continue reading, this is because Hyper-V does NOT SUPPORT NIC TEAMING! Hyper-V requires the hardware vendor of the nic to provide the software to do the teaming or failover or loadbalancing.. Vmware doesn't require this but does it through vmware.. Hence the reason they have a smaller list of compatible nics.. Not the other way around as you state it.. I think this is a HUGE HUGE HUGE shortcoming of hyper-v that Vmware should really hammer on but they don't.. I've called microsoft to task on this on their blogs on numerous occasions. I've spoken to members of microsofts hyper-v team and told them they need to fix this but they don't care…
Another point, microsoft does have a hardware compatibility list.. (HAL) and you can check it over to see what is compatible and what is not. But this is really not a point to choose microsoft or vmware over the other. Both run on most hardware.. (If they didn't they wouldn't be very good now would they?)
Thats my two cents worth.. otherwise your article is very interesting..

thanks for taking time to read ALL of my comments.. ;-)

]]> By: Hyper-V R2 oder doch VMware? - Seite 2 - MCSEboard.de MCSE Forum http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-485 Hyper-V R2 oder doch VMware? - Seite 2 - MCSEboard.de MCSE Forum Mon, 30 Nov 2009 12:17:11 +0000 http://www.gabesvirtualworld.com/?p=103#comment-485 [...] nog ziemlich einfag, siehe meine artikel ueber Hyper-V: "Hyper-V, not in my datacenter" Gabes Virtual World Blog Archive Hyper-V, not in my datacenter (part 1 – Hardware) Mit Hyper-V R2 under LiveMigration wird es schon ein stuck schwieriger obwohl einige punkte aus [...] [...] nog ziemlich einfag, siehe meine artikel ueber Hyper-V: "Hyper-V, not in my datacenter" Gabes Virtual World Blog Archive Hyper-V, not in my datacenter (part 1 – Hardware) Mit Hyper-V R2 under LiveMigration wird es schon ein stuck schwieriger obwohl einige punkte aus [...]

]]> By: gromas http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-719 gromas Thu, 22 Oct 2009 20:32:00 +0000 http://www.gabesvirtualworld.com/?p=103#comment-719 Hyper-V now at my datacentre. It is very stable and very simple to maintance for me. And it is free for me. Good luck. Hyper-V now at my datacentre. It is very stable and very simple to maintance for me. And it is free for me. Good luck.

]]> By: gromas http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-159 gromas Thu, 22 Oct 2009 13:32:00 +0000 http://www.gabesvirtualworld.com/?p=103#comment-159 Hyper-V now at my datacentre. It is very stable and very simple to maintance for me. And it is free for me. Good luck. Hyper-V now at my datacentre. It is very stable and very simple to maintance for me. And it is free for me. Good luck.

]]> By: Free_Dating_Service http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-157 Free_Dating_Service Mon, 03 Aug 2009 19:39:40 +0000 http://www.gabesvirtualworld.com/?p=103#comment-157 Awesome post it was the most enjoyable post i have read today! Awesome post it was the most enjoyable post i have read today!

]]> By: Hyper-V, not in my datacenter! « DeinosCloud’s Blog http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-158 Hyper-V, not in my datacenter! « DeinosCloud’s Blog Wed, 29 Apr 2009 13:35:43 +0000 http://www.gabesvirtualworld.com/?p=103#comment-158 [...] Hyper-V, not in my datacenter (part 1: Hardware) [...] [...] Hyper-V, not in my datacenter (part 1: Hardware) [...]

]]> By: vuemuer.pmiservice.biz » Blog Archive » Ancora ESX contro Hyper-V http://www.gabesvirtualworld.com/hyper-v-not-in-my-datacenter-part-1-hardware/#comment-156 vuemuer.pmiservice.biz » Blog Archive » Ancora ESX contro Hyper-V Tue, 27 Jan 2009 14:12:52 +0000 http://www.gabesvirtualworld.com/?p=103#comment-156 [...] Hyper-V, not in my datacenter (part 1 - Hardware) [...] [...] Hyper-V, not in my datacenter (part 1 – Hardware) [...]

]]>