off topic, but has anyone succesfully registered their Workstation Pro single user license with broadcom? I followed the instructions they send to my email like a month ago, but it still says on the broadcom portal that i am not eligible to download latest version despite me having a valid license. context: Broadcom has made Pro free for private users but you still need to register with them to download it.
VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
11–20 of 43 posts
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#12Having used Workstation, the graphic performance inside its GUI is really nice, it's better than anything else on the market by a far margin. It performs better than virt-manager/qemu on Linux. Could this move require VMWare/BC to release source code that could improve qemu/virt-manager? KVM is GPL if not mistaken.
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#13Having used Workstation, the graphic performance inside its GUI is really nice, it's better than anything else on the market by a far margin. It performs better than virt-manager/qemu on Linux. Could this move require VMWare/BC to release source code that could improve qemu/virt-manager? KVM is GPL if not mistaken.
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#14off topic, but has anyone succesfully registered their Workstation Pro single user license with broadcom? I followed the instructions they send to my email like a month ago, but it still says on the broadcom portal that i am not eligible to download latest version despite me having a valid license. context: Broadcom has made Pro free for private users but you still need to register with them to download it.
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#15Having used Workstation, the graphic performance inside its GUI is really nice, it's better than anything else on the market by a far margin. It performs better than virt-manager/qemu on Linux. Could this move require VMWare/BC to release source code that could improve qemu/virt-manager? KVM is GPL if not mistaken.
I believe (IANAL) the implementation of KVM is GPL because it's part of Linux, but that's not viral into user space.
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#16Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#17Having used Workstation, the graphic performance inside its GUI is really nice, it's better than anything else on the market by a far margin. It performs better than virt-manager/qemu on Linux. Could this move require VMWare/BC to release source code that could improve qemu/virt-manager? KVM is GPL if not mistaken.
Wouldn't KVM be part of the kernel interface to userspace? The emulated devices aren't really part of KVM, are they?
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#18Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#19Wouldn't that violate GPL?
Re: VMware Workstation Shifting from Proprietary Code to Using Upstream KVM
#20AIUI they already had to do something similar on Windows. Enabling certain features causes Windows to boot itself inside Hyper-V, and VMwares own hypervisor can't run nested under the Hyper-V hypervisor, so VMware gives up and runs its guests directly on Hyper-V instead.
Windows basically always runs inside a hyper-v VM these days.
If hyper-V is not enabled, then you’re running on metal.
You may notice a longer than normal reboot time when enabling or disabling Hyper-V compared to a normal reboot, and this is why; you’re moving from running on silicon to running in a privileged management VM or vice versa.