From: Yvette <yentlsoup@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: uclibc-dom0/xen 2.0.5 trivia
Date: Sun, 20 Mar 2005 21:36:51 -0600 [thread overview]
Message-ID: <cda406820503201936e88ff7@mail.gmail.com> (raw)
Uclibc seems to come up occasionally in the lists, and since I use one
of my uclibc-based build images as a domU, I thought I'd see for
myself if "no reason Xen _shouldn't work with a uclibc-based dom0"
meant that it _would_ work. (It's quite likely this has already been
addressed and I just missed it.) Admittedly I haven't stress-tested
the result, but the uclibc-based system seems to boot and bring up my
domains as well as the glibc-based one I normally use.
This was Xen 2.0.5, uclibc-snapshot circa July 2004, gcc 3.3.4 and
otherwise relatively standard components. I had to use a few normal
uclibc-type workarounds to get Xen to build (my image has the library
cache disabled, so any Xen check/build scripts that use "ldconfig -p |
grep something.so" fail; xentrace uses some things from argp, so one
would have to get by without it or use the stand-alone), but not
many.
Clearly this begs the question of if anybody would need or want such a
system. (I didn't, but now I have one...)
-Yvette
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-21 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 3:36 Yvette [this message]
2005-03-21 4:03 ` uclibc-dom0/xen 2.0.5 trivia Jacob Gorm Hansen
2005-03-21 5:35 ` Anthony Liguori
2005-03-21 6:02 ` Yvette
2005-03-21 7:10 ` Jacob Gorm Hansen
2005-03-21 15:26 ` Anthony Liguori
2005-03-21 20:15 ` Jacob Gorm Hansen
2005-03-21 20:24 ` Anthony Liguori
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=cda406820503201936e88ff7@mail.gmail.com \
--to=yentlsoup@gmail.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.