Windows VM Software Update on Proxmox 7

[nekton]

Hi!

Yes, I know I should be on version 9 of Proxmox but the upgrade of my cluster and backup server has me a bit intimidated. I plan to do it, but I am trying get a Windows 11 Pro VM working before I do that.

When I run the Windows Updates in the VM it just complains that my device is missing important security updates with a big red check mark!

My VM has 4 cores with a type of qemu64 (I have tried "host" as well and that doesn't work).
Secure Boot is enabled.
Machine is 35
TPM State is version 2.0
BIOS is OVMF(UEFI)

I am a bit of noob. I tried searching the forums for related issues but didn't find anything with the search tool.
Does anyone have quick fix, link or a cookbook page for running the latest version of Windows11 Pro with software updates working?

TIA

 

[SteveITS]

Pretty sure that CPU is unsupported in Windows. Try x86-64-v2-AES or v3. Host should also work unless it’s really old but there are issues with the nested virtualization/security and idle cpu usage if you search the forum.

 

[nekton]

Pretty sure that CPU is unsupported in Windows. Try x86-64-v2-AES or v3. Host should also work unless it’s really old but there are issues with the nested virtualization/security and idle cpu usage if you search the forum.

Hey SteveITS. Thanks for getting back to me. I don't see that CPU listed. I will try Host and report back.

 

[nekton]

Switching to "host" as the CPU did not solve the problem unfortunately. As noted, the x86-64-v2-AES host is not available in the list of CPUs. I wonder if that was ever available in Proxmox 7 or I need to bite the bullet and upgrade my Proxmox which is unfortunately production.

 

[Johannes S]

Is the actual hardware (so the real CPU) even supported by Windows11? CPU type host doesn't do much expect directly passing your host CPU to the guest os, so if your guest host doesn't support your CPU in the first place I wouldn't be surprised from any problems related to this.
An update won't help you then although you should update nontheless since running EOL software is an security desaster waiting to happen, see: https://forum.proxmox.com/threads/p...ble-to-some-type-of-0day-rce-non-auth.186078/ and https://forum.proxmox.com/threads/p...-type-of-0day-rce-non-auth.186078/post-869156 )

 

[nekton]

Is the actual hardware (so the real CPU) even supported by Windows11? CPU type host doesn't do much expect directly passing your host CPU to the guest os, so if your guest host doesn't support your CPU in the first place I wouldn't be surprised from any problems related to this.
An update won't help you then although you should update nontheless since running EOL software is an security desaster waiting to happen, see: https://forum.proxmox.com/threads/p...ble-to-some-type-of-0day-rce-non-auth.186078/ and https://forum.proxmox.com/threads/p...-type-of-0day-rce-non-auth.186078/post-869156 )

Yes. It is a security disaster waiting to happen. CPU "host" runs Windows 11 Pro on Proxmox 7, it is just the updates that don't work. I figured if it could boot Windows 11 and run software (including updating the antivirus definitions for Windows Security, it could install the other software updates as well. I am playing with fire but trying to figure out how/when to do the upgrade.

Appreciate the links!

 

[nekton]

I am going to consider this issue "solved" since running the x86-64-v2-AES CPU seems to be the solution. I will start another thread after I read through the update wiki docs if I have questions. Thanks for those who chimed in. One thing I see is it is a step-wise upgrade 7.1->7.4->8.4->9.x.

 

[leesteken]

One thing I see is it is a step-wise upgrade 7.1->7.4->8.4->9.x.

You could start a new cluster with the latest 9.2 on one node and restore VMs from backups. Start with one node (which your cluster should easily be able to miss) and test your most important VMs on it. Then extend it with more nodes and more VMs gradually. This saves you a lot of hoops to jump through since you are multiple versions behind.