On 04/28/11 03:54 AM, Jason Herring wrote:
> This all worked fine until I upgraded to snv_134 from 09/06
>
> I was running 3.x version of Vbox. Vbox interface starts OK. I start a VM and
> the Solaris kernel panics:
>
> Apr 28 00:09:04 atlantis ^Mpanic[cpu0]/thread=ff00064cbc60:
> Apr 28 00:
On Thu, Apr 28, 2011 at 18:39, Dmitry G. Kozhinov wrote:
>>I was running 3.x version of Vbox
>
> Have you tried to create a new virtual machine in the latest version of
> VirtualBox rather than trying to run the buggy instance of older version VM?
he did say that he had the same results with 4.0
>I was running 3.x version of Vbox
Have you tried to create a new virtual machine in the latest version of
VirtualBox rather than trying to run the buggy instance of older version VM?
This will require to install/configure OpenSolaris though, but this should not
be so hard to do.
--
This messa
More fun. I NFS mounted the VM from a Linux box and went to start the VM -
this also panicked the *opensolaris* kernel! Maybe this is something to do
with the network stack? Though I see a lot of references to sata/scsi and
si3124 (sata controller card in machine) in the panic:
Apr 28 08:52:
On 04/28/11 03:54 AM, Jason Herring wrote:
This all worked fine until I upgraded to snv_134 from 09/06
I was running 3.x version of Vbox. Vbox interface starts OK. I start a VM and
the Solaris kernel panics:
I upgraded to VBox 4.0.4 and then 4.0.6 and got the same result.
Did you remove the
This all worked fine until I upgraded to snv_134 from 09/06
I was running 3.x version of Vbox. Vbox interface starts OK. I start a VM and
the Solaris kernel panics:
Apr 28 00:09:04 atlantis ^Mpanic[cpu0]/thread=ff00064cbc60:
Apr 28 00:09:04 atlantis genunix: [ID 103648 kern.notice] recursive
