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

2018-12-14 Thread Daniel P . Berrangé
On Fri, Dec 14, 2018 at 01:26:59PM +0100, Kevin Wolf wrote: > Am 14.12.2018 um 11:59 hat De Backer, Fred (Nokia - BE/Antwerp) geschrieben: > > >>> Indeed, performance traces are important for issues like this. > > >>See strace of both FC27 and FC29 attached > > > > >Looks like you traced only the

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

2018-12-14 Thread Richard W.M. Jones
On Fri, Dec 14, 2018 at 12:52:34PM +, De Backer, Fred (Nokia - BE/Antwerp) wrote: > >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

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

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

2018-12-14 Thread Kevin Wolf
Am 14.12.2018 um 11:59 hat De Backer, Fred (Nokia - BE/Antwerp) geschrieben: > >>> 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

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

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

2018-12-13 Thread Nir Soffer
On Thu, Dec 13, 2018 at 11:14 PM De Backer, Fred (Nokia - BE/Antwerp) < fred.de_bac...@nokia.com> wrote: > > 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

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

2018-12-13 Thread Eric Blake
On 12/13/18 8:49 AM, Kevin Wolf wrote: We observe that in Fedora 29 the qemu-img, before imaging the disk, it fully zeroes it. Taking into account the disk size, the whole process now takes 35 minutes instead of 50 seconds. This causes the ironic-python-agent operation to time-out. The

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

2018-12-13 Thread Kevin Wolf
Am 13.12.2018 um 15:17 hat Eric Blake geschrieben: > On 12/13/18 7:12 AM, De Backer, Fred (Nokia - BE/Antwerp) wrote: > > Hi, > > > > We're using Openstack Ironic to deploy baremetal servers. During the > > deployment process an agent (ironic-python-agent) running on Fedora linux > > uses