Atemu@lemmy.ml to Linux@lemmy.ml · 2 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@lemmy.ml to Linux@lemmy.ml · 2 months agomessage-square8fedilinkcross-posted to: [email protected]
minus-squaremoonpiedumplings@programming.devlinkfedilinkarrow-up4·edit-22 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 Amoeba@lemmy.calinkfedilinkarrow-up3·2 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.
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.