Unable to add USB device

C

charon

Renowned Member
Nov 30, 2008
120
1
83
Hi,

i recently ran into problems with serial devices and now i got an issue with a usb device.
I normally do not use proxmox for hardware passthroughs, but i don't know how i can change the setup now easily.

#lsusb

Code: 
Bus 003 Device 003: ID 03eb:2018 Atmel Corp. at90usbkey sample firmware (CDC ACM

#qm set 101 --hostusb 03eb:2018

shutdown the vm
start vm

no usb passthrough and usb device is still in #lsusb
 
it also does not work with 1.4Beta

Code: 
qm> info usbhost
  Device 3.2, speed 1.5 Mb/s
    Class 00: USB device 051d:0002, Smart-UPS 750 FW:651.18.I USB FW:7.4
  Device 3.3, speed 12 Mb/s
    Communication: USB device 03eb:2018

qm> usb_add host:03eb:2018

qm> info usb
  Device 0.1, Speed 12 Mb/s, Product QEMU USB Tablet

how can i get more output?
 
Last edited:
charon said:
it also does not work with 1.4Beta

Code: 
qm> info usbhost
  Device 3.2, speed 1.5 Mb/s
    Class 00: USB device 051d:0002, Smart-UPS 750 FW:651.18.I USB FW:7.4
  Device 3.3, speed 12 Mb/s
    Communication: USB device 03eb:2018
Click to expand...

So device "03eb:2018" is already here.
 
but not in the kvm box. i want to add it into a windows XP vm.

but i can't add it with the hostusb option in the config file or with the monitor.
 
Last edited:
Hi, I wanted to ask a question relating to this topic: I've got ProxVE fresh installed (version 1.3, not the newest 1.4b2). I'm unclear - based on this thread, should I expect "usb passthrough" to *FAIL* on ProxVE 1.3 but to work on version 1.4b2 ?

I've got a license-USB-key-dongle attached to the physical ProxVE host
I've used "lsusb" to capture the device ID code
I've used appropriate qm command so that the VM.conf file under /etc/qemu-server dir contains a stanza as desired, reading "hostusb:XXXX:XXXX" for the correct device ID
I've done a stop and start on my WinXP KVM based VM
but inside the Windows VM I don't see the device still ..

Must I move to ProxVE 1.4(b2) in order to get this working ? Is there an upgrade path from 1.3 or do I need to backup VMs to another host, then clean install 1.4b2, and then bring VMs over .. ?

Thanks for any help / feedback,


Tim
 
fortechitsolutions said:
Must I move to ProxVE 1.4(b2) in order to get this working ?
Click to expand...

some users reports better results with 1.4b2

fortechitsolutions said:
Is there an upgrade path from 1.3 or do I need to backup VMs to another host, then clean install 1.4b2, and then bring VMs over .. ?
Click to expand...

Replace the 'pve' repositoty with 'pvetest' in /etc/apt/sources.list (to upgrade to v1.4b2)
 
i can confirm that, but i also have to say that several USB devices also work with the stable version
 
Thanks for the feedback (2 posts above) -- I appreciate the help. I'll try to upgrade to 1.4b2 in this manner and will post back the outcome of this test.


Tim
 
Hi,

I've updated the system to 1.4b2 but I'm still having issues. I wanted to check to see if I'm observing properly,

- usb device is attached to system and seen via lspci
- windows vhost is started fresh after inserting USB device
- then in 'kvm monitor' for the host I issue command to see if the usb device is visible.


Inside windows, I run a freeware app, "USBDeview" to see if I can see anything. No joy.

Is there some way to diagnose this further .. where things are falling down ?

Thanks,

Tim

Stuff is captured below for reference.

CONFIG FOR KVM BASED VHOST ON THE PROX_VE SYSTEM:

gwpve:/var/log# cd /etc/qemu-server/

gwpve:/etc/qemu-server# more 102.conf

name: gwpvm2.fqdn.goes.here
ide2: none,media=cdrom
smp: 1
vlan0: rtl8139=72:E9:31:BB:43:38
bootdisk: ide0
ide0: vm-102-disk.qcow2
ostype: wxp
memory: 512
onboot: 1
description: WinXP VHost
hostusb: 064f:03e9

gwpve:/etc/qemu-server#

OUTPUT FROM LSUSB ON PHYSICAL PROXVE HOST:


gwpve:/etc/qemu-server# lsusb
Bus 002 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 002: ID 064f:03e9 WIBU-Systems AG
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
gwpve:/etc/qemu-server#


In the Web-interface for VHost 102, the "KVM Monitor" shows me output as captured below when I pass it the "info usbhost" command:

qm> info usbhost
Device 5.2, speed 12 Mb/s
Class 00: USB device 064f:03e9, CodeMeter-Stick
qm>



Is there something I'm missing ? I found google hits that suggested maybe I should try "usb_hadd host:064f:03e9" in the qm> console but this didn't appear to have any impact.


Any thoughts / comments are certainly appreciated,


Tim
 
Last edited:
Problems with USB external hard drive

I think I am experiencing some issue with an external hard drive connected via USB, somewhat relevant to this post.

I connected an external USB hard drive to the back of the server. The hard drive has its own power connector (so it is not powered by the server).

The purpose is to mount it to a directory to use for vzdump backups.

Everytime I reboot the server the usb drive is not seen by the serve and is unavailable.

I have to manually turn off and on the usb hard drive in order for the server to then view it and mount it as /dev/sdb.

Any idea if this is a bug in Proxmox 1.4 b2?
 
Hi,

My last test on PVE 1.4 beta2 and KVM Win XP Pro :

Logitech usb headset, ID 046d:0a0b Logitech, Inc. works ok (but very bad sound)

USB DVD RW, ID 05e3:0701 Genesys Logic, Inc. USB 2.0 IDE Adapter ok

Regards,
Tesquenure
 
Re: Problems with USB external hard drive

dietmar said:
Any hint in kernel logs (dmesg)?
Click to expand...

Here are some extract from the kernel logs starting from where I found the word error till the end:


Code: 
Time: 18:04:59  Date: 10/06/09
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S4 S5)
ACPI: Using IOAPIC for interrupt routing
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
Error attaching device data
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE9._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 11 12 *14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 *11 12 14 15)
ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] -  80, should be 7D [20070126]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NET: Registered protocol family 8
NET: Registered protocol family 20

