xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Grant McWilliams <grantmasterflash@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Stephen Spector <stephen.spector@citrix.com>,
	Xen List <xen-users@lists.xensource.com>
Subject: Re: Re: [Xen-users] Xen 4.1 Feature Request List
Date: Wed, 07 Apr 2010 10:17:48 -0700	[thread overview]
Message-ID: <4BBCBE3C.8030203@goop.org> (raw)
In-Reply-To: <y2oed123fa31004070413id563f7d1p36f3cac15bb6c23c@mail.gmail.com>

On 04/07/2010 04:13 AM, Grant McWilliams wrote:
>
>    1. Figure out why you can't start a VM with a disk image residing
>       in a ramdisk (bug?)
>

What happens if you do that?

>    1. Nesting
>          1. As silly as this feature sounds it may be why I leave Xen
>             for KVM. This would be useful for teaching management of
>             VMs. A student could have a Dom0 and start up DomUs inside
>             it without each on needing their own physical machine.
>

Xen nests OK, so long as you're happy running purely PV guests within 
the inner Xen.

>         1.
>
>
>    1. Install PV DomU from CD without FTP/NFS tricks.
>          1. I don't care how it's done but it would be nice. The
>             "install from network" shuffle can pose a complexity for
>             people getting started in Xen. I'm aware that HVM does
>             this because of it's use of Qemu but it would be nice
>             everywhere. Maybe as Xen moves to Hybrid VMs instead of
>             PV/HVM this will no longer be an issue.
>

What I typically do is install systems as HVM, then just boot them as PV 
later on.  For Fedora installs, at least, it pretty much just works 
because they avoid having any direct device references for filesystems, 
etc.  It's a bit more fiddly without having HVM available.

     J

  parent reply	other threads:[~2010-04-07 17:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 17:41 Xen 4.1 Feature Request List Stephen Spector
2010-04-06 19:10 ` [Xen-users] " David Markey
2010-04-07 11:07   ` Stefano Stabellini
2010-04-07 11:15     ` Grant McWilliams
2010-04-07 11:18       ` [Xen-devel] " Stefano Stabellini
2010-04-07 11:27       ` Pasi Kärkkäinen
2010-04-07 13:06         ` David Markey
2010-04-07 14:07           ` Re: [Xen-users] " Stefano Stabellini
2010-04-07 11:13 ` Grant McWilliams
2010-04-07 14:51   ` Pasi Kärkkäinen
2010-04-07 20:59     ` Grant McWilliams
2010-04-07 21:04       ` [Xen-users] " Pasi Kärkkäinen
2010-04-07 17:17   ` Jeremy Fitzhardinge [this message]
2010-04-07 18:07     ` Keir Fraser
2010-04-07 13:51 ` Jeff Sturm
2010-04-08 12:33 ` Fantu
2010-04-08 17:30   ` Jeremy Fitzhardinge
2010-04-08 18:23     ` Fantu
2010-04-08 18:40       ` Jeremy Fitzhardinge
2010-04-08 19:00     ` Thomas Goirand
2010-04-08 19:46       ` Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Carsten Schiers
2010-04-08 20:12         ` Pasi Kärkkäinen
2010-04-10  9:26           ` AW: " Carsten Schiers
2010-04-12  7:59             ` Pasi Kärkkäinen
2010-04-08 20:46         ` Konrad Rzeszutek Wilk
2010-04-10 16:07       ` Xen 4.1 Feature Request List Christian Tramnitz
2010-04-10  2:09 ` Vincent, Pradeep
2010-04-20 10:32 ` Juergen Gross

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=4BBCBE3C.8030203@goop.org \
    --to=jeremy@goop.org \
    --cc=grantmasterflash@gmail.com \
    --cc=stephen.spector@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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).