[left-struck]

Oh man, unfortunately all the things I need windows for doesn’t work well in a VM:

Solidworks, needs special license to work in a VM that my company is not willing to pay for

DAWs, need real time access to low level audio stuff

Games, well, lets just say the experience is better with wine on linux

With the exception of work, at some point I decided that not only is windows dead to me, but any application that can only run on windows is also dead to me.

[PeterStuer]

At least on Proxmox the Solidworks and DAW latency problems are solvable.

[rewgs]

Do tell! Specifically the DAW latency problems. I love the idea of running a DAW in a VM on Proxmox.

[PeterStuer]

Assuming a decent host with virtualization support enabled and low latency network. Where you can allocate sufficient resources so the VM will not be starved:

Create the VM with the native cpu intruction model, not the portable version, give sufficient memory (no ballooning), harware passthrough an entire PCIe USB hub (not the simple USB passthrough) for controllers and soundcards (I think this needs the device to support ACS for VFIO). In your Windows VM, make sure you install the virtio-win drivers. Also enable the qemu guest agent.

People report better audio latency accessing the VM through NoMachine or Parsec rather than Remote Desktop.