From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] latest master: major slowdown (something spinning?)
Date: Wed, 10 Apr 2013 09:43:19 +0200 [thread overview]
Message-ID: <51651817.1050703@redhat.com> (raw)
In-Reply-To: <51645345.60005@linux.vnet.ibm.com>
Il 09/04/2013 19:43, Michael R. Hines ha scritto:
> *Here's the commit that causes the problem:*
>
> $ git checkout d185c094b404b4ff392b77d1244c0233da7d53bd
> qemu-char: eliminate busy waiting on can_read returning zero
Can you stil reproduce it after
commit 1e885b25275fb6763eb947b1e53b2d6911b967a8
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Mon Apr 8 15:03:15 2013 +0200
qemu-char: really fix behavior on can_read = 0
?
Paolo
> *Symptoms:*
>
> When the VM boots everything crawls and the host CPU is at 100%,
> messages are printing extremely slowly on the VM console
> and the VM is not making any boot progress......... printing kernel
> messages once a second or so.......
>
> Something in QEMU appears to be spinning.
>
> Here's my command line:
>
> qemu-system-x86_64 -enable-kvm -m 2048 -smp
> 2,sockets=1,cores=1,threads=1 -nodefconfig -rtc base=utc -no-shutdown
> disk.img -serial pty -monitor unix:/tmp/devguest,server,nowait -netdev
> type=tap,vhost=on,id=hostnet0,script=kvmifup.sh,downscript=kvmifdown.sh
> -device virtio-net-pci,netdev=hostnet0,mac=12:34:36:00:00:02 -usb
> -device usb-tablet,id=input0 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
>
> - Michael Hines
next prev parent reply other threads:[~2013-04-10 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 17:43 [Qemu-devel] latest master: major slowdown (something spinning?) Michael R. Hines
2013-04-10 7:43 ` Paolo Bonzini [this message]
2013-04-10 12:43 ` Michael R. Hines
2013-04-10 12:46 ` Paolo Bonzini
2013-04-10 13:16 ` Michael R. Hines
2013-04-13 3:19 ` Michael R. Hines
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=51651817.1050703@redhat.com \
--to=pbonzini@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--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).