Charles Duffy wrote:
This is virt-inspector-1.0.34-1.3 on CentOS 5:
$ virt-inspector --ro-fish --xml da.qcow2
qemu: loading initrd (0x33a576d bytes) at 0x0000000014c4a000
umount_all: guestfs_umount_all: call launch() before using this
function at /usr/bin/virt-inspector line 375.
Running with LIBGUESTFS_DEBUG=1, it
appears that this happened due to
the guest trying to do ext3 journal recovery against a read-only image.
If telling libguestfs to run in read-only mode implied passing the
-snapshot flag to qemu, and passing the snapshot=on option to each
-drive, this should allow changes to be *temporarily* created (stored to
unlinked copy-on-write files for the duration of the run), mooting
issues of this kind.