qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mike <qiudayu@linux.vnet.ibm.com>
To: Bug 1174654 <1174654@bugs.launchpad.net>
Cc: tobias <tobias@appelo.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host	machine resumed from suspend to ram
Date: Fri, 18 Oct 2013 10:33:39 +0800	[thread overview]
Message-ID: <52609E03.9020604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131017202953.11385.1927.malone@gac.canonical.com>

On 10/18/2013 04:29 AM, tobias wrote:
> hi,
>
> tried your option but it does not help. (cpu usage is still high)
> below my command line syntax:
> qemu-system-x86_64 -global mc146818rtc.lost_tick_policy=slew -machine accel=kvm:tcg -name win7 -S -machine pc-i440fx-1.4,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 813f5806-64ec-3319-452a-5e1834e753c9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive file=/data/vmware/win7.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -device usb-tablet,id=input0 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -vga std
Hi, have you enable the kernel CPU idle driver?  especially the guest 
kernel.

Thanks
Mike
>

  reply	other threads:[~2013-10-18  2:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 12:54 ` [Qemu-devel] [Bug 1174654] [NEW] " Serge Hallyn
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 13:52   ` Serge Hallyn
2013-04-30 13:42 ` Maxim Loparev
2013-04-30 14:20 ` Maxim Loparev
2013-04-30 14:41 ` Serge Hallyn
2013-04-30 14:50 ` Serge Hallyn
2013-05-08  9:11 ` Maxim Loparev
2013-05-08 15:25   ` Serge Hallyn
2013-05-08 19:01 ` John Basila
2013-07-31 13:34 ` Richard Jones
2013-10-12  9:06 ` tobias
2013-10-13 13:14 ` Paolo Bonzini
2013-10-17 20:29 ` tobias
2013-10-18  2:33   ` mike [this message]
2013-10-18  7:12     ` tobias appelo
2013-10-18  7:26       ` mike
2013-10-18  7:41 ` tobias
2013-10-18  8:31 ` tobias
2013-10-30 21:54 ` tobias
2014-02-04  7:15 ` Matt Keith
2015-07-20  2:59 ` derek
2015-12-18 22:10 ` varacanero
2016-10-06 21:25 ` Jürgen Veidt
2017-01-19 18:17 ` Francois Gouget
2018-12-08 18:43 ` Mark A. Hershberger
2020-11-10 17:57 ` Thomas Huth
2021-01-10  4:17 ` Launchpad Bug Tracker

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=52609E03.9020604@linux.vnet.ibm.com \
    --to=qiudayu@linux.vnet.ibm.com \
    --cc=1174654@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    --cc=tobias@appelo.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).