[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH devi

From: Kevin Wolf
Subject: Re: [Qemu-block] [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot
Date: Tue, 12 Jan 2016 16:26:54 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

Am 12.01.2016 um 16:16 hat Peter Maydell geschrieben:
> On 12 January 2016 at 15:13, Denis V. Lunev <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]