[Qemu-devel] [Bug 1511887] Re: USB device 1.1 not correctly passedthru from Linux host to Windows guest
** Also affects: wine1.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1511887 Title: USB device 1.1 not correctly passedthru from Linux host to Windows guest Status in QEMU: Triaged Status in wine1.6 package in Ubuntu: New Bug description: I have USB Digital Oscilloscope which works great on pure Windows machine but not work on virtualized one. I tried passthru the device from my Debian Jessie (64bit) host machine to Windows 7 (32bit) guest machine but unfortunately it does not work very well. It looks that device is passed thru so Windows machine knows about new device and loads HID device driver for it but the device driver failed to start the device and details of an error provided by device manager is "This device cannot start" Code 10. Installed Qemu version: 2.1+dfsg-12+deb8u4 0 USB device spec: Dynon Instruments ELAB-080, USB 1.1 On linux host computer --- lsusb identify it as: Bus 003 Device 009: ID 13a3:0001 lsusb -t identify it as: /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M This is how I started my Windows guest machine -- kvm -cpu host \ -m 2048MiB \ -hda test.vdi \ -ctrl-grab \ -parallel /dev/parport0 \ -usbdevice host:13a3:0001 ...also instead of last line I tried this one: -device usb-host,vendorid=0x13a3,productid=0x0001 none of them help to properly handle my device inside guest machine. Only one time the Windows guest machine properly start the device so software for that oscilloscope can identify the Oscilloscope and measure for a while but unfortunately after I guess 5 seconds of measurement the device was disconnected from Windows and never start working again even after couple of restarts of guest machine even after plug and unplug it's USB cable and power cable. I searched for a solution or some clues to get it work but none of my searching over the internet was successful. Because device works on pure Windows but not work on virtualized one, I think there is a problem with handling not standard USB devices (like sticks, keyboards, mouses etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1511887/+subscriptions
[Qemu-devel] [Bug 1307473] Re: guest hang due to missing clock interrupt
Ondergetekende, can you provide further details to why you believe Bug #1326367 is causing this? Would you be willing to test a 3.11.0-24-generic kernel (reported stable) + the futex fix, or a chosen stable version of the 3.13 or 3.15 kernel with just the futex fix. To verify that the futex fix is the problem? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in QEMU: New Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: A clock interrupt was not received on a secondary processor within the allocated time interval. - On linux VMs I'm noticing hrtimer: interrupt took 2992229 ns messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,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 -drive file=/home/damarion/iso/virtio- win-0.1-74.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=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions
[Qemu-devel] [Bug 458521] Re: kvm crash when using virtio for network, hardy guest
I went back and retested this and it has already been fixed and released (commit fcbc05a1be0a7600153e78207dcb8b62fe753a4a), it was just not properly closed. mapl, If you are running an updated hardy guest running the 2.6.24-29 kernel this bug should not be a problem. Can you please provide information on which kernel you are using. If you are still encountering a problem with an updated kernel this is a new bug and we will need to gather more information to reproduce. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/458521 Title: kvm crash when using virtio for network, hardy guest Status in QEMU: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “qemu-kvm” package in Ubuntu: Fix Released Status in “linux” source package in Hardy: In Progress Status in “qemu-kvm” source package in Hardy: Invalid Status in “linux” source package in Karmic: Fix Released Status in “qemu-kvm” source package in Karmic: Fix Released Bug description: Binary package hint: kvm I was running a kvm host with 5 virtual machines using jaunty. 1 running centos 5.4, 3 running karmic and 1 running hardy. I upgraded the host to karmic to test it and one of my virtual machines(the vm with hardy) crashs after some seconds of boot! I stack traced the kvm process and found a virtio-net truncating packet before process crash. No error in any log file. The VM just crash. I changed the model of network interface(the disk is still virtio) in VM.xml to rtl8139, redefined and started. The problem goes away. I don't know if it's a kvm bug or libvirt(regarding the bridge network) bug but definitely is a bug. All other VMs are running OK with virtio for both network and disk. === Karmic Release Notes: KVM Guest Crashes when Guest is Hardy and using Virtio Networking Ubuntu 8.04 LTS (Hardy) KVM guests using virtio networking may crash, when running on top of Ubuntu 9.10 (Karmic) hosts. As a workaround, such guests should use either e1000 or rtl839 as the networking model. A fix for the bug is currently in progress and should be addressed in an update to the qemu-kvm package in Karmic. === === SRU Justification This bug is a regression from the kvm-84 package in 9.04. Karmic users hosting 8.04 KVM guests and using virtio networking *will* crash their VM when the network connection is saturated. As the virtual machine crashes without sync buffers, there could very well be data lost in the guest filesystem or memory. I have posted the patch for review, and acked upstream: * http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg02495.html I am bundling this fix with two other minor fixes, for Bug #452323 and Bug #453441. TEST CASE: 1) Download and uncompress * http://rookery.canonical.com/~kirkland/hardy.img.bz2 2) Download a bridged networking script * http://rookery.canonical.com/~kirkland/bridge.sh 3) Start the vm with virtio and bridged networking * sudo /usr/bin/kvm -m 512 -net nic,model=virtio -net tap,script=bridge.sh -drive file=hardy.img,if=virtio,index=0,boot=on 4) The VM's username and password are both ubuntu. 5) In the guest, have nc listen on a port * nc -lp 1234 /dev/null 6) On your host, flood the guest with network traffic on that port * cat /dev/urandom | nc -w 3 guest_ip 1234 7) Without this fix, the guest will crash immediately, saying: * virtio-net truncating packet 8) With the fix, you will be able to send the guest with data over the virtio network ad nauseum. I get about 6MB/s throughput. ===
