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


RE: [Xen-devel] qemu-dm cpu utilization

To: "McAfee, Tommie M" <Tommie.McAfee@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] qemu-dm cpu utilization
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 27 Aug 2006 21:51:19 +0100
Delivery-date: Sun, 27 Aug 2006 13:52:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbJKv19/U8dkyKGQoGJXWqmnMhRxAA7oNNA
Thread-topic: [Xen-devel] qemu-dm cpu utilization
> It appears that qemu is adding too much overhead to
> virtual machines to display graphics.
> If I boot a sles9sp3 domVT in runlevel 5 with vga=0x314 for a
> graphicalboot, and immediately use
> vncviewer simply to watch the virtual machine as it boots,
> qemu-dm consumes 40% cpu as soon as vncviewer is launched and remains
> way throughout this entire process  without settling down when the
> screen appears.
> Even If I close the console that's viewing the virtual host,  qemu-dm
> remains at 40-44%.

That's considerably more than my experience. With a vncviewer connected
it's normal to see qemu-dm burning 5-10% CPU.

We do the majority of our HVM testing using windows as obviously the
best way of running linux is fully 'enlightened' (para-virtualized). It
would be good to test to see whether the issue that you're seeing is
sles9 specific.


Xen-devel mailing list

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