Search results

Maybe the issue is connected to HotPlug memory activated as @fireon suggested at https://forum.proxmox.com/threads/kb5012170-fails-to-install-on-win11-host.113561/page-2#post-502450 Disabling hotplug memory on Windows VM solved my similar issue.

As @thiagotgc asked, for Windows guest VMs is it sufficient to set balloon=0 on the host ? This way on the VMs I don't see anymore the Virtio Ballon Driver in Device Manager, but the Balloon Service is still running. Do I need to stop/disable the Balloon Service or furthermore uninstall it...

Disabled Memory Hotplug and I was able to change the UEFI disk, enabling enrolled keys- everything worked like a sharm. Thank you very much @fireon !

I'm really sorry and beg your and forum pardon, I should have been blind for a while (or erroneously have been looking to other VM). Sure: that VM has hotplug memory !!!! Sorry again, and thank you!

Here it is: ## Windows Server 2019 Standard Ita #__________________ agent: 1 audio0: device=ich9-intel-hda,driver=spice balloon: 8192 bios: ovmf boot: c bootdisk: scsi1 cores: 8 efidisk0: local-zfs:vm-110-disk-0,size=128K hotplug: disk,network,usb,memory,cpu machine: q35 memory: 12288 name...

Thank you @fireon, but there was no memory hotplug. Hotplug was activated just for Network, Disk and USB. I got the same issue on many servers, and no solution at the moment.

Since PVE 7.2-11 the procedure doesn't work anymore: if I substitute the EFI disk, Windows VM do not boot anymore, with "Guest has not initialized the display (yet)" on console. Old UEFI disk does not permit to install Windows updates. Does anybody know a solution?

Resolved the issue here on a Windows Server 2019: install of KB5012170 failed at 99%. Then I solved the problem this way: Poweroff Windows server 2019 VM Detach EFI disk Add a new one EFI DISK with "Pre-Enrolled Keys" Boot VM Start Windows Update Install pending update The update installed...

Nodes of my previous posts where the problem happened frequently: Model name: Intel(R) Xeon(R) Silver 4214 CPU @ 2.20GHz Work around applied on 2022.09.29 20:30. ~# uname -a Linux pve02 5.15.35-3-pve #1 SMP PVE 5.15.35-6 (Fri, 17 Jun 2022 13:42:35 +0200) x86_64 GNU/Linux...

As you suggested, I've tried the workaround: vi /etc/kernel/cmdline root=ZFS=rpool/ROOT/pve-1 boot=zfs kvm.tdp_mmu=N proxmox-boot-tool refresh reboot cat /sys/module/kvm/parameters/tdp_mmu N The installation completed at the first attempt with no issues!!!

Thank you! Have I to do this on all thee nodes, or may I just test the node where the affected VM runs?

Here too vm 121 unable to complete Windows Server 2022 (Std with desktop environment) installation, starting from 2 different DVD images containing the M$ evaluation release. On about 9 of 10 attempts the VM crashes before asking the Administrator Password. No matter if: I use virtio network...

Me to: please, enable to specify the per-node storage where the replica should be done