Skip to content

Conversation

@generic-pers0n
Copy link
Contributor

I recently tested OpenIndiana 2025.10 under KVM, and with the following configuration, it actually works pretty well in my opinion. I therefore have decided to update docs to reflect that right here.

The base configuration used is Generic Linux 2024. You need to make the following modification for OpenIndiana to work:

  • Chipset must be i440FX (otherwise neither the hard drive nor the ethernet adapter are detected for some reason)
  • Video adapter must be 'vmvga' with the custom XML
  • Sound must be AC97 (kept from the previous docs)
  • Firmware must be UEFI

Note that I can neither confirm nor deny if xsave instructions play any role. They might if under the legacy BIOS, but apparently under UEFI, they don't matter. Therefore, I decided to remove that mention, but it can be restored if necessary. I also haven't tested sound yet, so I'm keeping the recommendation to use AC97 for now.

Using a slightly modified Generic Linux 2024 configuration with slight
modifications actually works pretty well. Only the following
modifications need to be made:

- Chipset must be i440FX (otherwise neither the hard drive nor the
  ethernet adapter are detected for some reason)
- Video adapter must be 'vmvga' with the custom XML
- Sound must be AC97 (kept from the previous docs)
- Firmware must be UEFI

Note that I can neither confirm nor deny if xsave instructions play any
role. They might if under the legacy BIOS, but apparently under UEFI,
they don't matter. I also haven't tested sound yet, so I'm keeping the
recommendation to use AC97 for now.
Copy link
Contributor

@JMadgwick JMadgwick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about legacy BIOS won't work!, I think this is supposed to work. It would be good to have the configuration which supports this.

@generic-pers0n
Copy link
Contributor Author

generic-pers0n commented Nov 8, 2025

I'm not sure about legacy BIOS won't work!, I think this is supposed to work. It would be good to have the configuration which supports this.

My assumption right now is that it's because I didn't disable xsave CPU features, which is what the documentation previously said. I'll double check to ensure that the legacy BIOS configuration under KVM works with xsave features disabled.

@generic-pers0n
Copy link
Contributor Author

generic-pers0n commented Nov 20, 2025

So I finally remembered the real reason why I put "legacy BIOS won't work!": it doesn't. To try and troubleshoot this issue, I tried disabling the CPU xsave features with the following XML:

<cpu mode="custom" match="exact" check="none">
  <model fallback="forbid">qemu64</model>
  <feature policy="disable" name="osxsave"/>
  <feature policy="disable" name="xsaves"/>
</cpu>

Despite that, OpenIndiana won't boot under the legacy BIOS in virt-manager. With UEFI, however, I need no such configuration and everything works. (This might be another separate issue to report elsewhere too).

@JMadgwick
Copy link
Contributor

I had a look and remembered there's a known issue/quirk with using BIOS and booting from the USB image. If you were stuck with the "Requesting System Maintenance Mode" message and nothing happening then try the CD installer instead.

KVM is able to boot the USB image by specifying the boot media as a USB storage device. For QEMU this is done with -drive if=none,id=stick,format=raw,file=OI-hipster-gui.usb -device nec-usb-xhci,id=xhci -device usb-storage,bus=xhci.0,drive=stick, virt-manager should have an equivalent method.

@generic-pers0n
Copy link
Contributor Author

I had a look and remembered there's a known issue/quirk with using BIOS and booting from the USB image. If you were stuck with the "Requesting System Maintenance Mode" message and nothing happening then try the CD installer instead.

The issue I previously described here actually occurs with the CD installer. Whenever you attempt to boot the CD installer in a VM using the legacy BIOS in virt-manager, it boots for a few seconds only for it to crash a few seconds after and then quickly reboot the system. With that being said, I do wonder if there would be any difference with using the USB image.

KVM is able to boot the USB image by specifying the boot media as a USB storage device. For QEMU this is done with -drive if=none,id=stick,format=raw,file=OI-hipster-gui.usb -device nec-usb-xhci,id=xhci -device usb-storage,bus=xhci.0,drive=stick, virt-manager should have an equivalent method.

Noted! I'll try remembering this when booting from the USB installer! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants