From: "Richard W.M. Jones" <rjones@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qcow2, lazy_refcounts and killing qemu
Date: Mon, 1 Sep 2014 14:07:00 +0100 [thread overview]
Message-ID: <20140901130700.GV1302@redhat.com> (raw)
In-Reply-To: <20140901144102.0aaae712@bahia.local>
On Mon, Sep 01, 2014 at 02:41:02PM +0200, Greg Kurz wrote:
> On Sat, 30 Aug 2014 15:53:13 +0100
> "Richard W.M. Jones" <rjones@redhat.com> wrote:
> > I can reproduce this easily, although of course the reproducer will
> > involve libguestfs.
> >
> > Rich.
> >
>
> Can you share this reproducer ?
The immediate reproducer (not very useful for you) is virt-v2v, if you
enable lazy_refcounts by hacking the call to qemu-img here:
https://github.com/libguestfs/libguestfs/blob/master/v2v/v2v.ml#L102
I'll try to come up with an actual reproducer, but I stress it's still
going to use libguestfs because that's the only sane way to run qemu
for the purposes of this test.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
next prev parent reply other threads:[~2014-09-01 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 14:53 [Qemu-devel] qcow2, lazy_refcounts and killing qemu Richard W.M. Jones
2014-09-01 12:41 ` Greg Kurz
2014-09-01 13:07 ` Richard W.M. Jones [this message]
2014-09-01 14:19 ` Richard W.M. Jones
2014-09-01 14:23 ` Richard W.M. Jones
2014-09-01 14:30 ` Greg Kurz
2014-09-05 15:39 ` Stefan Hajnoczi
2014-09-05 17:41 ` Richard W.M. Jones
2014-09-08 7:16 ` Markus Armbruster
2014-09-08 18:29 ` Max Reitz
2014-09-08 9: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=20140901130700.GV1302@redhat.com \
--to=rjones@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).