Atemu to [email protected] • 14 hours agoVMware Workstation Shifting From Proprietary Code To Using Upstream KVMwww.phoronix.comexternal-linkmessage-square7fedilinkarrow-up138arrow-down10cross-posted to: [email protected]phoronix[email protected]phoronix
arrow-up138arrow-down1external-linkVMware Workstation Shifting From Proprietary Code To Using Upstream KVMwww.phoronix.comAtemu to [email protected] • 14 hours agomessage-square7fedilinkcross-posted to: [email protected]phoronix[email protected]phoronix
minus-square@[email protected]linkfedilink4•edit-29 hours 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•9 hours 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.
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.