VirtualBox

Ticket #2761 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

FreeBSD 7.0 crashes during boot (Assertion Failed / Expression: <NULL> / VBoxRecompiler.c(4325) cpu_abort) -> Fixed in SVN

Reported by: martin Owned by:
Priority: major Component: VMM
Version: VirtualBox 2.1.0 Keywords: freebsd, boot
Cc: Guest type: BSD
Host type: Windows

Description (last modified by frank) (diff)

Trying to boot FreeBSD 7.0 under VBox 2.1.0 Host Windows Vista 32 Bit Intel Core 2 Duo

00:00:21.238 !!Assertion Failed!!
00:00:21.238 Expression: <NULL>
00:00:21.238 Location  : C:/vbox/32/w32-rel/src/recompiler_new/VBoxRecompiler.c(4325) cpu_abort
00:00:21.238 fatal error in recompiler cpu: Trying to execute code with memory type
             addr_code=0000000028052020 addend=00000000d7fae000 at 0000000028052c56.
             (iHandlerMemType=0x40 iMMIOMemType=0x38)

With and Without VT-X I get the following error during the boot process. It happens very shortly after kernel loading/hardware detecting (The part where the kernel lsits all the devices found)

It happens at a slightly different location each time (sometimes it would output that all disks where "clean" (check-disk) , sometimes it goes down before.

I happens independent off the selected network adapter, and even if all networking is disabled.

Sound is disabled, cd is disabled. Only one disk is enabled, and configured as primary master. (other disks where enabled before, but it made no diff) PIIX3 or PIIX4 => no difference

I could not test SATA, that seems to fail at an earlier stage.

Attachments

FreeBSD7_0-2008-12-17-20-21-51.log Download (39.8 KB) - added by martin 5 years ago.
logfile
FreeBSD 7.1.xml Download (3.7 KB) - added by packet 5 years ago.
The VM config of my FreeBSD 7.1 VM
FreeBSD 7.1-2008-12-18-04-51-28.log Download (63.7 KB) - added by packet 5 years ago.
VM log of the most recent crash
VBox_with_ACPI_crash.log Download (52.1 KB) - added by GvM 5 years ago.
crash with acpi enabled (loading acpi kernel)
VBox_without_ACPI_ok.log Download (38.6 KB) - added by GvM 5 years ago.
booting without acpi from freebsd bootloader menu or by disablind acpi in vb

Change History

Changed 5 years ago by martin

logfile

comment:1 Changed 5 years ago by packet

Quite the same happens here with a FreeBSD 7.1 Beta 2 guest and a Ubuntu 8.04 host running VirtualBox 2.1: Some time after booting the guest, the VM aborts with the above mentioned "fatal error in recompiler cpu".

Changed 5 years ago by packet

The VM config of my FreeBSD 7.1 VM

Changed 5 years ago by packet

VM log of the most recent crash

comment:2 Changed 5 years ago by packet

Oh, I forgot to mention: The host runs the 64 bit version of Ubuntu.

comment:3 Changed 5 years ago by frank

  • Component changed from other to VMM
  • Description modified (diff)

comment:4 Changed 5 years ago by martin

Update: FreeBSd 6.3 does also crash. (booting from the install CD)

6.2 Install CD works

comment:5 Changed 5 years ago by GvM

Same on xp 32-bit sp3 host. Turning off ACPI in VirtualBox settings or booting FreeBSD without ACPI (from bootloader) makes it possible to run freebsd guest. attaching logs with and without acpi.

Changed 5 years ago by GvM

crash with acpi enabled (loading acpi kernel)

Changed 5 years ago by GvM

booting without acpi from freebsd bootloader menu or by disablind acpi in vb

comment:6 Changed 5 years ago by packet

I cannot confirm this. Booting FreeBSD 7.1 Beta2 (i386 / 32 bit) guest without ACPI (I disabled ACPI in the FreeBSD bootloader, I still have it enabled in VirtualBox) also crashed the guest VM. It seems to crash "faster" with more load on the guest OS: I can reproduce the crash by doing a cvsup update and portsnap fetch simultaneously and also by a make buildworld, but the FreeBSD guest runs pretty stable with less load. I will still try disabling ACPI in VirtualBox.

comment:7 Changed 5 years ago by packet

Disabling ACPI in VirtualBox also did not help. In fact, disabling ACPI - whether in FreeBSD or in VirtualBox - seems to crash the VM even faster than with ACPI enabled.

comment:8 Changed 5 years ago by GvM

packet, well, i was talking about freebsd 7.0 release, not 7.1 beta2 o_O
also the installation was minimal with linux binary compatibility and network disabled. lately X and windowmaker were installed and worked fine.

It seems to crash "faster" with more load on the guest OS: I can reproduce the crash by doing a cvsup update and portsnap fetch simultaneously and also by a make buildworld, but the FreeBSD guest runs pretty stable with less load.

packet, also the ticket is about crashing during boot process. we can't even boot the guest os when acpi is enabled ;)

comment:9 Changed 5 years ago by martin

For me disabling ACPI (via boot menu / loader.conf) works, but *only* if I switch VT-x off (host vista / guest FreeBSD 7.0)

comment:10 Changed 5 years ago by martin

Edit: I have 2 combinations to start (meaning get through the boot process without crash):

1) VBOX settings => Disable VT-x *and* ACPI FreeBSD => disable ACPI (boot menu / loader.conf 'hint.acpi.0.disabled="1"')

