SimonF

If you remove the mac address on the NIC it will remove the definition from the guest. You will still be able to access via VNC.

attach Diagnostics when the VM is started.

Do you have the connect plugin installed? and is it on the latest?

look for cups in CA.

Yes also check CSM is not enabled. These are from the manual for the MB. CSM Enable to launch the Compatibility Support Module. Please do not disable unless you’re running a WHCK test. Have you tried different settings for the option below? Legacy USB Support Enable or disable Legacy OS Support for USB 2.0 devices. If you encounter USB compatibility issues it is recommended to disable legacy USB support. Select UEFI Setup Only to support USB devices under the UEFI setup and Windows/Linux operating systems only.

Check for bios updates, do you have fast boot enabled? are you booting uefi?

New drivers released a few days ago. mm268/build 248

Any reason why you are not using host passthru for the CPU? First one is missing the feature lines below are the ones you have on the 2nd working one. <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>qemu64</model> <topology sockets='1' dies='1' cores='1' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='lahf_lm'/> <feature policy='disable' name='svm'/> </cpu>

Yes it maybe release as 7.

Have you change anything else in the xml, maybe post your xml

that is fine the file should be in the hooks/qemu.d dir now.

No that is the code for pre 6.10 that gets inserted into the qemu file. If you run the following it should create the hooks /usr/local/emhttp/plugins/usb_manager/scripts/install.sh Looks like it is not recreating at boot because lbvirt is not mounted until services start will look into it.

if you are running < 6.10 the lines are added to qemu in the hooks dir. it should have the code inserted near the top. #begin USB_MANAGER\nif ($argv[2] == 'prepare' || $argv[2] == 'stopped'){ shell_exec("/usr/local/emhttp/plugins/usb_manager/scripts/rc.usb_manager vm_action '{$argv[1]}' {$argv[2]} {$argv[3]} {$argv[4]} >/dev/null 2>&1 & disown") ; } #end USB_MANAGER Also check the permission on the file that it is execurtable. ls -l you have the x in the flags. can you also check usb.ini in /usr/local/emhttp/state/ Entries should look similar to this [001/111] ishub = "" connected = "" parents = "1-9,usb1,0000:00:14.0,pci0000:00" bus = 001 dev = 111 ID_VENDOR_FROM_DATABASE = "Dresden Elektronik" ID_VENDOR_ID = "1cf1" ID_MODEL = "ConBee_II" ID_MODEL_ID = 0030 USBPort = "1-9.3" class = "interface" ID_SERIAL = "dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE" isSerial = "1" isSerialPath = "usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE-if00" bNumInterfaces = 2 isSerialDevPath = "/dev/ttyACM1"

Which vers of the plug and unraid are you running Does this file exist root@computenode:~# cat /etc/libvirt/hooks/qemu.d/USB_Manager #!/usr/bin/env php <?php #begin USB_MANAGER if ($argv[2] == 'prepare' || $argv[2] == 'stopped'){ shell_exec("/usr/local/emhttp/plugins/usb_manager/scripts/rc.usb_manager vm_action '{$argv[1]}' {$argv[2]} {$argv[3]} {$argv[4]} >/dev/null 2>&1 & disown") ; } #end USB_MANAGER ?> root@computenode:~#

Next release i.e. 6.13

Just to confirm you do have spin down set to a time value in disk settings. How long do they stay spun down, if there is IO on the disks during the set period then they will not be automatically spun down.

Thanks for reporting will look in to it

Looking for unraid diags to look at hardware etc

Depends on what you have removed. if just /dev fi!es a reboot

Have you increase the partition within the disk also? Also check you have set power options not to suspend etc.

I cannot anything to say what is stopping the VM, do you have any backups running that may shutdown the VM or any processes running in the VM?

Yes usb3 and 4 are virtual vhci_hcd are the virtual hubs. /sys/bus/usb/devices/3-1

Yes that is correct.

That was changed to load drivers by default. I think was in early 6.10 series.

Are you able to post diagnostics, Also is there a reason why you have a snapshot for the vdisk with a backing file. Have you looked at this thread?