tb037

Okay - nevermind. The third reboot fixed it.

Anyone else seeing issues starting VMs? Getting strange resource errors trying to boot VMs, and each VM displays a different error. VM1: Hook script execution failed: cannot fork child process: Resource temporarily unavailable VM2: internal error: qemu unexpectedly closed the monitor: (process:10743): Spice-ERROR **: 11:33:41.130: red-worker.c:1394:red_worker_run: create thread failed 11 VM3: internal error: qemu unexpectedly closed the monitor: 2019-02-26T17:48:25.222596Z qemu-system-x86_64: Initialization of device kvm-pit failed: Create kernel PIC irqchip failed: Unknown error -12 Not sure if this is due to the 6.6.7 update, but that is when I noticed it. Tried stopping/starting array and bouncing the server with no avail. Not sure how else to troubleshoot, each was working fine though at a past point in time. Thanks in advanced! Thomas

Worked like a dream, thanks bud! Interesting part for me was I previously had a mapped USB device within the VM Manager. I removed the device while the VM was off, and the VM wouldn't start up. I tried to remove the mapping but within the UI there were no USB device entries. I found the entry in XML view, added <source startupPolicy='optional'> and boom. Perfect boot. Thanks again!! Thomas