Looping Solaris Bootup

[angela_z]

I'm currently loading a Solaris image into Vbox on a Windows 7 system. The file I want to use is a VMDK on another machine (using Mac host OS), and the Windows and Mac OS are mapped by their network drive. That VMDK file is working very well and have no problem whatsoever.
So I chose the option to 'use existing storage' and located the VMDK file and the problem occurs right after I start the virtual machine.

There is the blue booting option screen to choose the failsafe option or booting the system option. I chose the normal bootup process, and enters the black prompt screen. There are a few lines printed out like 'Oracle' owned' and interestingly, the system then jumps back to its initial state that says starting the virtual machine and repeat the whole process over again.
Does someone have a clue about what is going on here?

Regards,
Angela

[icetwig]

I have the exact same problem VB 4.0.12 on a MacBook Pro, either on Apple OS or my dual boot Windows 7, I know the VMDK works because I tried it locally already but when stored on a network drive, neither Windows 7 running VB or MacOS running VB will boot the "Solaris 11 Express image for VB" Mine however gets to the Solaris Splash screen and the red progress bar gets 1/10 of the way and reboots.

[georgelinux]

Could you paste in the bit of your log file from where it reboots from Machine > Show Log...?

[icetwig]

Lots of info in this log... here is the beginning and end, thank you for the help.


00:00:08.049 VirtualBox 4.0.12 r72916 win.x86 (Jul 15 2011 18:06:47) release log
00:00:08.049 Log opened 2011-08-30T03:46:26.520000000Z
00:00:08.049 OS Product: Windows 7
00:00:08.049 OS Release: 6.1.7600
00:00:08.049 OS Service Pack:
00:00:08.740 DMI Product Name: MacBookPro5,1
00:00:08.952 DMI Product Version: 1.0
00:00:09.009 Host RAM: 2791MB RAM, available: 1134MB
00:00:09.009 Executable: C:\PROGRA~1\Oracle\VIRTUA~1\VirtualBox.exe
00:00:09.009 Process ID: 5896
00:00:09.009 Package type: WINDOWS_32BITS_GENERIC
00:00:09.009 Installed Extension Packs:
00:00:09.009 None installed!
00:00:09.943 SUP: Loaded VMMR0.r0 (C:\PROGRA~1\Oracle\VIRTUA~1\VMMR0.r0) at 0x89a18000 - ModuleInit at 0000000089a2ca00 and ModuleTerm at 0000000089a2ca70 using the native ring-0 loader
00:00:09.943 SUP: VMMR0EntryEx located at 0000000089a2d840, VMMR0EntryFast at 0000000089a2cbe0 and VMMR0EntryInt at 0000000089a2cbd0
00:00:09.943 SUP: windbg> .reload /f C:\PROGRA~1\Oracle\VIRTUA~1\VMMR0.r0=0x89a18000
00:00:10.493 File system of 'C:\Users\PeterMAC\VirtualBox VMs\Solaris\Snapshots' (snapshots) is ntfs
00:00:10.493 File system of 'C:\Users\PeterMAC\VirtualBox VMs\Solaris\Snapshots/{ae50c207-4afa-4f2d-9f07-a8bd961c4ed5}.vmdk' is ntfs
00:00:11.002 VBoxSharedClipboard mode: Bidirectional


skipping....

