Page 1 of 1
Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 11:49
by Guff
This is a newly installed VirtualBox 5.0.12 on a nearly new Macbook Pro (8GB RAM running 10.11.2.
I created a Solaris 64 VM to install SmartOS and attached the SmartOS USB VMDK and a new VMDK for the Zpool. On poweron, SmartOS went through configuration OK, but when it rebooted (as per usual) I got a Critical error.
The log is attached. The screen is
- VBox.png (1.31 KiB) Viewed 3637 times
Gareth
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 12:47
by socratis
You have the following in your log:
00:00:04.995627 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:04.995628 !!
00:00:04.995628 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:04.995646 !!
00:00:04.995669 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:04.995675 !!
00:00:04.995675 !! {mappings, <NULL>}
For Guru Meditation errors (especially Triple Faults), you should head to the
bugtracker and either search for an appropriate bug where you'll attach your logs and other vital information, or open a new bug report.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 12:57
by loukingjr
Actually SmartOS claims to be a Type 1 Hypervisor. VirtualBox doesn't support nested hypervisors.
Plus it's meant to run on bare metal…
SmartOS is a specialized Type 1 Hypervisor platform based on illumos. It supports two types of virtualization:
OS Virtual Machines (Zones): A light-weight virtualization solution offering a complete and secure userland environment on a single global kernel, offering true bare metal performance and all the features illumos has, namely dynamic introspection via DTrace
KVM Virtual Machines: A full virtualization solution for running a variety of guest OS's including Linux, Windows, *BSD, Plan9 and more
SmartOS is a "live OS", it is always booted via PXE, ISO, or USB Key and runs entirely from memory, allowing the local disks to be used entirely for hosting virtual machines without wasting disks for the root OS. This architecture has a variety of advantages including increased security, no need for patching, fast upgrades and recovery.
SmartOS is typically "installed" by downloading and copying the OS image onto a USB key and then booting that key. On the first boot a configuration utility will configure your base networking, allow you to set the root password, and allow you to select which disks to use to create the ZFS Zpool which will provide persistent storage.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 13:26
by mpack
IME, triple fault means that the guest did something really nasty. As you say, VirtualBox doesn't support nested hypervisors, so I wouldn't consider this a bug: VBox just caught the exception.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 13:30
by loukingjr
FWIW, From their Wiki page, I saw no evidence SmartOS was supposed to run in Solaris or any other OS.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 21. Dec 2015, 21:56
by socratis
Well, I did a bit of reading and I actually downloaded SmartOS to try it out. According to their website, SmartOS is not a type-1 hypervisor, neither requires nested virtualization. What they offer is a VM so you can try it out. VMWare is their default, but they do offer VirtualBox setup instructions. From their website:
-
https://wiki.smartos.org/display/DOC/Sm ... lBox+Guest
-
https://wiki.smartos.org/display/DOC/Sm ... VirtualBox
In VirtualBox, create a New machine. Set the OS as "Solaris 11 64bit". Attach the VMDK you just created as the boot drive. (Give the VM at least 2GB of RAM, preferably more.)
So, Guff did the right thing. He created a Solaris 11 VM, attached the VMDK (I personally did it with a VDI
) and a new VDI for the zpool, according to the instructions. Boots OK, setup (seems to) run fine, but on reboot you get a Guru Meditation. I've tried changing different settings to no avail.
So, to sum it up: this is a valid setup and a valid bug. @Guff, see my previous message:
socratis wrote:For Guru Meditation errors (especially Triple Faults), you should head to the
bugtracker and either search for an appropriate bug where you'll attach your logs and other vital information, or open a new bug report.
Don't forget to add the ticket number here so that other users can benefit from it.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 3. Jan 2016, 16:13
by Guff
loukingjr wrote:FWIW, From their Wiki page, I saw no evidence SmartOS was supposed to run in Solaris or any other OS.
Actually, SmartOS is built on Solaris foundations.
Gareth
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 3. Jan 2016, 16:14
by Guff
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 3. Jan 2016, 17:06
by michaln
Don't be surprised if there's no interest in fixing it. It would help if you could somehow show that a triple fault isn't the expected result. Sure it's not what you expected, but under what circumstances does it not occur? Or to put it differently, how do we know this isn't a bug in the guest OS?
Naturally if you told us how to reproduce the triple fault with Oracle Solaris it would help a lot.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 3. Jan 2016, 18:51
by Guff
I followed the instructions in:
https://wiki.smartos.org/display/DOC/Sm ... Box+Guest
From traffic in the SmartOS forums, plenty of other people have followed this set of instructions; though probably not on a Mac host.
Personally I'm not bothered if it's fixed. I just needed a simple SmartOS environment to try something out rather than do it on my production SmartOS system. I avoided the problem by installing VMWare ESXi on some spare hardware and installed SmartOS in a VMWare VM. Zero problems.
I was just reporting it for the benefit of the community.
Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12
Posted: 3. Jan 2016, 21:45
by socratis
Guff wrote:From traffic in the SmartOS forums, plenty of other people have followed this set of instructions; though probably not on a Mac host.
Well, I may have not put it explicitly, but it's on my info on the right-hand side that I am actually on a Mac and
I did try the suggestion on the exact same page with the same failure. But I also think that Michal's statements stand correct.