Upgraded to 5.4 and get error starting Win2008 server

bsnipes

Member
Mar 23, 2010
19
2
23
The error in the task viewer is:
kvm: kernel doesn't allow setting HyperV VP_INDEX

Any thoughts on getting it started is appreciated. The old version was 5.2 and it booted fine in it.

Edit: Looks like if I can modify the kvm cpu options to add "-hv_vpindex" it might boot. Any ideas on how to edit that?

Edit 2: Manually running the task with "hv_vpindex" removed from the cpu options does let the VM start properly.
 
Last edited:
I tried qm set to set the cpu but cannot seem to get the options set correctly. I think that might solve my issue if I can figure out the syntax.

Code:
agent: 1
balloon: 4096
bootdisk: ide0
cores: 1
ide0: tn1-vm209:209/vm-209-disk-1.raw,size=60G
ide2: none,media=cdrom
memory: 6192
name: win2008
net0: bridge=vmbr0,e1000=02:26:00:68:6B:DB
numa: 0
onboot: 1
ostype: w2k8
smbios1: uuid=4c3f153a-ac4e-494b-8b56-e902271865d6
sockets: 2
 
Same problem for me.


bootdisk: ide0
cores: 4
cpuunits: 120000
ide0: local-lvm:vm-104-disk-1,cache=writeback,size=52G
kvm: 0
memory: 3000
name: Win2008
net0: e1000=32:39:36:33:37:32,bridge=vmbr2
numa: 1
onboot: 1
ostype: win8
smbios1: uuid=0beaa789-7e83-4ecd-90ab-1aa05b024501
sockets: 1
vga: cirrus
 

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!