kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: win7 bad i/o performance, high insn_emulation and exists
Date: Mon, 20 Feb 2012 19:17:55 +0100	[thread overview]
Message-ID: <4F428E53.2010602@dlh.net> (raw)

Hi,

I came a across an issue with a Windows 7 (32-bit) as well as with a 
Windows 2008 R2 (64-bit) guest.

If I transfer a file from the VM via CIFS or FTP to a remote machine,
i get very poor read performance (around 13MB/s). The VM peaks at 100%
cpu and I see a lot of insn_emulations and all kinds of exists in kvm_stat

efer_reload                    0         0
exits                    2260976     79620
fpu_reload                  6197        11
halt_exits                114734      5011
halt_wakeup               111195      4876
host_state_reload        1499659     60962
hypercalls                     0         0
insn_emulation           1577325     58488
insn_emulation_fail            0         0
invlpg                         0         0
io_exits                  943949     40249
irq_exits                 108679      5434
irq_injections            236545     10788
irq_window                  7606       246
largepages                   672         5
mmio_exits                460020     16082
mmu_cache_miss               119         0
mmu_flooded                    0         0
mmu_pde_zapped                 0         0
mmu_pte_updated                0         0
mmu_pte_write              13474         9
mmu_recycled                   0         0
mmu_shadow_zapped            141         0
mmu_unsync                     0         0
nmi_injections                 0         0
nmi_window                     0         0
pf_fixed                   22803        35
pf_guest                       0         0
remote_tlb_flush             239         2
request_irq                    0         0
signal_exits                   0         0
tlb_flush                  20933         0

If I run the same VM with a Ubuntu 10.04.4 guest I get around 60MB/s 
throughput. The kvm_stats look a lot more sane.

efer_reload                    0         0
exits                    6132004     17931
fpu_reload                 19863         3
halt_exits                264961      3083
halt_wakeup               236468      2959
host_state_reload        1104468      3104
hypercalls                     0         0
insn_emulation           1417443      7518
insn_emulation_fail            0         0
invlpg                         0         0
io_exits                  869380      2795
irq_exits                 253501      2362
irq_injections            616967      6804
irq_window                201186      2161
largepages                  1019         0
mmio_exits                205268         0
mmu_cache_miss               192         0
mmu_flooded                    0         0
mmu_pde_zapped                 0         0
mmu_pte_updated                0         0
mmu_pte_write            7440546         0
mmu_recycled                   0         0
mmu_shadow_zapped            259         0
mmu_unsync                     0         0
nmi_injections                 0         0
nmi_window                     0         0
pf_fixed                   38529        30
pf_guest                       0         0
remote_tlb_flush             761         1
request_irq                    0         0
signal_exits                   0         0
tlb_flush                      0         0

I use virtio-net (with vhost-net) and virtio-blk. I tried disabling hpet 
(which basically illiminated the mmio_exits, but does not increase
performance) and also commit (39a7a362e16bb27e98738d63f24d1ab5811e26a8
) - no improvement.

My commandline:
/usr/bin/qemu-kvm-1.0 -netdev 
type=tap,id=guest8,script=no,downscript=no,ifname=tap0,vhost=on -device 
virtio-net-pci,netdev=guest8,mac=52:54:00:ff:00:d3 -drive 
format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-eeef4e007-a8a9f3818674f2fc-lieven-windows7-vc-r80788,if=virtio,cache=none,aio=native 
-m 2048 -smp 2 -monitor tcp:0:4001,server,nowait -vnc :1 -name 
lieven-win7-vc -boot order=dc,menu=off -k de -pidfile 
/var/run/qemu/vm-187.pid -mem-path /hugepages -mem-prealloc -cpu host 
-rtc base=localtime -vga std -usb -usbdevice tablet -no-hpet

What further information is needed to debug this further?

Thanks,
Peter

             reply	other threads:[~2012-02-20 18:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 18:17 Peter Lieven [this message]
2012-02-20 18:40 ` win7 bad i/o performance, high insn_emulation and exists Gleb Natapov
2012-02-20 19:04   ` Gleb Natapov
2012-02-20 19:24     ` Peter Lieven
2012-02-20 19:59     ` Peter Lieven
2012-02-20 20:45       ` Gleb Natapov
2012-02-21 10:50         ` Peter Lieven
2012-02-21 10:56           ` Gleb Natapov
2012-02-21 10:59             ` Peter Lieven
2012-02-21 11:00               ` Gleb Natapov
2012-02-21 11:16                 ` Peter Lieven
2012-02-21 11:46                   ` Gleb Natapov
2012-02-21 12:05                     ` Peter Lieven
2012-02-21 13:56                       ` Vadim Rozenfeld
2012-02-21 14:10                         ` Peter Lieven
2012-02-21 16:48                           ` Vadim Rozenfeld
2012-02-21 18:21                             ` Peter Lieven
2012-02-20 19:15   ` Peter Lieven
2012-02-20 20:42     ` Gleb Natapov

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=4F428E53.2010602@dlh.net \
    --to=pl@dlh.net \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).