Ticket #17947 (new defect)

Opened 4 years ago

Last modified 4 years ago

Virtualbox 5.2.18 (and 5.2.19) crash on OpenIndiana Hipster

Reported by: mnespen Owned by:
Component: other Version: VirtualBox 5.2.18
Keywords: Cc:
Guest type: all Host type: other


Hi, ref:

When starting a VM on 5.2.18/19 from hostOS openindiana (illumOS) it crashes in


#echo disable_smap/d | mdb -k disable_smap: disable_smap: 1


vbox.patch Download (836 bytes) - added by alp 4 years ago.
as_map() fix

Change History

comment:1 Changed 4 years ago by michael

Not a Solaris person I'm afraid - do I read the last line correctly as saying that SMAP is disabled? For classical Solaris we advise disabling it in /etc/system (don't have the details, sorry). More generally, since we do not have the spare resources to support OpenSolaris in the core team, it might be worth finding people in the OpenSolaris community willing to invest the time into understanding how VirtualBox works, at least the host (kernel and other) integration parts, so that they can take over maintenance of an OpenSolaris port themselves. People from the FreeBSD community (possibly others) do this and we incorporate their patches, usually with host-specific ifdefs. It should be doable for people who have a reasonable understanding of how the kernel works, for example because they write or maintain drivers.

You can look at our Linux kernel code as an example of how to deal with SMAP, as we already support it on Linux hosts.

comment:2 Changed 4 years ago by alp

It is not related to SMAP.

I know nothing about FPU operations, but it seems that recent changes related to FPU and GDT in illumos-gate has caused this - and .

The corresponding KVM fixes looked like (FPU-related fix) and (GDT-related fix).

Changed 4 years ago by alp

as_map() fix

comment:3 Changed 4 years ago by alp

The following patch ( fixes VirtualBox. The issue was analyzed and fixed by Andy Fiddaman.

comment:4 Changed 4 years ago by mnespen


Looking forward to try out this fix. What are the timeline for getting this out to official 5.2.x release?


comment:5 Changed 4 years ago by andyf



is created, this is going to need wrapping in an #ifdef for illumos as the patch would break Solaris.

comment:6 Changed 4 years ago by michael

I am wondering (I may have wondered this before) whether it would make more sense for Illumos to build their own packages, like FreeBSD (and possibly other BSDs) too. We carry their source changes, as we could probably carry yours (I will check that) but they make sure that everything builds and works. That would probably benefit both sides, as we do not really have the resources to put effort into Illumos support, and you would be in control of the port.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use