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

Re: [Xen-devel] Poor HVM performance with 8 vcpus

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Poor HVM performance with 8 vcpus
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 07 Oct 2009 09:17:22 +0100
Cc:
Delivery-date: Wed, 07 Oct 2009 01:17:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0177D81F@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpHG0XK5xmB8kD/RKuruKf1efbf0QABvKHgAACjVMAAAHSgrQ==
Thread-topic: [Xen-devel] Poor HVM performance with 8 vcpus
User-agent: Microsoft-Entourage/12.20.0.090605
On 07/10/2009 09:08, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> Are there any other of these heuristics tucked away in xen? Would there
> be any benefit to specifying the OS being virtualised in the config? Eg
> "os=windows"?

There aren't really any others. The timer_mode config is along the same
lines I suppose, in that you would set it depending on guest kernel time
handling behaviour. In the specific case of shadow-code heuristics, however,
auto-detecting the OS type by methods such as try-previous-successful-first
would be the sensible way to go.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel