Date: Sat, 29 May 2021 19:43:03 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 168298] VirtualBox using AIO on a zvol crashes Message-ID: <bug-168298-27103-i3MVuZ2y6x@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-168298-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D168298 --- Comment #54 from Tom Rushworth <tbr@acm.org> --- (In reply to Guido Falsi from comment #52) Thanks for pointing out the VBox contributor information, and all the relat= ed background stuff :). It looks, from the licensing info there, that I have to be the one sending = it upstream if anyone is going to. I guess, given who owns the project, they = do have to work in a "lawyer rich environment" :). I don't have a strong stance on any particular software license, except for= the belief that contributions should be licensed in the same way as the original authors did or as close to their intent as can be determined. The VBox contributor information page seems to offer only a legal agreement with Ora= cle or the MIT license, while the original project seems to be GPL. Certainly = the file I patched is GPLv2. I don't think I care for the idea that future contributions to VirtualBox have to be either specifically licensed to Ora= cle (i.e. free of the GPL), or MIT licensed (i.e. also free of the GPL). It se= ems to me that would indicate a desire to gradually change the original authors intent. I'll have to think about it for a while before I do try to upstrea= m it :(. In the meantime, I guess I'll also have look at the copyright issues for contributions to the FreeBSD ports area :(. My intent was simply to provide help to other FreeBSD users in whatever the usual FreeBSD way was, while spending the least amount of my own time on it. It looks like I should dot= a few more 'i's and cross a few more 't's before the FreeBSD port maintainers= can accept it. Anyway, until I do, if any FreeBSD user runs into this problem, please feel free to stick the patch into your /usr/ports/emulators/virtualbox-ose/files directory as a possible workaroud, with whatever modifcations you might wan= t.=20 It's working just fine for me in FreeBSD 13.0 for VBox 6.1.20 at the moment, and an earlier version of it seems to be working in FreeBSD 12.1 for Vbox 5.2.34. I can't promise any quick responses if things change, but FreeBSD = is my working desktop, which I try to keep fairly up to date with released FreeBSD, and I need a working emulator :). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-168298-27103-i3MVuZ2y6x>