VirtualBox 3.1 for kernel 2.6.30.5 (puppy 4.3)

[fyujj]

Thanks, tim! I'm not in Puppy now but I'll check it.

Edit - oh, my...there's an SDL .pet attached to the first post (facepalm dramatising).

[MatthewBrian]

I have mounted the devx and kernel source, and VirtualBox has successfully installed. But when I want to run a virtual OS (Win XP in this case), an error comes:

Code: Select all

Failed to open a session for the virtual machine Windows XP.
Virtual machine 'Windows XP' has terminated unexpectedly during startup.

> Details
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Machine
Interface: 
IMachine {540dcfda-3df2-49c6-88fa-033a28c2ff85}

Then a dialog box appears whth the title "Error in suplibOsinit". The content of the window :

Code: Select all

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

What should I do with that error?

Thank you.


EDIT: Actually in /etc/init.d there are NO vboxdrv file there.

[gray]

The file in this pet is actually /etc/rc.d/rc.vboxdrv
It is started by the rc.local script in /etc/rc.d
make sure the rc.local script has the line
/etc/rc.d/rc.vboxdrv start

to activate the virtualbox driver at boot up.

[MatthewBrian]

Thanks.

But, when I start the command, it gives me an error.

Code: Select all

# /etc/rc.d/rc.vboxdrv start
Starting VirtualBox kernel module ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why"

# dmesg
..... [a lot of lines] ....
vboxdrv: disagrees about versions of symbol struct_module
vboxdrv: disagrees about versions of symbol struct_module

What happen with that? I can't understand what does it mean.

[Lobster]

I got it working
and I have a 32bit and 64bit area
when I mount the recommended ISO file
m m m now what?
Ideally I would like to boot another Puppy from a virtual box
How? (question as well as greeting)

[VBoxUser]

Hi Gray,

I find your comment very useful:

For puppy guest OS on windows host use the following pet package in the guest puppy OS:

http://www.puppylinux.asia/tpp/NOP/virt ... 6.30.5.pet

You will need to restart your computer / virtual machine after installing the pet(s).

Unfortunately for me i cannot access this link as it requires a user name and password. if u can provide that or different link would really appreciate it!

[MatthewBrian]

Unfortunately for me i cannot access this link as it requires a user name and password. if u can provide that or different link would really appreciate it!

You can see the bottom of this site (http://puppylinux.asia/) for login details.

[VBoxUser]

After some struggling with xorg server at startup i finally managed to install the guest additions.
I had to add also a "vboxadd" user to my system.

Right now i have another problem: the resizing feature does not work properly... It looks that the guest main window is resizing, the screen flickers a couple of times, but in the end all i see is the same size of the guest window.
Have u had this issue?

I am running a Puppy 4.3 on a vista home machine.
kernel 2.6.30.5

thanks

[VBoxUser]

Figured out the problem with resizing: the guest window can be resized but u need to restart the XServer all the time, for each resize....

Is there a way to make resizing in a seamless way? I know Guest additions on ubuntu support this.

Thanks

[chris]

Thanks Gray for the VirtualBox pet. A godsend after I failed to install VBox 3.0.10 manually.

I noticed that after installing the Vbox pet and rebooting, my rc.local file was overwritten by Vbox without my original being backed up first during installation. Not sure if this is "normal" practice and I didn't lose much I couldn't replace but it might be worth adding a note to your opening post about this behaviour in case someone has a more extensive rc.local file.

Now I've got a nice new virtual puppy that I can use for code tweaking without destroying my main pup and without having to reboot into another installation.

Perhaps I could put another virtual pup inside this virtual pup and use that for testing my tweaked code.

I wonder how deep the rabbit hole goes

[chris]

I installed guest additions from the iso. Seemed to go okay but didn't get the mouse integration when I rebooted. Further checking showed that starting of VBoxClient in .xinitrc failed because there is a test inserted the installer that reads:

if 'readline /usr/X11R7/bin/X' == 'Xorg' .

This is a check for a symbolic link. I had no such link in my puppy 4.3.1 installation. Rather is should be /usr/bin/X. Fixed this up, rebooted and now I'm sending this message from puppy 4.3.1 inside puppy 4.3.1 with mouse integration so the virtualpup looks just like another window. Awesome.

[gray]

Updated to Virtualbox 3.0.10 - see main post.

[lenistamx]

¡Hi eveyone!
i'm post the correct link's for Vbox

bye

http://www.puppylinux.asia/tpp/NOP/VBox ... onsIso.tgz
http://www.puppylinux.asia/tpp/NOP/VBox ... md5sum.txt
http://www.puppylinux.asia/tpp/NOP/virt ... 6.30.5.pet
http://www.puppylinux.asia/tpp/NOP/virt ... md5sum.txt
http://www.puppylinux.asia/tpp/NOP/virt ... 6.30.5.pet
http://www.puppylinux.asia/tpp/NOP/virt ... md5sum.txt

[gray]

Updated to Vbox 3.0.12 - see main post

[JohnSnyder]

I'm running Windows 7 Ultimate on my computer. I've installed VirtualBox 3.0.12, and I've now installed Puppy Linux 4.3.1 inside of VirtualBox. Using the VirtualBoxAdditions pet mentioned at the start of this thread, I've installed the Guest Additions.

However, as things stand, I've only gotten the screen portion to work. I am able to resize the screen (and then restart the X-server) in order to get the screen size I desire. However, the mouse integration isn't working. I still have to press the right control key in order to get the mouse out to my host operating system. As a rank beginner in Linux, I don't even know where to start looking for a problem. Any suggestions?

[Later...I compared the /etc/X11/xorg.conf file in someone else's installation with the same file in mine. Turns out my mouse driver was "mouse" and not "vboxmouse" Changing the driver to "vboxmouse" fixed the problem.]

Also, how do I gain access to my host computer's file system? I've listed a shared folder in the VirtualBox configuration, but I don't know how to access it in Puppy Linux. I think I need to "mount" it. Once again, I'd really appreciate any help offered.

[Later...Once again, I found the answer in this forum (http://murga-linux.com/puppy/viewtopic.php?t=45028).

To share files between host and guest:
1. You can either create a new folder on the host to share or you can use an existing folder.
2. Right-Click the folder icon in the tray at the bottom right corner of VirtualBox, Click the Add New Shared Folder icon and navigate to a folder to share on the host machine; VirtualBox will provide a "sharename" to refer to that folder (or you can make your own sharename, for instance, Puppy).
2. Then create a folder in puppy (for instance, /mnt/Puppy) to mount the host file on.
3. Use this command in a terminal to mount the host folder in Puppy: "mount -t vboxsf sharename mountingpoint" (for instance, mount -t vboxsf Puppy /mnt/Puppy)]

Thanks.

[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!