From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Laszlo Ersek <lersek@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>,
Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Juan Quintela <quintela@redhat.com>,
David Gilbert <dgilbert@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 0/2] pflash (UEFI varstore) migration shortcut for libvirt
Date: Fri, 19 Sep 2014 10:13:09 +0200 [thread overview]
Message-ID: <541BE595.6090905@redhat.com> (raw)
In-Reply-To: <541BD1BC.8090501@ozlabs.ru>
Il 19/09/2014 08:48, Alexey Kardashevskiy ha scritto:
> Right now we use NVRAM on sPAPR as:
> -drive id=id3,if=none,file=qemu_nvram.img
> -global spapr-nvram.drive=id3
>
> So the NVRAM file is BlockDriverState and HMP's "migrate -b" copies the
> content just fine.
>
> What is missing here? Thanks.
"migrate -b" is a big hammer, because it transfers all disks. In some
cases it is useful to have shared storage for disks and non-shared
storage for variable stores.
For UEFI, we are using RAM migration to transfer non-volatile RAM from
the source to the destination. This is done by loading the whole
contents of nvram into a RAM MemoryRegion at VM startup, and storing it
at postload time. The latter is done with this patch.
Paolo
next prev parent reply other threads:[~2014-09-19 8:13 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 [this message]
2014-08-27 8:58 ` Daniel P. Berrange
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=541BE595.6090905@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=mprivozn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.