Event Id: 3050: Source: Microsoft-Windows-Hyper-V-Worker: Description%1' failed to initialize memory:%3 (%4). (Virtual machine%2) Event Information: According to Microsoft: Cause: This event is logged when failed to initialize memory. Resolution: Retry virtual machine start.
Event ID 3054 — Virtual Machine Start Operation Updated: April 7, 2009 Applies To: Windows Server 2008 This is preliminary documentation and subject to change. Virtual Machine Start Operation Event Details Product: Windows Operating System ID: 3054 Source: Microsoft-Windows-Hyper-V-Worker Version: 6.0 Symbolic Name: MSVMLMMPAGESALLOCATEDINREMOTENUMAWARNING Message: ‘%1’ successfully allocated memory, but a subset of the physical pages was allocated on a remote non-uniform memory architecture (NUMA) node. This configuration is not recommended because it will reduce performance. (Virtual machine%2) Resolve Resolve remote NUMA problem If the Non-Uniform Memory Architecture (NUMA) ratio on your physical system is close to 1, you should not see a drop in the performance of your VM you should not have to worry. On the other hand, if you have a bad ratio and the performance is of the VM is poor, you need to:. Ensure that the memory associated with the VM is not larger than the memory associated with the NUMA node.
Set the preferred/required NUMA settings for each VM. These settings are exposed via the following properties in the MsvmVirtualSystemSettingsData object in the WMI model: NumaNodeList and NumaNodesAreRequired. Verify The virtual machine is able to start successfully. Related Management Information Related:.