Description of problem: Starting a 32 bit Ubuntu guest Ubuntu 12.04 LTS. Version-Release number of selected component: qemu-system-x86-1.4.2-4.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name Ubuntu1204LTS_32bit -S -machine pc-0.15,accel=kvm,usb=off -cpu core2duo,+lahf_lm,+pdcm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 27c7acf9-c969-5f18-8044-536e6cf3f6aa -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Ubuntu1204LTS_32bit.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/pub/VMimages/ubuntu-12.04.2-desktop-i386.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/pub/VMimages/Ubuntu1204LTS_32bit.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 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:53:57:29,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-host,hostbus=7,hostaddr=2,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 crash_function: usb_handle_packet executable: /usr/bin/qemu-system-x86_64 kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 107 xsession_errors: Truncated backtrace: Thread no. 1 (8 frames) #4 usb_handle_packet at hw/usb/core.c:412 #5 uhci_handle_td at hw/usb/hcd-uhci.c:897 #6 uhci_process_frame at hw/usb/hcd-uhci.c:1079 #7 uhci_frame_timer at hw/usb/hcd-uhci.c:1178 #8 qemu_run_timers at qemu-timer.c:394 #10 qemu_run_all_timers at qemu-timer.c:452 #11 main_loop_wait at main-loop.c:422 #12 main_loop at vl.c:2001
Created attachment 768962 [details] File: backtrace
Created attachment 768963 [details] File: cgroup
Created attachment 768964 [details] File: core_backtrace
Created attachment 768965 [details] File: dso_list
Created attachment 768966 [details] File: environ
Created attachment 768967 [details] File: limits
Created attachment 768968 [details] File: maps
Created attachment 768969 [details] File: open_fds
Created attachment 768970 [details] File: proc_pid_status
Created attachment 768971 [details] File: var_log_messages
Hans, any thoughts?
Adding some info: The crash has to do with sharing a host USB webcam with the virtual machine. The crash occurs every time no matter, if the webcam is present at vm boot time or added later on. You need more information, let my know.
Try to start an Windows 7 guest reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name Starmony -S -machine pc-0.15,accel=kvm,usb=off -cpu SandyBridge,+osxsave,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -m 2000 -smp 1,sockets=1,cores=1,threads=1 -uuid d081559b-d51e-ffcf-a1ab-dc250386c25c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Starmony.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot order=cd,menu=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x8.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x8 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x8.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x8.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/Starmony.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/libvirt/images/ISO/virtio-win-0.1-52.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:a5:d6:c5,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5902,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-host,hostbus=2,hostaddr=8,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 crash_function: usb_handle_packet executable: /usr/bin/qemu-system-x86_64 kernel: 3.9.9-302.fc19.x86_64 package: qemu-system-x86-1.4.2-4.fc19 reason: Process /usr/bin/qemu-system-x86_64 was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 107 xsession_errors:
Started a Windws 7 KVM guest. The Windows login gui flashed on the screen; qemu crashes. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name win7 -S -machine pc-0.15,accel=kvm,usb=off -cpu Nehalem,+rdtscp,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -m 2048 -mem-prealloc -mem-path /dev/hugepages/libvirt/qemu -smp 2,sockets=2,cores=1,threads=1 -uuid 96fec046-bba4-8cbd-0db3-a2e302bedb56 -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 -boot order=c,menu=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0xa.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0xa -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0xa.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0xa.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/dev/vg_pyro/lv_kvm_win7_00,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 -drive if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e7:48:f9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5901,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -device usb-host,hostbus=8,hostaddr=2,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 crash_function: usb_handle_packet executable: /usr/bin/qemu-system-x86_64 kernel: 3.10.3-300.fc19.x86_64 package: qemu-system-x86-1.4.2-4.fc19 reason: Process /usr/bin/qemu-system-x86_64 was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 107
Removing a mapped USB device allows the VM to start up successfully.
(In reply to Cole Robinson from comment #11) > Hans, any thoughts? This is the same bug as bug 983814 (or the other way around really), this is a known issue with usb-host redirection, bug 983814 has a link to a patch: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=628e54857a82a3cb65ef96c12640c30d6307a064 Adding this patch to the Fedora packages should fix this. Cole, can you take care of this ?
*** Bug 983814 has been marked as a duplicate of this bug. ***
Thanks Hans, I'll do a build tomorrow.
Trying to cherry-pick that patch now, but hw/usb/host-libusb.c doesn't exist on 1.4.2, and there's already an equivalent USB_DEV_FLAG_IS_HOST line in hw/usb/host-linux.c. What am I missing here?
Hi, (In reply to Cole Robinson from comment #19) > Trying to cherry-pick that patch now, but hw/usb/host-libusb.c doesn't exist > on 1.4.2, and there's already an equivalent USB_DEV_FLAG_IS_HOST line in > hw/usb/host-linux.c. What am I missing here? Ah, this is 1.4.x not 1.5.x, sorry my bad. So the patch which you want / need to fix this is: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=756335292f2b46775992c314cc70b54480a46d26 Regards, Hans
qemu-1.4.2-5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/qemu-1.4.2-5.fc19
Package qemu-1.4.2-5.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing qemu-1.4.2-5.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14058/qemu-1.4.2-5.fc19 then log in and leave karma (feedback).
qemu-1.4.2-6.fc19.x86_64 fixes it for me.
qemu-1.4.2-6.fc19.x86_64 fixes the crash issue, but introduces a new side effect: The system log is spammed by billions of these messages: [12148.367895] usb 7-2: usbfs: process 2437 (qemu-system-x86) did not claim interface 0 before use after a system resume from hibernation to disk, where the VM is left running, i.e., the VM is not explicitly hibernated itself, but by the host OS.
qemu-1.4.2-6.fc19.x86_64 fixes the crash issue, but introduces a new side effect: The system log is spammed by billions of these messages: [12148.367895] usb 7-2: usbfs: process 2437 (qemu-system-x86) did not claim interface 0 before use after a system resume from hibernation to disk, where the VM is left running, i.e., the VM is not explicitly hibernated itself, but by the host OS. A work around is to remove the USB host device from the configuration and add it again.
(In reply to Andre Vehreschild from comment #24) > qemu-1.4.2-6.fc19.x86_64 fixes the crash issue, but introduces a new side > effect: Are you sure this is a new side effect, have you checked this does not happen with previous versions? > The system log is spammed by billions of these messages: > > [12148.367895] usb 7-2: usbfs: process 2437 (qemu-system-x86) did not claim > interface 0 before use This sounds like a kernel bug to me, system hibernate should be transparent to the application (in this case qemu), but it seems that the kernel forgets the claimed state of the interface over a hibernate. It is probably best to send a mail about this to linux-usb <linux-usb.org>.
I did not have this problem in versions of qemu available in fedora 17. In Fedora 19 qemu <= 1.4.2-2 was not able to handle the sharing of the usb device w/o crashing, so I can't tell, if the hibernation problem showed up there, too.
(In reply to Andre Vehreschild from comment #27) > I did not have this problem in versions of qemu available in fedora 17. In > Fedora 19 qemu <= 1.4.2-2 was not able to handle the sharing of the usb > device w/o crashing, so I can't tell, if the hibernation problem showed up > there, too. Ok, I'm pretty sure this is a kernel bug, as said before the best way to get this resolved is probably to send an email to linux-usb <linux-usb.org>.
qemu-1.4.2-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.