virtualbox guest additions don't start on moblin2.1 and openSUSE 12.1 -> fixed as of 28 Sept 2011

[timeless]

1. download ​http://mirrors.kernel.org/moblin/releases/2.1/images/moblin-2.1-final-20091103-002.img
2. create an openSUSE (x86) vm
   • 512mb
   • 1 cpu
   • vt-x/amd-v enabled
   • nested paging enabled
   • 12mb video
   • 3d accel disabled
   • 2d accel disabled
   • 8gb vdi (growing)
   • floppy empty
   • cdrom=moblin-2.1-final-20091103-002.img
3. boot the vm, and install to your hard disk
4. power down the vm
5. change the cdrom to "empty"
6. power it up and press alt-f1 immediately after the virtualbox screen appears
7. "e" (edit); <down>; "e" (edit)
8. replace everything from "quiet" to the end with "3"
9. <enter>; "b" (boot)
10. this should boot you to a text mode
11. log in and use sudo su -
12. edit /etc/grub.conf to apply the change from step 8 permanently
13. edit /etc/inittab to change the default mode to 3: 'id:3:initdefault:'
14. yum install gcc make kernel-netbook-devel
15. from virtualbox select install guest additions
16. mount /dev/cdrom /media
17. /media/VBoxLinuxAdditions-x86.run
18. reboot

actual results:

rc.vboxadd-service doesn't work, it complains it can't find "daemon"

expected result:

rc.vboxadd-service should treat moblin like redhat (well, i was told by a moblin-ish person to do this, and it worked).

[timeless]

patch

[Freek de Kruijf]

Not only in moblin but also in openSUSE 12.1 M5 the same problem exists. The same patch would work for any openSUSE version, because /var/run/ always exists, where /var/lock/subsys/ does not exist in 12.1. Creating it also solves the problem, but I have read somewhere that /var/lock is meant not to be used for storing a pid. In openSUSE there are many applications/daemons that store their pid in /var/run/. Maybe the filename should be /var/run/vbox-service.pid.

[Michael Thayer]

Both the openSUSE problem and the original (Moblin 2.1 is no longer very relevant, but the fix might apply to other systems too) are now fixed and the fix will be present in any future 4.1 or later releases.

[Frank Mehnert]

VBox 4.1.4 contains the fix.