PROXMOX 5.2-10 ERROR START ALL VM WINDOWS

Nov 8, 2018
2
0
1
55
Hello, this morning I performed my proxmox update to Rel. 5.2-10, and then I followed the wits of all my Windows and Linux Vm. When the Node proxmox is restarted, the linux machines are distributed without problems, while ALL WINDOWS VMs 7,10,2008,2012,2016 are not distributed, returning this error during startup:
"Hyper-V SynIC is not supported by kernel
kvm: kvm_init_vcpu failed: Function not implemented"

TASK ERROR: start failed: command '/usr/bin/kvm -id 113 -name Win2016Std -chardev 'socket,id=qmp,path=/var/run/qemu-server/113.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qemu-server/113-event.qmp,server,nowait' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/113.pid -daemonize -smbios 'type=1,uuid=46c4e0ac-a0ee-4415-bb96-2352804ec2c0' -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/113.vnc,x509,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,enforce' -m 4096 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:daf623c6bb82' -drive 'file=/mnt/VMachine/images/113/vm-113-disk-2.qcow2,if=none,id=drive-ide1,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1,bootindex=200' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap113i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=46:6F:13:F7:4A:4A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1
The only way to restart Windows VMs was to set up in the Os Type "Microsoft Windows Vista / 2008
or Microsoft Windows XP / 2003
Before this update, all the windows vm started correctly.

My subscription is: pve1c-....

I kindly await your response, for the resolution of this problem, as well as for my proxmox, especially for customers who I follow and assist, to which I installed Proxmox with its subscription, which have dozens of Windows Vm.

Thank you very much and best regards
PEONIA Filippo
 
please post your:

> pveversion -v

and the VM config:

> qm config 113
 
Hello, my pveversion -v

----------------------------------------------------
root@proxmox2:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.4.6-1-pve)
pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)
pve-kernel-4.4.6-1-pve: 4.4.6-48
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-3
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-29
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-38
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
----------------------------------------------
My VM 113 config
----------------------------------------------
boot: dcn
bootdisk: ide1
cores: 2
ide1: VMachine:113/vm-113-disk-2.qcow2,size=40G
ide2: none,media=cdrom
memory: 4096
name: Win2016Std
net0: e1000=46:6F:13:F7:4A:4A,bridge=vmbr0
numa: 0
ostype: w2k8
parent: PRIMA_DI_MODIFICA_RDP
scsihw: virtio-scsi-pci
smbios1: uuid=46c4e0ac-a0ee-4415-bb96-2352804ec2c0
sockets: 1
[PRIMA_DI_MODIFICA_RDP]
boot: dcn
bootdisk: ide1
cores: 2
ide1: VMachine:113/vm-113-disk-2.qcow2,size=40G
ide2: none,media=cdrom
machine: pc-i440fx-2.11
memory: 4096
name: Win2016Std
net0: e1000=46:6F:13:F7:4A:4A,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=46c4e0ac-a0ee-4415-bb96-2352804ec2c0
snaptime: 1531993023
sockets: 1
vmstate: VMachine:113/vm-113-state-PRIMA_DI_MODIFICA_RDP.raw
------------------------------------------------------------------------------------------------

Thanks for your help. Kind regards

PEONIA Filippo
 

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!