Call for Testers: VirtualBox 4.0.6 (PBIs now available)

Bernhard Froehlich decke at
Wed Apr 27 20:18:16 UTC 2011

On Wed, 27 Apr 2011 15:28:11 -0400, Ryan Stone wrote:
> (Sorry for the noise earlier about the PBIs not working under PC-BSD;
> I'm not sure how I missed that had been already reported).
> I tried the new amd64 PBI and I am able to successfully start VMs now.
>  I had one VM(running some relatively recent version of amd64 HEAD)
> boot up fine, but a second one (also running amd64 HEAD, but maybe a
> different svn revision) gets a Guru Meditation during startup.  I'm
> not sure what is causing the crash.  In their original configurations
> the working VM booted off of an emulated IDE disk while the broken VM
> booted of an emulated SATA disk, however I just tried changing the
> SATA disk to instead be an IDE disk and it doesn't seems to have
> resolved the problem.
> I'm not getting a corefile for the crash(or I'm unable to find it).  I
> do have kern.sugid_coredump=1 and I'm running the PBI.  Is this
> expected for a Guru Meditation, or should it be putting a core
> somewhere?  I've put the VBox.log for the most recent crash here:

No, that looks fine.

> This seems to be easy to reproduce so let me know if there's any more
> information that I can gather.

I've added it to the Todo list for 4.0.6 and will report it to the vbox
developers tomorrow. Sorry, don't have a clue what is going wrong there
- but i'm sure they know.

> Also, the working VM was emulating uniprocessor machine.  I tried
> adding a second CPU and that VM started crashing, too.  I tried
> changing the broken VM to have only one core but it still crashes.
> I'm not sure if it's related to the first crash or not.

Look at the relevant parts of VBox.log and see if they look about the

00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current pointer
ffffffffffffffff vs 0000000084362000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current VMCS version e
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Entered Cpu 3
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current Cpu 2
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current pointer
0000000000000000 vs 0000000084365000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current VMCS version 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Entered Cpu 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current Cpu 0
00:00:08.374 !!
00:00:08.374 !!                 Guru Meditation -4001
00:00:08.374 !!
00:00:08.374 !!
00:00:08.374 !! {mappings, <NULL>}
00:00:08.374 !!

Bernhard Froehlich

More information about the freebsd-ports mailing list