SimonF

If you are not using PCI passthru you can either leave blank or remove. Changes where made to stop autostart if vfio binding fails as could indicate PCI numbers have chaged due to hardware removal/additions etc. If the VM autostarts and now as the wrong device is allocated to the VM due to PCI number changes it could lookup or crash the host.
 
Before   
07:00.0 VGA Card(Passthru to VM)
08:00.0 Disk Controller(Unraid)
 
After
07:00.0 DIsk Controller(Unraid)
 
If the VM autostarts the diskcontroller would be allocated to the VM and all the Unraid disks would not been seen on the host as a simple example.
 
 

Are you still have issues, You logs are full of these errors. 
Tower winbindd[6662]: set_global_winbindd_state_offline: Offline requested Feb 22 09:34:10 Tower winbindd[6662]: [2024/02/22 09:34:10.370664, 0] ../../source3/winbindd/winbindd_cache.c:3465(set_global_winbindd_state_offline)
 
Can you post current diagnostics if having the issue still.

1024Gb is 1Tb? But it will start as a sparse file so the vdisk on the physical disk will be smaller until data is put into it.

single append line.
 

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.

Yes domains is the vm share, appdata is the container path. configs are normally stored in system for both.

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>

You need to be careful with this on 6.12 as overlay filesystems are in use which are still using the previous bz files.
 
Doing a 2nd update will cause an issue as it will delete the bz files in previous and move the current. Likely to get a system issue before reboot.

Yes that is correct.

The state of the connections should be as below so looks like it is not connected as serial. Are you able to unplug and reconnect the device?
 

Will auto connect
 
 

Does you vm auto start, maybe hardware has chnaged and pci device is not correct in vm.
 
You can rename the qemu command in /usr/local/sbin to stop it autostarting

yes

Yes plugins would be on flash.
 
search ca for qnap there is a plugin for fan controller

You dont need to login on the console. You can login just from the windows pc

Remove docker.folder.plg - 2023.03.18  (Deprecated)  (Up to date) as it is not compatible with 6.12.x
 
and install
 

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