00:00:17.900 Changing the VM state from 'CREATING' to 'CREATED'.
00:00:17.912 Changing the VM state from 'CREATED' to 'POWERING_ON'.
00:00:17.912 AIOMgr: Endpoints without assigned bandwidth groups:
00:00:17.912 AIOMgr: C:\Users\PeterMAC\VirtualBox VMs\Solaris\Snapshots/{ae50c207-4afa-4f2d-9f07-a8bd961c4ed5}.vmdk
00:00:17.912 AIOMgr: Z:\solaris\OracleSolaris11Express2010_11-disk1.vmdk
00:00:17.913 Changing the VM state from 'POWERING_ON' to 'RUNNING'.
00:00:17.958 Guest Log: BIOS: VirtualBox 4.0.12
00:00:17.958 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:18.057 2D video acceleration is disabled.
00:00:18.172 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:18.183 AHCI ATA: Ctl: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:18.183 AHCI ATA: Ctl: finished processing RESET
00:00:18.184 Guest Log: BIOS: ata2-0: PCHS=16383/16/63 LCHS=1024/255/63
00:00:18.184 AHCI ATA: Ctl: RESET, DevSel=1 AIOIf=0 CmdIf0=0xec (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:18.184 AHCI ATA: Ctl: finished processing RESET
00:00:18.185 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:18.207 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=06650000 w=640 h=480 bpp=32 cbLine=0xA00, flags=0x1
00:00:20.671 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:20.672 Guest Log: BIOS: Boot from Floppy 0 failed
00:00:20.672 Guest Log: BIOS: CDROM boot failure code : 0003
00:00:20.673 Guest Log: BIOS: Boot from CD-ROM failed
00:00:20.682 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
00:00:21.053 Guest Log: BIOS: Booting from Hard Disk...
00:00:21.054 AHCI ATA: Ctl: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:21.054 AHCI ATA: Ctl: finished processing RESET
00:00:22.559 AHCI ATA: Ctl: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:22.559 AHCI ATA: Ctl: finished processing RESET
00:00:40.561 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=06650000 w=640 h=480 bpp=0 cbLine=0x140, flags=0x1
00:01:02.041 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
00:01:02.099 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=06650000 w=640 h=480 bpp=0 cbLine=0x140, flags=0x1
00:02:46.891 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.892 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.892 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.892 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.897 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.897 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:46.949 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:02:47.014 AHCI ATA: Ctl: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:02:47.014 AHCI ATA: Ctl: finished processing RESET
00:02:47.293 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:47.293 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:47.321 PIT: mode=0 count=0xffff (65535) - 18.20 Hz (ch=0)
00:02:47.371 PIT: mode=2 count=0x2e9b (11931) - 100.00 Hz (ch=0)
00:02:52.667 Changing the VM state from 'RUNNING' to 'RESETTING'.
00:02:52.676 CPUMSetGuestCpuIdFeature: Enabled APIC
00:02:52.676 CPUMSetGuestCpuIdFeature: Disabled x2APIC
00:02:52.676 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:02:52.685 AHCI ATA: Ctl: finished processing RESET
00:02:52.685 AHCI ATA: Ctl: finished processing RESET
00:02:52.685 Audio: set_record_source ars=0 als=0 (not implemented)
00:02:52.686 Changing the VM state from 'RESETTING' to 'RUNNING'.
00:02:52.690 Guest Log: BIOS: VirtualBox 4.0.12
00:02:52.690 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:02:52.695 OHCI: root hub reset completed with VINF_SUCCESS
00:02:52.746 AHCI ATA: Ctl: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:02:52.746 AHCI ATA: Ctl: finished processing RESET
00:02:52.747 Guest Log: BIOS: ata2-0: PCHS=16383/16/63 LCHS=1024/255/63
00:02:52.747 AHCI ATA: Ctl: RESET, DevSel=1 AIOIf=0 CmdIf0=0xec (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:02:52.747 AHCI ATA: Ctl: finished processing RESET

[ozziefirst]

I had similar problems with all guests (XP Pro Host) with virtual box, tried every solution offered with no luck.

Discovered this solution accidentally, since I'm a not wizard, can't take credit for it.

Settings, System, Processor, Execution Cap; reset to a lower value (by default it's 100%). I reset mine to 70% and bingo
everything works so far. I hope this helps some with similar problems.

I also enabled PAE/NX, though to be honest I didn't try it without PAE/NX disabled.

[gkoziol]

I had similar problems with all guests (XP Pro Host) with virtual box, tried every solution offered with no luck.

Discovered this solution accidentally, since I'm a not wizard, can't take credit for it.

Settings, System, Processor, Execution Cap; reset to a lower value (by default it's 100%). I reset mine to 70% and bingo
everything works so far. I hope this helps some with similar problems.

I also enabled PAE/NX, though to be honest I didn't try it without PAE/NX disabled.

For future generations:
Changing "Processsor usage" from default 100% to ~70% still works in 2023 for Windows 11 host and Solaris 11.4 : )