From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 36222] New: kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown
Date: Mon, 30 May 2011 08:40:25 GMT [thread overview]
Message-ID: <bug-36222-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=36222
Summary: kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown
Product: Virtualization
Version: unspecified
Kernel Version: 3.0.0-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: edwintorok@gmail.com
Regression: Yes
Created an attachment (id=60022)
--> (https://bugzilla.kernel.org/attachment.cgi?id=60022)
config-3.0.0-rc1
Host is 3.0.0-rc1, guest is 3.0.0-rc1.
After shutting down the guest, KVM on the host uses 100% CPU.
gdb shows for KVM:
6 Thread 0x7f00d1875700 (LWP 32105) 0x0000003e278ce2f7 in ioctl () at
../sysdeps/unix/syscall-template.S:82
5 Thread 0x7f00d1074700 (LWP 32106) 0x0000003e278ce2f7 in ioctl () at
../sysdeps/unix/syscall-template.S:82
4 Thread 0x7f00d0873700 (LWP 32107) 0x0000003e278ce2f7 in ioctl () at
../sysdeps/unix/syscall-template.S:82
3 Thread 0x7f00d0072700 (LWP 32108) 0x0000003e278ce2f7 in ioctl () at
../sysdeps/unix/syscall-template.S:82
2 Thread 0x7f00cf871700 (LWP 32109) 0x0000003e278ce2f7 in ioctl () at
../sysdeps/unix/syscall-template.S:82
* 1 Thread 0x7f00d1e95760 (LWP 32100) 0x0000003e278ceda3 in select () at
../sysdeps/unix/syscall-template.S:82
This seems to be a problem with the 3.0.0-rc1 guest, because if I boot 2.6.39
in the guest (still keeping same 3.0.0-rc1 running on the host), then shutdown
completes normally, no 100% CPU usage loop.
.config for KVM guest attached.
KVM command-line (created by libvirt):
/usr/bin/kvm -S -M pc-0.14 -cpu
phenom,+wdt,+skinit,+osvw,+3dnowprefetch,+misalignsse,+sse4a,+abm,+cr8legacy,+extapic,+cmp_legacy,+lahf_lm,+rdtscp,+pdpe1gb,+popcnt,+cx16,+ht,+vme
-enable-nesting -enable-kvm -m 3072 -smp 5,sockets=5,cores=1,threads=1 -name
debian-enc -uuid 55782a0a-937c-fa7b-8db5-86876d151a08 -nodefconfig -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/debian-enc.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot
order=c,menu=off -drive
file=/var/lib/libvirt/images/debian-enc.img,if=none,id=drive-virtio-disk0,boot=on,format=raw
-device
virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0
-drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev
tap,fd=18,id=hostnet0,vhost=on,vhostfd=19 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:52:de:54,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
-usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
Bisecting...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-05-30 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 8:40 bugzilla-daemon [this message]
2011-05-30 8:48 ` [Bug 36222] kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown bugzilla-daemon
2011-05-30 9:18 ` bugzilla-daemon
2011-05-30 9:20 ` bugzilla-daemon
2011-05-30 9:55 ` Avi Kivity
2011-05-30 9:26 ` bugzilla-daemon
2011-05-30 10:31 ` bugzilla-daemon
2011-05-30 10:55 ` bugzilla-daemon
2011-05-30 10:58 ` bugzilla-daemon
2011-05-30 11:01 ` bugzilla-daemon
2011-05-30 11:09 ` bugzilla-daemon
2011-05-30 11:38 ` bugzilla-daemon
2011-05-30 11:43 ` bugzilla-daemon
2011-05-30 12:26 ` bugzilla-daemon
2011-06-06 10:57 ` bugzilla-daemon
2012-06-13 15:07 ` bugzilla-daemon
2012-06-13 15:07 ` bugzilla-daemon
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=bug-36222-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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