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/
Home Products Support Community News


[Xen-users] Open SSI fully virtualized

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Open SSI fully virtualized
From: Tim Post <tim.post@xxxxxxxxxxxxxxx>
Date: Wed, 20 Sep 2006 18:13:23 +0800
Delivery-date: Wed, 20 Sep 2006 03:14:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Net Kinetics
Reply-to: tim.post@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello list, 

Has anyone played with Open SSI on Xen 3.0.x fully virtualized? If so
can you share experiences / frustrations / successes, and which version
of OpenSSI (and Xen) you worked with, as well as the processor / MB

I've had great success with SSI/Xen using 2.0.7 and will soon be doing a
similar project, but want to get away from 2.0.7. 

My point in asking is to determine if time is better spent porting the
SSI/Xen kernel over to a para virtualized version for 3.0.2, or go for
it as a fully virtualized guest. Hoping for some feedback prior to
endeavoring to do either.

My configuration plans will never allocate more than 3 GB per SSI node,
however I plan to again have several independent clusters running on
each virtualized node, which will have up to 32 GB ECC. 

Best to all, and thanks :)


Xen-users mailing list

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