All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 897466] Re: UHCI Host Controller no longer present with -usb
       [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
@ 2011-11-29 18:48 ` Serge Hallyn
  2020-08-07  7:55 ` Thomas Huth
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 5+ messages in thread
From: Serge Hallyn @ 2011-11-29 18:48 UTC (permalink / raw)
  To: qemu-devel

Reproduced with today's qemu git head as well.

** Also affects: qemu
   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/897466

Title:
  UHCI Host Controller no longer present with -usb

Status in QEMU:
  New
Status in “qemu-kvm” package in Ubuntu:
  Confirmed
Status in “qemu-kvm” source package in Precise:
  Confirmed

Bug description:
  If on an up to date 12.04 install and I start a VM with:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2

  Then use the 'info usbhost' in the monitor, I get:
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
  $

  In Oneiric and eariler, 'info usbhost' would show a UHCI Host Controller. Eg:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  QEMU 0.14.1 monitor - type 'help' for more information
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
    Device 1.1, speed 12 Mb/s
      Hub: USB device 1d6b:0001, UHCI Host Controller

  This breaks QRT/scripts/test-qemu.py and appears to be a regression,
  but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15
  issue. I should mention this is happening with qemu without /dev/kvm
  available (ie, I am running test-qemu.py in an up to date precise VM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/897466/+subscriptions

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 897466] Re: UHCI Host Controller no longer present with -usb
       [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
  2011-11-29 18:48 ` [Qemu-devel] [Bug 897466] Re: UHCI Host Controller no longer present with -usb Serge Hallyn
@ 2020-08-07  7:55 ` Thomas Huth
  2020-10-07  4:17 ` Launchpad Bug Tracker
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 5+ messages in thread
From: Thomas Huth @ 2020-08-07  7:55 UTC (permalink / raw)
  To: qemu-devel

Looking through old bug tickets... is this still an issue with the
latest version of QEMU, or could we close this ticket nowadays?


** Changed in: qemu
       Status: New => Incomplete

** Changed in: qemu-kvm (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: qemu-kvm (Ubuntu Precise)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/897466

Title:
  UHCI Host Controller no longer present with -usb

Status in QEMU:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  Incomplete
Status in qemu-kvm source package in Precise:
  Incomplete

Bug description:
  If on an up to date 12.04 install and I start a VM with:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2

  Then use the 'info usbhost' in the monitor, I get:
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
  $

  In Oneiric and eariler, 'info usbhost' would show a UHCI Host Controller. Eg:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  QEMU 0.14.1 monitor - type 'help' for more information
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
    Device 1.1, speed 12 Mb/s
      Hub: USB device 1d6b:0001, UHCI Host Controller

  This breaks QRT/scripts/test-qemu.py and appears to be a regression,
  but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15
  issue. I should mention this is happening with qemu without /dev/kvm
  available (ie, I am running test-qemu.py in an up to date precise VM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/897466/+subscriptions


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 897466] Re: UHCI Host Controller no longer present with -usb
       [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
  2011-11-29 18:48 ` [Qemu-devel] [Bug 897466] Re: UHCI Host Controller no longer present with -usb Serge Hallyn
  2020-08-07  7:55 ` Thomas Huth
@ 2020-10-07  4:17 ` Launchpad Bug Tracker
  2020-10-07  4:17 ` Launchpad Bug Tracker
  2020-10-07  4:17 ` Launchpad Bug Tracker
  4 siblings, 0 replies; 5+ messages in thread
From: Launchpad Bug Tracker @ 2020-10-07  4:17 UTC (permalink / raw)
  To: qemu-devel

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]

** Changed in: qemu-kvm (Ubuntu)
       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/897466

Title:
  UHCI Host Controller no longer present with -usb

Status in QEMU:
  Expired
Status in qemu-kvm package in Ubuntu:
  Expired
Status in qemu-kvm source package in Precise:
  Expired

Bug description:
  If on an up to date 12.04 install and I start a VM with:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2

  Then use the 'info usbhost' in the monitor, I get:
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
  $

  In Oneiric and eariler, 'info usbhost' would show a UHCI Host Controller. Eg:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  QEMU 0.14.1 monitor - type 'help' for more information
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
    Device 1.1, speed 12 Mb/s
      Hub: USB device 1d6b:0001, UHCI Host Controller

  This breaks QRT/scripts/test-qemu.py and appears to be a regression,
  but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15
  issue. I should mention this is happening with qemu without /dev/kvm
  available (ie, I am running test-qemu.py in an up to date precise VM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/897466/+subscriptions


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 897466] Re: UHCI Host Controller no longer present with -usb
       [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
                   ` (2 preceding siblings ...)
  2020-10-07  4:17 ` Launchpad Bug Tracker
@ 2020-10-07  4:17 ` Launchpad Bug Tracker
  2020-10-07  4:17 ` Launchpad Bug Tracker
  4 siblings, 0 replies; 5+ messages in thread
From: Launchpad Bug Tracker @ 2020-10-07  4:17 UTC (permalink / raw)
  To: qemu-devel

[Expired for qemu-kvm (Ubuntu Precise) because there has been no
activity for 60 days.]

** Changed in: qemu-kvm (Ubuntu Precise)
       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/897466

Title:
  UHCI Host Controller no longer present with -usb

Status in QEMU:
  Expired
Status in qemu-kvm package in Ubuntu:
  Expired
Status in qemu-kvm source package in Precise:
  Expired

Bug description:
  If on an up to date 12.04 install and I start a VM with:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2

  Then use the 'info usbhost' in the monitor, I get:
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
  $

  In Oneiric and eariler, 'info usbhost' would show a UHCI Host Controller. Eg:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  QEMU 0.14.1 monitor - type 'help' for more information
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
    Device 1.1, speed 12 Mb/s
      Hub: USB device 1d6b:0001, UHCI Host Controller

  This breaks QRT/scripts/test-qemu.py and appears to be a regression,
  but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15
  issue. I should mention this is happening with qemu without /dev/kvm
  available (ie, I am running test-qemu.py in an up to date precise VM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/897466/+subscriptions


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 897466] Re: UHCI Host Controller no longer present with -usb
       [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
                   ` (3 preceding siblings ...)
  2020-10-07  4:17 ` Launchpad Bug Tracker
@ 2020-10-07  4:17 ` Launchpad Bug Tracker
  4 siblings, 0 replies; 5+ messages in thread
From: Launchpad Bug Tracker @ 2020-10-07  4:17 UTC (permalink / raw)
  To: qemu-devel

[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/897466

Title:
  UHCI Host Controller no longer present with -usb

Status in QEMU:
  Expired
Status in qemu-kvm package in Ubuntu:
  Expired
Status in qemu-kvm source package in Precise:
  Expired

Bug description:
  If on an up to date 12.04 install and I start a VM with:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2

  Then use the 'info usbhost' in the monitor, I get:
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
  $

  In Oneiric and eariler, 'info usbhost' would show a UHCI Host Controller. Eg:
  $ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
  $ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
  QEMU 0.14.1 monitor - type 'help' for more information
  (qemu) info usbhost
  husb: using sys file-system with /dev/bus/usb
    Device 1.1, speed 12 Mb/s
      Hub: USB device 1d6b:0001, UHCI Host Controller

  This breaks QRT/scripts/test-qemu.py and appears to be a regression,
  but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15
  issue. I should mention this is happening with qemu without /dev/kvm
  available (ie, I am running test-qemu.py in an up to date precise VM).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/897466/+subscriptions


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-10-07  4:51 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20111128231908.14324.64245.malonedeb@gac.canonical.com>
2011-11-29 18:48 ` [Qemu-devel] [Bug 897466] Re: UHCI Host Controller no longer present with -usb Serge Hallyn
2020-08-07  7:55 ` Thomas Huth
2020-10-07  4:17 ` Launchpad Bug Tracker
2020-10-07  4:17 ` Launchpad Bug Tracker
2020-10-07  4:17 ` Launchpad Bug Tracker

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.