WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Xen at scale

To: Xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen at scale
From: David Becker <becker@xxxxxxxxxxx>
Date: Thu, 18 Mar 2004 10:44:56 -0500
Delivery-date: Thu, 18 Mar 2004 15:58:41 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Mail-followup-to: Xen-devel@xxxxxxxxxxxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.5.1+cvs20040105i
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>