VirtualBox 3.1 for kernel 2.6.30.5 (puppy 4.3)

[JohnSnyder]

How do I get the VirtualBox host file system to automatically mount at startup? Into which startup file do I place the mounting instructions?

[Later...Perusal of the Internet resulted in finding a suggestion to place the mount command in the /etc/rc.d/rc.local file. Guess what! It works!]

[gray]

Updated to Virtualbox 3.1 - see main post

[pavl]

Hi all!

Using Puppy 4.3.1 I am trying to install Virtual Box the way Gray descibes.

After installing the menulink is there, but it's not working. When starting from a terminal the reply is:

VirtualBox: supR3HardenedMainGetTrustedMain: dlopen ("opt/VirtalBox/VirtualBox.so",) failed: libGLU.so.1: cannot open shared object file: No such file or directory

I read that I should change the rights to /opt/VirtualBox and so I did. But to no avail and I cannot find another solution online.

Does any of you have an idea?

Thanks in advance,

Paul

[gray]

Looks like the latest version of Vbox has a new dependency - OpenGL. Didn't spot that as I already have the nvidia drivers (& hence OpenGL) already installed. If you have an nvidia graphics card install the nvidia drivers. Alternatively install the following pet for the mesa GL libs.

ftp://distro.ibiblio.org/pub/linux/dist ... -7.3-1.pet

[pavl]

Did the trick!

Thanks Gray!

[Mixael]

gray,
I am very grateful for your work on the VirtualBox pet. I'm using Puppy as the host machine, and created a DOS virtual with it. I was able to setup DOS 6.22, along with a DOS application program I wanted to run. Everything works including the application program until I decide to use the serial port for the application program which is required for it to do its job. That's when the virtual machine won't start unless I disable the comm port in the VirtualBox settings. In searching the various sites, seems like I'm not the only one with serial port issues on VirtualBox (although others with problems are usually USB/Serial adapters). I'm hoping you might have some ideas; here's where I'm at:

Checking that the port is OK from the Puppy side:

Code: Select all

dmesg | grep ttyS0
serial8250: ttyS0 at I/O 0x3F8 (irq=4) is a 16550A
00:09: ttyS0 at I/O 0x3F8 (irq=4) is a 16550A

Settings for VirtualBox Serial Port:

Code: Select all

Enabled
Com1
HostDevice
/dev/ttyS0

When I try to start the DOS virtual machine, i get

Code: Select all

Failed to open host device
/dev/ttyS0 (VERR_FILE_NOT_FOUND)
Unknown errorcreating VM(VERR_FILE_NOT_FOUND).

Under the error code details:

Code: Select all

