Can not start vm after upgrade from 5.4 to 6.2

E

eaedv

New Member
Sep 18, 2020
4
0
1
47
I just updated proxmox from 5.4 to 6.2 (and therefore debian from stretch to buster). The update process runs smooth but after the update, I am not able to start a virtual machine again, I get:

kvm: --redir: invalid option
TASK ERROR: start failed: QEMU exited with code 1

I tried to clone the machine, but even the cloned machine throws this error.

Does anyone has an idea how to solve this?
 
Try starting the VM from CLI.
Check logs in /var/log and see what is going on.
Share the config file of the affected VM. Maybe we can spot something in there.
 
Do you use any specific scripts when starting your VM?
Could you also post the output of pveversion -v?
Qemu depreciated the '"-redir" parameter and use "-netdev" or "-nic" in current version [1], but I guess '-redir' is still being used somewhere upon starting the VM.

1. https://wiki.qemu.org/Features/RemovedFeatures
 
Thanks for the hint, I just get exactly the same error starting the machine.
However, looking in the machine config was a good idea (thanks for that!), the redir command is deprecated in new qemu version.
Old config:
args: --redir tcp:11122::22
Chaned to:
-nic user,hostfwd=tcp::11122-:22
seems to work.

My conf:
args: --nic user,hostfwd=tcp::11122-:22
balloon: 1024
bootdisk: scsi0
cores: 4
memory: 24048
name: websrv
net0: virtio=56:CF:B0:B6:B4:11,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local:101/vm-101-disk-1.qcow2,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=e8f8c273-764b-4504-9420-afe6f4da20b5
sockets: 1

pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-1
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-2
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1


Now I stuck with:
kvm: -device VGA,id=vga,bus=pci.0,addr=0x2: PCI: slot 2 function 0 not available for VGA, in use by e1000
start failed: QEMU exited with code 1
 
Last edited:
Looks like the new qemu version forces the network card to be on slot 2.
Removing the network card and creating a new one does not help. It is not possible to remove the vga card.

How can I configure proxmox to put the network card on another slot?
 
Ok, I solved it. I created a new machine with similar settings and used the hard disk of the original vm.
 
You must log in or register to reply here.
Top Bottom