I'm trying to create a simple Hyper-V test machine, and am having more problems than expected with the basic networking.
All other hypervisors I've used (vmware server, vmware player, virtualbox) allow me to use the default single NIC in my machine, and then create guests with "bridged" mode so they appear like a normal machine on the network.
With the Hyper-V server, when I create a Virtual Switch and set it to "external", I lose all network access from the host.
- I create a new virtual switch called "vSwitch External"
- I select
- After I close that dialog, my physical NIC has all items disabled apart from "Hyper-V Extensible Virtual Switch"
- A new NIC appears called "vEthernet (vSwitch external)" with all the usual items enabled
- There is no network access from the host to the outside
Is it really that complex to get a simple, single-NIC Hyper-V server going, in such a way that I can still use the host? Or is there some problem stopping my networking working correctly? As I see little mention of this problem when searching, I'm guessing the latter.
The host is Windows 8.
Removing and re-adding the vSwitch with reboots between each attempt seems to have worked, to the degree that my host machine can access the rest of the network now. Neither NIC has the Hyper-V extensible switch service enabled on it now.
A problem remains, however, in that the guests cannot access any network. I've only tried Ubuntu Server guests so far, and they detect the interfaces okay, but cannot get any access to the network, either with DHCP or static interfaces.
(Incidentally, to the four people that close-voted this question, wouldn't it be polite to comment why? This is supposed to be an educational forum, after all. The question does seem to relate to servers and networking.)