C
cirroz
Guest
[Solved] VM crashed when usb_add executed
I recently upgraded PVE and updated windows kvm guest drivers (SCSI, NIC and Balloon) to version 0.1.22
Now I found out my VM with usb dongles doesn't start if I add the line hostusb: host:xxxx:yyyy to VM's config.
When I remove this line the VM starts well. But it crashes when I'm trying to add usb device manually from qm-console: usb_add host:xxxx:yyyy.
The command with specified bus.port - usb_add host:1.10 - doesn't work too.
I tested Windows XP SP3 and Windows 2008R2 x64 with recent updates.
No one works.
What may it be?
# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
P.S.
I checked VM with old 0.1.15 guest drivers. It crashes now too.
Looks like it depends with last PVE update
Help, please.
I recently upgraded PVE and updated windows kvm guest drivers (SCSI, NIC and Balloon) to version 0.1.22
Now I found out my VM with usb dongles doesn't start if I add the line hostusb: host:xxxx:yyyy to VM's config.
When I remove this line the VM starts well. But it crashes when I'm trying to add usb device manually from qm-console: usb_add host:xxxx:yyyy.
The command with specified bus.port - usb_add host:1.10 - doesn't work too.
I tested Windows XP SP3 and Windows 2008R2 x64 with recent updates.
No one works.
What may it be?
# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
P.S.
I checked VM with old 0.1.15 guest drivers. It crashes now too.
Looks like it depends with last PVE update
Help, please.
Last edited by a moderator: