Atemu to [email protected] • 8 months agoVMware Workstation Shifting From Proprietary Code To Using Upstream KVMwww.phoronix.comexternal-linkmessage-square8fedilinkarrow-up167arrow-down10cross-posted to: [email protected]
arrow-up167arrow-down1external-linkVMware Workstation Shifting From Proprietary Code To Using Upstream KVMwww.phoronix.comAtemu to [email protected] • 8 months agomessage-square8fedilinkcross-posted to: [email protected]
minus-squareAvid Amoebalinkfedilink8•8 months agoIf we get VirtIO 3D acceleration in Windows guests from this, I’d be really happy.
minus-square@[email protected]linkfedilink4•edit-28 months agoI found this: https://github.com/tenclass/mvisor-win-vgpu-driver But it is for another foss kvm based hypervisor called mvisor.
minus-squareAvid Amoebalinkfedilink3•8 months agoThere’s a WIP VirtIO driver in a PR but it’s not done yet. VMware’s own VMSVGA is open source if I remember correctly. I wonder if they’ll adapt it to KVM and if they do, whether that’ll be usable in KVM without VMware.
If we get VirtIO 3D acceleration in Windows guests from this, I’d be really happy.
I found this: https://github.com/tenclass/mvisor-win-vgpu-driver
But it is for another foss kvm based hypervisor called mvisor.
There’s a WIP VirtIO driver in a PR but it’s not done yet. VMware’s own VMSVGA is open source if I remember correctly. I wonder if they’ll adapt it to KVM and if they do, whether that’ll be usable in KVM without VMware.