Puppy Linux Guest Additions Error

[HwyChld]

I got the following error in my VBoxGuestAdditions.log file after attempting to install the Guest Additions:

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong int
o /etc/modprobe.d/.
Starting the VirtualBox Guest Additions ...fail!
(Cannot change owner vboxadd:1 for device /dev/vboxguest)
Starting VirtualBox Guest Addition service VirtualBox Additions module not load
ed!

Any ideas why? It appears some functions on working (keyboard is captured and released automatically). If I go full screen and then back to regular than the mouse capture and release works, although not that great. The video support doesn't appear to be working at all, no full size or re-size.

Host: Windows XP
VBox: PUEL 3.2.10
Guest: Lucid Puppy 5.1.1

Thanks for the help.

[HwyChld]

OK, so I have figured out the initial error that I received. For some reason the GA installation script is not able to create the vboxadd system user on my version of Puppy (maybe all Puppies?). So I was able to fix that by adding

Code: Select all

adduser -S -G daemon -u 999 -h /var/run/vboxadd vboxadd

I then reinstalled the guest additions and made it further this time, all the way up to the desktop setup. I then got this error:

Code: Select all

VirtualBox Guest Additions installation, Window System and desktip setup
Could not set up the VBoxClient desktop service.  
To start it at log-in for a given user, add the command VBoxClient-all 
to the file .xinitrc in their home directory

I added this line to the the .xinitrc file but it didn't work. At some point during my debugging I forced the loading of the vboxguest and vboxsf during boot (using the Boot Manager configuration tool). At first this just caused an error during boot due to not having the vboxadd user. Now it boots and loads those modules without error. So I am able to have mouse pointer integration and shared folders working. The only thing that still doesn't work is the resizing of the guest.

I am thinking that when the guest additions are installed it must create a VBoxVideo module, but I can't find this module (otherwise I would force it to load at boot as well).

Anybody have any ideas on how to fix the video aspect of the guest additions?

Thanks

[HwyChld]

This is a little frustrating, but I need to clear a few things up for anybody who tries my suggestions above. I have been switching between a Puppy 4.3.1 guest and a Puppy 5.1.1 guest.

In 4.3.1 I have shared folders running and mouse integration, but no guest re-sizing. In 5.1.1 the only thing I can get working is the shared folders. I would really like to get the mouse integration working and it would be nice to have the guest re-sizing.

[HwyChld]

So I noticed that if I run the vboxadd-service status I get that the service is not running. If I try to start the service I get the following:

Code: Select all

 sh rc.vboxadd-service start
Starting VirtualBox Guest Addition service rc.vboxadd-service: line 255: daemon: command not found
 ...done.

I think this corresponds to the following portion of the script:

Code: Select all

start() {
    if ! test -f $PIDFILE; then
        begin "Starting VirtualBox Guest Addition service ";
        vboxaddrunning || {
            echo "VirtualBox Additions module not loaded!"
            exit 1
        }
        testbinary
        daemon $binary > /dev/null
        RETVAL=$?
        test $RETVAL -eq 0 && echo `pidof VBoxService` > $PIDFILE
        succ_msg
    fi
    return $RETVAL
}

specifically the line: test $RETVAL -eq 0 && echo `pidof VBoxService` > $PIDFILE

So for some reason the VBoxService is not starting. I can verify this by executing:

Code: Select all

# ps aux | grep -v grep | grep VBox
root      7157  0.0  0.7   6124  1960 ?        Sl   16:41   0:00 /usr/bin/VBoxClient --clipboard
root      7168  0.0  0.6   6164  1716 ?        Sl   16:41   0:00 /usr/bin/VBoxClient --display
root      7174  0.0  0.5   6104  1332 ?        Sl   16:41   0:00 /usr/bin/VBoxClient --seamless

I would expect to see another entry in the above output on a fully functional system (/usr/sbin/VBoxService). So if anybody can shed some light on this it would be appreciated.

Thanks