SimonF

Work as expected for me. Which browser are you using, also does the /mnt/user/isos share exist? Are yiu using an unassigned device for the VM storage locations? SERVICE="enable" IMAGE_FILE="/mnt/user/system/libvirt/libvirt.img" IMAGE_SIZE="2" DEBUG="no" DOMAINDIR="/mnt/disks/250240800110/VMs/" MEDIADIR="/mnt/user/isos/"

Which version of the plugin are you running?

Which GPU and can you provide a screen shot?

You can run qemu-img info last_snap_file | grep backing and this will show the tree. You can use the flatten method as that is a solution that would be used to make a backup. The bug is just removing the snapshotdb entry for the gui if there are more than 2 snaps. Select on the last snap and commit using --base and --top this will collapse the whole tree back into the base image. root@computenode:~# qemu-img info /mnt/user/domains2/Arch9/vdisk1.S20250321211701qcow2 | grep backing backing file: /mnt/user/domains2/Arch9/vdisk1.img backing file format: raw root@computenode:~#

The db is just tracking for the gui. If you put the files in the original directory it will do the block commit and remove the entries from the db.

The way snapshots work is it creates an overlay file which has a backing file. The VM could not find the backing file as it was moved. The info on the backing files are stored within the qcow2 file and not within the template. Yes VM service needs to be started so the libvirt image file is mounted. root@computenode:~# qemu-img info /mnt/user/domains2/Arch9/vdisk1.S20250321211701qcow2 | grep backing backing file: /mnt/user/domains2/Arch9/vdisk1.img backing file format: raw

When you do the block commit it will remove the snapshot. You would also need to update the XML as the path would be wrong. The snapshotdb may be incorrect also. Can you cat /etc/libvirt/qemu/snapshotdb/VM name/snapshots.db There is an option in qemu-img to rebase the base image in the overlay file but I have not tried. I would just do the commit and then move etc.

On the menu line there is USB which will take you to Click on the second icon device mapping, first is port mapping. Then it will take you to the settings. Select the VM and enable auto connect at plugin and VM start. The printer will need to be active for it to show in the view.

No there is no option to bind devices to usbip via the plugin.

Have a look at my USB manager plugin, you can remove from the VM template and it will add to the VM when it is active. You would create a device mapping for the printer and connect to VM at start and when connected.

Bcards use XE driver and dont support SRIOV unless it is a pro card. It may be a requirement to have a later kernel

Hi it may be some that could be looked into, How do you think this would work, are you looking for a different banks for disks to be allocated to a specific fan group. When the disks spin down the is an override option to use a different sensor.

Do you not get an option in the plugins page to install the new version?

Looking at the manual for the mother board it has only 2 cooling zones. 1-5 and A/B. You would need to request from Supermicro more details on the IPMI and levels of control.

When doing the commit select the last one if you want to commit all into the original you can leave the defaults. There is a bug I am working on that the snapshots in the GUI will leave info about the middle snapshot but it is just a ghost record in the snapshotdb file. base is the first image in the tree with top being the latest.

as you are on 7.2.2. try setting this to 39bits.

I would post on the nvidia plugin support thread. If it is not working correctly with the open source one.

Does look like you do need the open source one.

Try the production one, But may be worth posting in the Nvidia plugin thread if that does not work.

I think the version of the driver you have does not support 50xx series cards. Try the latest driver. The NVIDIA 580.95.05 driver supports a wide range of GPUs, including the latest Blackwell (RTX PRO), Ada Lovelace (RTX 40 Series/Ada), and Ampere (A-Series, RTX A-series) architectures, plus older professional Quadro RTX, Tesla (T, V, P-Series), and some GeForce cards, offering features like YCbCr 4:2:2 HDMI support for Blackwell and Coherent Driver-Based Memory Management for GB200 platforms.

Should pickup the intel drivers as they are included. You will need to an /dev/dri to the containers for them to find the GPU.

Have you bound it to vfio in system devices? If bound to vfio Nvidia driver will not be able to see the card. Within Plex you also need to enable Nvidia runtime and the device in the template. lspci -ks 0000:01:00.0 should show the driver on the card?

I have now fixed these two issues. @joshua777

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

Sorry for the delay in getting back to you. The Windows VM looks like it is not using the snapshot files but I don't know why the snapshot.db is still there as the entries should be removed. Unless you manually change the disk images. Files are stored as follows. In domains/VMName Disk files, overlayfiles, memory dump, and running config. in /etc/libvirt/qemu XML, NVRAM, /snapshotdb/VMName is the snapshot db. Looking at the XML the windows vm is using the main image files so any snapshot overlay files should be ok to remove. you can remove the snapshotdb. Will look at the debian one soon. It you want to send me ls of the directories I can check further. I will create a utility to do a sence check on Snapshots to look for issues and do some testing to see if an issue has crept in.