I've installed Windows Server 2008 R2 and enabled the Hyper-V role, on a computer with a single NIC and 1GB of physical RAM. (Yes I know that's not recommended, but I haven't seen anything report that Hyper-V fails to work on such a system.) Since I need to manage this system remotely, I did NOT select it for use with a virtual network.
I've enabled NX/DEP and VT (virtualization assist) in BIOS.
I've configured VM's successfully in a half-dozen or so combinations of initial settings (type of disk, type of networking support, amount of RAM, amount of disk space), but haven't ever been able to get any VM's started - i.e. not one of them has an installed OS. I keep running into the error:
Failed to create partition: Insufficient system resources exist to complete the requested service. (0x800705AA)
I've even tried generating a new partition on my single disk, and pointing new VM's at the new partition, thinking there was either (a) a permissions error or (b) a problem in looping back all VM storage onto the same partition where Windows Server 2008 is installed (yes I've seen the recommendations that urge us to use a separate drive - but presumably for performance' sake, and not because Hyper-V will fail entirely).
I've found no errors in the Hyper-V-VMMS event log, but plenty of errors in the Hyper-V-Worker event log, two of each of the following errors for each occasion when I've tried and failed to Start the VM:
- ID 3110: "Failed to create partition: Insufficient system resources exist to complete the requested service. (0x800705AA)"
- ID 3040: "'New Virtual Machine' could not initialize. (Virtual machine ID C639CD93-DDA7-44B8-B3BB-53D26E898B41)"
I uninstalled and reinstalled Hyper-V role:
- selected the only NIC on my device for virtual networking (so this server won't be remotely manageable)
- install & reboot completed
- looked into the Hyper-V events summary - found a few errors and warnings around the time I uninstalled and/or installed the Hyper-V role:
- "The Integration Services Setup Disk image could not be updated: The system cannot find the path specified. (0x80070003)"
- "The Virtual Machine Management Service could not register update notifications for the Integration Services Setup Disk image: Illegal operation attempted on a registry key that has been marked for deletion. (0x800703FA)"
- I reconfigured the Hyper-V manager to point the Virtual Hard Disks *and* Virtual Machines default directory to the new data partition
I've done a ton of tracing analysis with ProcMon to see what is going on under the covers (i.e. what raw error messages are being generated, that the Hyper-V console is interpreting on my behalf). The only potentially related errors I've seen are two INVALID_DEVICE_REQUEST errors, generated when the VMWP.EXE process performs an "" operation on the following two file paths:
- J:\Shared VMs\Virtual Machines\C639CD93-DDA7-44B8-B3BB-53D26E898B41\C639CD93-DDA7-44B8-B3BB-53D26E898B41.vsv
- J:\Shared VMs\Virtual Machines\C639CD93-DDA7-44B8-B3BB-53D26E898B41\C639CD93-DDA7-44B8-B3BB-53D26E898B41.bin
Q: Does anyone have any clue what is going wrong here?
ParanoidMike (Intel)