hostusb not working after upgrading to 1.9

A

Abrin

New Member
Oct 13, 2011
6
0
1
Hello all,

I've only been using Proxmox for a few months now and I love it, does everything I need it to until today. Yesterday I decided to check up on my Proxmox server and noticed the 1.9 upgrade so I used aptitude to apply it, since then I can't get a single one of my VMs to recognize any USB device I try to connect to it. I use qm set to set the USB and verify it in the .conf file but upon boot, nothing. The server can see the device when I lsusb but nothing in the VM itself. Wouldn't be a problem but I've got a couple development VMs that use smart cards for authentication so currently any work with them has stopped.

Any help would be appreciated, thanks!
 
Abrin said:
Wouldn't be a problem but I've got a couple development VMs that use smart cards for authentication so currently any work with them has stopped.
Click to expand...

Well, I guess that is impossible to debug here, because we do not have such 'smart cards'.
 
These are the readers we use, they're pretty basic to be honest. I've tried this and a dell keyboard with a smart card reader built in, both with no luck.

http://www.iogear.com/product/GSR201/

I'll grab a thumb drive and see if I can get that to read, that will at least narrow it down if it's something specific with smart card readers
 
Ok, tried it with a plain old Memorex thumb drive and the VM still isn't seeing it though the Proxmox server does.
 
Hello!
I have another problem with USB after Proxmox upgrade to 1.9 and reboot.
KVM with guest Debian Squeeze stopped after access to USB device from inside guest.

In /etc/qemu-server/103.conf line "hostusb: 12d1:*" for GSM modem Huawei E1550 (switched to modem mode).
Guest show device by lsusb
Bus 001 Device 004: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 003: ID 0000:0000
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Click to expand...
and say in syslog
Oct 14 00:08:36 debian kernel: [ 3.766179] Initializing USB Mass Storage driver...
Oct 14 00:08:36 debian kernel: [ 3.766297] usbcore: registered new interface driver usb-storage
Oct 14 00:08:36 debian kernel: [ 3.766300] USB Mass Storage support registered.
Oct 14 00:08:36 debian kernel: [ 3.777700] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input5
Oct 14 00:08:36 debian kernel: [ 3.971994] usbcore: registered new interface driver usbserial
Oct 14 00:08:36 debian kernel: [ 3.972117] USB Serial support registered for generic
Oct 14 00:08:36 debian kernel: [ 3.972226] usbcore: registered new interface driver usbserial_generic
Oct 14 00:08:36 debian kernel: [ 3.972228] usbserial: USB Serial Driver core
Oct 14 00:08:36 debian kernel: [ 3.984192] USB Serial support registered for GSM modem (1-port)
Oct 14 00:08:36 debian kernel: [ 3.984781] option 1-2.1:1.0: GSM modem (1-port) converter detected
Oct 14 00:08:36 debian kernel: [ 3.985109] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB0
Oct 14 00:08:36 debian kernel: [ 3.985242] option 1-2.1:1.1: GSM modem (1-port) converter detected
Oct 14 00:08:36 debian kernel: [ 3.985344] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB1
Oct 14 00:08:36 debian kernel: [ 3.985357] option 1-2.1:1.2: GSM modem (1-port) converter detected
Oct 14 00:08:36 debian kernel: [ 3.985777] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB2
Oct 14 00:08:36 debian kernel: [ 3.985908] usbcore: registered new interface driver option
Oct 14 00:08:36 debian kernel: [ 3.985910] option: v0.7.2:USB Driver for GSM modems
Click to expand...

But after access to /dev/ttyUSB2 by minicom or simply cat /dev/ttyUSB2 guest going to Stop state without any messageg and no records in logs. All other VM (without access to USB) work fine.

How can i enable debug for get more info about problem? Have any ideas?
 
Just did a check in Qemu monitor and found this:

Device 0.1, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
Device 0.2, Port 2, Speed 12 Mb/s, Product QEMU USB Hub
Device 0.3, Port 2.1, Speed 12 Mb/s, Product SCRx31 USB Smart Card Reader
Click to expand...

The VM in question is Server 2008 but I've tried it on a Vista VM and had the same results. I admit that I'm not much of a Linux guy so I don't want what else to show to help solve this. Everything appears that it should be working but no matter what I try, the VM just doesn't see it.
 
Last edited:
Abrin said:
I admit that I'm not much of a Linux guy so I don't want what else to show to help solve this.
Click to expand...

You can either start hacking on the qemu sources, or try to find a workaround - maybe downgrade pve-qemu-kvm to the previous version.
 
crash vm not start at all (crash before VNC access)
With 0.15 the VM crash when Windows trying access too USB

-----------------

dpkg -i pve-qemu-kvm_0.15.0-2_amd64.deb
pveversion -v
pve-qemu-kvm: 0.15.0-2

-----------------
On /etc/qemu-server/ file
comment #hostusb:
Start VM ... Working

-----------------
EDIT : dpkg -i pve-qemu-kvm_0.14.0-3_amd64.deb
VM working without problem ...

----------------
Look at this
http://www.kraxel.org/cgit/qemu/refs/heads

branch stable.... and branch usb.xx ... qemu team have problem with usb ? :)
 
Last edited:
Yes, it looks as problem...
After comment assert() on lines 315, 336 and 346 have "Segmentation fault" :(
 
Hi,
I also have been using a hostusb option (to pass through a usb hardware license key required for an office server).
I also had this same problem after upgrading to 1.9 with pve-qemu-kvm: 0.15.0-2
The VM completely failed to start with the error:

kvm: /home/dietmar/svn-devel/pve-qemu-kvm/qemu-kvm/hw/usb.c:333: usb_packet_complete: Assertion `p->owner != ((void *)0)' failed.
Aborted


After downgrading to pve-qemu-kvm_0.14.1-1_amd64.deb
The VM booted fine as before.

Any eta to getting a fix for this in the PVE release schedule?
 
joeschmoe said:
Hi,
I also have been using a hostusb option (to pass through a usb hardware license key required for an office server).
I also had this same problem after upgrading to 1.9 with pve-qemu-kvm: 0.15.0-2
The VM completely failed to start with the error:

kvm: /home/dietmar/svn-devel/pve-qemu-kvm/qemu-kvm/hw/usb.c:333: usb_packet_complete: Assertion `p->owner != ((void *)0)' failed.
Aborted


After downgrading to pve-qemu-kvm_0.14.1-1_amd64.deb
The VM booted fine as before.

Any eta to getting a fix for this in the PVE release schedule?
Click to expand...

Thanks for the hint: it seems to be ok also for me (identical situation).

Have anybody tried this fix?
http://repo.or.cz/w/qemu.git/commitdiff/80cf7cf74f29a219e02b50f27c12b1c792ebf99b
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom