OmniOS: Illumos-based OS from OmniTI
omnios.omniti.com
omnios.omniti.com
And we don't have 100% solaris api/abi compatibility.
Or a Sun compiler.
Or Sun drivers, necessarily.
Or a real guarantee of future source releases from Oracle.
Who/what is this for?
People who want to run ZFS for storage usage. ZFS is still better than Linux alternatives like LVM, BTRFS etc. To be picky, there is not an exact counterpart to ZFS under Linux.
And with clones etc. you can set up 1 master KVM image and then clone it 10 or 100 times, saving a lot of disk space in the process (ZFS clones only use the amount of space that is different from the original).
People who have a lot of Solaris experience or have to maintain a lot of Solaris systems already. Also people who are using Solaris zones.
People who are building backend systems that require or can use any/all of the above. Right now, no one cares what your Web SaaS service runs on, as long as it stays up and doesn't lose their data.
Solaris still has a better VM subsystem, IMHO, than Linux does, and performs very well under heavy loads that include disk activity.
Second, Oracle is encumbering Solaris with a not-nice license. I haven't followed the latest developments because I no longer care, since I will never use a non-free OS.
Whether you meant to ask, "Why Illumos over Solaris" or "Why SmartOS or OmniOS over Illumos?" I think I have answered your question :-)
http://dtrace.org/blogs/bmc/2011/08/15/kvm-on-illumos/
Hopefully the next release of OpenIndiana will add support for it as well, seeing how they also use the Illumos kernel.
I compare OpenSolaris/Illumos to the Linux kernel. You typically don't just install them just like you typically don't install Linux. Instead you install a Illumos distribution or you install a Linux distribution. Obviously this isn't a perfect comparison since Illumos contains a lot more of the user land than Linux does.
Current distributions of Illumos appear to include: OpenIndiana, SmartOS, Nexenta, and now OmniOS.
Where do you get that we don't have 100% solaris api/abi compatibility?
One of the pressing projects appears to be to make the Sun Compiler optional. Illumos' preferred compiler to be built with is GCC 3.4.3. They do still rely on dmake and the lint from SunStudio though. Hopefully that can be resolved.
I don't know why we need Sun drivers specifically, unless we are using Sun hardware.
I think we can safely assume now that there will be NO future source releases from Oracle.
As to who this is for, I believe other comments do a good job expressing that.
OpenIndiana, SmartOS and OmniOS are all distributions of the illumos kernel and associated libraries and programs.
OpenIndiana is geared more towards desktop users (though it can be used for servers well enough). OI is funded primarily through everycity.co.uk.
SmartOS is a PXE/USB booting server operating system, where all services are meant to be encapsulated in zones and KVM. SmartOS zones use pkgsrc for packaging (via pkgin). SmartOS is useful for building clouds, for instance. It is the core of Joyent's SmartDatacenter product.
OmniOS is a more traditional server operating system in that you install bits on metal, use IPS for packages, and have an upgrade path other. OmniOS has been used in production inside OmniTI for a while (as I understand it), but is the newest player on the block.
As with Linux distributions, each distribution above has different operating and development philosophies, but they all push code back up through the illumos gate.
Sun is dead. Oracle ate Sun, took their ball, and went home. illumos is the successor of the OpenSolaris idea (sans asinine governance model), and the core of open source Solarish distributions.
This talk by ex-Sun kernel engineer (and creator of DTrace) Bryan Cantrill is both instructive and hilarious: http://smartos.org/2011/12/15/fork-yeah-the-rise-and-develop...
Relevant to this discussion : Joyent releasing SmartOS http://news.ycombinator.com/item?id=2887170
AMD support from SmartOS wiki: http://wiki.smartos.org/display/DOC/SmartOS+Technical+FAQs#S...
Joyent's original work is worse than just Intel only, it requires features found in Core iX and relate Xeon CPUs. This means it doesn't work on Xeon 5xxx chips that are getting affordable and it doesn't work on C2D chips that support VT-x. It sounds like AMD support is further along than supporting older Intel chips.
I have a hacked up SmartOS ISO from a month ago with a build of the "pre-ept" KVM module replacing the stock module. If you'd like to test it out, with the disclaimer that it might not work for you, it's here: http://alpha.sysmgr.org/smartos-20120223-jmc2.iso
If it works for you I'd love to hear about it. If it doesn't work and you can provide crash dumps or even remote console access to the machine for me to debug the problem then I'll try and help out. My goal is to get the new support tested and working on as many different bits of hardware as possible and then get it integrated into Joyent's repo once cleaned up and proven.
A lot of us hang out in #illumos on freenode (IRC) if you'd like to chat -- I'm LeftWing.
This one does, according to release notes.
Looks like they have tweaked some of the libraries and they provide both 32 and 64bit versions of Python also (this can be a pain to build sometimes as the configure tools don't always pull in the right libs, so you end up with mixed 32 and 64bit objects or other weirdness).
Also, the installer is minimal, basically just asks you what disk to install on. You do all other configuration after you have booted it for the first time.
They could just port KVM to FreeBSD instead; FreeBSD already has ZFS, DTrace and all other necessary bells and whistles for cloud webhosting infrastructure. But in contrast to (Open)Solaris they have community support for new hardware, a lot of already working drivers for existing hardware and also much safer legal position.
Are there any technical difficulties with porting KVM to FreeBSD? Can anyone elaborate?
As for why not to just move from Solaris to FreeBSD... because they're totally different beasts? And we happen to like Solaris? :-)
Porting KVM to Solaris was apparently quite non-trivial:
Some nice features:
A nice VM overview/start/manage screen A way to group VM's so it starts multiple VM's with a single "click" (in a pre defined order).
Switching between VM's with a shortcut and/or alt-tab/expose visual style.
Host menu to openen up new VM's, looking at stats etc. maybe a fold down over the current VM
Many people, my self included, are using Solaris mainly for big storage where the safety of data comes first and foremost. There is still not good competitor to ZFS that works as well and provides the same gaurantees.