[Bug 1851547] Re: qemu 4 crashes with this parameter attached -usb -device usb-host, hostbus=1, hostaddr=7 \

2021-06-21 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1851547 Title: qemu 4

[Bug 1851547] Re: qemu 4 crashes with this parameter attached -usb -device usb-host, hostbus=1, hostaddr=7 \

2021-04-22 Thread Thomas Huth
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the

[Bug 1851547] Re: qemu 4 crashes with this parameter attached -usb -device usb-host, hostbus=1, hostaddr=7 \

2019-11-07 Thread Marietto
001:008 Compx 2.4G Receiver. Problem arise because I've detached one of my USB disk and the numbering of the USB devices attached changed. specially the compx 2.4g receiver changed from hostaddr 7 to 8 and when this happens qemu 4 seems to work not as good as qemu 3. -- You received this bug

[Bug 1851547] Re: qemu 4 crashes with this parameter attached -usb -device usb-host, hostbus=1, hostaddr=7 \

2019-11-07 Thread Dr. David Alan Gilbert
Hi Marietto, Can you attach an lsusb output from your host? I'm curious what host bug 1, addr 7 and 8 are. Dave -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1851547 Title: qemu 4 crashes with

[Bug 1851547] Re: qemu 4 crashes with this parameter attached -usb -device usb-host, hostbus=1, hostaddr=7 \

2019-11-06 Thread Marietto
problem resolved changing this line : -usb -device usb-host,hostbus=1,hostaddr=7 \ with this : -usb -device usb-host,hostbus=1,hostaddr=8 \ it works with qemu 4. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.