Applies To: Windows Server 2008 This is preliminary documentation and subject to change. Virtual Machine Start Operation Event Details Product: Windows Operating System ID: 15500 Source: Microsoft-Windows-Hyper-V-VMMS Version: 6.0 Symbolic Name: MSVM_VMMS_START_WP_ERROR Message: '%1' failed to start worker process:%3 (%4). Smart Kit River Crossing Game. (Virtual machine ID%2) Resolve Retry virtual machine start Check the environment in which the start virtual machine operation was being attempted, including: • access and permissions to the configuration file, memory file and all image files • prior error messages in the event log • available RAM on the system • configuration settings • disk space for the memory file and any expanding virtual hard disks Once the necessary issues have been rectified, try to start the virtual machine again. If the problem continues, restart the VMMS Service. To restart VMMS using the Service Manager: 1. In the Hyper-V Manager click the server on which you want to stop the service, then click Action, then click Stop Service. Click Action, and then click Start Service.

Apr 07, 2009 Event ID 3054. Event ID 3055. Event ID 15500 — Virtual Machine Start Operation. Updated: April 7, 2009. ID: 15500: Source: Microsoft. Event Id: 3054: Source: Microsoft-Windows-Hyper-V-Worker: Description%1' successfully allocated memory, but a subset of the physical pages was allocated on a remote. DB:4.22:Warning Event Id 3054 Source Hyper-V-Worker a1. Windows 2008 Standard with 2 virtual machines. Source: Microsoft-Windows-Hyper-V-Worker Event ID: 3430. Event Id: 3040: Source: Microsoft-Windows-Hyper-V-Worker: Description%1' failed to initialize. (Virtual machine%2) Event Information: According to Microsoft.

To restart the VMMS service using the command prompt: 1. On the computer that has the stopped service, open a command prompt as local administrator and type the following: net stop nvpswmi If the service is not running, you will see the error ' The Hyper-V Networking Management service is not started.' On the command prompt type the following command to start the nvpswmi service net start nvspwmi If the service start starts you will see the message ' The Hyper-V Networking Management service was start successfully.' To restart VMMS using PowerShell: 1. On the computer that has the stopped service, open a command prompt as local administrator and type the following: C: PS>restart-service vmms Verify The virtual machine is able to start successfully. Related Management Information.

Have a Windows XP SP3 VM on a 2008 R2 Hyper-V Server. Have migrated the machine from a 2008 Hyper-V Host with SCVMM 2008 R2. Now, every time I start the Windows XP VM, the Hyper-V R2 Host logs 4 Hyper-V-worker 3054 events: 'wswinxp1-d' 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 ID 0AED03FF-71FF-4B28-9CC7-FB6BB41E6D91) Have changed the CPU of the VM to the most basic one (Pentium 3, 1GHz) and the VM has only 512 MB RAM. Have found a Hotfix (but this seems not to be for R2. Have found information and Ran numa.ps1 /clear wswinxp1-d, have got some output, no error.