On Mon, Dec 14, 2015 at 8:25 PM, Alan Somers <[email protected]> wrote:
> I'm a FreeBSD developer sitting on a backlog of about a hundred ZFS > patches that I want to push into OpenZFS. Thank you! > But I've never been able to > build and test on Illumos. I've spent the last two days trying, but > to no avail. Here's what I've tried: > > * Booting all three isos from > http://omnios.omniti.com/wiki.php/Installation on KVM. They all > crash. I see a row of dots at the top of the screen, and suddenly my > VM reboots. > * Booting the Vagrant file from that same website. But before I got > too far, Will Andrews informed me that it's missing some critical > parts of the toolchain > * Booting an OpenIndiana Hipster 20151003 iso in KVM. But it crashes > just like OmniOS. > * Booting a custom Vagrant box made by Will Andrews in VirtualBox. I > got the furthest with this one. But sshd won't start, because it's > linked against the wrong version of OpenSSL. I tried upgrading using > onu, but that failed because something was trying to resolve > "ipkg.sfbay". Google tells me that that system was a private server > behind Sun's firewall five years ago. > > What shall I do? Is the KVM crash a known issue? Is there an OmniOS > r20151016 vagrant box somewhere? I'll let those more familiar with these systems address these questions. I share your frustration with how difficult it is to get illumos running in a VM. I've been successful with: - an older version of OI on VirtualBox on OSX - both OI and OmniOS (various versions) on VMware ESX (seems to "just work") - more recently with OmniOS r151012 on AWS (specifically, ami-96f44efeon on t1.micro) Is it ok to just blindly submit my > patches without even compile testing? > It is possible to do so, using the procedure described here: https://github.com/openzfs/openzfs You submit a pull request and then we will do builds and regression tests on your patch, and review the changes. Are the patches from FreeBSD already in FreeBSD-HEAD? If so they would be good candidates for using this process since they are likely to work on the first try. The automated build/test process is not a very good one for iterating since the builds/tests take several hours and the build artifacts (upgrade packages) are not automatically provided to you. If your changes aren't in FreeBSD-HEAD, you can still use pull requests, but you will probably also need to do your own builds so that you can iterate more quickly, and do manual testing of your changes. But that's just a rule of thumb. --matt
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
