Re: [Qemu-devel] [libvirt-users] Using virsh blockcopy -- what's it supposed to accomplish?

[Paolo Bonzini <pbonzini@redhat.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 08/01/2015 22:04, Eric Blake wrote:
> Where are you specifying the format?  I have not personally played
>  with NBD much.  But here's my guess: Even though 
> /tmp/dsk.test.qcow2 is a qcow2 file, the NBD server is serving up a
> RAW image through /dev/nbd2. Thus, if you are trying to treat 
> /dev/nbd2 as the destination of your copy, you MUST tell qemu that
>  the file format of the copy is to be raw (regardless of the file 
> format of the original that is being copied from).  If you omit the
> --raw (also spelled --format=raw in newer libvirt) parameter to the
> virsh blockcopy command, then libvirt has to guess at the 
> destination format; if the source was qcow2, then libvirt will 
> guess that the destination should be qcow2 as well.  But writing 
> qcow2 data to a raw NBD disk means you have created a nested file 
> in /tmp/dsk.test.qcow2 - it is a qcow2 file whose contents are a 
> qcow2 file whose contents are the raw data (not typical usage, and
>  a bit weird to wrap your head around).

I think you're right.

Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJUrvL9AAoJEL/70l94x66DkusIAJX9/MtI65eOZeW57upOBxuX
NOEZA34X8f/JY3WUI6Fhyfeoi/EZet4lEtPDnqG5isrYYhm7TMmJFCLt0fu4pr1Z
KSOgMlGN/Ze5m+ty/XdoYn21Ujw/nmSplaMVAc0iqfSXUXnd15LWzICemjXNSnHS
zOp0y7uLEM64EygW4vHrPAZZo5JCFj2JbQiRUiWjDyT14JeJ7EWRJ3vYSrZEAclB
RVDlm/Q6p9wirFSNbjfZgo1Fn5cHvVvsGvmNvWwLOnijBGeQwOD5LaqSsuAD3ZLN
QAQw77eLnVxwES+lR96vQcVWOKfR2pECD9pDEAwTVTqn/xbw0dqWuEwMSIZbfXU=
=Asfg
-----END PGP SIGNATURE-----