OpenSolaris 2009.06 won't run on v3.2.x?

[dleffler]

I've been unable to get my OS 2009.06 to run since upgrading to vbox v3.2.0 and newer versions. I've been using the image downloaded from http://virtualboxes.org/, but it now always reboots itself during the "thermometer" screen.

[jkeil]

Could be a kernel panic.

To find out more information about the possible cause, in GRUB edit the
boot menu entry (type the 'e' key), and delete the splashimage, foreground
and background lines, edit the kernel$ line and remove the -B
",console=graphics" option and append options " -kvs" at the end
of the kernel$ line. Boot the modified entry. Does it stop in the
kernel debugger with a kernel panic? What kind of panic is it?

[baf]

That image and xml file works fine for me in os x 10.6 vbox 3.2.4

[jkeil]

Yep, same here. On an OpenSolaris b134 host running vbox 3.2.4 I was
able to install an OpenSolaris 2009.,06 guest (64-.bit), and rebooted it
several times. No problems. Guest additions worked, too.

[pstein]

I have problems too booting OpenSolaris 2009.06 in VirtualBox 3.2.4 on WinXP hostOS

After booting of OpenSolaris for a while the progressbar of the boot process collapses and the VirtualBox boot screen reappears. This re-occurs in an endless loop.

I am using the OpenSolaris *.vmdk from vmplanet.net

Whats wrong?

Peter

[jkeil]

I have problems too booting OpenSolaris 2009.06 in VirtualBox 3.2.4 on WinXP hostOS

After booting of OpenSolaris for a while the progressbar of the boot process collapses and the VirtualBox boot screen reappears. This re-occurs in an endless loop.

I am using the OpenSolaris *.vmdk from vmplanet.net

This one - http://vmplanet.net/node/99 ?

That is a vmware image, isn't it? I doubt that vmware and
virtualbox emulate exactly the same hardware, so most likely
the vmware installation won't find the physical boot device
when you boot that image under virtualboix. The OpenSolaris
kernel will panic in such a case because it is unable to mount
the root device. Boot the opensolaris kernel with the kernel
debugger to make sure (delete foreground, background and
splashimage lines from the grub boot menu entry, remove
the ",console=graphics" option from the kernel$ line, and
append options " -kv" at the end of the kernel$ grub boot
command line).

[pstein]

This one - http://vmplanet.net/node/99 ?

yes, exactly this.

That is a vmware image, isn't it? I doubt that vmware and
virtualbox emulate exactly the same hardware, so most likely
the vmware installation won't find the physical boot device
when you boot that image under virtualboix. The OpenSolaris
kernel will panic in such a case because it is unable to mount
the root device. Boot the opensolaris kernel with the kernel
debugger to make sure (delete foreground, background and
splashimage lines from the grub boot menu entry, remove
the ",console=graphics" option from the kernel$ line, and
append options " -kv" at the end of the kernel$ grub boot
command line).

Hmm, I read a couple of time that *.vmdk format is compatible with VirtualBox.
From my point of view it means that VB CAN boot each *.vmdk.

Anyway, you write that I should boot VB with the kernel debugger"
and modify some parameters.

How do I boot VB with kernel debugger?
Where exactly should I change the paarmeters?

Is there a working OpenSolaris (2009.06) VM image already pre-installed for VB, ready to download?

Peter

[jkeil]

Hmm, I read a couple of time that *.vmdk format is compatible with VirtualBox.
From my point of view it means that VB CAN boot each *.vmdk.

AFAIK, Virtualbox is able to use vmware *.vmdk files, so it should (and apparently
does) start the boot from such an image. But whether the vmware installed
opensolaris works under virtualbox is another story. Apparently it crashes with a panic.

Note that such a panic happens in case you move an opensolaris installed /
bootable hdd from one computer to another computer with different physical
hardware / device paths; opensolaris won't boot on the new machine; to fix it
you have to boot the new computer from the OpenSolaris LiveCD, and run
"zpool import -f rpool". After that the hdd should become bootable in the
new computer.

See also this bug: http://bugs.opensolaris.org/bugdatabase ... id=6513775
and: http://bugs.opensolaris.org/bugdatabase ... id=6795637

Anyway, you write that I should boot VB with the kernel debugger"
and modify some parameters.

How do I boot VB with kernel debugger?
Where exactly should I change the paarmeters?

To find out why opensolaris panic'ed, boot opensolaris
(not VB) with the kernel debugger. I already explained
the steps (twice) in this thread. See my first reply in
this thread.

Is there a working OpenSolaris (2009.06) VM image already pre-installed for VB, ready to download?

The original poster that started this thread seems to use a virtualbox image
from http://virtualboxes.org/, but that didn't work with vbox 3.2.x
Maybe the virtual box guest needs different configuration settings, e.g.
the disk controller needs to be p-ata instead of ahci or something like that.
We really need to get the kernel panic messages, but they hide
behind the boot graphic...

[pstein]

AFAIK, Virtualbox is able to use vmware *.vmdk files, so it should (and apparently
does) start the boot from such an image. But whether the vmware installed
opensolaris works under virtualbox is another story. Apparently it crashes with a panic.

Note that such a panic happens in case you move an opensolaris installed /
bootable hdd from one computer to another computer with different physical
hardware / device paths; opensolaris won't boot on the new machine; to fix it
you have to boot the new computer from the OpenSolaris LiveCD, and run
"zpool import -f rpool". After that the hdd should become bootable in the
new computer.

Very interesting thank you.
However I wonder why it makes sense to access a *.vmdk if I cannot boot from it.

But ok. What is about an OpenSolaris.vdi image? I mean a VirtualBox propriatary VM.
Can I take/move/copy such a VM to other computers/USB sticks and run it from there without problems?
Is there full hardware abstraction?

Peter

[dleffler]

Thanks to your insightful observations....I moved the .vdi file from an SATA/AHCI controller to the exisiting IDE/ICH6 controller. Came up as it used to do. Not sure why the SATA controller worked in pre 3.2.x and crashes now, but I have what I needed!

[jkeil]

But ok. What is about an OpenSolaris.vdi image? I mean a VirtualBox propriatary VM.
Can I take/move/copy such a VM to other computers/USB sticks and run it from there without problems?
Is there full hardware abstraction?

You have to make sure that the different VBox hosts have the same hardware configuration
for the opensolaris vbox guest (esp. the disk controller). When the virtualized hardware is the
same, the opensolaris disk image should work when attached to different vbox guests.

[MarkZ3]

Hi. I installed 2009.06, updated all in package manager and rebooted and now I'm getting the constant reboots. I have not installed the guest additions. I installed and updated 2009.06 twice and it's the same behavior. When I try to boot my BE, it reboots. I'm using VB 4.0.0.