From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: libguestfs@redhat.com, Peter Lieven <pl@kamp.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Effect of qemu-img convert -m and -W options
Date: Thu, 16 Nov 2017 18:00:54 +0000 [thread overview]
Message-ID: <20171116180054.GZ2787@redhat.com> (raw)
In-Reply-To: <CAJSP0QWop2Xvjp5bObJ0yRoJ=W-6cH84fGHXj5b93Qb6TxCxDA@mail.gmail.com>
On Thu, Nov 16, 2017 at 05:30:48PM +0000, Stefan Hajnoczi wrote:
> On Thu, Nov 16, 2017 at 3:10 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> > Both local filesystems, but on different SATA devices.
>
> Okay. I'm curious what the strace -f output looks like (only the
> preadv(2)/pwritev(2) syscalls are interesting at the moment).
Here's the full strace from one run:
http://oirase.annexia.org/tmp/strace.xz
The command is (with the output.qcow2 file created in a previous run):
$ strace -o /tmp/strace -f -s 1024 qemu-img convert -f raw fedora-27.img -O qcow2 /var/tmp/output.qcow2 -m 8 -W -n
The version of qemu is: qemu-2.10.0-7.fc28.x86_64
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
next prev parent reply other threads:[~2017-11-16 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 11:52 [Qemu-devel] Effect of qemu-img convert -m and -W options Richard W.M. Jones
2017-11-16 14:47 ` Stefan Hajnoczi
2017-11-16 14:51 ` Peter Lieven
2017-11-16 15:12 ` Richard W.M. Jones
2017-11-16 17:20 ` Stefan Hajnoczi
2017-11-16 15:10 ` Richard W.M. Jones
2017-11-16 17:30 ` Stefan Hajnoczi
2017-11-16 18:00 ` Richard W.M. Jones [this message]
2017-11-20 15:57 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171116180054.GZ2787@redhat.com \
--to=rjones@redhat.com \
--cc=libguestfs@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).