Node vm is down and unable to start

[scorpoin]

I'm was trying to backup one of my Node vm . I shut it down to start back and now it is not getting start.

()
kvm: kernel doesn't allow setting HyperV VP_INDEX
TASK ERROR: start failed: QEMU exited with code 1

I've restarted service but yet no use. Any idea what went wrong with it.

Regards

 

[Hannes Laimer]

Hey,

could you post the output of cat /etc/pve/qemu-sever/<vmid>.conf and pveversion -v. Has that happened before? Did you change anything in the config since the last successful restart?

 

[scorpoin]

Hey,

could you post the output of cat /etc/pve/qemu-sever/<vmid>.conf and pveversion -v. Has that happened before? Did you change anything in the config since the last successful restart?

pveversion -v

proxmox-ve: 6.4-1 (running kernel: 4.10.17-1-pve)
pve-manager: 6.4-14 (running version: 6.4-14/15e2bf61)
pve-kernel-5.4: 6.4-15
pve-kernel-helper: 6.4-15
pve-kernel-5.4.174-2-pve: 5.4.174-2
pve-kernel-4.10.17-1-pve: 4.10.17-16
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
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.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-2
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-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.7-pve1

cat /etc/pve/qemu-server/103.conf

bootdisk: ide0
cores: 2
ide0: local:103/vm-103-disk-1.qcow2,size=399G
ide2: none,media=cdrom
memory: 6144
name: wn_NODE252
net0: e1000=02:00:00:97:c8:85,bridge=vmbr0
net1: e1000=22:A8:54:5D:75:C5,bridge=vmbr1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=4f8fe4fe-ef89-4740-a443-3726210d8ff8
sockets: 1

 

[Hannes Laimer]

The kernel you are currently running is super old(4.10 from ~2017), is there any reason you are using such an old kernel? This could definatly cause the problem.

 

[scorpoin]

it does have pve-kernel-5.4.174-2-pve: 5.4.174-2 as well they why it is not using it? How do I resolve this issue.

Regards

 

[scorpoin]

it does have pve-kernel-5.4.174-2-pve: 5.4.174-2 as well they why it is not using it? How do I resolve this issue.

Regards

My other vm on node working fine although there is windows and linux both. But having issue with only one windows vm .Afet upgrade of promox from 5.x to 6.x all vmz were started. I started a new backup for this vm but I stopped it in middle of backup and shut down the vm. After that vm is not more booting up / starting.