Raw disks (LVM) are not included while --raw is being used

[insidesec]

Hi there,

when I try to do a full backup (with level copy) of a domain that contains the following disk definition:

<disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vg2/lv0'/> <target dev='vda' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk>

no backup will be running and the output of the command contains:

[2025-03-25 10:13:49] WARNING virt client - getDomainDisks [MainThread]: Skipping direct attached block device [vda]. [2025-03-25 10:13:49] WARNING virt client - getDomainDisks [MainThread]: Skipping direct attached block device [vdb]. [2025-03-25 10:13:49] ERROR root virtnbdbackup - main [MainThread]: Unable to detect disks suitable for backup.

where the options --raw and _--type copy are given.

Am I doing something wrong or is virtnbdbackup not able to create a (full) backup of that scenario?

Best regards
Matthias

[abbbi]

the current implementation detects raw devices only via:

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>

so if they are backed by a file, not by an LVM volume as in your situation.

[abbbi]

In short: the scenario with LVM direct attached (passthrough) volumes has not been implemented currently.