@ph7 Do you have compression turned on for the backups? I have a couple vms that I don't compress because of the old error, I didn't update yet or Red enable compression to see what that status is.

@nikade Hey Nikade, Did you try to create a new job that will do a new chain ? Just for test.

I did get a snapshot at one of the CR VM's with the 449e7 version. I don't with 5bdd7

In theory Harvester supports nested virtualization, but I haven't tried it yet. Might be worth setting up a single host to try it. I think Proxmox also supports it, again might be worth a single host if that would handle the load.

@DustyArmstrong Thanks for responding to the GitHub issue. It’s great that more people want this working; it’s difficult to gain traction otherwise. Regarding your list, it’s correct. A reboot should be on the second place. You need to reboot only to detach your PCI device (video card) from its driver and assign it to the pciback driver instead on the next boot. This effectively creates a reservation for the device and allows you to dynamically assign it to VMs. Once your card is free from other kernel drivers, the rest doesn’t require a reboot.