Proxmox 6.4-3 / Starting VM works or Doesn't...

[smorvan]

Hello all,

I recently upgraded my proxmox install and am now faced with 2 annoying issues:

1. USB id are changing across VM restart. I have a hardware USB dongle (received from a 3DMouse) that I share across several VMs manually, and I must assign ports to a VM by their ID.

2. Starting up VM from the web interface is a hit or miss. I get timeouts. I can start them just fine from the cmd line though.

Any suggestions?

Thx!

 

[oguz]

hi,

I recently upgraded my proxmox install and am now faced with 2 annoying issues:

please post pveversion -v

1. USB id are changing across VM restart. I have a hardware USB dongle (received from a 3DMouse) that I share across several VMs manually, and I must assign ports to a VM by their ID.

how do you share it across several VMs?

2. Starting up VM from the web interface is a hit or miss. I get timeouts. I can start them just fine from the cmd line though.

any error messages? can you post the configs of some of VMs? (qm config VMID)

 

[smorvan]

hi,


please post pveversion -v

Here it is:

proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-5 (running version: 6.4-5/6c7bf5de)
pve-kernel-5.4: 6.4-1
pve-kernel-helper: 6.4-1
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-2
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-1
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-3
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

how do you share it across several VMs?

I plug and unplug across different USB port when switching from one VM to another (each port is shared with a specific VM).

any error messages? can you post the configs of some of VMs? (qm config VMID)

Besides the timeout, no... Here is the output from qm config for one such VM:

agent: 1
bios: ovmf
boot: cd
bootdisk: scsi0
cores: 6
cpu: host
efidisk0: nvmeraid:vm-106-disk-0,size=1M
hostpci0: 05:00,pcie=1,rombar=0
ide2: local:iso/virtio-win-0.1.185.iso,media=cdrom,size=403872K
machine: pc-q35-5.2
memory: 24576
name: Windows10-Machine1
net0: virtio=BA:E7:3B:01:54:11,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
scsi0: nvmeraid:vm-106-disk-1,iothread=1,size=80G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=8425ff7f-61c4-4e73-9b04-6bc142c90301
sockets: 1
tablet: 0
usb0: host=2-5,usb3=1
vmgenid: c2edaed7-a444-4529-ad09-9770c2e802e2

I found out that if I issue the full multiline command required to invoke the start of the VM (not just qm start <VMID>), it takes a while and it eventually starts. I have plenty of RAM available, but I have a disk intensive VM which eats up RAM indirectly (I use a zfs filesystem for all my VMs). This is most likely linked but I have no way to back it up.

 

[oguz]

If I issue the full multiline command required to invoke the start of the VM (not just qm start <VMID>), it takes a while and it eventually starts.

* and when you use qm start it also hangs?

Besides the timeout, no...

* do you see anything in the system journal when it's hanging?

 

[smorvan]

Yep, it hangs with 'got timeout'.

* and when you use qm start it also hangs?

Yep, I eventually get a 'got timeout' error message.

* do you see anything in the system journal when it's hanging?

I must say I struggled a bit to find which system journal I was supposed to look at.

 

[oguz]

I must say I struggled a bit to find which system journal I was supposed to look at.

you can just run journalctl > journal.txt and then open it in an editor. you could then attach it here, the timeframe where the error occurs +-10 minutes should be enough for debugging any error messages.

(you can also use the GUI: Node -> System -> Syslog)