Can you run illumos on a VPS?

Can you run illumos on a VPS?

You can run illumos on a VPS, but only on a plan that gives you full hardware virtualisation and a way to boot your own install media. Container plans sold as OpenVZ or LXC cannot run it at all, because they share the host's Linux kernel while illumos brings its own. A provider that offers only a fixed menu of vendor images cannot run it either, because illumos is not on that menu and you have no way to add it.

illumos is the open source continuation of the OpenSolaris kernel and its userland. It is not a Linux distribution. Almost every surprise below comes back to that one sentence.

The practical checklist is short. Confirm the plan is KVM or Xen HVM. Confirm the panel accepts a custom ISO and gives you console access. Then install by hand over VNC, the way servers were installed before cloud images existed. If one of those pieces is missing at a given provider, the answer there is no, and support cannot change it.

What "illumos" means when you go and download it

illumos is a kernel plus a core userland, not a finished product with a download button. Distributions build on top of it, and a distribution is what you install. Four names come up:

• OpenIndiana is the general purpose one, with both desktop and server media. The OpenIndiana downloads page, read in September 2026, gives the current snapshot as Hipster 2026.04.
• Tribblix is a small distribution maintained by Peter Tribble. The Tribblix site, read in September 2026, lists Milestone 41 for x86, dated 5 August 2026.
• OmniOS Community Edition aims at storage and server duty. The OmniOS site, read in September 2026, lists r151058 as the current stable release, dated 4 May 2026, and r151054 as the long term support release from May 2025, with LTS releases supported for three years.
• SmartOS boots from USB or over the network and never installs to disk by design, which makes it the wrong shape for an ordinary VPS.

The line runs from Sun's OpenSolaris through the 2010 fork, and the story of how Solaris turned into illumos is worth reading before you download anything. It explains why commands that share a name with their Linux equivalents take different flags and print different output.

Requirement one: full hardware virtualisation, on x86

A VPS sold as OpenVZ, LXC, or plainly "container" runs your processes on the host's Linux kernel. There is no second kernel to install, so there is nothing for illumos to be. This is not a policy your provider can lift, and a larger plan of the same type does not help. What you need is KVM, Xen HVM, VMware, or bare metal, where the guest boots a kernel of its own.

If you are not sure which kind you bought, the difference between KVM, Xen and container VPS plans shows how to tell from the outside. On a Linux instance you already have, systemd-detect-virt settles it in one command: it prints kvm for the full virtualisation you need, and lxc for the kind that will never work.

Architecture is the second half of this requirement. The illumos virtio(4D) manual page, read in September 2026, states that the virtio driver is supported on x86 only, and the OpenIndiana downloads page offers 64-bit x86 images only. An ARM plan is therefore out. how ARM and x86 VPS plans compare matters for plenty of other workloads, but for illumos the question is closed.

Requirement two: custom ISO upload, or an install console

Booting your own installer needs one of two features from the panel: an ISO you upload or point at by URL, or a rescue mode that lets you write an image to the boot disk yourself. Providers use different words for it. Look on the product page for "custom ISO", "own ISO", "upload image", or "boot from ISO", and look before you buy rather than after.

Read the small print on that feature. The usual limits are a size cap on the ISO, a fixed list of hosts the URL may come from, image storage billed per gigabyte, and a rule that the custom ISO must be detached before the instance can be rebuilt. The minimal OpenIndiana media exists partly for reasons like these.

Where the feature does not exist, the honest alternatives are a dedicated server or a machine on your own desk. There is no clever workaround. A provider that will not let you boot foreign media has already decided what runs on that hardware.

Requirement three: virtio disk and network drivers

Your guest sees the disks and network cards the hypervisor hands it, and illumos needs a driver for each one. The illumos virtio(4D) manual page, read in September 2026, documents a virtio framework that handles feature negotiation and virtqueue management for the drivers above it. It names vioblk for virtio block devices and vioif for virtio network devices, with vioscsi covering virtio SCSI.

That is the combination to ask for when the hypervisor lets you choose: virtio block or virtio SCSI for the disk, virtio net for the interface. Where the panel exposes no choice, you find out by booting the installer and looking. An installer that offers no disk to install to is telling you about the disk controller, not about the disk. A system that boots with no network interface is telling you about the emulated card, so check that before you edit any config file.

