Hi all,

Looking for some help with my VMs after updating to Unraid 7.2.2.

System info

• Unraid version: 7.2.2

• CPU: Intel i7-12700K

• VMs: Windows 11 and a couple of test Linux VMs

• VM storage: /mnt/user/domains

• ISOs: /mnt/user/isos

What I am seeing

After the update from 7.1 to 7.2.2 my VMs no longer behave correctly. I had not started them since the upgrade until now.

• In the GUI I can click Start on a VM and it appears to start.

• The VM shows as running, but when I click the VNC icon I cannot get a console.

• I tried with my existing Windows 11 VM and also with a brand new test VM.

• I also got the “Libvirt service failed to start” banner at one point, so I deleted and recreated libvirt.img from Settings → VM Manager. After that the libvirt service starts, but the VM issues remain.

Paths and files

My ISO share looks like this:

/mnt/user/isos contains:

• virtio-win-0.1.240.iso

• virtio-win-0.1.248-1.iso

• virtio-win-0.1.262-2.iso

• virtio-win-0.1.266-1.iso

• virtio-win-0.1.285-1.iso

• Win10_22H2_English_x64v1.iso

• Win11_24H2_English_x64.iso

• Windows.iso (directory)

So the VirtIO ISO files absolutely exist at the paths shown.

Current Windows 11 VM config (summary)

• Name: Windows 11

• Machine: i440fx-9.2 (I also tried Q35)

• BIOS: OVMF TPM

• CPU Mode: Host Passthrough

• vCPUs: 4, 4 GB RAM

• Primary vDisk: /mnt/user/domains/Windows 11/vdisk1.img on VirtIO bus, boot order 1

• Graphics: Virtual, VNC, QXL video

• Network: br0, model e1000

• USB devices: currently none selected

• Unraid Share Mode: set to None now

I have already set both to as a test:

• OS Install ISO = None

• VirtIO Drivers ISO = None

I have also tried each of the iSOs no joy. There is nothing that i can see in my logs to explain this either.

And I have removed any CD-ROM devices that referenced VirtIO ISOs in the form view.

Libvirt log errors

Even after clearing the ISO fields, the libvirt log keeps spamming errors like this when I start the VM:

2025-12-08 00:04:17.070+0000: 3485216: warning : qemuDomainObjTaintMsg:5535 : Domain id=2 name='Windows 11' uuid=fe0e40e5-c2bd-0612-999b-2007f1edbdcc is tainted: high-privileges
2025-12-08 00:04:17.987+0000: 3485216: error : qemuDomainGetBlockInfo:10584 : invalid argument: invalid path /mnt/user/isos/virtio-win-0.1.262-2.iso not assigned to domain
2025-12-08 00:04:18.005+0000: 3485216: error : qemuDomainGetBlockInfo:10584 : invalid argument: invalid path /mnt/user/isos/virtio-win-0.1.262-2.iso not assigned to domain
2025-12-08 00:04:28.521+0000: 3485216: error : qemuDomainGetBlockInfo:10584 : invalid argument: invalid path /mnt/user/isos/virtio-win-0.1.262-2.iso not assigned to domain
...

The path in the error is valid and the file exists, but libvirt says it is “not assigned to domain”. I assume the GUI is still trying to query block info for that ISO even though I removed it, or there is still something stuck in the domain XML.

What I have tried

1. Turned VMs off in Settings → VM Manager, deleted and recreated libvirt.img, then recreated the Windows 11 VM and pointed it at the existing vdisk1.img.

2. Created a brand new simple test VM (Linux, new vdisk, VNC only, no USB, no VirtIO ISO). I still get errors in the libvirt log and cannot get a working VNC console.

3. Changed machine type between i440fx-9.2 and Q35.

4. Removed OS Install ISO and VirtIO Drivers ISO in the form view, and removed USB devices and Virtiofs share.

At this point libvirt runs, the VMs say “running” in the UI, but I cannot actually connect over VNC and the libvirt log keeps complaining about qemuDomainGetBlockInfo and the VirtIO ISO path.

Questions

• Is there something that changed between 7.1 and 7.2.2 in how VNC or ISO devices are handled that I should adjust?

Happy to provide full diagnostics and the current XML. Just trying to figure out why the VM appears to start but VNC does not work and why libvirt is still tied to this VirtIO ISO path.

tower-diagnostics-20251207-1709.zip

Nothing has changed that I am aware of. Have you changed any of the underlying filesystem locations.

There is a preprocessor which converts the /mnt/user path to the real disk location.

Can you provide the output from: getfattr --absolute-names --only-values -n system.LOCATION /mnt/user/isos/virtio-win-0.1.262-2.iso

I didnt change any of the filesystem locations.
root@Tower:~# getfattr --absolute-names --only-values -n system.LOCATION /mnt/user/isos/virtio-win-0.1.262-2.iso

cache
root@Tower:~#

this matches where the file is located.