Bug 963966
Summary: | [abrt] WARNING: at include/linux/kref.h:42 handle_tx+0x5f5/0x630 [vhost_net]() | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||||
Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 19 | CC: | amit.shah, berrange, cfergeau, crobinso, dwmw2, gansalmon, itamar, jasowang, jonathan, kernel-maint, madhu.chinakonda, mrunge, mst, pbonzini, rjones, scottt.tw, virt-maint | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:f3f8c0f70bdfc866423b64737863ad7ff219af8f | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-05-25 19:03:38 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Chris Murphy
2013-05-16 22:06:42 UTC
Created attachment 749080 [details]
File: dmesg
This is triggered by a qemu-kvm session in Virtual Machine Manager. So far it seems issuing a reboot or poweroff command while ssh'd into the VM triggers this. Created attachment 749131 [details]
dmesg 3.10.0-0.rc1.git5.1.fc20.x86_64
Same problem occurs with kernel 3.10.0-0.rc1.git5.1.fc20.x86_64.
I can consistently reproduce by starting a qemu-kvm session with Virtual Machine Manager, ssh'ing into the VM, and issuing a reboot command.
Host system:
3.10.0-0.rc1.git5.1.fc20.x86_64
libvirt-1.0.5-3.fc19.x86_64
virt-manager-0.10.0-0.4.gitb68faac8.fc19.noarch
VM system uses kernel 3.9.0-301.fc19.x86_64
Host system: qemu-kvm-1.4.1-2.fc19.x86_64 libvirt-daemon-driver-qemu-1.0.5-3.fc19.x86_64 qemu-guest-agent-1.4.1-2.fc19.x86_64 qemu-common-1.4.1-2.fc19.x86_64 ipxe-roms-qemu-20130103-1.git717279a.fc19.noarch qemu-system-x86-1.4.1-2.fc19.x86_64 qemu-img-1.4.1-2.fc19.x86_64 Created attachment 749132 [details]
dmesg 3.10.0-0.rc1.git5.1.fc20.x86_64 part 2
previous 3.10-0 dmesg ends at [ 961.566821] This continues on with more info, same boot.
This is probably a duplicate of 954181 Regression testing: The above description and comments through #6 is F19 beta TC on qemu-kvm on F19 with all current updates on baremetal. If I replace F19 with F18 fully updated on baremetal, but keep the F19 qemu, I cannot reproduce the problem with kernel 3.9.2-200.fc18.x86_64. So I wonder if there's something new in F19 qemu-kvm or libvirt on F19 that's triggering some latent bug in the kernel that wasn't previously being poked with F18 versions of qemu-kvm and libvirt. F18 host: virt-manager-0.9.5-1.fc18.noarch qemu-img-1.2.2-11.fc18.x86_64 qemu-kvm-1.2.2-11.fc18.x86_64 ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-daemon-driver-qemu-0.10.2.4-1.fc18.x86_64 qemu-common-1.2.2-11.fc18.x86_64 qemu-system-x86-1.2.2-11.fc18.x86_64 *** This bug has been marked as a duplicate of bug 954181 *** |