Mittwoch, 2. Mai 2012 15:25
I'm trying to get Hyper-V setup so i can run the windows 8 server certification programs. A collegue installed the Hyper-V VM but had the network connection connected to an invalid network connection.
I changed the Virtual Switch to Connection Type: External, selected the single connected network card & ticked "Allow management operating system to share this network adapter". When this change was saved it resulted in all connections to the host OS being lost. The only access to the machine was via the console.
I tried rebooting the server but it remained that no connections could be made into the host OS. The only way to get network connectivity back to the host was to setup the networking as internal/private. This of course prevents external access into the VM which is required.
The machine running Windows 8 beta is an IBM running 2x Intel Xeon x5670 CPUs
Has anyone else seen this problem?
Mittwoch, 2. Mai 2012 15:51Moderator
Your description sounds inverse of what I would expect. But maybe not.
Creating an External Virutal Network - creates a vSwitch and binds it to a physical NIC. Selecting the checkbox to allow the managment OS to share - in turn creates a vNIC on the vSwitch and connects the management OS to that.
Default OS behavior is that this should get the same IP address that the hardware NIC previously had.
Since you can get to the console, you should be able to verify the IP that the management OS has prior to and after checking this box.
You can also verify that the physical NIC associated with the External vSwitch is indeed connected to a physical network.
In regards to an Internal network - this is between the VMs and the Management OS only. Traffic cannot exit the physical Server.
A Private Network is similar except that the managment OS is excluded as well (VM to VM only).
It is because of all this that I am a bit confused by your description and why I would expect different behavior than you described.
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.
Mittwoch, 2. Mai 2012 20:40
I think we are on the same song sheet just describing it slightly different. My expectation was that by ticking the box would allow both the HostOS and the Guest to use the same network card. I had not realized it created a vNIC which took the HostsIP but this is obviously the part which is not quite working properly.
I'll take another look at the setup tomorow and see if I can see why the Host is not trying to use the vNIC
Donnerstag, 3. Mai 2012 02:32Moderator
Please have a read of the following blog.
How does basic networking work in Hyper-V?
- Als Antwort markiert Vincent HuModerator Dienstag, 8. Mai 2012 08:41