From: Anthony Liguori <anthony@codemonkey.ws>
To: xen-devel@lists.xensource.com
Subject: Re: qemu-dm cpu utilization
Date: Tue, 29 Aug 2006 19:43:05 -0400 [thread overview]
Message-ID: <44F4D109.507@codemonkey.ws> (raw)
In-Reply-To: <5E735516D527134997ABD465886BBDA63A3B6C@USTR-EXCH5.na.uis.unisys.com>
McAfee, Tommie M wrote:
> Using an 8-way ES7000 with 32GB of ram, I'm running xen at changset 11217
> with dom0_mem=3092M as a kernel parameter on a x86_64 hyperviser.
>
> 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 that way throughout this entire process without settling down when the login screen appears.
> Even If I close the console that's viewing the virtual host, qemu-dm remains at 40-44%.
Almost everything in the VNC code resets when a guest disconnected
except for the timer. If a client disconnects, the timer routine should
be almost a nop but it's possible that it's somehow causing qemu-dm to
do something funky.
If you delete the timer (and set vs->timer = NULL) in
vnc_client_io_error(), does it reduce the usage?
BTW, if you're using 800x600, I suspect that you may be falling back to
MMIO instead of a linear framebuffer. Try moving to 1024x768 and see if
that helps.
Regards,
Anthony Liguori
>
> When booting the same domVT in runlevel 5 without ever attempting to connect to it with
> vncviewer, qemu-dm fluctuated from 1-3% while the host was booting and then settled to 0.2% after 4-5 mins. Assuming that the boot process was complete, I launched vncviewer and qemu-dm jumped up to a 40-44% range again.
>
> Lastly I started the same host in runlevel 3 in pure text mode without any
> vga parameters on the kernel line, connected to the virtual machine with
> vncviewer, and watched the machine boot until a login prompt appeared. At
> this point, top showed qemu-dm as using 0% of the cpu. Logging into the
> virtual machine and running 'startx' however sent qemu-dm back up to a 40-
> 44% range.
>
> Why is qemu-dm consuming so much of the cpu? Why is qemu-dm still high
> even when I close my vncviewer?
>
> Tommie,
> Xen Test Team
> Unisys
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-08-29 23:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 16:16 qemu-dm cpu utilization McAfee, Tommie M
2006-08-29 23:43 ` Anthony Liguori [this message]
[not found] ` <5E735516D527134997ABD465886BBDA63A3B7C@USTR-EXCH5.na.uis.unisys.com>
2006-08-30 17:42 ` McAfee, Tommie M
2006-08-30 18:05 ` McAfee, Tommie M
[not found] ` <44F5FD81.6000809@cs.utexas.edu>
2006-08-31 17:26 ` McAfee, Tommie M
-- strict thread matches above, loose matches on Subject: below --
2006-08-27 20:51 Ian Pratt
2006-08-28 14:45 ` Puthiyaparambil, Aravindh
2006-08-28 14:57 Ian Pratt
2006-08-28 15:00 ` Puthiyaparambil, Aravindh
2006-08-28 16:13 ` McAfee, Tommie M
2006-08-28 17:30 ` George Dunlap
2006-08-28 17:58 Ian Pratt
2006-08-28 22:19 ` Puthiyaparambil, Aravindh
2006-08-28 23:08 Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F4D109.507@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.