6 ms·
LWN has a very clear explanation of just how clear-cut this is: https://lwn.net/SubscriberLink/635290/e501ce0264c182f4/ https://lwn.net/SubscriberLink/635290/e5
by JoshTriplett 12y ago
LWN has a very clear explanation of just how clear-cut this is: https://lwn.net/SubscriberLink/635290/e501ce0264c182f4/ https://lwn.net/SubscriberLink/635290/e501ce0264c182f4/
In particular, this isn't just a question of whether a kernel module is a derived work of the kernel. Apparently VMWare has copied code from the Linux kernel, with GPLed headers on top, and compiled that code directly into some of their code.
- tbrownaw 12y agoIt sounded to me like they have two things: one that's proprietary and the other that has modified kernel code in it.
- geofft 12y agoInteresting. My reading is that there are two components. The first is the Linux bootstrap, which they are entirely in compliance for. The second is vmkernel, which includes some GPL code whose source they're releasing, but vmkernel as a whole is not GPL; this is almost certainly out of compliance (but also easily fixable), unless they're doing something to isolate "vmkdrivers" from the rest of vmkernel. (Can I legally port, say, the GPLv2 ext4 filesystem driver from Linux to a non-GPL OS like OS X? Can Apple pick up that port, and distribute ext4.kext and its source in OS X, without putting the entire xnu kernel under GPLv2?) The harder and fuzzier part is that the ESX boot process works by asking Linux to "load" vmkernel, using the vmklinux helper module. If this is in the sense of loading a kernel module, it's (mostly) clearly wrong. If this is in the sense of loading a userspace app (as if vmklinux was a binfmt module, and vmkernel was a non-ELF executable), then this is (mostly) clearly okay. But it's doing neither of those. It's loading vmkernel above Linux, making the Linux process the first world, analogous to a Xen domU. So this isn't userspace, but it's also arguably a new address space. Neither of which are legal concepts per se, so it's hard to tell where this lies. This fuzzy part is neither the first component (Linux / "vmnix" / the bootstrap) nor the second (vmkernel), but the way in which they interact and are designed around each other. This itself might be an infringement, even if the first is not infringing, and the second is fixed.
- kion 12y agovmnix aka Service Console aka Console OS aka the Fuzzy part, was part of ESX, which was discontinued with the 5.0 series of ESX products.
- geofft 12y agoThey still use it for bootstrapping, right? I know they've gotten rid of the Red Hat-ish userspace, but according to the LWN article, there's still a Linux kernel involved and a kernel module used to pass control to vmkernel. (Is the word "vmnix" wrong? Does it apply only to the entire Red Hat-ish distribution in the COS, and not to the Linux stepping stone alone?)
- kion 12y agoNope, that stuff is all gone with the ESXi product. The vmkernel can bootstrap itself now. Basically the old 1.0 - 4.0 process for _ESX_ was like this: * Bootloader * Linux Kernel boot * Load VMnix module. * Load VMkernel * hardware control passed to VMkernel * Linux continues running as a sort of 'super' VM with some limited hardware access. For _ESXi_ from 4.0 - now : * Bootloader * VMkernel
- deleted 12y ago[deleted]
- fl0wenol 12y agoWhat's curious is that VMkernel's "personality" for ESXi userworlds (which are analogous to sessions IIRC) is it implements the x64 Linux ABI, with some signal/syscalls masked. I don't know if this was to make the transition for stuff like vpxa from ESX 4 on easier internally, or to make it easier for 3rd parties to develop against, or both. Is it lazily wrapping some functionality that should be open sourced that fills in where the service console would normally be? Probably not, but I can see why people would be a little suspicious.
- kion 12y ago
- deleted 12y ago[deleted]
- belorn 12y agoWait, Microsoft is distributing and loading GPL'ed kernel modules for windows? I did not even know windows kernel had modules, and even less so that they distribute and use third-party developed gplv2 modules. Are Microsoft shipping this with windows 7, windows 8, or windows server 2012, and is there a list somewhere for the shipped modules?
- deleted 12y ago[deleted]
- belorn 12y agoIf I understand you correctly, you think Microsoft would be held liable for copyright infringement if someone installs a GPLv2 driver into their own personal installation of windows? That is not how copyright infringement work. To be held liable, you have to distribute* a copyrighted work and then fail to comply with the license. Microsoft is as you say not distributing GPL'ed kernel modules, so there is no possible way* for them to help liable for GPLv2 windows kernel modules. A third-party windows distributor could be help liable if they bundled the modules with preinstalled windows machines. In that case, that third party would have to stop distributing the module, or beg Microsoft to release the source code for windows under GPLv2. * The pirate bay crew got charged for assisting in copyright infringement without distribution, but at least there was the accusation that someone somewhere did distribute a copyrighted work without permission.
- maxlybbert 12y agoSince the comment you were responding to has been deleted, I'm not sure if my comment will clarify anything for you. But it is possible, so here goes: > Wait, Microsoft is distributing and loading GPL'ed kernel modules for windows? A few years ago, the Linux kernel project accepted several patches from Microsoft that were meant to make it easier to run Linux in a VM hosted on a Windows machine ( http://www.dwheeler.com/blog/2011/07/14/#microsoft-linux-author http://www.dwheeler.com/blog/2011/07/14/#microsoft-linux-aut... ).
- delsarto 12y agoI don't think it is as clear cut at all, but that makes it much more interesting. I left a comment there, but it bears some repeating I think ESXi's kernel does not bootstrap itself from Linux at all. There is no linux kernel as such [1] ESXi does reuse linux kernel drivers ... a lot of them. But the way this happens is through a well-defined API provided by (proprietary) vmkernel called vmkapi. What you are seeing in the code above is the mapping between various Linux API's and these calls to the vmkernel. I have no idea about the complaint. VMware's position is probably that anyone can go and write anything they want against the vmkernel's vmkapi interface. Indeed some vendors ship drivers written espeically for this API. VMware have chosen to write a linux<->vmkapi interface, which then allows them to re-use many linux drivers. All of the linux<->vmkapi interface is released, along with the drivers and any modifications and this is considered sufficient. My guess is that the software conservatories position is that it is not. Note exactly the other thing happens on the "other" side -- between user-land and the vmkernel. ESXi uses glibc ... but of course that interfaces to vmkernel via standard system calls. Maybe that's part of it too, I don't know. So this may be a fight over API boundaries and where the GPL starts and stops. That's quite interesting... [1] There was with the ESX product, which shipped a version of Red Hat. That hasn't been around for ages
- geofft 12y agoThank you, that makes a lot of sense. I can see now how VMware can believe in good faith that they're in compliance (and in fact did a fairly major move towards compliance with ESXi) and Conservancy can believe in good faith that they're not.
- rnovak 12y agoFrom reading the linked article, it read to me like the complaint asserts that VMKernel itself is a violation of the GPL. If I'm wrong, please feel free to correct me, but these statements seems to point in this direction Conservancy discovered that VMware had failed to provide nor offer any source code for the version of BusyBox included in VMware's ESXi products But ESXi is not a purely open-source product; it also contains a proprietary component called "vmkernel." VMware's developers appear to have taken a substantial amount of kernel code, adapted it heavily, and built it directly into vmkernel itself If so, that would be like me finding some code on Github, changing it a little, and then including it in my own closed source application, clearly a violation of the GPL. Obviously though, I'm not sure how to prove that without the source of VMKernel Again, this is honestly just how I'm reading it, if I'm wrong feel free to correct it.
- jordigh 12y agoAside, shouldn't you be parsimonious with subscriber links for LWN and not post them publicly? I haven't had a LWN subscription in a while, but I really like their business model. I would not have posted this link myself.
- lambda 12y agoNo, the subscriber links are for exactly this kind of situation. They are to allow you to link to articles when it's relevant to a discussion, as long as you don't abuse them by doing something like posting a regular feed of all LWN articles or submitting every single one to Reddit/HN. Jonathan Corbet, editor of LWN, frequently posts his own subscriber links to LWN articles: https://news.ycombinator.com/submitted?id=corbet https://news.ycombinator.com/submitted?id=corbet And has explicitly endorsed posting occasional links to HN: https://news.ycombinator.com/item?id=5688938 https://news.ycombinator.com/item?id=5688938
- JoshTriplett 12y agoReasonable question (and I don't think you should be downvoted for it), but no, LWN editors (including Jonathan Corbet) have explicitly said that they're very happy to see LWN subscriber links posted to social networking sites and discussion sites. The main thing they don't want to see is someone systematically posting links for every single subscriber-only article.