Search results

  1. J

    Upgraded to 5.4-13 and Windows VMs wont boot

    Oh yea sorry, i did get this resolved. I had everything fully updated but for some reason the server didnt change kernels to the newest proxmox kernel. I had to get KVM access to the server to check which kernel it was booting into to find out it was using an old one and had to switch it.
  2. J

    kvm: kernel doesn't allow setting HyperV VP_INDEX

    I just updated today to 5.4-13 I wasnt on a very old version before that. it was probably within the last year or so. and Yes ive rebooted proxmox after updating as other services that were updated required a reboot to fully apply
  3. J

    kvm: kernel doesn't allow setting HyperV VP_INDEX

    I tried Raj's fix and it lets me boot my windows VM's but after like a minute or two the vms just freeze entirely, even on a setup iso (so its not the os itself) VM worked perfectly before updating but now i cant boot them at all. and using the disabled KVM virtualization its so unbelievably...
  4. J

    Upgraded to 5.4-13 and Windows VMs wont boot

    Im fairly new to proxmox and before i had updated to the latest version from apt-get, all my vms were working fine, but after the update all windows vms will not boot. The error that shows is this kvm: kernel doesn't allow setting HyperV VP_INDEX TASK ERROR: start failed: command '/usr/bin/kvm...

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!