From: Ulrich Schreiner <ulrich.schreiner-sZDnKEZIvs8b1SvskN2V4Q@public.gmane.org>
To: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avik-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: kvm very slow
Date: Tue, 07 Aug 2007 14:25:12 +0200 [thread overview]
Message-ID: <1186489512.3370.30.camel@vaio> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160D17A197-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
well there are running some "default F7 daemons".
yum-updatesd (python)
setroubleshootd (python)
hald
...
but no process is really running, when doing a "htop" i the processor
has a load of 0.7%
what is the "efer_reload"?
while i'm writing this email i have kvm_stat in another shell in the
background and this value always is between 5000 and 7000
btw: i patched kvm_stat to make the screen refresh faster/slower, so
that i can mark the output with the mouse and copy it (to my posts :-).
is there a need for this?
</usc>
Am Dienstag, den 07.08.2007, 04:51 -0700 schrieb Dor Laor:
> >today morning i compiled kvm-33 and the output of kvm-stat is much
> >better now (guest in idle):
> >
> >kvm statistics
> >
> > efer_reload 10944273 6504
> > exits 13722688 6967
> > halt_exits 1084344 935
> > invlpg 0 0
> > io_exits 7668914 5070
> > irq_exits 27886 2
> > irq_window 11477 1
> > light_exits 2778416 462
> > mmio_exits 2153709 498
> > pf_fixed 1085923 0
> > pf_guest 459144 0
> > request_irq 0 0
> > signal_exit 25818 0
> > tlb_flush 228295 5
>
>
> It's much better. What does the guest do? It's weird it reloads the
> efer.
>
> >
> >
> >i don't know if these numbers are ok; do you still need the generated
> >qemu.log for ioport access? if you need it i will upload it to my
> public
> >server.
> >
> >but: the system is slow. it is extremely slow when booting and the
> >guest-system clock ist twice as slow as the host-system clock (both are
> >idle; ok, the host as a runnung qemu-instance :-).
> >
> >when starting i get:
> >
> >Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a
> >fatal
> >error, but for better emulation accuracy either use a 2.6 host Linux
> >kernel or
> >type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
> >
> >well i HAVE a 2.6kernel (2.6.22.1-41.fc7), but i cannot set
> >dev.rtc.max-user-freq, i only can set the high precision event timer
> >
> >dev.hpet.max-user-freq = 1024
> >
> >which i have done. but the message always appears. i don't know if this
> >is ignorable.
> >
>
> The problem is that qemu calculates time using either sigalarm or rtc.
> (the later in more accurate)
> Seems like qemu doesn't get enough signals to inject timer irq to the
> guest.
>
> Luca claims the HPET intefer the RTC. Can it be disabled? ( I know some
> new chipsets implement rtc using HPET).
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-07 12:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 5:22 kvm very slow Ulrich Schreiner
2007-08-01 16:41 ` Avi Kivity
[not found] ` <46B0B7D0.9080203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-01 19:45 ` Ulrich Schreiner
[not found] ` <46B0E2F0.1070701-sZDnKEZIvs8b1SvskN2V4Q@public.gmane.org>
2007-08-02 8:24 ` Avi Kivity
[not found] ` <46B194C5.5040508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-02 19:31 ` Ulrich Schreiner
2007-08-07 7:20 ` Ulrich Schreiner
2007-08-07 7:44 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D17A0EA-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-07 9:43 ` Ulrich Schreiner
2007-08-07 11:32 ` Luca
2007-08-07 11:51 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D17A197-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-07 12:08 ` Luca
[not found] ` <68676e00708070508w3d9e5ab8gd26263c44bf59f0d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-07 12:30 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D17A1C2-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-07 12:50 ` Ulrich Schreiner
2007-08-07 14:38 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01E45A1D-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-08-07 14:50 ` Dor Laor
2007-08-07 20:49 ` Luca Tettamanti
[not found] ` <20070807204922.GA27976-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2007-08-08 6:28 ` Ulrich Schreiner
2007-08-07 12:25 ` Ulrich Schreiner [this message]
2007-08-09 23:23 ` Matthew Kent
2007-08-10 0:09 ` Matthew Kent
2007-08-10 5:32 ` Ulrich Schreiner
2007-08-10 6:39 ` Ulrich Schreiner
2007-08-16 9:56 ` Avi Kivity
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=1186489512.3370.30.camel@vaio \
--to=ulrich.schreiner-szdnkezivs8b1svskn2v4q@public.gmane.org \
--cc=avik-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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.