Describe the bug
If I will pass USB serial port (zigbee gateway - ch340 serial) VM will not boot most of times anymore.
But if I will login there by using SSH and run qm monitor it will boot up almost everytime.
To Reproduce
Steps to reproduce the behavior:
- Add USB Device
- Turn on VM from web Console noVNC
- See error like it trying to connecting and it wont start up
Expected behavior
Start up VM with USB Serial connected
Screenshots
ENV (please complete the following information):
- Radxa Rocky 5 ITX+ 24GB
- OS: Debian 13
- ARCH: aarch64
- Versions
# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.1.115-vendor-rk35xx)
pve-manager: 9.0.10-2 (running version: 9.0.10-2/74d1bcc54a6e6730)
proxmox-kernel-helper: 9.0.4
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown: residual config
ifupdown2: 3.3.0-1+pmx10
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.6
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.6-2
proxmox-backup-file-restore: 4.0.6-2
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.6
pve-edk2-firmware: 4.2025.02-3
pve-firewall: 6.0.3
pve-firmware: not correctly installed
pve-ha-manager: 5.0.3
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4+port1
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.22
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.10.1
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
Additional context
As wrote above, if I will turn qm monitor in console, it will boot up and device is visible... But I can not turning on VM by running qm monitor in logged user-space.
I do not know where to check some more logs.
Only vncproxy timeout (but VM not running) or QEMU exited with code 1 (but what the hell is this error code, would be nice to have some better output than Microsoft style "there was error")
If something more will help, I can provide more
Describe the bug
If I will pass USB serial port (zigbee gateway - ch340 serial) VM will not boot most of times anymore.
But if I will login there by using SSH and run qm monitor it will boot up almost everytime.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Start up VM with USB Serial connected
Screenshots
ENV (please complete the following information):
Additional context
As wrote above, if I will turn qm monitor in console, it will boot up and device is visible... But I can not turning on VM by running qm monitor in logged user-space.
I do not know where to check some more logs.
Only vncproxy timeout (but VM not running) or QEMU exited with code 1 (but what the hell is this error code, would be nice to have some better output than Microsoft style "there was error")
If something more will help, I can provide more