From: Jerome Brown <jerome@concepts.net.nz>
To: xen-devel@lists.sourceforge.net
Subject: Re: uClibc
Date: Wed, 22 Dec 2004 09:52:19 +1300 [thread overview]
Message-ID: <41C88D03.2090409@concepts.net.nz> (raw)
In-Reply-To: <41C8894D.8060201@diku.dk>
Jacob Gorm Hansen wrote:
> I don't think Xen itself is compiled against any libc. I have a
> busybox-based (though using glibc right now) initrd which you can use
> for your unprivileged domains. You can download it from
> http://www.diku.dk/~jacobg/self-migration/
What size does this run at? I am looking to make dom0 as small as
possible, and run all the applications that I require under other
domains, to allow moving them to other machines if required.
> I am working on exactly the same thing, though I am using self-migration
> in XenLinux rather than the managed migration in Xen. I am already able
> to migrate to a minimal Xen-host (the network-facing privileged code is
> about 50 lines of C, there is not even a TCP/IP stack running), and I am
> currenly working on being able to create new domains using the same
> mechanism (almost there).
How does the XenLinux self-migration differ from the Xen managed
migration? What are the advantages of each option. I have only just
started to look into this, so am not stuck to a specific way of doing
things at this stage :)
> I am currently on Xen 1.3, because the current Xend is too
> resource-hungry and complex for my needs. I am crossing my fingers for
> someone to implement the basics of Xend in C, and when that happens I
> plan to move to Xen 2.0.
How do the resources used differ? Is Xend currently in python? Is there
a plan to change this? What has been the reasoning behind developing it
in python?
> Input and cooperation is welcomed.
I'd love to help. I like the idea of a 'self installing' dom0 that sets
up another control domain, thereby abstracting all the running processes
into unprivileged domains for security reasons. As part of this I will
look to create a HowTo document that details how I acheive this :)
Regards
Jerome
-------------------------------------------------------
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-21 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 20:14 uClibc Jerome Brown
2004-12-21 20:36 ` uClibc Jacob Gorm Hansen
2004-12-21 20:52 ` Jerome Brown [this message]
2004-12-21 21:11 ` uClibc Jacob Gorm Hansen
2004-12-21 22:44 ` uClibc Kip Macy
2004-12-21 15:20 ` uClibc Jacob Gorm Hansen
2004-12-21 23:36 ` uClibc Jacob Gorm Hansen
2004-12-22 1:48 ` uClibc Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2015-12-19 9:18 uclibc Markus Volk
2015-12-19 9:34 ` uclibc Khem Raj
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=41C88D03.2090409@concepts.net.nz \
--to=jerome@concepts.net.nz \
--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.