Search results

'x86-64-v3' type has AVX and works for MongoDB

Yeah, seems to work on my 1030s too, weird. It is annoying how KVM settings behave differently with every other new version.. My VM fails to boot with 0xc0000001 after installing Hyper-V no matter if I pass GPU in at all.

What is vga: .conf setting is configured to then?

This probably means Win GUI is CPU-rendered (does not use GPU-acceleration), isn't it? Not sure what you need GPU here for.

Yes, I'd be surprised if it did. Follow PVE passthrough wiki page (there are two versions both worth reading btw), fall back to Arch wiki on the subject for troubleshooting. Use my confings only as an example not the reference. Update certainly has nothing to do here.

Upgrade to v8 went smooth.

Ok, so this was Gigabyte fixing something in my case then. proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve) pve-manager: 7.4-16 (running version: 7.4-16/0f39f621) I'll find some time to upgrade PVE and see if it breaks.

Don't know where those 'news' about nvidia making anything easier at all are coming from, but it is definitely necessary to patch nowadays. In fact, it was not a thing before (pre PVE 7 I believe), so passthroug became more complicated if anything. If it was baremetal and not a VM, then it may...

No. Issue is somewhere in your dumping or patching process. I found this Win GUI wrapper ( RecreationalGarbage / NVIDIA-vBIOS-VFIO-Patcher-GUI ) to be easy and reliable for patching. And used nvflash CLI tool (Linux) version to dump vBios from PVE host, although Win version of nvflash is easier...

I do not have desktop linux install handy to test, but it might not require romfile at all. The patch we are applying is Win code 43 specific indeed, isn't it? vBios is an OEM specific firmware, so may be has to do with Gigabyte, if other 1030s were not affected.

I started to have issues with my GV-N1030D5-2GL too, although it was working with the same settings couple month back. Plugged it back today, worked ok only until selected as primary GPU ( x-vga=1 ). Meanwhile my GV-N1030D4-2GL (GDDR4 version) worked as expected with the same settings except...

GRUB_CMDLINE_LINUX_DEFAULT="quiet gfxpayload=text nomodeset" GRUB_GFXMODE=1024x768 GRUB_GFXPAYLOAD_LINUX=keep Do not forget to update-grub To list available resolutions, in Grub console use vbeinfo for BIOS and videoinfo for EFI mode.

Open chrome://flags/#touch-events Set Touch Events API to Disabled

Still no way to disable? These messages are equal to spam...

nvm, RAM issue. Was set to 1860 mhz. 1333 MHz fixed the problem, although DIMMs are capable of 2133..

proxmox-ve_3.4-102d4547-6 md5 verified. Hangs during install. Tried USB, DVD, normal & debug mode - zero reaction. System: P7P55D-E CMZ8GX3M2X2133C9R x2 i5-750 Thanks in advance