Recent content by need2gcm

Perhaps the error is specific to iscsi connections. Reviewing logs of another Windows 2022 VM with VirtIO on 285 but no iscsi, multi-gig traffic does not seem to experience any errors.

Do the servers without the errors use iscsi connections? If so, do they experience multi-gigabit load?

Ran into the same issue running Windows Server 2022 on a Veeam proxy between our SAN and the backup repository with VirtIO virtual hardware used everywhere possible. Backups were failing and iscsi/disk errors were filling the System log. Tried various reconfigurations of the VM with no impact to...

Also ensure the spinners are CMR and not SMR (shingled). Those will give you serious performance hits, especially when running with non-synthetic reads and writes.

I've never had that be an issue with my Windows VMs. Backed up, restored, migrated. If you changed machine type and CPU type, and/or more virtual hardware parameters though you may be risking a re-activation. That should still be resolvable with a manual activation as well.

As an update: Updated to the 5.15.39-1 kernel this morning and disabled the hookscript. Upon reboot the VM started without issue, and I verified passthrough was behaving as expected. So it looks like at some point a kernel update resolved the issue causing the framebuffer to improperly reserve...

This is a now known issue, been kicking around for a little bit: https://forum.proxmox.com/threads/windows-vms-stuck-on-boot-after-proxmox-upgrade-to-7-0.100744/

No BOOTFB in /proc/iomem. And I did run the update-initramfs -u and proxmox-boot-tool refresh. As stated, it worked fine before the 5.15 branch. I am still on 5.15.35-6, so maybe I need to update again and try removing the hookscript and see what happens.

I sure did not install any drivers on the Proxmox host. Only changes I've made to the install are the steps to enable pcie passthrough. I will verify again next time I can reboot the host, but for what its worth all of this was set up and working before the 5.15 kernel. I only had to start...

Ah, I did end up doing that. Went through my configs and found them as expected. However, with lscpi -nnk are we only concerned with the kernel driver in use, or also the kernel modules? Because as of now I do have the nouveau and nvidia drivers blacklsited and the kernel driver in use is vfio-pci.

I don't believe so. I just followed this guide: https://pve.proxmox.com/wiki/PCI(e)_Passthrough

Host OS GPU (console, post, etc.): ASPEED Graphics Controller (rev41) Passthrough GPU: NVIDIA GeForce GP106 (GTX1060 6GB)

I do have a boot GPU specified in BIOS, but this issue affected my system anyways. I have the hookscript setup working well for me, but I have been keeping an eye out for a more "persistent" change. Not sure I want to kill my access to boot logging though.

And there's no way to disable per GPU?

Are there any downsides to disabling the simple framebuffer?