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>
Subject: Re: [Xen-devel] qemu-dm cpu utilization
From: "George Dunlap " <dunlapg@xxxxxxxxx>
Date: Mon, 28 Aug 2006 13:30:30 -0400
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Delivery-date: Mon, 28 Aug 2006 10:31:31 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=d01VwYNZFc2VBPi0Mq5tKaleilRQPLpFc547SP/qTFCW/EnISqNbV36nuxPnxYei2W1i+q3FDkFTeXZp54kDzkcGWUvf2KD/8KXBYrVe5JCLYNuaMcSAMupqSN41ssMtg++HrSKMpTn5i3LJZD9+vA47l+bhry4bs/A4FqJplmo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5E735516D527134997ABD465886BBDA63A3B70@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <EF8D308BE33AF54D8934DF26520252D30528CE4F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5E735516D527134997ABD465886BBDA63A3B70@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Another pertinent question is, what size screen are you using?

From what I've heard, rather than trap on every MMIO instruction, HVM
guests are given direct access to the virtual framebuffer.  But this
means that QEMU needs to scan the framebuffer on a regular basis to
find changes, and then do diffs to make appropriate VNC changes.  This
probably scales linearly with the number of pixels to be scanned.

Try using a lower resolution, and see what you get.


On 8/28/06, McAfee, Tommie M <Tommie.McAfee@xxxxxxxxxx> wrote:

> No, at least with w2k3. Could you try and repro with w2k3?

I'm getting the same results with win2k3 that I get with the winXP and sles9, 
so it's probably not a sles9 issue.  I started the win2k3 guest and waited 
about 4-5 mins for it to finish booting.  At this point qemu-dm used 0% CPU.  
When I launched vncviewer to display the win2k3 guest, qemu-dm jumped to 

What do you think is causing this to happen?

Tommie McAfee

-----Original Message-----
From: Puthiyaparambil, Aravindh
Sent: Mon 8/28/2006 11:00 AM
To: Ian Pratt; McAfee, Tommie M; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: ian.pratt@xxxxxxxxxxxx
Subject: RE: [Xen-devel] qemu-dm cpu utilization

> No, at least with w2k3. Could you try and repro with w2k3?

Will do.  BTW, we are seeing the same issue if we use SDL.

> What VNC client are you using?

TightVNC viewer version 1.2.9

> Thanks,
> Ian

Xen-devel mailing list

Xen-devel mailing list

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