SimonF

You may have to force_probe the card. Have a look to see if there are any messages in syslog or dmesg?

Yes it is fine I have had 4 gpus in my test server AMD, intel arc, intel igpu and Nvidia.

Yes install the tail scale client for the VM os.

install Network UPS Tools (NUT) by desertwitch from Community Applications
 
 
 

One of the reason for them being plugins it allows out of cycle updates and fixes. If was rolled into the core then would be max 3/4 updates a year.

root@computenode:/mnt/user/domains2/Arch9# qemu-img info --backing-chain -U vdisk1.S20250321211701qcow2 image: vdisk1.S20250321211701qcow2 file format: qcow2 virtual size: 5 MiB (5242880 bytes) disk size: 196 KiB cluster_size: 65536 backing file: /mnt/user/domains2/Arch9/vdisk1.img backing file format: raw Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Child node '/file': filename: vdisk1.S20250321211701qcow2 protocol type: file file length: 192 KiB (197120 bytes) disk size: 196 KiB image: /mnt/user/domains2/Arch9/vdisk1.img file format: raw virtual size: 5 MiB (5242880 bytes) disk size: 1 MiB Child node '/file': filename: /mnt/user/domains2/Arch9/vdisk1.img protocol type: file file length: 5 MiB (5242880 bytes) disk size: 1 MiB root@computenode:/mnt/user/domains2/Arch9# cat /etc/libvirt/qemu/snapshotdb/Arch9/snapshots.db { "S20250321211701": { "name": "S20250321211701", "parent": "Base", "state": "shutoff", "desc": null, "memory": { "@attributes": { "snapshot": "no" } }, "creationtime": "1742591822", "method": "QEMU", "backing": { "hdc": [ "\/mnt\/xfspool\/domains2\/Arch9\/vdisk1.S20250321211701qcow2", "\/mnt\/user\/domains2\/Arch9\/vdisk1.img" ], "rhdc": [ "\/mnt\/user\/domains2\/Arch9\/vdisk1.img", "\/mnt\/xfspool\/domains2\/Arch9\/vdisk1.S20250321211701qcow2" ], "hdd": [ "\/mnt\/xfspool\/domains2\/Arch9\/vdisk2.S20250321211701qcow2", "\/mnt\/user\/domains2\/Arch9\/vdisk2.img" ], "rhdd": [ "\/mnt\/user\/domains2\/Arch9\/vdisk2.img", "\/mnt\/xfspool\/domains2\/Arch9\/vdisk2.S20250321211701qcow2" ], "hde": [ "\/mnt\/vmpoolzfs\/domains\/vdisk3.S20250321211701qcow2", "\/mnt\/user\/domains\/vdisk3.qcow2" ], "rhde": [ "\/mnt\/user\/domains\/vdisk3.qcow2", "\/mnt\/vmpoolzfs\/domains\/vdisk3.S20250321211701qcow2" ], "hdf": [ "\/mnt\/xfspool\/domains2\/Arch9\/vdisk4.S20250321211701qcow2", "\/mnt\/user\/domains2\/Arch9\/vdisk4.img" ], "rhdf": [ "\/mnt\/user\/domains2\/Arch9\/vdisk4.img", "\/mnt\/xfspool\/domains2\/Arch9\/vdisk4.S20250321211701qcow2" ], "hdg": [ "\/mnt\/xfspool\/domains2\/Arch9\/vdisk5.S20250321211701qcow2", "\/mnt\/user\/domains2\/Arch9\/vdisk5.qcow2" ], "rhdg": [ "\/mnt\/user\/domains2\/Arch9\/vdisk5.qcow2", "\/mnt\/xfspool\/domains2\/Arch9\/vdisk5.S20250321211701qcow2" ], "hdh": [ "\/mnt\/vmpoolzfs\/domains\/vdisk2.S20250321211701qcow2", "\/mnt\/user\/domains\/vdisk2.img" ], "rhdh": [ "\/mnt\/user\/domains\/vdisk2.img", "\/mnt\/vmpoolzfs\/domains\/vdisk2.S20250321211701qcow2" ] }, "primarypath": "\/mnt\/xfspool\/domains2\/Arch9", "disks": [ { "@attributes": { "name": "hdc", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/xfspool\/domains2\/Arch9\/vdisk1.S20250321211701qcow2" } } }, { "@attributes": { "name": "hdd", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/xfspool\/domains2\/Arch9\/vdisk2.S20250321211701qcow2" } } }, { "@attributes": { "name": "hde", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/vmpoolzfs\/domains\/vdisk3.S20250321211701qcow2" } } }, { "@attributes": { "name": "hdf", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/xfspool\/domains2\/Arch9\/vdisk4.S20250321211701qcow2" } } }, { "@attributes": { "name": "hdg", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/xfspool\/domains2\/Arch9\/vdisk5.S20250321211701qcow2" } } }, { "@attributes": { "name": "hdh", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/vmpoolzfs\/domains\/vdisk2.S20250321211701qcow2" } } } ] } }root@computenode:/mnt/user/domains2/Arch9# Path is in the image and also it is stored in my snapshotdb.

Are you looking to commit the snap image into the base.
 
You can use qemu-img to do that. https://blog.programster.org/qemu-img-cheatsheet#get-information-about-a-file
 
Snapshots will be none as the snapshotdb will have had the entries removed.

It just is a way to disable the flag. It can allow more performance for the VM. At present there is nothing to migrate between hosts using libvirt.

Looks like it may be a setting in the bios due to tile nature of TRs, Set this to enabled.
 

The snapshot implementation does not create a full copy of the disk image. It creates a QCOW2 overlay in the same dir as the disk. It is not possible to create a snapshot via script/Cmdline currently. The database for snapshots is stored in /etc/libvirt/qemu/snapshotdb/VM name/
 
Planned for a future release to provide backups, but not in scheduled timeline as yet.
 
 

Not currently but I am working on virgl for a future release. 
 

No, it is enabled by default. Turing off can provide additional performance increase hence the option has been added. For a VM to be migrated across hosts QEMU reduces the available cpu features. No plans in current pipeline to support migration between hosts.

Via the web gui or external clients, try clearing cookies.

Have you enabled in the settings?

Did you toggle slider from basic to advanced top right?

Do you have fastboot enabled in the bios, If yes disable it.

Should become available when Kernel is raised to 6.12 currently looking at 7.1 for that.

So you are trying to pass thru the igpu? This is problematic and needs a special bios.
 
 

Remove the settings from the VM template and add mappings within the plugin, if they have the same serial number you will need to do a port mapping.
 
When the VM starts it will connect the device if you enabled in the mappings.

Try install AMD reset plugin

Looks like one of the host controllers is being removed are you passing into a VM? I would disable the usbip options if not using.

In system devices select check box for the NVME, mine are not allowed due to being used in a pool.
 

 
Then in the VM Template it should show here.
 
 

VM template uses vendor product to map devices 10c4:ea60. 
Have a look at my usb manager plugin as supports mapping by bus devids. You remove from VM template if using usb manager
Have a look at my usb manager pl

You may need to blacklist the AMD driver.