Search results

I had the same problem running a 6.14.xx kernel (I forget exactly which one). None of the ethtool tweaks worked for me - I had to revert the kernel to 6.8.12-8.

Thanks for the replies. For clarification, I'm passing the disks (ext4) from pve to an openmediavault VM, where they are pooled using mergerfs. Disks are a mix of consumer grades, plugged directly into the motherboard (i.e., SATA). So no HBA - yet anyway. I only got into virtualisation about six...

Just to follow up, I upgraded to OMV6 (bullseye) and the proxmox-backup-client backup command using namespaces worked. Many thanks.

Yes, my disks are passed through as per that link. I'll have a look at the config files, thanks. As an aside, I passed through the disks when first setting up the VM because it seemed like the right approach. Having read a little more since, I wonder what the best practice is - are there...

Currently, I have a VM (essentially a NAS) that has a number of physical disks directly passed through to it. How can I move these disks to a new VM (within the same node)? Can/should I first move the disks to a storage pool (e.g., LVM) and then attach the disks to the new VM from there?

Unfortunately I'm trying to run proxmox-backup-client from a client using buster (openmediavault v5), for which the latest version is 1.1.14 - which means (I think) I have to upgrade the client to bullseye (i.e., OMV v6) first.

I'm having problems with the --ns option for proxmox-backup-client. I can back up a client directory to the Root Namespace, as expected, using the following: proxmox-backup-client backup --backup-type host clientdata.pxar:/path/to/client/data --repository root@pam@192.168.1.10:8007:backups I...