Do not take a driver's presence on trust from a forum post about somebody else's hypervisor. The OpenIndiana downloads page points at the illumos hardware compatibility list and the OpenIndiana community list, and suggests booting live media and running the Device Driver Utility. That is a twenty minute check that saves a wasted evening.

Requirement four: a console you can watch while it installs

There is no unattended path here. The OpenIndiana text installer is an interactive curses program, and you drive it with the arrow keys. So the panel has to give you VNC or a serial console, and it has to hold that session open for the length of the install.

VNC is the easier of the two, because the installer draws correctly on an emulated VGA display. Serial is the one worth learning, because it survives reboots and copies out as text. The illumos loader(7) manual page, read in September 2026, documents a console variable that names the current console, accepts more than one value, and can be set to a serial console using the names ttya through ttyd. The same page says the loader sets that variable to serial automatically when the previous boot stage used serial, which is what makes a provider's serial console work at all.

One firmware detail decides whether you get a boot menu or a blank screen. The OpenIndiana handbook, read in September 2026, says OpenIndiana supports UEFI without secure boot, so secure boot has to be off. If your provider boots instances in UEFI mode and offers no legacy option, confirm that before you upload anything.

Which OpenIndiana image do you upload?

[
  {
    "label": "Minimal install DVD",
    "download_mb": 470
  },
  {
    "label": "CloudImage, compressed",
    "download_mb": 831
  },
  {
    "label": "Text install DVD",
    "download_mb": 970
  },
  {
    "label": "Live GUI DVD",
    "download_mb": 1900
  }
]

4 of the entries on the OpenIndiana downloads page, read in September 2026, are worth considering for a headless server. These are the sizes the project publishes, not sizes anyone measured here.

The minimal install DVD is the smallest at 470 MB, and it gives you a core system with no desktop. The text install DVD at 970 MB is the one most people want, because it runs the full text installer, including the ZFS mirror and RAIDZ options, on a plain console. The live GUI DVD at 1900 MB carries a desktop you will never start on a server, so uploading it spends storage and upload time for nothing.

The odd one out is the CloudImage at 831 MB compressed. It is a disk image rather than install media, so it helps only if your provider imports raw or qcow2 disks, which is a rarer feature than ISO upload. Two things are worth knowing before you plan around it. On the downloads page in September 2026 it was still at version 2025.10 while the ISOs were at 2026.04, so it lags the snapshot. And OpenIndiana's own notes describe a metadata agent that gives limited autoconfiguration from cloud-init data, with only simple networking and SSH keys properly tested. If you are expecting what cloud-init normally does on a first boot, expect considerably less than that.

What you get if the install works

• ZFS is the root filesystem on a default install, so the operating system itself lives in a pool. Snapshots and checksums cover the boot filesystem, not only your data.
• Boot environments are the payoff from that. beadm snapshots the whole system before an update, and the previous environment stays in the boot menu, so a bad upgrade costs a reboot instead of a restore.
• Zones are the native operating system level container, and they predate Docker by about a decade. how jails and Docker containers differ describes the same model from the FreeBSD side, and zones belong to that family.
• DTrace is part of the base system. It is the tracing tool that most later tracing tools copied.

If ZFS is the only item on that list you care about, stop here. You do not need illumos for it. running ZFS on FreeBSD and on Linux covers the two routes that are one click away on almost every provider, and either one gets you snapshots and scrubs today.

What you give up

• Packages. OpenIndiana's IPS repository covers a working desktop and the common server software, and it is far smaller than Debian's or Ubuntu's. Expect to build some things from source, and expect a few of those builds to need patches.
• Drivers. Hardware compatibility lists exist for illumos because the coverage is genuinely narrower than Linux coverage.
• Vendor convenience. There is no marketplace image and no one-click application stack. Provider backup and monitoring agents ship for Linux, sometimes for FreeBSD, and effectively never for illumos.
• Answers. When something breaks at 2am, the search results are thin, and the fix usually comes from a mailing list thread or the distribution's IRC channel.

Docker images do not run on illumos. Zones are a good container model, and they are not compatible with Docker's images or its tooling.

Does SSD Nodes offer illumos images?

No. There is no OpenIndiana, Tribblix, OmniOS or SmartOS entry in the panel, and there is no plan to add one. This is the same position we take on FreeBSD, and the reason is the same. We publish the images we can keep patched and help you recover, and an operating system nobody here runs in production is not one we can honestly support at 3am.

