[Bug]: Boot loop with OmniOS or OI Hipster

Open
#969 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

Start with the attached boot log and screenshot, then trace the VM boot path for the reported OmniOS and OpenIndiana guest versions in the VirtualBox source. Compare the behavior with a working guest or earlier ISO to narrow down where the rapid reboot begins. Done means identifying and fixing the cause so fresh VMs boot successfully with the reported ISOs.

Written by the indexing model from the issue text.

Description

bug
Version

7.2.22

Host OS Type

Linux

Host OS name + version

Debian Unstable, Nov 10th, 2026

Host Architecture

x86

Guest OS Type

Solaris

Guest Architecture

x86

Guest OS name + version

omnios-r151060 or OI-hipster-minimal-20261030

Component

Unspecified

What happened?

OmniOS-2026-11-10-07-54-21.log

Existing VMs (installed a few months ago) or fresh empty VMs using the latest ISOs of OmniOS or OI Hipster enter a boot loop.

I am attaching the log, but it shows nothing special. On the boot screen, we can see an error ; after several attempts (it lasts very shortly), I could take a screenshot which I am also including.

Image
How can we reproduce this?

Boot a fresh VM with the latest ISO of OmniOS (https://downloads.omnios.org/media/stable/omnios-r151060.iso) or OI Hipster (https://dlc.openindiana.org/isos/hipster/20261030/OI-hipster-minimal-20261030.iso). When starting the VM, it starts booting and then reboots very quickly.

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.