how to start virtualbox on opensolaris
Will Parsons
x86 but can't seem to start it. According to the documentation, one should
be able just to type "VirtualBox" in a terminal window, but when I do this
I get:
uid: Undefined variable
Unknown application - .
Am I missing something obvious?
--
Will
Thommy M.
There's a menu item for it in Applications I think, or somewhere...
Oscar del Rio
Applications - System Tools - Sun VirtualBox
Will Parsons
Tried that. Nothing happened. Presumably, it failed for the same reason
that starting it in a terminal window fails - except I can't see the error
messages.
--
Will
hume.sp...@bofh.ca
> uid: Undefined variable
> Unknown application - .
>
> Am I missing something obvious?
Nothing obvious that I can see. What does 'which VirtualBox' tell you?
Which version of OpenSolaris?
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
Dick Hoogendijk
> Tried that. Nothing happened. Presumably, it failed for the same
> reason that starting it in a terminal window fails - except I can't
> see the error messages.
Did you reboot? It's weird and maybe not wanted, but vbox needs a reboot
to load the kernel drivers. I know it shouldn't, but hey..
--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
+http://nagual.nl/ | SunOS 10u7 05/09 ZFS+
Ian Collins
> quoting Will Parsons (27 Jun 2009 00:59:40 GMT):
>
>> Tried that. Nothing happened. Presumably, it failed for the same
>> reason that starting it in a terminal window fails - except I can't
>> see the error messages.
>
> Did you reboot? It's weird and maybe not wanted, but vbox needs a reboot
> to load the kernel drivers. I know it shouldn't, but hey..
That's news to me and I've installed and run it on a dozen servers!
--
Ian Collins
Dick Hoogendijk
> Dick Hoogendijk wrote:
>> Did you reboot? It's weird and maybe not wanted, but vbox needs a
>> reboot to load the kernel drivers. I know it shouldn't, but hey..
>
> That's news to me and I've installed and run it on a dozen servers!
Were those servers running OpenSolaris?
On S10 and Nevada a reboot is not necessary.
It might be something in the IPS? No idea, but when you install the vbox
packages from the repo and try to start VirtualBox it does _not_ work.
Note: haven't tried this lately. Experience comes from 2.2.0 and before.
Always rebooted since than. It might have been resolved.
Ian Collins
> quoting Ian Collins (Sat, 27 Jun 2009 20:25:48 +1200):
>> Dick Hoogendijk wrote:
>>> Did you reboot? It's weird and maybe not wanted, but vbox needs a
>>> reboot to load the kernel drivers. I know it shouldn't, but hey..
>> That's news to me and I've installed and run it on a dozen servers!
>
> Were those servers running OpenSolaris?
> On S10 and Nevada a reboot is not necessary.
Ah, all were Solaris 10 or Nevada.
--
Ian Collins
Will Parsons
> quoting Will Parsons (27 Jun 2009 00:59:40 GMT):
>
>> Tried that. Nothing happened. Presumably, it failed for the same
>> reason that starting it in a terminal window fails - except I can't
>> see the error messages.
>
> Did you reboot? It's weird and maybe not wanted, but vbox needs a reboot
> to load the kernel drivers. I know it shouldn't, but hey..
I hadn't, but when I attempted this, the boot process hung with a message
about not being able to load a kernel module. (Unfortunately, I didn't jot
down the exact message, but I think vboxusbmon was the culprit). I've
managed to recover for the time being by booting into failsafe mode and
renaming every file under /platform/i86pc/kernel/drv that begins with
"vbox", after which I was able to reboot normally. I'll investigate
further when I can.
--
Will
Nomen Publicus
Sounds like corrupt driver files or possibly incorrect drivers for the
platform?
--
Church: Local branch of The International House of Myths
Dick Hoogendijk
> Will Parsons <w...@nodomain.invalid> wrote:
>> Dick Hoogendijk wrote:
>>> Did you reboot? It's weird and maybe not wanted, but vbox needs a
>>> reboot to load the kernel drivers. I know it shouldn't, but hey..
> Sounds like corrupt driver files or possibly incorrect drivers for the
> platform?
In addition to this: a reboot is not needed on OpenSolaris either -IF-
you install the svr4 pkg from the VirtualBox site. The post-install of
these packages loads the needed kernel drivers :-)
The IPS package does not, however. So it's a culprit on IPS
installation. Hope it'll be solved when 3.0 comes in the repo.
Will Parsons
Since my initial attempt at installing VirtualBox, I've retried again with
version 3.0.0 that has just been released, but the postinstall fails:
# pkgadd -d VirtualBox-3.0.0-SunOS-r49315.pkg
....
## Executing postinstall script.
Loading VirtualBox kernel modules...
devfsadm: driver failed to attach: vboxdrv
Warning: Driver (vboxdrv) successfully added to system but failed to attach
can't load module: Invalid argument
## Aborting due to attach failure.
## Loading failed. Aborting installation.
pkgadd: ERROR: postinstall script did not complete successfully
Output of uname -a is:
SunOS beech 5.11 snv_55b i86pc i386 i86pc
Any idea of what's wrong?
--
Will
Gary R. Schmidt
[SNIP]
> Output of uname -a is:
> SunOS beech 5.11 snv_55b i86pc i386 i86pc
>
> Any idea of what's wrong?
>
numbers that I have missed?
I would try something more recent, either a current Nevada, the latest
OpenSolaris, or Solaris 10u7.
Cheers,
Gary B-)
Douglas Kweku Nyamekye Gaisie
hi there,
i had some problems when i want to run virtualbox on opensolaris,
luckily, i was able to solve it by installing it. follow the steps in
the links below.
you might want to look at this link there is a help for you there
http://blogs.sun.com/JoeBonasera/entry/using_the_virtualbox_hypervisor_on
http://blogs.sun.com/manoj/entry/indiana_preview_2_and_virtualbox
Douglas Kweku Nyamekye Gaisie
hi there,
Douglas Kweku Nyamekye Gaisie
hi there,