Yes, we can confirm it's broken again inNow, there is some talk in these threads about 8.1 not working again.
pve-qemu-kvm >= 8.1.2-1
.This is indeed the culprit. Since that commit was only fixing a cosmetic issue,I haven't tested this, but if I had to take a wild guess, I'd guess that this commit breaks it again
x86: acpi: workaround Windows not handling name references in Package properly - https://github.com/qemu/qemu/commit/44d975ef340e2f21f236f9520c53e1b30d2213a4
pve-qemu-kvm >= 8.1.2-2
will include a revert to avoid the breakage until there is a proper fix.The issues disappear when using the q35 hardware model. Everything is working fine now.
So I tried to test this. First, I stopped the machine > changed the machine type (OS Type in the hardware settings) from q35 to the default i440fix. That didn't seem to help. I also tried creating a new machine with the correct settings, and that fixed it!!!The issues disappear when using the q35 hardware model. Everything is working fine now.
did you install the latest version of the virtio-win guest drivers https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers ? Those are required for VirtIO devices.Don't know if it still affects someone here, i got the same issue with proxmox v8 after freshly installing windows server, i switched the adapter model from virtlo paravirtualized to intel E1000 and you got it! hope this tip helps someone
why would you recommend that when the issue persists since multiple years?Hi,
did you install the latest version of the virtio-win guest drivers https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers ? Those are required for VirtIO devices.
I just stated that installing VirtIO drivers is required to use a VirtIO network device with Windows. The issue does not persist, see below. If you do still have an issue with VirtIO drivers installed and using current versions, it most likely is not the same issue. Please open a separate thread and provide all the necessary details.why would you recommend that when the issue persists since multiple years?
As already mentioned earlier in the thread,There's some hope that applying KB5046615 could work, see the end of the upstream thread on the issue and, optionally, follow the link from there.
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/750#issuecomment-2929374694
pve-qemu-kvm >= 8.1.2-2
included a revert to fix that issue, so it hasn't affected Proxmox VE since 1.5 years ago. And the proper fix mentioned there is included since pve-qemu-kvm >= 9.2.0-1
(and there, the revert could be dropped).We use essential cookies to make this site work, and optional cookies to enhance your experience.