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-users

[Xen-users] Xen 3.0 and SMP

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Xen 3.0 and SMP
From: "Alan Greenspan" <alan@xxxxxxxxxxx>
Date: Thu, 19 May 2005 12:20:05 -0400
Delivery-date: Thu, 19 May 2005 16:21:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: egenera
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Questions about the roadmap for 3.0 and SMP?
 
Can a domU be a larger SMP than the underlying host, e.g. can one make a 5-way domU on a 4-way host?   If not, what are the constraints on the #CPU for an SMP domU.
 
How do SMP domUs get scheduled?   For example, if there are 2 2-way domUs running on a 2-way host, can both domUs be running simultaneously (1 CPU from each) or does each SMP domU get scheduled en mass, using both host CPUs when running at all times?
 
What is the expected loss in performance of running a domU with identical SMP characteristics to its host?   In other words,  if running a single 4-way domU on a 4-way host, what would one expect the performance loss to be?
 
Can an SMP domU migrate to a host with less cpus, more cpus?
 
Alan
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>