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.
-
@Kelly said in Hyper-V homework question:
@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.
From the article, you create two separate vSwitches, one for each adapter, then set up teaming inside of Hyper-V for the guest.
So you're suggesting do not setup teaming inside of Server Manager? That doesn't really make sense to me because you have to create the team in Server Manager, then add the virtual switch, choosing the team as the adapter...
-
TL;DR
a) Type: External Switch
b) Host sharing allowed? E.g. is the host getting its "own virtual NIC"?
c) Type of teaming: Only "Switch independent mode" does work without the switch being aware of the team.Maybe look at Aidan Finn's blog for some more info, he got quite a few good posts about this topic there.
-
@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.
If you have Hyper-V there is a VM. There is no way for Hyper-V to work without one. Any interaction with Hyper-V is through a VM. Only a VM can get an IP address for example. Whatever GUI or API you are using is from the VM.
-
@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.
-
@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?
@BBigford what @coliver is saying makes sense, you don't want teaming inside the Dom0, you want teaming inside Hyper-V which has to be done (I'm assuming) as he suggests inside Hyper-v Manager, not inside Dom0. It's confusing because it seems like that first install is what is controlling the box, but it really isn't any more once you install Hyper-V role.
-
@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.
-
@Dashrender said in Hyper-V homework question:
@BBigford what @coliver is saying makes sense, you don't want teaming inside the Dom0, you want teaming inside Hyper-V which has to be done (I'm assuming) as he suggests inside Hyper-v Manager, not inside Dom0. It's confusing because it seems like that first install is what is controlling the box, but it really isn't any more once you install Hyper-V role.
Hyper-V itself can't be networked. Only the Dom0 / Physical VM can be. Same with Xen. The hypervisors in both cases are sans networking. It's exclusively VMs that get to see the network at all.
-
@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?
@BBigford what @coliver is saying makes sense, you don't want teaming inside the Dom0, you want teaming inside Hyper-V which has to be done (I'm assuming) as he suggests inside Hyper-v Manager, not inside Dom0. It's confusing because it seems like that first install is what is controlling the box, but it really isn't any more once you install Hyper-V role.
Thank you @Dashrender for putting it so much better than I had been able to.
-
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.
-
@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.
They're doing it exactly like we'd expect someone to teach it that doesn't have any real world experience, just like 90% of every college course.
-
@travisdh1 said in 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.
They're doing it exactly like we'd expect someone to teach it that doesn't have any real world experience, just like 90% of every college course.
Even without experience you'd hope that the professor would have looked into it or read the book or something.
-
@scottalanmiller said in Hyper-V homework question:
@travisdh1 said in 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.
They're doing it exactly like we'd expect someone to teach it that doesn't have any real world experience, just like 90% of every college course.
Even without experience you'd hope that the professor would have looked into it or read the book or something.
Well, sure, reading the lesson plans the night before. The attitude I hear way to often is "If you don't know something, the best way to learn it is to teach it."
-
@scottalanmiller said in Hyper-V homework question:
@travisdh1 said in 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.
They're doing it exactly like we'd expect someone to teach it that doesn't have any real world experience, just like 90% of every college course.
Even without experience you'd hope that the professor would have looked into it or read the book or something.
Seriously? Have you taken any of these courses before?
During my brain dump "training" class (see what I did there?) the instructor said he didn't use folder redirection or personal drive mappings, as if they were a crazy thing to use.
-
@travisdh1 said in Hyper-V homework question:
@scottalanmiller said in Hyper-V homework question:
@travisdh1 said in 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.
They're doing it exactly like we'd expect someone to teach it that doesn't have any real world experience, just like 90% of every college course.
Even without experience you'd hope that the professor would have looked into it or read the book or something.
Well, sure, reading the lesson plans the night before. The attitude I hear way to often is "If you don't know something, the best way to learn it is to teach it."
Eh? I've never heard that!
-
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.
-
@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?
-
@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.
