qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, lampahome <pahome.chen@mirlab.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Can I only commit from active image to corresponding range of its backing file by qemu cmd?
Date: Thu, 13 Sep 2018 15:06:54 -0500	[thread overview]
Message-ID: <c7fc2563-00f1-db67-8635-e15a6087d988@redhat.com> (raw)
In-Reply-To: <81bba910-3e33-376d-f490-151fcccd4322@redhat.com>

On 9/13/18 2:41 PM, Max Reitz wrote:
> On 13.09.18 20:37, Max Reitz wrote:
> 
> [...]
> 
>> Or, we would have to use backing=null, but for some reason that doesn't
>> work.  I'll have to investigate.
> 
> Turns out this was fixed in e59a0cf17b1b9932b65e6fc25d6856976f5e4831.
> 
> (Why does Fedora still have only qemu 2.11?)

Fedora 28 + virtmaint-sig-virt-preview COPR has qemu 3.0.  Come join us 
on the bleeding edge :)

> So starting with 2.12, putting a "'backing':null" behind
> "'driver':'qcow2," will work just as well as rebasing img.003.

Good to hear.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-09-13 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  3:33 [Qemu-devel] Can I only commit from active image to corresponding range of its backing file by qemu cmd? lampahome
2018-09-13 13:22 ` Max Reitz
2018-09-13 17:05   ` Eric Blake
2018-09-13 18:37     ` Max Reitz
2018-09-13 19:41       ` Max Reitz
2018-09-13 20:06         ` Eric Blake [this message]
2018-09-13 20:01       ` Eric Blake
2018-09-13 20:44         ` Max Reitz
2018-09-14  2:19           ` lampahome
2018-09-14 14:48             ` Eric Blake

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=c7fc2563-00f1-db67-8635-e15a6087d988@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pahome.chen@mirlab.org \
    --cc=qemu-block@nongnu.org \
    --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).