From: "Barry Silverman" <barry@disus.com>
To: mark.williamson@cl.cam.ac.uk
Cc: xen-devel@lists.sourceforge.net
Subject: RE: Really really small xen0
Date: Mon, 8 Nov 2004 11:19:41 -0500 [thread overview]
Message-ID: <002501c4c5ae$c428dc10$6400a8c0@gandalf> (raw)
In-Reply-To: <200411081608.35569.mark.williamson@cl.cam.ac.uk>
>>Yeah. For the minimal driver kernels, we had the backend driver in
the domain
>>automatically set up bridging, etc. For flexibility and cleanness, we
now
>>set this up all from userspace.
>>We already have a generic control message framework for passing
messages to
>>other domains from domain 0. We'd need to add some more message types
in
>>order to issue bridge setup commands, etc.
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...
-------------------------------------------------------
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 16:19 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 [this message]
2004-11-08 23:21 ` Jacob Gorm Hansen
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='002501c4c5ae$c428dc10$6400a8c0@gandalf' \
--to=barry@disus.com \
--cc=mark.williamson@cl.cam.ac.uk \
--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.