Really strange ... I can't pinpoint exactly when this problem started happening, but I have a Win10 VM set to autostart, but it won't auto start (ie after a reboot of unraid).  It manually starts with no problems at all.

 

I've tried disabling autostart, then re-enabling it. I've also tried upgrading from 6.1.3 to 6.1.6, but both OS versions have the same issue.

 

Is there a config file I can check to see if the autostart setting is in fact set?

 

The VM's xml file doesn't have an autostart option in there that I can see, so I'm guessing it's in a different config file.

 

Anyway, any help is greatly appreciated, thanks!

Really strange ... I can't pinpoint exactly when this problem started happening, but I have a Win10 VM set to autostart, but it won't auto start (ie after a reboot of unraid).  It manually starts with no problems at all.

 

I've tried disabling autostart, then re-enabling it. I've also tried upgrading from 6.1.3 to 6.1.6, but both OS versions have the same issue.

 

Is there a config file I can check to see if the autostart setting is in fact set?

 

The VM's xml file doesn't have an autostart option in there that I can see, so I'm guessing it's in a different config file.

 

Anyway, any help is greatly appreciated, thanks!

 

It's probably windows.  Look at the windows reliability history to see if it is crashing the first time it is started.

Ok, I checked the reliability history in Windows, but everything looks ok.

 

Any other ideas? What's the config file/setting that controls the autostart?

When a VM is set to autostart, a symlink to its original XML is created in a subfolder called "autostart".  /etc/libvirt/qemu is where the XML files are stored and /etc/libvirt/qemu/autostart is where the symlinks go.

I would check the libvirt log (a link to it can be found under Settings -> VM Manager and turning on help)

I would check the libvirt log (a link to it can be found under Settings -> VM Manager and turning on help)

 

Ahh that did the trick (I didn't know about the Help button ... pretty cool feature!) ... anyway, here's the log...

 

2015-12-07 10:51:13.075+0000: 8142: info : libvirt version: 1.2.18

2015-12-07 10:51:13.075+0000: 8142: error : virUSBDeviceFindByVendor:242 : internal error: Did not find USB device 45e:cb

2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 001.008 in list of active USB devices

2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices

2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices

2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices

2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices

2015-12-07 10:51:13.108+0000: 8142: error : qemuAutostartDomain:302 : Failed to autostart VM 'Win10VM': internal error: Did not find USB device 45e:cb

2015-12-07 10:52:06.469+0000: 8125: warning : qemuDomainObjTaint:2065 : Domain id=2 name='Win10VM' uuid=0ea65933-a1b4-fb12-0206-1e29ea25f5cf is tainted: high-privileges

2015-12-07 10:52:06.469+0000: 8125: warning : qemuDomainObjTaint:2065 : Domain id=2 name='Win10VM' uuid=0ea65933-a1b4-fb12-0206-1e29ea25f5cf is tainted: host-cpu

 

Sure enough, looks like a USB issue ... it's just a bit surprising that when I do a manual start of the VM, it starts ok (and all the USB devices work fine).

 

I'm not too concerned, I have my mouse/kbd/phone charger all passing through the usb hub that's built in to my monitor, and it's often a bit flaky. I'll eventually get around to bypassing the monitor's usb hub and going direct to the server's motherboard (or using an external USB hub).

 

Thanks!

I seem to have the same problem, My Pfsense VM dosent auto start?

 

Looking at the log I can see this:

2020-04-07 16:49:48.026+0000: 31248: warning : qemuDomainObjTaint:9301 : Domain id=1 name='pfSense 2' uuid=009d5016-771a-4082-09e4-25423bed1eb9 is tainted: high-privileges
2020-04-07 16:49:48.026+0000: 31248: warning : qemuDomainObjTaint:9301 : Domain id=1 name='pfSense 2' uuid=009d5016-771a-4082-09e4-25423bed1eb9 is tainted: host-cpu

 

But I haven't set any High privileges on the VM settings?

Hello, do not know if you have fixed your issue. I couldn't find an answer why my vm would not autostart after a windows update.  So I created a script that runs every hour. It is kicked off with user scripts.

 

Here is the script:

 

#!/bin/bash
if [ ! -f "/tmp/vm.txt" ]; then rm /tmp/vm.txt ; fi
virsh list --state-running > /tmp/vm.txt
if grep -q "running" /tmp/vm.txt; then exit
else
virsh start  "Windows Server 2016"
fi

 

I only have one VM but you can replace grep "running" with VM name instead if you have multiple vms

 

Hope this helps

Edited October 23, 20205 yr by ximian