From: Jacob Gorm Hansen <jacob@melon.dk>
To: Barry Silverman <barry@disus.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Really really small xen0
Date: Tue, 09 Nov 2004 00:21:49 +0100 [thread overview]
Message-ID: <418FFF8D.6070103@melon.dk> (raw)
In-Reply-To: <002501c4c5ae$c428dc10$6400a8c0@gandalf>
Barry Silverman wrote:
> Rather than have to carry python and all the rest of the toolset, would
> it be possible to:
> 1) Save a pre-built configuration database to send to xen
> and/or
> 2) Save a recording of the control message traffic between dom0 and the
> other domains using a BIG xen0, store the recording in an initrd and
> then replay it back at startup time? (and log any errors somewhere!!)
>
> It would be nice not to have to carry any shared libraries...
I am doing the following for my self-migration stuff:
- Building my own domain creation etc tools using straight libxc. All
statically linked. Now I can instantiate a new domain in 0.017s.
- Sticking with Xen 1.3 which has all the drivers in ring 0, until xend
is either massively simplified or rewritten in C. The old way of
handling networking was much easier for what I am doing.
- Writing my own unprived mini-os, running the tiny UIP TCP-stack, to
receive incoming migrations, so that ultimately I can remove dom0
completely. Almost there now, at least I can ping the thing now.
:-)
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-08 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 14:51 Really really small xen0 Barry Silverman
2004-11-08 15:20 ` Mark A. Williamson
2004-11-08 15:39 ` Barry Silverman
2004-11-08 16:08 ` Mark A. Williamson
2004-11-08 16:19 ` Barry Silverman
2004-11-08 23:21 ` Jacob Gorm Hansen [this message]
2004-11-08 16:39 ` Nathan Lutchansky
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=418FFF8D.6070103@melon.dk \
--to=jacob@melon.dk \
--cc=barry@disus.com \
--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.