PolicyLink
asked on
Is it OK for a virtual machine use the same NIC as the host?
I am setting up a new server 2008R2 server with Hyper -V and trying to figure out the NIC assignments.
The server has two built in NICS and a four port add in NIC. I would like to assign the nics as follows: The logic being that the onboard nics are best suited to the SAN. By assigning the fourth port to the host and the last VM, until the fourth vm comes online the host gets exclusive use on the nic and when I do need the nic for a vm I will make sure it is one that gets little use. I am assuming also that the host VM doesn't actually use the nic very often.
Built In NIC A: Connection A to SAN on seperate ICSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Built In NIC B: Connection B to SAN on Seperate ISCSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Add In NIC A: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC B: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC C: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC D: VM1 windows 2008 SP2 64BIT + Host Hyper-V 2008R2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
The server has two built in NICS and a four port add in NIC. I would like to assign the nics as follows: The logic being that the onboard nics are best suited to the SAN. By assigning the fourth port to the host and the last VM, until the fourth vm comes online the host gets exclusive use on the nic and when I do need the nic for a vm I will make sure it is one that gets little use. I am assuming also that the host VM doesn't actually use the nic very often.
Built In NIC A: Connection A to SAN on seperate ICSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Built In NIC B: Connection B to SAN on Seperate ISCSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Add In NIC A: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC B: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC C: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC D: VM1 windows 2008 SP2 64BIT + Host Hyper-V 2008R2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry, I didn't fishish editing after a cut and paste. The configuration should say:
Built In NIC A: Connection A to SAN on seperate ICSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Built In NIC B: Connection B to SAN on Seperate ISCSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Add In NIC A: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC B: VM2 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC C: VM3 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC D: VM4 windows 2008 SP2 64BIT + Host Hyper-V 2008R2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
The two nics for the san are required so I only have four left to use. Dedicating one to the host leaves me only three. It sounds like I should live with the three and share one between two VMs if I end up with four VMs.
Built In NIC A: Connection A to SAN on seperate ICSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Built In NIC B: Connection B to SAN on Seperate ISCSI LAN (Broadcom NIC not reccommended for Hyper-V VM)
Add In NIC A: VM1 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC B: VM2 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC C: VM3 windows 2008 SP2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
Add In NIC D: VM4 windows 2008 SP2 64BIT + Host Hyper-V 2008R2 64BIT (Four port Intel NIC recommended for Hyper-V VM)
The two nics for the san are required so I only have four left to use. Dedicating one to the host leaves me only three. It sounds like I should live with the three and share one between two VMs if I end up with four VMs.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to have one for Hyper-V host management. You can share the same virtual network without multiple VMs.
As far as your question is concerned, it is advised not have share the NIC between host (for management) and VMs. I haven't run into problems by doing so.
What surprises me is that you have six NICs and still can't spare one NIC for management.
Regards,
Shahid