vgpu-proxmox VS kvm-guest-drivers-windows

This is a good guide on setting up vGPU. https://gitlab.com/polloloco/vgpu-proxmox

A better way [for me, anyways] is getting GRID drivers running. However, this only works with the 9xx cards up to the 2080.

https://gitlab.com/polloloco/vgpu-proxmox

We've followed PolloLoco's guide and confirmed we had vGPU functioning on the host and could pass vGPU with an A profile to a Windows 10 VM. Profile was overridden to the following (NOTE: nvidia-49 is a Q profile):

Look into proxmox and vgpu, craft has a couple videos on it itself. If you have an ampere + (rtx 3k,rtx 4k series)card, you're out of luck. At least for the "free" version. Also, don't use his videos as step by step guides. They're outdated but good for a general "road map" of his it'll be to set up. I followed this gitlab to setup a test server with a 1660 ti. In theory you should be able to do a windows and Linux VM off the same card. I say in theory because the 5 minutes I tried to set it up it didn't work. I was in a hurry and just haven't gotten back to trying it out.

Although not quite what you want, the T1000, as a Turing-based card, is one of the ones that can support the vGPU hack: https://gitlab.com/polloloco/vgpu-proxmox

For the GPU portion, you can unlock vGPU support in proxmox for free with this script

Most AI projects are going to need a GPU to work. If you really want to get into AI I recommend moving to proxmox and use a Vgpu unlock script to split your GPUs between VMs instead of being limited to one pass through GPU per VM.

There's mature VirtIO drivers for just about everything already, under the virtio-win umbrella: https://github.com/virtio-win/kvm-guest-drivers-windows

My desktop PC is using libvirt+qemu (on an Arch host. I use Arch, btw) to PCI passthru my RTX 4090 GPU to a Windows guest. I installed the guest initially with emulated SATA for the main drive. Once Windows was up and running, I installed virtio-win and the guest is now using virtIO accelerated drivers for the network interface, main disk. I'm also sharing some filesystems using virtio-fs.

So, I started configuring the PC with ubuntu desktop (since I need a GUI for my use case). Then I setup a windows KVM with this. In my use case, I want the windows VM to be always connected to a VPN (Mullvad) that has the toggle of LAN connections turned on. This is because I want to use sunshine on the KVM to stream my desktop to a firestick. This is how I have been configuring one PC till now for my family to be able to watch TV. The issue is that I cannot use sunshine or parsec cos there are no encoders in the VM, thus the performance sucks. (I could use software encoders, but I would use too much CPU for windows VM, which would make me unable to run a LLM (this was my plan) )

Note also: it just got an experimental Windows driver!

[1]https://github.com/virtio-win/kvm-guest-drivers-windows/pull...

virtio-GPU for Windows for now is just a basic display driver, without any kind of acceleration, so there shouldn't be any difference between using it and QXL, which is fully emulated and in it, if necessary, you can increase the VRAM to be able to use high resolutions, as explained here. Note: this link is just from a quick search, I tried this for myself some time ago but my intention was not to increase the resolution but just to find out if it was possible to have some kind of 3D acceleration, as it happens in VirtualBox, but is not possible yet.

The only sorta-responsive display tech I've found is Virt with GL (3D) enabled. And if your physical box has 4k video you can forget about going anywhere near full screen with that guest VM.

I suggest you open a new issue in the repository describing this, or search if there is one open reporting the same. Also, keep in mind that as an early stage it might be a good idea to avoid copying important files using this, you could end up losing data unless you do an integrity check (recently I tried installing a game on the VM in a host directory and it didn't work. I'm thinking of an alternative or going back to using VirtualBox, since the shared folders worked very well for this purpose).

The problem was really bad with latest virtio drivers, so I downgraded to version 204, as per: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/623