qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Denis V. Lunev" <den@openvz.org>,
	Laszlo Ersek <lersek@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot
Date: Tue, 12 Jan 2016 16:26:54 +0100	[thread overview]
Message-ID: <20160112152654.GH4841@noname.redhat.com> (raw)
In-Reply-To: <CAFEAcA8OgVxXt4LUUaWk7R2+oUpNYQ4UPpGE9gW6EE7bL_itCg@mail.gmail.com>

Am 12.01.2016 um 16:16 hat Peter Maydell geschrieben:
> On 12 January 2016 at 15:13, Denis V. Lunev <den@openvz.org> wrote:
> > The idea of this patch was trivial. First of all, I would like to keep
> > this image internally snapshoted. That is why the ultimate goal
> > was to switch from raw to qcow2 to keep changes inside the
> > image.
> >
> > Though in this case this drive could be selected to save VM
> > state, which could be big. The function being changed selects
> > the image for VM state saving.
> >
> > here I would like to skip IP_PFLASH from being selected to keep
> > it small as required by libvirt guys.
> 
> This has to be a board specific decision. Some of our machine
> models might have no backing storage other than an IP_PFLASH
> drive, but it's still nice to be able to do vmsave/vmload on them.

Maybe we can give flash images lower priority than other images?

I'm not sure if we don't break compatibility with such a change, though.
loadvm on existing snapshots could fail now. We might need to change
that first so that it can find snapshots even on images that wouldn't be
the VM state image for new snapshots any more.

Kevin

  reply	other threads:[~2016-01-12 15:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  6:03 [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot Denis V. Lunev
2016-01-12 14:16 ` Kevin Wolf
2016-01-12 14:59   ` Paolo Bonzini
2016-01-12 15:13     ` Denis V. Lunev
2016-01-12 15:16       ` Peter Maydell
2016-01-12 15:26         ` Kevin Wolf [this message]
2016-01-12 15:20     ` Kevin Wolf
2016-01-12 15:35       ` Paolo Bonzini
2016-01-12 15:47       ` Denis V. Lunev
2016-01-12 16:35         ` Denis V. Lunev
2016-01-12 16:52           ` Kevin Wolf
2016-01-12 16:58             ` Denis V. Lunev
2016-01-12 17:40             ` Markus Armbruster
2016-01-12 17:50               ` Kevin Wolf
2016-01-12 17:54                 ` Denis V. Lunev
2016-01-13  8:09                 ` Markus Armbruster
2016-01-13 10:43                 ` Laszlo Ersek
2016-01-12 17:53               ` Denis V. Lunev
2016-01-13 10:41               ` Laszlo Ersek
2016-01-13 10:37         ` Laszlo Ersek
2016-01-13 11:11           ` Denis V. Lunev
2016-01-13 12:15             ` Laszlo Ersek
2016-01-12 15:10   ` Denis V. Lunev
2016-01-12 15:28     ` Kevin Wolf
2016-01-14 11:33 ` [Qemu-devel] [PATCH 1/1] RESUME " Denis V. Lunev

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=20160112152654.GH4841@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=den@openvz.org \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).