$Inherit = "ContainerInherit, ObjectInherit" The first attempt is to try and set the right access permissions in the registry key by running the following PowerShell commands: $ACL = Get-Acl -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization" On the working nodeĪs you can see, NT VIRTUAL MACHINE\Virtual Machines and NT SERVICE\TrustedInstaller permissions are missing from the list. When I checked the registry permissions on the working node and on the affected node, I noticed a lot of access permissions were missing. Most of these errors were related to invalid access and permissions issues accessing the registry. Finding the causeĪfter digging in the Hyper-V logs, I’ve found a lot of errors related to Hyper-V-Worker, Hyper-V-SynthNic, and Hyper-V-VMMS. The virtual machine won’t start whatsoever.
#Find network mac address on old windows installation Patch
Hyper-V will generate new Max and Min MAC addresses.ĥ) Expand the Maximum and Minimum MAC addresses range in Hyper-V.Ħ) Make sure that both nodes are running the same patch level.Īll the troubleshooting steps above did not lead anywhere. The basic troubleshooting process is as follows:ġ) Restart the Hyper-V Virtual Machine Management (VMMS) service.Ģ) Remove the VM network adapter, then add it again and try to start the virtual machine.Ĥ) Remove MaximumMacAddress and MinimumMacAddress registry keys, and then restart the VMMS service. So, what is wrong with that particular node? Troubleshooting Why? because the Dynamic MAC was moved along with VM from the healthy node. Moreover, if I migrate a VM from the healthy node to the affected node, the VM is live migrating and starting successfully. I was also able to Quick Migrate that VM and start it on the second node. On the second node, the VM is getting a Dynamic MAC and is starting without any issue. In other words, the Hyper-V server is not allocating any Dynamic MAC addresses for virtual machines. What I found is, that the affected node cannot start any VM with the Dynamic MAC address assigned.
I tried to set a static MAC Address for that VM and I was able to start it. However, I have only 18 VMs running on that node! Because by default, each Hyper-V server can allocate a maximum of 254 MAC addresses. The only time you would expect to receive No available MAC address for ‘Network Adapter’ is if you are running more than 254 virtual machines. This is not my case, I am creating a new VM. The only time you would expect to have a virtual machine with the MAC address set to zero is, if you have imported the virtual machine and specified that you are copying (and not moving) the virtual machine. When checking the virtual network adapter for that virtual machine, I noticed that the MacAddress is set to zero 00:00:00:00:00:00
I have two nodes Storage Spaces Direct (S2D) Hyper-Converged cluster, when creating a new VM on one of the nodes, I could not start that virtual machine. You can also configure this range yourself if you want to. If you use static MAC addresses you need to manually specify the MAC address to use, but Hyper-V will never change it.Įach Hyper-V server has a MAC address range that it uses for generating new dynamic MAC addresses. Since Hyper-V’s inception back in 2008, you can configure a virtual machine to use a dynamic or a static MAC address for any given network adapter.īy default, Hyper-V uses a dynamic MAC address – which means that Hyper-V will generate an initial MAC address for each network adapter, either for VM (vmNIC) or for the host (vNIC), and it will regenerate the MAC address if it believes it is necessary.
0 kommentar(er)
