All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Easier interface for kickstarting Xen VMs
Date: Tue, 21 Sep 2010 14:32:57 -0400	[thread overview]
Message-ID: <1285093817-sup-6885@ezyang> (raw)
In-Reply-To: <alpine.DEB.2.00.1009211741010.2721@kaball-desktop>

Excerpts from Stefano Stabellini's message of Tue Sep 21 12:46:53 -0400 2010:
> You should be aware that we are trying to move away from xend to xl,
> that generally supports the same VM config file format with just one
> exception: embedded python.

Stefano, that's really interested!  None of our current team was aware of
this fact; probably because we're still on Ubuntu 8.04 due to Xen's
special packaging situation on this platforms.

> Considering that kickstarting Xen VMs is a common problem and probably
> the main headache for sysadmins when moving from xend to xl, I would
> welcome a clean and small solution to this problem that doesn't involve
> embedded python.

That's great to hear.  The point of the solution is to do away with the
embedded Python.

> If we go with the temporary fs strategy, I guess there isn't any actual
> code to be committed to xen-unstable, but rather a wiki page to
> describe the solution and a link to the initrd? 

Considering that any given Kickstart file needs to be converted into an
initrd, there would be code involved.  I am also unconvinced that Anaconda
actually /works/ with layered initrd, see my post here:

    https://www.redhat.com/archives/kickstart-list/2010-September/msg00015.html

Cheers,
Edawrd

  reply	other threads:[~2010-09-21 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 17:04 Easier interface for kickstarting Xen VMs Edward Z. Yang
2010-09-21 16:46 ` Stefano Stabellini
2010-09-21 18:32   ` Edward Z. Yang [this message]
2010-09-22 11:23     ` Stefano Stabellini

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=1285093817-sup-6885@ezyang \
    --to=ezyang@mit.edu \
    --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 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.