2) VBOX settings => Enable VT-x *and* ACPI FreeBSD => disable ACPI (boot menu / loader.conf 'hint.acpi.0.disabled="1"')

So in VBOX settings ACPI and VT-x (for me) either must be both enabled, or both disabled.

offtopic: Without VT-X, I do get the SigReturn issue

comment:11 Changed 5 years ago by 3vi1

I see the same problems running a FreeBSD 7.1rc2 guest under VirtualBox on a Kubuntu 9.04a2 host.

To get it to run, I have to disable ACPI in the VBox VM config, then use option 2 from the FreeBSD menu.

I've noticed that option 2 CHANGES WORDING depending upon if you have ACPI enabled in the VBox VM config. It will say "Boot FreeBSD with ACPI enabled" if you disabled it in the VM. I'm not sure if the menu's screwed up and option 2 always boots with it disabled, but the changing wording had me really confused at first.

-J

comment:12 follow-up: ↓ 13 Changed 5 years ago by GvM

3vi1, well, bootloader\kernel\someoneelse detects if you have acpi available on your pc (guest) or not. so it sets the right one for default boot (the one without acpi if you disabled it in vbox or the one with acpi if you enable it) and as option 2 it gives you alternative boot variant (so if freebsd detection was wrong)
note that freebsd 7.0 in my case fails to boot if you disable acpi in vbox and try to choose 2nd boot option (boot with acpi) or if you enable acpi in vbox and boot 1st option (so in both cases it loads acpi.ko module and phails), but having acpi disabled from boot menu (even with vbox acpi option on) or booting default one when acpi off in vbox works fine for me.

comment:13 in reply to: ↑ 12 Changed 5 years ago by 3vi1

Agreed... which makes it seem to me as if 7.1rc2 is somehow detecting the *opposite* of how ACPI is actually configured in VBox. That, or they have a bug and they're always showing the opposite text of what option 2 really does.

comment:14 Changed 5 years ago by ni81036

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from FreeBSD 7.0 crashes during boot (Assertion Failed / Expression: <NULL> / VBoxRecompiler.c(4325) cpu_abort) to FreeBSD 7.0 crashes during boot (Assertion Failed / Expression: <NULL> / VBoxRecompiler.c(4325) cpu_abort) -> Fixed in SVN

Problem was related to issue in the way recompiler executes code on monitored physical pages, what could happen if some special memory, for example pages used for page table reused as general purpose memory. This scenario most likely happens when system is in tight memory conditions (small RAM in the guest).

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use