From: Anthony PERARD <anthony.perard@citrix.com>
To: QEMU-devel <qemu-devel@nongnu.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [Qemu-devel] [PATCH 0/5] Have a working migration with Xen
Date: Thu, 24 Nov 2011 16:08:08 +0000 [thread overview]
Message-ID: <1322150893-887-1-git-send-email-anthony.perard@citrix.com> (raw)
Hi all,
This patch series provide some fix to have migration working with Xen. The main
issue with Xen is that the guest RAM is not handle by QEMU.
So, first of all, the RAM will not be saved in the QEMU state file.
Then, during the initialisation that append before the migration, QEMU should
not try to allocate again the VRAM of the vga emulation, because it's already
there. (The guest RAM is restored before calling QEMU)
And last but not least, in QEMU with Xen, a call to set_memory (with different
address for start_addr and phys_offset) actually move the the memory, and the
only way to have a pointer to this memory is to ask a ptr with the new addr.
So, there is a patch that check for the right guest address to map.
There is probably a better way to do some of this.
Regards,
Anthony PERARD (5):
vl.c: Do not save RAM state when Xen is used.
xen mapcache: Check if a memory space has moved.
Introduce premigrate RunState.
xen: Change memory access behavior during migration.
vga-cirrus: Workaround during restore when using Xen.
hw/cirrus_vga.c | 20 +++++++++++++++++---
qapi-schema.json | 2 +-
vl.c | 10 ++++++++--
xen-all.c | 32 ++++++++++++++++++++++++++++++++
xen-mapcache.c | 8 ++++++--
xen-mapcache.h | 1 +
6 files changed, 65 insertions(+), 8 deletions(-)
--
Anthony PERARD
next reply other threads:[~2011-11-24 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 16:08 Anthony PERARD [this message]
2011-11-24 16:08 ` [Qemu-devel] [PATCH 1/5] vl.c: Do not save RAM state when Xen is used Anthony PERARD
2011-11-24 17:23 ` Stefano Stabellini
2011-11-24 18:06 ` Anthony PERARD
2011-11-24 16:08 ` [Qemu-devel] [PATCH 2/5] xen mapcache: Check if a memory space has moved Anthony PERARD
2011-11-24 17:40 ` Stefano Stabellini
2011-11-24 17:57 ` Stefano Stabellini
2011-11-24 16:08 ` [Qemu-devel] [PATCH 3/5] Introduce premigrate RunState Anthony PERARD
2011-11-24 16:08 ` [Qemu-devel] [PATCH 4/5] xen: Change memory access behavior during migration Anthony PERARD
2011-11-24 16:08 ` [Qemu-devel] [PATCH 5/5] vga-cirrus: Workaround during restore when using Xen Anthony PERARD
2011-11-24 18:30 ` Stefano Stabellini
2011-11-24 18:49 ` Anthony PERARD
2011-11-25 11:51 ` Stefano Stabellini
2011-11-25 12:33 ` Anthony PERARD
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=1322150893-887-1-git-send-email-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).