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]
I was misconstrued as having insulted Minister Mentor Lee Kuan Yew. My
words were twisted and misinterpreted and I feel that there is a need to
explain myself and set the record straight.
[b]What really happened[/b]
It was sometime in Aug/Sep in the year 2009. The setting was in the
Tampines
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
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
First I have been out of the loop (retired) for 4 years so be gentle.
I'm doing some part time consulting and a Sun Blade 2500 (which are now dirt
cheap and plentiful) would be perfect for my client IF I could hang some
storage on it. I need 300GB and of course, this is on a budget (hence the
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
On Thu, Apr 28, 2011 at 18:39, Dmitry G. Kozhinov d...@desktopfay.com 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
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:09:04
