> >Am I understanding all of this correctly?
>
> All you need to do is unbind TCP on the host with the NICs that are
> dedicated to the VM's. =A0That way the host wont need an IP address for
> those NICs and wont use them for any of it's own communications.
>
> --
> Bob Comer

>Maybe I'm missing something here but I can only find passing comments
>on this with no good descriptions.
>
>I have a 2008 Std install with Hyper-V role. The server has 4
>physical NIC ports.
>I have one NIC devoted to the server
>The first virtual machine (2008) is using the second NIC
>The second virtual machine (2003) is using the other 2 NIC ports (the
>app requires 2)
>
>In Virtual Network Manager I have created 3 External virtual networks
>and then added the adapters to the VM settings (1 for each port).
>
>Everything is communicating fine but it looks like I am required to
>supply an IP address to the physical NIC on the host system as well as
>the virtual NIC in the VM. We can afford the IPs but it adds to
>confusion and makes the host multihomed - this has several issues in
>the MS world. It's also a little unclear how the apps will respond to
>this method.
>
>It looks like I could add the NIC in the VM as a legacy adapter to
>solve this but that is documented as slower performance as well as
>locking you to 100MB.
>
>Am I understanding all of this correctly?

>It looks like I could add the NIC in the VM as a legacy adapter to
>solve this but that is documented as slower performance as well as
>locking you to 100MB.
>Maybe I'm missing something here but I can only find passing comments
>on this with no good descriptions.
>
>I have a 2008 Std install with Hyper-V role. The server has 4
>physical NIC ports.
>I have one NIC devoted to the server
>The first virtual machine (2008) is using the second NIC
>The second virtual machine (2003) is using the other 2 NIC ports (the
>app requires 2)
>
>In Virtual Network Manager I have created 3 External virtual networks
>and then added the adapters to the VM settings (1 for each port).
>
>Everything is communicating fine but it looks like I am required to
>supply an IP address to the physical NIC on the host system as well as
>the virtual NIC in the VM. We can afford the IPs but it adds to
>confusion and makes the host multihomed - this has several issues in
>the MS world. It's also a little unclear how the apps will respond to
>this method.
>
>It looks like I could add the NIC in the VM as a legacy adapter to
>solve this but that is documented as slower performance as well as
>locking you to 100MB.
>
>Am I understanding all of this correctly?

>On Feb 12, 9:29 am, Robert Comer <(email address - cut out)>
>wrote:
>> >Am I understanding all of this correctly?
>>
>> All you need to do is unbind TCP on the host with the NICs that are
>> dedicated to the VM's.  That way the host wont need an IP address for
>> those NICs and wont use them for any of it's own communications.
>>
>> --
>> Bob Comer
>
>If you unbind IP the VM loses connection the the network.

> Also,
>
>>It looks like I could add the NIC in the VM as a legacy adapter to
>>solve this but that is documented as slower performance as well as
>>locking you to 100MB.
>
> That really wouldn't make any difference in this case. (And the
> legacy NIC isn't locked to 100Mb, even though that's what it says, it
> goes at the real NIC's speed.) The Legacy NIC is quite a bit slower
> than the other type though, lots more overhead.
>
> --
> Bob Comer
>
>
> On Thu, 12 Feb 2009 07:09:59 -0800 (PST), (email address - cut out) wrote:
>
>>Maybe I'm missing something here but I can only find passing comments
>>on this with no good descriptions.
>>
>>I have a 2008 Std install with Hyper-V role. The server has 4
>>physical NIC ports.
>>I have one NIC devoted to the server
>>The first virtual machine (2008) is using the second NIC
>>The second virtual machine (2003) is using the other 2 NIC ports (the
>>app requires 2)
>>
>>In Virtual Network Manager I have created 3 External virtual networks
>>and then added the adapters to the VM settings (1 for each port).
>>
>>Everything is communicating fine but it looks like I am required to
>>supply an IP address to the physical NIC on the host system as well as
>>the virtual NIC in the VM. We can afford the IPs but it adds to
>>confusion and makes the host multihomed - this has several issues in
>>the MS world. It's also a little unclear how the apps will respond to
>>this method.
>>
>>It looks like I could add the NIC in the VM as a legacy adapter to
>>solve this but that is documented as slower performance as well as
>>locking you to 100MB.
>>
>>Am I understanding all of this correctly?