I will give an example of creating virtual switches, configuring network and NAT in Hyper-V.Continue reading “Hyper-V Network Configuration”
I will describe the procedure for adding the Hyper-V role to Windows Server:Continue reading “Install Hyper-V”
Suppose the server has one network card and in network connections it can be seen as “Ethernet”, but after adding the Hyper-V role, a virtual switch vEthernet (…) is created.
Virtual machines can be seen from other computers but can not be seen from the local.
Therefore, for virtual machines to be accessible from the local machine, you must disable the DHCP client to Ethernet, or assign an IP address manually, then the virtual switch vEthernet (…) will receive IP instead of Ethernet because they have the same The MAC address.
I noticed once on one HP server, after installing Hyper-V, that virtual workstations are not being launched, giving the following error:
An error occurred while attempting to start the selected virtual machine(s).
Virtual machine could not be started because the hypervisor is not running.
As it turned out, the problem was in the Intel (R) Virualization Tech not activated in BIOS, after changing from “Disabled” to “Enabled” and start the system, the virtual workstations were successfully launched.