Result Code:NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: |Console{  lot of numbers here which I haven't typed in }

It may have had no impact in Puppy's single user setup, but based on some posts I read I even tried adding a group named vboxusers, and then manually edited the file /etc/group to add the user root in the line that was appended to the end of the file after I'd added the group. The line looked like:

Code: Select all

vboxusers:x:1001:root

I also executed the command

Code: Select all

chmod a+rw /dev/vboxdrv

I rebooted, tried starting the DOS virtual machine again, but got the same error. Any ideas?

[TheAsterisk!]

Both of the PETs for version 3.1.0 are available, but the link to the compressed guest additions ISO returns a 404 error, as does trying to get at it by navigating in from puppylinux.ca and .asia.

@gray: Why don't you just link to the ISOs here, buried in the VirtualBox site? I'd think that's easier than compressing 'em and hosting them yourself.

These VirtualBox PETs you package up so nicely are wonderful, by the way. Thanks for the time spent!

[Mixael]

I think I've figured out the serial port issue when using VirtualBox serial ports on a Puppy host. I'll confirm it after I test the actual application, but the VirtualBox client I have running DOS/WFW will now start up when I enable the serial port. After much unneccessary reading about pipes, dev/ttyS0, mkfifo, and socat it turned out all I needed was one command issued BEFORE the VirtualBox application is started (not just the client in VirtualBox). I've appended the following line to the file /etc/rc.d/rc.local to ensure it is executed on bootup.

Code: Select all

setserial /dev/ttyS0

[Mixael]

The serial port does indeed function with that change. I've documented the entire process to setup a DOS/WFW client at
www.murga-linux.com/puppy/viewtopic.php?t=51317

[davidwillis]

I am trying to install 3.1.4 and I get this

[Revolverve]

Thanks , a real time saver for me ,installation is faster for M$ $ht OS...I was keeping a Vi$ta partition on my laptop,well , 2 partitions...for convenience 2 or 3 time a year...even thru those very few needs , I manage to got it corrupted!!!!!
Grrrr...I will now flush those...half relief...

Was a long time since I have installed Virtualbox ,it support 3d acceleration now
or a kind of .. anyway..I dont play game.

Would have love to find a sfs for 431...if possible... but the pet roll fine!!!

Thanks again..
Virtualbox rock!!!!
Puppy rock!!!!

[volkanos666]

I install Virtual Box on my 1000ha for running WinXP, all work fine but I don't have keyboard on full screen (any keys works).

Any have idea??

[cosworth88]

excuseme i can't download becouse i haven't got user and password...
someone could help me please??

[TheAsterisk!]

excuseme i can't download becouse i haven't got user and password...
someone could help me please??

When in doubt with Puppy Linux sites, use "p u p p y" and "l i n u x" as your username and password, minus the quotes and the spaces.

Additionally, a couple of the previously posted links seem to be dead, so just go to http://www.puppylinux.asia/tpp/NOP/ and select the most recent version listed there (which I think would be 3.1.4).

[cosworth88]

thanks for the password!
when i try to start the virtual box i receive an error message

Code: Select all

RTR3Init failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/etc/init.d/vboxdrv setup'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

what i have to do?? i'm using lucid puppy
someone could help me please? ;(

[TheAsterisk!]

thanks for the password!
when i try to start the virtual box i receive an error message

Code: Select all

RTR3Init failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/etc/init.d/vboxdrv setup'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

what i have to do?? i'm using lucid puppy
someone could help me please? ;(

That's most likely because the VirtualBox packages in this thread are built for Puppy 431 and its kernel version 2.6.30.5. Lucid Puppy (500 or 501) uses a newer kernel, so it can't use these particular packages.
I'll look around a bit, and see if there's already a package for Lucid Puppy or not, and then I'll edit this post accordingly.

EDIT: Well, I can't find a package for Lupu, but if you want there is one for Lighthouse Pup 500. It has the same kernel version as Lupu, but is an Spup (I think), so I don't know if the package would work with Lupu, but it definitely works with LightousePup (as intended). Just something to consider.
There was mention in one of the main Lupu threads that a VBox package might be developed. I've no idea when that'll happen, though.
Otherwise, Oracle distributes a *.run installer for VBox that you can try out. It's over here.

[TheAsterisk!]

Sorry. Accidentally double-posted.

[gronos04]

You will need the correct devx and kernel sources for your puppy version.
For lupu there is no kernel sources at this point.
There is a "wary kernel sources" for the same kernel but there is a disparity in the gcc version that it was compiled on and it doesn't work with VBox in lupu.
So if you would like to run VBox then you will need to choose another puppy version.
Download the latest .run version from VBox
Load devx
Load kernel souces for your kernel
to find kernel version, in terminal [ uname -r ]
SDL pet
QT pet
ftp://distro.ibiblio.org/pub/linux/dist ... -7.3-1.pet
in terminal [ adduser -D -H vboxusers ]
run the VBox.run.
That should do it.
Good luck

[TheAsterisk!]

You will need the correct devx and kernel sources for your puppy version.
For lupu there is no kernel sources at this point.

No, there is a kernel source SFS for Lucid Puppy. It's right here.

Download the latest .run version from VBox
Load devx
Load kernel souces for your kernel
to find kernel version, in terminal [ uname -r ]
SDL pet
QT pet
ftp://distro.ibiblio.org/pub/linux/dist ... -7.3-1.pet
in terminal [ adduser -D -H vboxusers ]
run the VBox.run.
That should do it.
Good luck

Point is, the packages in this thread still won't work, as they were made on and for Puppy 430 and 431 with kernel 2.6.30.5.

[gronos04]

That was the one I was referring to.
The VBox install log is helpful.
Go vanilla and get it working might be a good approach. Then go back and have another go on lupu.