On Thu, Jan 18, 2018 at 12:35:00PM +0100, Kevin Wolf wrote: > Am 17.01.2018 um 21:06 hat Jack Schwartz geschrieben: > > Before I proceed with adding my multiboot test file, I'll clarify here that > > I started with a version from the grub2 tree. In that file I expanded a > > header file, also from the same tree. Neither file had any license header, > > though the tree I got them from (Dated October 2017) contains the GNU GPLv3 > > license file. > > I see. QEMU as a whole is GPLv2, so this might be a problem. It's > probably not as bad as merging GPLv3 code into QEMU proper because it's > a standalone test kernel that I suppose could have a different license. > But IANAL and maybe it's safer not to go there.
As long as the GPLv3 code is not linked / otherwise combined with any of the GPLv2 code in QEMU that will be ok. Since it is a self-contained test kernel, that would not be an issue in this case - it only interfaces to QEMU via the x86 machine ABI. It just means that the QEMU source tar.gz will be under a conjunction of licenses "GPLv2 and GPLv2+ and GPLv3 and ...all our other licenss..." The resulting binaries for emulators/tools will still be GPLv2 as they're only linking in the GPLv2 + GPLv2+ source, never linking the GPlv3 test image. For simplicity of understanding though, it could be desirable to avoid this if not an unreasonable amount of extra work > Maybe it would be less hassle to just reimplement the tests, based on > the MIT licensed tests that are already in tests/multiboot/. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|