From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: [RFC PATCH 0/15]: PVH xen: Patches for PVH guests
Date: Fri, 11 Jan 2013 17:22:39 -0800 [thread overview]
Message-ID: <20130111172239.7cd8b120@mantra.us.oracle.com> (raw)
Hi All,
I'm excited (and a bit nervous) to finally submit xen PVH patches for
your input. This is Phase I. Kindly ignore the 'noinline' for now, it
helps me debug. Of course, in the final patches that won't be there.
Phase I:
- Establish a baseline of something working. These patches allow for
dom0 to be booted in PVH mode, and after that guests to be started
in PV, PVH, and HVM modes. I also tested booting dom0 in PV mode, and
starting PV, PVH, and HVM guests.
There are few fixme's that I thought we could punt to Phase II.
Also, the disk must be specified as phy: in vm.cfg file:
> losetup /dev/loop1 guest.img
> vm.cfg file: disk = ['phy:/dev/loop1,xvda,w']
I've not tested anything else.
Phase II:
- Shutdown cleanup. I need to look at shutdown path during dom0 reboot.
- arch_get_info_guest() and other fixmes.
- Change xl to support other modes other than "phy:".
Phase III:
- Migration, shadow code. I've skipped shadow code for now.
Thanks for all the help,
Mukesh
next reply other threads:[~2013-01-12 1:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 1:22 Mukesh Rathor [this message]
2013-01-14 17:28 ` [RFC PATCH 0/15]: PVH xen: Patches for PVH guests Roger Pau Monné
2013-01-14 22:40 ` Mukesh Rathor
2013-01-15 16:38 ` Roger Pau Monné
2013-01-15 19:49 ` Mukesh Rathor
2013-01-15 22:46 ` Roger Pau Monné
2013-01-15 23:55 ` Mukesh Rathor
2013-01-16 8:58 ` Roger Pau Monné
2013-01-16 22:21 ` Mukesh Rathor
2013-01-16 23:15 ` Roger Pau Monné
2013-01-17 0:40 ` Mukesh Rathor
2013-01-17 9:49 ` Roger Pau Monné
2013-01-18 3:22 ` Konrad Rzeszutek Wilk
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=20130111172239.7cd8b120@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.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).