Windows & 6.x upgrade

synthetic

New Member
Sep 22, 2019
6
0
1
45
Hello,

So after I upgraded, everything is starting up fine except for my windows instances,

Hyper-V IPI send support (requested by 'hv-ipi' cpu flag) is not supported by kernel
kvm: kvm_init_vcpu failed: Function not implemented
TASK ERROR: start failed: command '/usr/bin/kvm -id 104 -name windows -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/104.pid -daemonize -smbios 'type=1,uuid=b561b107-592a-4c62-b1ef-55e620998359' -smp '8,sockets=2,cores=4,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/104.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,enforce' -m 8192 -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'vmgenid,guid=f24be535-45a5-4670-b4ab-635bac4793b5' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:f858aa3e7487' -drive 'file=/dev/pve/vm-104-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=9E:C9:3B:9D:0A:22,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

I have done a bit of research to see if I can just re-compile the kernel to support hv-ipi support but there is a lack of documentation on how to do this. Any thought's would be helpful. Thank you.
 
did you upgrade your kernel but did not reboot?

what is the output of 'pveversion -v'?
 
I upgraded and then rebooted.

root@mox:/# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.15.18-20-pve)
pve-manager: 6.0-7 (running version: 6.0-7/28984024)
pve-kernel-4.15: 5.4-8
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.11-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-8
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2
root@mox:/#

 
So I just noticed that I did not have the right version of kernel installed and I fixed it.

To answer for those that wouldn't know how to, what I did was 'apt search pve-kernel' which gave me the result of:

pve-firmware/stable,now 3.0-2 all [installed]
Binary firmware code for the pve-kernel

pve-kernel-5.0/stable 6.0-8 all
Latest Proxmox VE Kernel Image

pve-kernel-5.0.12-1-pve/stable 5.0.12-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.15-1-pve/stable 5.0.15-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.18-1-pve/stable 5.0.18-3 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.21-1-pve/stable 5.0.21-2 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.21-2-pve/stable,now 5.0.21-3 amd64 [installed]
The Proxmox PVE Kernel Image

pve-kernel-5.0.8-1-pve/stable 5.0.8-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.8-2-pve/stable 5.0.8-2 amd64
The Proxmox PVE Kernel Image

pve-kernel-helper/stable 6.0-8 all
Function for various kernel maintenance tasks.

So then I just pruged the other kernels by doing 'apt purge pve-kernel-4*' and what ever the kernel version was. Then I installed the newest most stable one which is pve-kernel-5.0.21-2-pve and then rebooted, everything works now.

Thank you for pointing it out. Some time's it just takes a second pair of eyes.
 
So I just noticed that I did not have the right version of kernel installed and I fixed it.

To answer for those that wouldn't know how to, what I did was 'apt search pve-kernel' which gave me the result of:

pve-firmware/stable,now 3.0-2 all [installed]
Binary firmware code for the pve-kernel

pve-kernel-5.0/stable 6.0-8 all
Latest Proxmox VE Kernel Image

pve-kernel-5.0.12-1-pve/stable 5.0.12-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.15-1-pve/stable 5.0.15-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.18-1-pve/stable 5.0.18-3 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.21-1-pve/stable 5.0.21-2 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.21-2-pve/stable,now 5.0.21-3 amd64 [installed]
The Proxmox PVE Kernel Image

pve-kernel-5.0.8-1-pve/stable 5.0.8-1 amd64
The Proxmox PVE Kernel Image

pve-kernel-5.0.8-2-pve/stable 5.0.8-2 amd64
The Proxmox PVE Kernel Image

pve-kernel-helper/stable 6.0-8 all
Function for various kernel maintenance tasks.

So then I just pruged the other kernels by doing 'apt purge pve-kernel-4*' and what ever the kernel version was. Then I installed the newest most stable one which is pve-kernel-5.0.21-2-pve and then rebooted, everything works now.

Thank you for pointing it out. Some time's it just takes a second pair of eyes.

Not to necro, but this saved me a lot of time when sorting the issue after an upgrade. Thank you!
 
Hi there!
I have gotten a similar error:
Code:
Hyper-V paravirtualized IPI (hv-ipi) is not supported by kernel kvm: kvm_init_vcpu failed: Function not implemented TASK ERROR: start failed: QEMU exited with code 1

So, after a little bit googling I have implemented this one solution:

Datacenter -> Node -> VM 10* -> Options -> OS Type : Linux and Version: 5.x - 2.6 Kernel
Screenshot_2.png

and launch my VM again without future warnings and error

I'll be happy if it helps :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!