SimonF

There are bug reports like this one, https://access.redhat.com/solutions/5624631. Does the issue happens if you remove the igpu?

NVMEs go into low power mode by default, but disks will not show spun done. Function is being added in next release so you can see power draw but if changes very often. ps is the powerstate and as you can see when I started a VM it went from 3 to 0
 
ps    0 : mp:7.80W operational enlat:0 exlat:0 rrt:0 rrl:0
          rwt:0 rwl:0 idle_power:- active_power:-
ps    1 : mp:2.90W operational enlat:0 exlat:0 rrt:1 rrl:1
          rwt:1 rwl:1 idle_power:- active_power:-
ps    2 : mp:2.80W operational enlat:0 exlat:0 rrt:2 rrl:2
          rwt:2 rwl:2 idle_power:- active_power:-
ps    3 : mp:0.0250W non-operational enlat:2500 exlat:7500 rrt:3 rrl:3
          rwt:3 rwl:3 idle_power:- active_power:-
ps    4 : mp:0.0050W non-operational enlat:10500 exlat:65000 rrt:4 rrl:4
          rwt:4 rwl:4 idle_power:- active_power:-
root@computenode:~# nvme get-feature /dev/nvme0 -f2
get-feature:0x02 (Power Management), Current value:0x00000003
root@computenode:~# nvme get-feature /dev/nvme0 -f2
get-feature:0x02 (Power Management), Current value:0x00000003
root@computenode:~# nvme get-feature /dev/nvme0 -f2
get-feature:0x02 (Power Management), Current value:00000000
root@computenode:~# 
 
 

Do you have fastboot enabled in the bios, change to disabled.

Remove docker.folder.plg - 2023.03.18  (Deprecated)  (Up to date)

Try removing BT modules as  per this thread.
 
 

Does seem to indicate a PCIe Hardware issue.
 
Dec  4 15:45:09 UnRAID kernel: xhci_hcd 0000:0d:00.0: Abort failed to stop command ring: -110
Dec  4 15:45:09 UnRAID kernel: xhci_hcd 0000:0d:00.0: xHCI host controller not responding, assume dead
Dec  4 15:45:09 UnRAID kernel: xhci_hcd 0000:0d:00.0: HC died; cleaning up
Dec  4 15:45:09 UnRAID kernel: xhci_hcd 0000:0d:00.0: Timeout while waiting for setup device command
 
Glad you like the plugin

You need to use bus and device ID for same type. I have a plugin that will do that automatically for you based on the port it is connection or device+serial and map into the VM when it starts or is hot plugged. Also you need to set USB3 in the vm as USB2 will not have enough free USB ports.
 
look for USB Manager in CA. You will need to remove the mappings from the VM Template of the ones you want to map using my plugin.

It is already in the OS. It just needs to be started. Check here.
 

Rename /usr/local/sbin/qemu to qemu.old then start VM manager disable auto start and then rename the file back

likely to be because you have these in the XML
 
<memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> remove the memfd and shared lines. You may have tested virtiofs which requires these but does not remove when you dont use that option anymore.

The vnc is part of qemu/libvirt stack. You can use external clients I use virt viewer but should work with other vnc clients.
 

On flash drive on another machine change autostart to no in this file
 
root@GUITest:~# cat /boot/config/disk.cfg
# Generated settings:
startArray="no"
 
Rename /boot/config/vfio-pci.cfg to .old
 
put flash back in server boot.
 
log in
 
open terminal or use console.
mv /usr/local/sbin/qemu /usr/local/sbin/qemu.old
 
start array vm's should not autostart.
 
update VM. 
mv /usr/local/sbin/qemu.old /usr/local/sbin/qemu
 
Dont forget to set autostart in disk settings.
 

goto device manager and load the qxl driver from the libvirt cd

Yes that would fix the issue also. 

Have you tried advanced view on docker page, It will show orphan images and you can delete from there.
 

https://www.amazon.com/FebSmart-Self-Powered-Technology-No-Additional-FS-U4-Pro/dp/B072LS4JH7/ref=sr_1_2_sspa?crid=1G0S54HDT3TLT&keywords=usb%2Bpci%2Blinux&qid=1694979890&sprefix=usb%2Bpci%2Blinux%2Caps%2C313&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1 looks like linux supported.

<memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking>  
Remove these two lines
<source type='memfd'/> <access mode='shared'/> 
 
 
If you had tried virtiofs it would have added them in but does not remove if you remove the mappings in the gui. You will need to do via the XML editor.

https://github.com/ich777/intel-gpu-top/blob/master/intel-gpu-top.plg

Should be fairly quick have you got 1Gb memory allocated try increasing.

Stop vm,
Edit xml and change to XML view via the slider top right 

 
Make a copy of the XML before changing. Creating diagnostics will have a copy of the xml in it also.
 
You will now see the XML view scroll to be bottom. Be careful not to remove sections.
 
 

 
So would look like this. But you may not have the usb part as that is a passed through USB device
 

Maybe change to SATA for the bus type on CD. It may be you just missed the press any key when at this screen type reset + enter and hopefully you will see press any key to boot from CD?

Not found any way to enable logging. The following will show connections when active.
 
root@computenode:/mnt/user/appdata/NUT-unRAID/plugin# virsh qemu-monitor-command Slackware3 --pretty  query-vnc
{
  "return": {
    "enabled": true,
    "auth": "vnc",
    "family": "ipv4",
    "clients": [
      {
        "family": "ipv4",
        "service": "23698",
        "host": "192.168.1.41",
        "websocket": false
      },
      {
        "family": "ipv4",
        "service": "49494",
        "host": "127.0.0.1",
        "websocket": true
      }
    ],
    "service": "5901",
    "host": "0.0.0.0"
  },
  "id": "libvirt-459"
}
root@computenode:/mnt/user/appdata/NUT-unRAID/plugin# 
 
I have requested a feature request to QEMU team for a security log.

You need to edit this file. currently it has blacklist i915. I dont know what the value would be for your CPU. But it should be in the system log when the driver loads currently it is set not to load.
 
root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
options i915 force_probe=56a0
root@computenode:~# 

do ls /dev/disk/by-id/
 
and use the one that matches you device here 
 

I have copied your XML into my system and it allows me to update with no issues.