From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Mark Williamson <maw48@cantab.net>
Cc: xen-devel@lists.sourceforge.net, John L Griffin <jlg@us.ibm.com>
Subject: Re: Multiple priviliged domains
Date: Sun, 19 Dec 2004 12:52:11 +0100 [thread overview]
Message-ID: <41C56B6B.7080204@diku.dk> (raw)
In-Reply-To: <200412191825.06913.maw48@cantab.net>
Mark Williamson wrote:
l.
>
> Obviously, dom0 will need control of some physical devices inorder to have
> something to boot from (unless ofcourse you use a *really big* initrd :-) ).
>
hi,
In my setup, you do not need a very large initrd to do this.
Essentially, the only thing running in dom0 is a simple ICMP/ping
server. You send a specially formatted and signed ping payload to dom0,
and in response to that it fires up a new VM with a UIP TCP/IP stack
inside. You then connect to that TCP/IP stack, and self-migrate or
(eventually, not implemented yet) bootstrap directly into the
unprivileged guest. Dom0 does not need to have a TCP/IP stack, and at
present the ping server main loop is only 50 lines of code.
With pre-NGIO version of Xen 1.3 that I am currently using, all you need
in your dom0-initrd is the ping server and an ELF image from which to
create UIP guest VMs. I am hoping that in the future the parts of xend
that have to do with setting up network interfaces to domains will split
out into a small C executable, as that would allow me to provide similar
functionality for Xen 2.0 or 2.1.
Source and binaries are available from
http://www.diku.dk/~jacobg/self-migration/
Jacob
PS: I do apologize to the long-time subscribers who are fed with me
spamming this list with ads for self-migration stuff every time a new
user who could find this relevant shows up on the list. Perhaps I can
convince the Xen webpage maintainers to link to my stuff as a related
project?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-19 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 5:52 Multiple priviliged domains John L Griffin
2004-12-19 9:22 ` Ian Pratt
2004-12-19 14:02 ` Jan Kundrát
2004-12-19 17:05 ` Bin Ren
2004-12-19 18:25 ` Mark Williamson
2004-12-19 11:52 ` Jacob Gorm Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-19 21:44 Neugebauer, Rolf
2004-12-19 14:52 ` Jacob Gorm Hansen
2004-12-19 22:29 ` Ian Pratt
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=41C56B6B.7080204@diku.dk \
--to=jacobg@diku.dk \
--cc=jlg@us.ibm.com \
--cc=maw48@cantab.net \
--cc=xen-devel@lists.sourceforge.net \
/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.