3 ms·
I support GPL enforcement in general, but I am sort of conflicted about who's in the right in this particular case (which is why I'm definitely supportive of a
by geofft 10y ago
I support GPL enforcement in general, but I am sort of conflicted about who's in the right in this particular case (which is why I'm definitely supportive of a court hearing the actual arguments!).
VMware has segregated their proprietary "stuff", namely the hypervisor monitor, from the variant of the Linux kernel that runs a bunch of hardware drivers. This segregation doesn't involve a separate address space, and does not (I think) use the official Linux userspace ABI that is documented as one border of where the GPL ends. So, on the surface, the default assumption should be that it violates the GPL.
But it seems like it would be conceptually straightforward to use something like Xen's driver domains (http://wiki.xen.org/wiki/Driver_Domain http://wiki.xen.org/wiki/Driver_Domain) to run Linux in a separate virtual address space and pass through all the hardware to it. There might be technical complexity, but it's doable; VMware already has a product (Workstation) which takes a normal, running Linux machine, loads some GPL'd kernel modules written by VMware, and inserts the VMware hypervisor above the current kernel. ESXi could, in theory, do the same thing.
If the result of the lawsuit were to force ESXi to make that architectural change, would that really be a win for free software? And if that architectural change is doable, and results in no benefit to Hellwig (maybe just some annoyance on the part of VMware's developers), what legally-actionable damage is being done by Hellwig's code being used the way it currently is?