Search results

It's a pretty huge development but unrelated to the issue I was having. The Nvidia update simply disables the artificial Code 43 block in the driver, which wasn't what I was experiencing at all.

The issue seems to have resolved itself, there were some updates in the meantime so I assume those fixed it. I've since changed the CPU type from Host as well so the IBPB bug seems to either have been fixed or the Max CPU model doesn't have the same issue.

My motherboard has a COM header, so I recently got the equipment I needed to hook it up and manage via serial. However, I'm unable to use serial after the system is booted. The port is at "ttyS0". I set it up in GRUB (note that my setup is serial-only until SSH comes up, the only GPU in the...

No, I use the VM as a gaming machine. Hence why it was more cost effective to build a good hypervisor which is fast enough for gaming, if it was a workstation I 100% would not have virtualized it at all (though I do use VMs pretty frequently to host different environments for different tasks...

If you could post yours for comparison that would be a good sanity check. I was on kernel 5.4.78 before the BSoD issue came up, and I know there was an update to pve-qemu-kvm as well at around the same time which could have been related to the passthrough issue, so I'm not surprised your setup...

Yes, I did. For good measure, I blacklisted all the Nvidia ones I saw in /etc/modprobe.d/blacklist.conf: blacklist nouveau blacklist nvidia blacklist nvidiafb blacklist nvidia-gpu blacklist ucsi_ccg blacklist snd_hda_intel blacklist i2c-nvidia-gpu Then "update-initramfs -u -k all" and reboot...

Recently, my working GPU passthrough configuration broke almost completely. I have a Windows 10 VM used for passthrough, with a very simple config including a single entry to pass all GPU functions through and the CPU set to "host". For almost a year, this configuration has been working fine...