That is a statement about images rather than a judgement about illumos. choosing an operating system for your VPS walks through the decision most readers are really making, and where FreeBSD earns its place on a server next to Linux covers the closest neighbour that does have real provider support.

If illumos is the requirement, shop for it directly. The provider you want advertises custom ISO upload on the product page, or sells dedicated hardware. A workstation with 16 GB of RAM under your desk also qualifies, and it bills you nothing per month.

Install it in a local VM first

Do this before you rent anything. Install your chosen distribution in a virtual machine on the computer you already own, and give it a real workload for a week.

The OpenIndiana handbook, read in September 2026, lists VirtualBox, VMware Workstation and Fusion, VMware vSphere, Linux KVM, illumos KVM and bhyve as known-working hosts. The same handbook gives minimums of 2 GB of RAM with 16 GB of disk for a server install, and 4 GB with 20 GB for a desktop.

Tribblix is the quickest way to see what an illumos system looks like, because it installs from a live environment with a single command. The Tribblix install page, read in September 2026, documents this form:

./live_install.sh -G c1t0d0

Every command in this guide is quoted from a project's own documentation, with the source named and the date it was read. Run them yourself in a VM and check the output before you trust them on hardware you are paying for. Flags and version numbers move, and the project's page is the authority.

Two details in that line are worth understanding now. c1t0d0 is an illumos disk name in controller, target and disk form, so nothing here is called /dev/sda, and the name you pass has to be the one your VM actually shows. And -G selects GPT partitioning while -b selects legacy MBR, which is the same choice your hypervisor's firmware makes for you: UEFI wants the first, an old BIOS wants the second. Getting that wrong produces a system that installs cleanly and then will not boot.

Most people stop at the local VM. Stopping is a result rather than a failure, because you learned what the migration would cost without paying a hosting bill to find out.

The decision

There are two honest paths, and they split on what you actually want.

If you want ZFS, snapshots and a steady server, you do not need illumos. FreeBSD gives you those on the providers that support it, and Linux with OpenZFS gives you them nearly everywhere. Both come as installable images with vendor agents, and both have answers when you paste an error message into a search box at 2am.

If you want zones or DTrace, or you keep Solaris era software alive, illumos is the point and nothing else substitutes. Then the work is provider selection. Find one that advertises custom ISO upload or bare metal, and budget an evening for a manual install over VNC after you have proved the whole procedure locally. Judge the plan on whether you can boot your own media, because a cheap plan you cannot boot your own media on is worth nothing for this job.

FAQ

Can I install OpenIndiana on an OpenVZ or LXC VPS?

No. A container VPS shares the host's Linux kernel, and every process inside it is a Linux process. illumos ships its own kernel, so there is nothing to start it with, and no provider setting changes that. You need KVM, Xen HVM, VMware, or bare metal. On a Linux instance you already have, systemd-detect-virt tells you which kind you are on: kvm works, lxc never will.

Which illumos distribution should I try first?

OpenIndiana, using the text install DVD. It has the largest package repository among the illumos distributions and the most complete documentation, and its text installer is built for a console rather than a desktop. Tribblix is a good second look if you want a smaller system, and its documented one-line installer makes a VM test fast. OmniOS Community Edition is the choice when the machine is a storage server and you want a long term support release.

Do I need virtio drivers, or will emulated IDE and e1000 work?

Ask for virtio wherever the hypervisor lets you choose. The illumos virtio(4D) manual page, read in September 2026, documents vioblk for virtio block devices and vioif for virtio network devices, with vioscsi for virtio SCSI, and notes that the framework is supported on x86 only. Where you get no choice, boot the installer and look at what it finds. An installer listing no disk points at the disk controller, and a booted system with no network interface points at the emulated card. Check the illumos and OpenIndiana hardware compatibility lists before you commit money to a plan.

Does SSD Nodes offer illumos or FreeBSD images?

No, neither. There is no OpenIndiana, Tribblix, OmniOS or SmartOS option in the panel, and no FreeBSD option either. We publish the images we can keep patched and help you recover. If illumos is a hard requirement, pick a provider that advertises custom ISO upload, or use dedicated hardware, and validate the entire install in a local virtual machine before you pay for anything.