From: "Daniel P. Berrange" <berrange@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>,
David Gilbert <dgilbert@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] pflash (UEFI varstore) migration shortcut for libvirt
Date: Wed, 27 Aug 2014 09:58:33 +0100 [thread overview]
Message-ID: <20140827085832.GA15714@redhat.com> (raw)
In-Reply-To: <1408789147-18675-1-git-send-email-lersek@redhat.com>
On Sat, Aug 23, 2014 at 12:19:05PM +0200, Laszlo Ersek wrote:
> Libvirt is growing support for x86_64 OVMF guests:
>
> http://www.redhat.com/archives/libvir-list/2014-August/msg01045.html
>
> An important feature of such guests is the persistent store for
> non-volatile UEFI variables. This is implemented with if=pflash drives.
> The referenced libvirt patchset sets up the varstore files for
> single-host use.
>
> Wrt. migration, two choices have been considered:
> (a) full-blown live storage migration for the drives backing pflash
> devices,
> (b) vs. a shortcut that exploits the special nature of pflash drives
> (namely, their minuscule size, and a RAMBlock that keeps the full
> contents of each pflash drive visible to the guest, and is
> up-to-date, at all times.)
So, IIUC, with option b), libvirt will merely need to make sure that
the NVRAM var store file exists with the right size. QEMU will then
just 'do the right thing' for migration copying across the contents ?
If so that sounds nice to me.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-08-27 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 10:19 [Qemu-devel] [PATCH 0/2] pflash (UEFI varstore) migration shortcut for libvirt Laszlo Ersek
2014-08-23 10:19 ` [Qemu-devel] [PATCH 1/2] pflash_cfi01: fixup stale DPRINTF() calls Laszlo Ersek
2014-08-23 10:19 ` [Qemu-devel] [PATCH 2/2] pflash_cfi01: write flash contents to bdrv on incoming migration Laszlo Ersek
2014-08-25 10:33 ` [Qemu-devel] [PATCH 0/2] pflash (UEFI varstore) migration shortcut for libvirt Paolo Bonzini
2014-09-19 6:48 ` Alexey Kardashevskiy
2014-09-19 8:13 ` Paolo Bonzini
2014-08-27 8:58 ` Daniel P. Berrange [this message]
2014-08-27 9:21 ` Laszlo Ersek
2014-09-01 15:53 ` 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=20140827085832.GA15714@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.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).