Re: [Qemu-devel] [Qemu-block] Request for clarification on qemu-img convert behavior zeroing target host_device

2018-12-14 Thread De Backer, Fred (Nokia - BE/Antwerp)
>Of course, we should also think about the other problem you mentioned, related >to copying a smaller image to a larger block device. Does this require zeroing >the parts after the image or should we leave them alone? > >I'd tend to say that since you're passing the whole block device as a target

Re: [Qemu-devel] [Qemu-block] Request for clarification on qemu-img convert behavior zeroing target host_device

2018-12-14 Thread De Backer, Fred (Nokia - BE/Antwerp)
>>> Indeed, performance traces are important for issues like this. >>See strace of both FC27 and FC29 attached >Looks like you traced only the main thread. All the I/O is done in other >threads. >These flags would be useful: > >    strace -o log -f -T -tt New straces attached with mentioned flag

[Qemu-devel] Request for clarification on qemu-img convert behavior zeroing target host_device

2018-12-13 Thread De Backer, Fred (Nokia - BE/Antwerp)
Hi, We're using Openstack Ironic to deploy baremetal servers. During the deployment process an agent (ironic-python-agent) running on Fedora linux uses qemu-img to write a qcow2 file to a blockdevice. Recently we saw a change in behavior of qemu-img. Previously we were using Fedora 27 containi