[SOLVED] USB printer not seen by VM

[r4dh4l]

Hi,

following https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines I wanted to add an USB printer to a VM running CUPS.

So in Proxmox I did:

root@proxmox:~# lsusb | grep Epson
Bus 002 Device 003: ID 04b8:08a8 Seiko Epson Corp.
root@proxmox:~# qm set 109 -usb0 host=04b8:08a8
update VM 109: -usb0 host=04b8:08a8
root@proxmox:~# qm monitor 109
Entering Qemu Monitor for VM 109 - type 'help' for help
qm> info usbhost
  Bus 2, Addr 3, Port 4, Speed 480 Mb/s
    Class 00: USB device 04b8:08a8, EPSON L355 Series
qm>

After restarting the CUPS VM I can not see the attached printer:

root@vm-cups:~# lsusb | grep Epson
root@vm-cups:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@vm-cups:~#

What did I forget?

 

[lhorace]

Hello there,

Did you power recycle the VM after the USB device was added? What does dmesg say while it's booting with the USB device plugged in?

Cheers

 

[r4dh4l]

Thx or your reply!

Did you power recycle the VM after the USB device was added?

Sure, but just tried again:

1. Switched on printer.
2. Reattached printer to Proxmox-Hypervisor.
3. Rebootet CUPS-VM.
4. Printer is still not listed under CUPS -> Administration -> Find New Printers.

Did you power recycle the VM after the USB device was added? What does dmesg say while it's booting with the USB device plugged in?

root@vm-cups:~# dmesg | grep usb
[    1.705504] usbcore: registered new interface driver usbfs
[    1.705518] usbcore: registered new interface driver hub
[    1.712049] usbcore: registered new device driver usb
[    1.995811] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[    1.995813] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.995815] usb usb1: Product: UHCI Host Controller
[    1.995816] usb usb1: Manufacturer: Linux 4.9.0-9-amd64 uhci_hcd
[    1.995818] usb usb1: SerialNumber: 0000:00:01.2
[    2.121334] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    2.121337] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.121339] usb usb2: Product: UHCI Host Controller
[    2.121340] usb usb2: Manufacturer: Linux 4.9.0-9-amd64 uhci_hcd
[    2.121342] usb usb2: SerialNumber: 0000:00:1d.0
[    2.188436] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.188439] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.188459] usb usb3: Product: EHCI Host Controller
[    2.188461] usb usb3: Manufacturer: Linux 4.9.0-9-amd64 ehci_hcd
[    2.188462] usb usb3: SerialNumber: 0000:00:1d.7
[    2.324145] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[    2.411591] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    2.411594] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.411596] usb usb4: Product: UHCI Host Controller
[    2.411597] usb usb4: Manufacturer: Linux 4.9.0-9-amd64 uhci_hcd
[    2.411599] usb usb4: SerialNumber: 0000:00:1d.1
[    2.473672] usb 1-1: not running at top speed; connect to a high speed hub
[    2.501067] usb 1-1: New USB device found, idVendor=0627, idProduct=0001
[    2.501070] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5
[    2.501072] usb 1-1: Product: QEMU USB Tablet
[    2.501074] usb 1-1: Manufacturer: QEMU
[    2.501075] usb 1-1: SerialNumber: 42
[    2.516521] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    2.516523] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.516525] usb usb5: Product: UHCI Host Controller
[    2.516527] usb usb5: Manufacturer: Linux 4.9.0-9-amd64 uhci_hcd
[    2.516529] usb usb5: SerialNumber: 0000:00:1d.2
[    2.538184] usbcore: registered new interface driver usbhid
[    2.538186] usbhid: USB HID core driver
[    2.540526] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
[    2.540937] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
root@vm-cups:~#

 

[lhorace]

3. Rebootet CUPS-VM.

Not reboot, certain settings don't get applied while the QEMU process is running, which means complete shutdown.

qm stop <vmid>
qm start <vmid>

ps aux | grep qemu #On the hypervisor to see if the right flags are sent to QEMU

 

[r4dh4l]

Not reboot, certain settings don't get applied while the QEMU process is running, which means complete shutdown.

qm stop <vmid>
qm start <vmid>

ps aux | grep qemu #On the hypervisor to see if the right flags are sent to QEMU

Thank you so much - rebooting instead of stop/start was the problem. Printer is recognized by the VM now!

 

[danielniroo]

Hey,
I also faced the same USB printer problem. Then I updated the driver but another Canon Printer Error 5200 message shown on my system screen.I tried many processes but could not be solved.Need to solution about that printer problem