public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd von Egidy <lists@egidy.de>
To: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: disappointing speed with virtio_blk
Date: Sat, 19 Apr 2008 00:32:41 +0200	[thread overview]
Message-ID: <200804190032.41458.lists@egidy.de> (raw)
In-Reply-To: <20080418214910.GA24619@dmt>

Hi Marcelo,

thanks for the quick reply.

> When the hang happens, can you run kvm-stat --once (script can be found
> kvm-66 directory) and paste the result?

efer_reload                    0         0
exits                    4943909      2036
fpu_reload                222178         0
halt_exits                896464       999
halt_wakeup                17690         0
host_state_reload        2279013      1027
insn_emulation           2640886      1001
insn_emulation_fail            0         0
invlpg                         0         0
io_exits                  396350        28
irq_exits                 200020         1
irq_window                     0         0
mmio_exits                900583         0
mmu_cache_miss             54441         0
mmu_flooded                63313         0
mmu_pde_zapped             46114         0
mmu_pte_updated           554813         0
mmu_pte_write             639377         0
mmu_recycled                   0         0
mmu_shadow_zapped          63313         0
pf_fixed                 1205697         0
pf_guest                   92134         0
remote_tlb_flush               1         0
request_irq                    0         0
signal_exits                   1         0
tlb_flush                 609240         5

> Can you confirm that reverting the patch fixes it?

It seems to be some kind of race condition, it doesn't completely hang the 
system always at the same position but probably brings the io to a halt at 
some time.

I just got it to boot, but when running bonnie++ it halted at some time. The 
kvm_stat output above is from that one. I was still able to type in stuff
at the console but the console couldn't break the system call bonnie was in.

Booting a qemu-kvm without the patch completely fixes these problems.

Kind regards,

Gerd

-- 
Address (better: trap) for people I really don't want to get mail from:
james@cactusamerica.com

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-04-18 22:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 21:04 disappointing speed with virtio_blk Gerd von Egidy
2008-04-13 21:22 ` Charles Duffy
2008-04-13 21:55   ` Gerd von Egidy
2008-04-14  0:29 ` Marcelo Tosatti
2008-04-16 23:05   ` Gerd von Egidy
2008-04-16 23:40     ` Marcelo Tosatti
2008-04-18 21:27       ` Gerd von Egidy
2008-04-18 21:49         ` Marcelo Tosatti
2008-04-18 22:32           ` Gerd von Egidy [this message]
2008-04-14  1:41 ` Anthony Liguori

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=200804190032.41458.lists@egidy.de \
    --to=lists@egidy.de \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox