Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".
** Changed in: qemu (Ubuntu Hardy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/156085
Title:
Could not open /proc/bus/usb/devices
Status in QEMU:
Fix Released
Status in Virtualbox:
Fix Released
Status in “apcupsd” package in Ubuntu:
Invalid
Status in “fxload” package in Ubuntu:
Fix Released
Status in “kvm” package in Ubuntu:
Fix Released
Status in “madfuload” package in Ubuntu:
Fix Released
Status in “midisport-firmware” package in Ubuntu:
Fix Released
Status in “qemu” package in Ubuntu:
Fix Released
Status in “sysvinit” package in Ubuntu:
Won't Fix
Status in “usbview” package in Ubuntu:
Triaged
Status in “vmware-server” package in Ubuntu:
Invalid
Status in “apcupsd” source package in Gutsy:
Invalid
Status in “fxload” source package in Gutsy:
Won't Fix
Status in “kvm” source package in Gutsy:
Won't Fix
Status in “madfuload” source package in Gutsy:
Won't Fix
Status in “midisport-firmware” source package in Gutsy:
Won't Fix
Status in “qemu” source package in Gutsy:
Won't Fix
Status in “sysvinit” source package in Gutsy:
Invalid
Status in “usbview” source package in Gutsy:
Won't Fix
Status in “vmware-server” source package in Gutsy:
Won't Fix
Status in “apcupsd” source package in Hardy:
Invalid
Status in “fxload” source package in Hardy:
Won't Fix
Status in “kvm” source package in Hardy:
Won't Fix
Status in “madfuload” source package in Hardy:
Won't Fix
Status in “midisport-firmware” source package in Hardy:
Won't Fix
Status in “qemu” source package in Hardy:
Won't Fix
Status in “sysvinit” source package in Hardy:
Won't Fix
Status in “usbview” source package in Hardy:
Won't Fix
Status in “vmware-server” source package in Hardy:
Won't Fix
Status in “apcupsd” source package in Jaunty:
Invalid
Status in “fxload” source package in Jaunty:
Fix Released
Status in “kvm” source package in Jaunty:
Fix Released
Status in “madfuload” source package in Jaunty:
Fix Released
Status in “midisport-firmware” source package in Jaunty:
Fix Released
Status in “qemu” source package in Jaunty:
Fix Released
Status in “sysvinit” source package in Jaunty:
Won't Fix
Status in “usbview” source package in Jaunty:
Won't Fix
Status in “vmware-server” source package in Jaunty:
Invalid
Status in “usbview” package in Debian:
Fix Released
Status in “qemu” package in openSUSE:
Fix Released
Bug description:
On Gutsy 64-bit using qemu/kvm (also VirtualBox and, I believe,
VMWare) and the "-usb" switch no USB devices are available since
qemu/kvm looks for the description of them in the 'devices' file of a
usbfs mount at
/proc/bus/usb/
but the code previously providing the usbfs mount that is created at
start-up via /etc/rcS/S11mountdevsubfs.sh -->
/etc/init.d/mountdevsubfs.sh was commented out. The USB devices are
now reported at
/dev/bus/usb/
but currently there is no usbfs file-system mounted/linked there to
provide the 'devices' text-file.
qemu/kvm reports:
qemuctl -qemu vdeq kvm -boot c -m 512 -hda /home/all/VirtualMachines
/WindowsXP-SP2.ovl -net nic,vlan=0 -soundhw es1370 -usb -net vde
info usbhost
Could not open /proc/bus/usb/devices
$ ls -l /proc/bus/usb
total 0
WORKAROUND:
To re-enable it edit the file '/etc/init.d/mountdevsubfs.sh' and uncomment
the code after line 40 so it reads:
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs
-obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb
Execute the script manually to enable the change before a system reboot:
$ sudo /etc/init.d/mountdevsubfs.sh start
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/156085/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
