Hyper-V homework question
-
@scottalanmiller said in Hyper-V homework question:
They really should not have you installing the GUI, why are they avoiding standard good practices for hypervisor installation in a class? Shouldn't they be teaching how to do it in real life, not how to not do it? They are teaching it in the way that we are constantly telling people to avoid.
We also did core installs and connect them to Hyper-V Manager on workstations as well.
-
@Tim_G said in Hyper-V homework question:
I don't understand the issue. Is this ONLY happening on specific workstations? As in mfg/model?
I ask, because, I have installed Server 2012 R2 so many times and have also set up NIC Teaming via Server Mangler.... using an Integrated nic with a NIC on an add-in card. Created External vswitches and never had any issues what so ever.
The only issues I have run across were due to them being Broadcom NICs and having to disable Virtual Machine Queues option in the advanced properties of the NIC on the hosts. (before any teaming or anything is done). This needs to be done via Powershell on hosts running Core as well. I still have the commands handy if needed.
I've also never had any issues. These are all on the same whitebox workstations (built by a local shop. Asus boards/etc).
-
@scottalanmiller said in Hyper-V homework question:
@Dashrender said in Hyper-V homework question:
@scottalanmiller said in Hyper-V homework question:
@BBigford said in Hyper-V homework question:
@scottalanmiller said in Hyper-V homework question:
@BBigford said in Hyper-V homework question:
@scottalanmiller said in Hyper-V homework question:
Does the physical hosts' NIC get added to the switch?
As a NIC team, yes.
But does the physical VM ever get adding back to the switch?
I guess I don't understand the question as VMs are taken out of the equation... it's the physical host (the workstation I'm sitting at in this case) that loses all connectivity to the external network/Internet.
Hyper-V is a type 1 hypervisor. Bare metal. There can't be any other code on the bare metal. Your "physical host" is a VM.
Do recall correctly, the OPs first VM is Dom0?
Dom0 is what we call it in the Xen world. Microsoft, in their infinite desire to make Hyper-V hard, calls it the "Physical" VM. The dumbest name ever. But same thing, potato, poe-tah-toe.
Ok that is making some sense... kinda. As far as the physical host then becoming a virtual machine.
-
So maybe the question I should be asking if the physical host is then becoming a VM in sorts, is how do you control teaming in Hyper-V... Because to start, we have a physical workstation we sit at, that has Server 2012 R2 installed... we configure our two NICs on the host for teaming. Then install the Hyper-V role and create a virtual switch. Once we take the team that was created in Server Manager on the physical host and attach it to the virtual switch, then things go TU.
-
This post is deleted! -
@BBigford said in Hyper-V homework question:
So maybe the question I should be asking if the physical host is then becoming a VM in sorts, is how do you control teaming in Hyper-V... Because to start, we have a physical workstation we sit at, that has Server 2012 R2 installed... we configure our two NICs on the host for teaming. Then install the Hyper-V role and create a virtual switch. Once we take the team that was created in Server Manager on the physical host and attach it to the virtual switch, then things go TU.
What happens if you do not configure NIC Teaming until after the Hyper-V role is installed? Does the issue still happen?
-
@BBigford said in Hyper-V homework question:
So maybe the question I should be asking if the physical host is then becoming a VM in sorts, is how do you control teaming in Hyper-V... Because to start, we have a physical workstation we sit at, that has Server 2012 R2 installed... we configure our two NICs on the host for teaming. Then install the Hyper-V role and create a virtual switch. Once we take the team that was created in Server Manager on the physical host and attach it to the virtual switch, then things go TU.
Maybe take a look at the diagram here, it explains what @scottalanmiller said about the "physical VM": https://en.wikipedia.org/wiki/Hyper-V#Architecture
-
@thwr said in Hyper-V homework question:
@BBigford said in Hyper-V homework question:
So maybe the question I should be asking if the physical host is then becoming a VM in sorts, is how do you control teaming in Hyper-V... Because to start, we have a physical workstation we sit at, that has Server 2012 R2 installed... we configure our two NICs on the host for teaming. Then install the Hyper-V role and create a virtual switch. Once we take the team that was created in Server Manager on the physical host and attach it to the virtual switch, then things go TU.
Maybe take a look at the diagram here, it explains what @scottalanmiller said about the "physical VM": https://en.wikipedia.org/wiki/Hyper-V#Architecture
The very best way I've heard it explained was in a podcast I listened to recently:
Isolated User Mode in Windows 10 with Mark Minasi
http://www.runasradio.com/Shows/Show/480I think it starts around 1/4 the way in, but the whole episode is good.
-
@Dashrender said in Hyper-V homework question:
@Tim_G said in Hyper-V homework question:
I don't understand the issue. Is this ONLY happening on specific workstations? As in mfg/model?
I ask, because, I have installed Server 2012 R2 so many times and have also set up NIC Teaming via Server Mangler.... using an Integrated nic with a NIC on an add-in card. Created External vswitches and never had any issues what so ever.
The only issues I have run across were due to them being Broadcom NICs and having to disable Virtual Machine Queues option in the advanced properties of the NIC on the hosts. (before any teaming or anything is done). This needs to be done via Powershell on hosts running Core as well. I still have the commands handy if needed.
But did you have the Hyper-V role installed in those servers? and if yes, did you use Teaming inside Hyper-v or inside the Dom0 VM?
Yes, I really don't do any teaming or anything until after I install the Hyper-V role. I usually create the team on the physical Host OS (Dom0?) via server manager or powershell. After that, I go in to Hyper-V Manager and go in to Virtual Switch Manager and create a vswitch from the nicteam...
-
@BBigford said in Hyper-V homework question:
@Kelly said in Hyper-V homework question:
I posted this on that other site, but it appears that you do the teaming inside of Hyper-V, and not in the host OS: http://www.serverwatch.com/server-tutorials/configuring-nic-teaming-for-virtual-machines-with-hyper-v-3.0.html.
As soon as the team is added, connectivity is lost. Can't even get as far as adding the adapter before connectivity is lost.
So... once you create the virtual switch in Hyper-V Manager Virtual Switch Manager, using the NIC Team you created on the Host OS, all connectivity is lost?
At that point, what do the event logs say? Is there some kind of weird MAC conflict? When you look at the connection status of the virtual switch in Control Panel -> Network Connections, what does it look like? Are you getting a 169 address? Is it all 0's? What's actually going on and what does Event Viewer say?