For the remaining lines after this piece see attached.
 

Attachments

  • kernel_logs.txt
    18.6 KB · Views: 3
Re: Problems with USB external hard drive

hisaltesse said:
Here are some extract from the kernel logs starting from where I found the word error till the end:
Click to expand...

No idea whats wrong. Maybe you can contact the vendor of that drive - or search the vendor forum if this is a known issue with linux 2.6.24?
 
Hi Tesquenure,

Thanks for your help with this. Much appreciated.

Please note - for testing I've added another USB device concurrently with the "CodeMeter" device. The 2 devices attached are

(a) CodeMeter USB device
(b) kingston data traveler usb 'memory stick / thumb drive'


In windows, I can see the USB Kingston removable media perfectly. I still can't see any sign of the CodeMeter device.


this is what I see in the Qemu Monitor for my Windows XP VM:

qm> info usb

Device 0.4, speed 480 Mb/s, Product DataTraveler 2.0
Device 0.3, speed 12 Mb/s, Product QEMU USB Hub
Device 0.2, speed 12Mb/s, Product QEMU USB Tablet

qm> info usbhost

Device 5.2, speed 12 Mb/s
Class 00: USBB Device 064f:03e9, Codemeter-Stick
Device 2.3, speed 480 Mb/s
Class 00: USB device 0951:1603, DataTraveler 2.0


Please let me know if there is other info I can provide.

Thanks!


Tim
 
Hi Tim,

Try with bus and device address

Exemple :

Code: 
lsusb
Bus 002 Device 001: ID 0000:0000  
Bus 007 Device 001: ID 0000:0000  
Bus 006 Device 001: ID 0000:0000  
Bus 005 Device 001: ID 0000:0000  
Bus 001 Device 002: ID 05e3:0701 Genesys Logic, Inc. USB 2.0 IDE Adapter
Bus 001 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 00[COLOR=RoyalBlue]3[/COLOR] Device 00[COLOR=RoyalBlue]2[/COLOR]: ID 046d:0a0b Logitech, Inc. 
Bus 003 Device 001: ID 0000:0000
then
Code: 
qm set 102 -hostusb [COLOR=RoyalBlue]3[/COLOR].[COLOR=RoyalBlue]2[/COLOR]
Then
Stop/start your VM

Then

Code: 
info usb
Regards,
Tesquenure
 
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
Back