From: Alex Bligh <alex@alex.org.uk>
To: xen-devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, Alex Bligh <alex@alex.org.uk>
Subject: QEMU: Enabling live-migrate on HVM on qemu-xen device model in 4.2
Date: Sat, 19 Jan 2013 17:56:45 +0000 [thread overview]
Message-ID: <1358618210-16475-1-git-send-email-alex@alex.org.uk> (raw)
This patch series consists of 2 parts:
* 5 patches to QEMU
* 11 patches to libxl
These patches enable live-migrate on HVM using the upstream qemu-xen
device model under Xen 4.2. Currently this is unimplemented. In the
main they are backports of patches in xen-unstable, thought the
QEMU side in particular needed some fiddling.
The patches are the same as previously submitted under the same
subject line as a 'request for comment', save that:
1. An additional obviously-correct patch has been added as the
11th patch to libxl, where a parameter was always being passed
as NULL.
2. They are now tested in our environment. With that test case,
live migrate works as well as it did under 4.1 with the previous
qemu device model. I do not claim all use cases are tested.
I would suggest these patches should be included in 4.2.2.
next reply other threads:[~2013-01-19 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 17:56 Alex Bligh [this message]
2013-01-19 17:56 ` [PATCH 1/5] QMP, Introduce xen-set-global-dirty-log command Alex Bligh
2013-01-19 17:56 ` [PATCH 2/5] xen: Introduce xen_modified_memory Alex Bligh
2013-01-19 17:56 ` [PATCH 3/5] exec: Introduce helper to set dirty flags Alex Bligh
2013-01-19 17:56 ` [PATCH 4/5] exec, memory: Call to xen_modified_memory Alex Bligh
2013-01-19 17:56 ` [PATCH 5/5] xen: Set the vram dirty when an error occur Alex Bligh
-- strict thread matches above, loose matches on Subject: below --
2013-01-19 17:57 QEMU: Enabling live-migrate on HVM on qemu-xen device model in 4.2 Alex Bligh
2013-02-12 15:34 ` Ian Jackson
2013-02-13 18:33 Alex Bligh
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=1358618210-16475-1-git-send-email-alex@alex.org.uk \
--to=alex@alex.org.uk \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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).