From: David Becker <becker@cs.duke.edu>
To: Xen-devel@lists.sourceforge.net
Subject: Xen at scale
Date: Thu, 18 Mar 2004 10:44:56 -0500 [thread overview]
Message-ID: <20040318154456.GQ3473@cs.duke.edu> (raw)
I'm using Xen for our cluster management project. At the moment 219
xen-1.2 nodes are up (my interest in multicast is to udpcast virtual disk
images to all those hosts). At this time I'm just running two domains on
each host but that will be going up soon (as well as the total number of hosts).
For the most part all is well. Sometimes a domain will spontaneously stop and
I've yet to figure out why. The leading suspect is memory pressure.
My wish list based on my experience so far:
HIGHMEM4G - This is my top wish, and I will work on it myself
when I get a chance, though I can't say when that will be.
halt - Xen is unstoppable!!!! :-)
We had an A/C outage the other night, and while trying to
remotely shutdown sections of the cluster I discovered that
halting DOM0 just caused xen to reboot.
system info/logging -
It would be very handy to have total phys memory reported
somehow. The cluster is heterogenous, and memory upgrades
happen, and the net result is I rely on /proc/meminfo to know
what is in each host. The xenolinux meminfo just says what
that domain was allocated. Is total RAM reported somewhere
I don't know?
Viewing the vfr rules without resorting to xen_read_console
would be handy as well.
Getting xen console output to a log file would be useful.
Running hundreds of xen_read_console is not so practical.
This would help in identifying those mysterious reboots.
Most hosts in this cluster do not have serial lines or heads
attached. I think I saw console output was changing in 1.3
so maybe this has been worked on already.
multicast - as mentioned
FreeBSD - I'd love a freebsd domain. I know y'all said this was
in the works. Is there any current status?
Perhaps some of this is already there, and I just don't know. More docs
are always welcome. My own documentation track record is not so great so I
can sympathize on this one.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-03-18 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <becker@cs.duke.edu>
2004-03-18 15:44 ` David Becker [this message]
2004-03-18 16:00 ` Xen at scale Ian Pratt
2004-03-18 16:27 ` David Becker
2004-03-18 16:21 ` Mark Williamson
2004-03-23 22:37 MAGENHEIMER,DAN (HP-FtCollins,ex1)
2004-03-23 22:59 ` Alex Ho
2004-03-23 23:08 ` Ian Pratt
2004-03-23 23:23 ` Christian Limpach
2004-03-24 6:54 ` Kip Macy
2004-03-24 10:31 ` Christian Limpach
2004-03-24 10:49 ` Keir Fraser
2004-03-24 12:12 ` Christian Limpach
2004-03-24 15:56 ` Kip Macy
2004-03-24 17:15 ` Christian Limpach
2004-03-24 18:39 ` Kip Macy
2004-03-24 19:41 ` Christian Limpach
2004-03-24 19:55 ` Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 23:47 MAGENHEIMER,DAN (HP-FtCollins,ex1)
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=20040318154456.GQ3473@cs.duke.edu \
--to=becker@cs.duke.edu \
--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.