Any insight as to why OS vendors (RHEL and Ubuntu in particular)
aren't supporting blockdev-snapshot?
- RHEL claims no support for Qemu-based snapshots in any flavor
- Ubuntu hasn't enabled blockdev-snapshot in it's 19.10 release
-craig
: "Qemu-devel" To: Kevin Wolf Cc: Craig Mull , John Snow , qemu-devel@nongnu.org, Qemu-block , Leo Luan Subject: [EXTERNAL] Re: Qemu Dirty Bitmap backup to encrypted targetDate: Tue, Oct 1, 2019 6:45 AM
On Tue, Oct 01, 2019 at 10:45:53 +0200, Kevin Wolf wrote:> Am 01.10.2019 um 02:24
How can have QEMU backup write the output to an encrypted target?
Blocks in the dirty bitmap are unencrypted, and as such when I write them with QEMU backup they are written to the target unencrypted.
I've experimented with providing a json string as the target but with no luck.
transaction='
How do you change the passphrase for QCOW2 native encrypted volume?
I've played with qemu-img create and it appears I can only add a passphrase to slot 0 at volume creation time. I don't believe cryptsetup is supported with QCOW2 native encryption to manage LUKS slots.
thxs, -craig
___
