virtualbox.org

I recently upgraded my Fedora installation to Fedora 8 as a guest on a Vista host. The VirtualBox guest additions appeared to install successfully, but after rebooting the guest, mouse integration and other additions features didn't seem to be working. Previously on Fedora 7 the additions were working great.

Does anyone else have this problem, or a workaround?

Thanks,
David

VirtualBox 1.5.2 on a Windows Vista host with Fedora 8 (upgraded from 7 by yum) guest (kernel 2.6.23.1-42.fc8 #1 SMP).

http://forums.virtualbox.org/viewtopic.php?t=2480

Check this.

Thanks for pointing out that forum thread. I checked and the vboxadd and vboxvfs services are indeed running, and I am able to access the host filesystem through Shared Folders. Unfortunately the mouse integration does not appear to be working. I tried restarting the X server (ctrl-alt-backspace) and couldn't find the RUN_PARALLEL option mentioned in the thread (is that SuSE-specific?).

Is Xorg reconfiguring the server somehow? Or is there a way to restart vboxadd after starting X (stopping vboxvfs and running "sudo /sbin/service vboxadd restart" gave an error that the module is in use)?

Looks like someone just posted a bug ticket:
http://www.virtualbox.org/ticket/874

Hi, this will probably need to be manually added whenever a change is made to the xorg.conf from the dialogs, but you could add to the ServerLayout section the Line "InputDevice "VBoxMouse"" and then set the SELinux AVC settings to Permissive and voila Mouse Integration enabled. Hope this helps.

Hi,

Simply setting the policy to 'permissive' and relabeling the files worked for me.

Cheers,
Julien

That works great for me...thanks for posting the workaround. I continue to get SELinux AVC warnings about Xorg accessing vboxadd and a mislabeled device, so maybe the mouse integration had simply to do with SELinux permissions?

It's nice to be able to flip between host<-->guest smoothly again!

To get VirtualBox running in Fedora 8, I first downloaded the VirtualBox rpm VirtualBox-1.5.2_25433_fedora7-1.i586.rpm

I found that the downloaded .rpm had been deposited into /tmp. I cd'd to /tmp
then unpacked/installed it with
Since I had the kernel-dev headers installed, I shortly saw a message that said:

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Success!

I then clicked on KDE Menu-> innotek VirtualBox and the VirtualBox 1.5.2 gui came right up. Just make sure you add your regular "user" to the vboxusers group using KDE Menu->Administration->Users and Groups. then vboxusers properties then click on your normal user to so normal user is a Group Member of vboxusers group ID 501 which should then show up similar to this:

vboxusers 501 normaluser

where normaluser is the normal (not root nor admin) user who normally logs into this PC


You innotek guys and gals are amazing.

If you want to use the additions without disabling SeLinux the solution is on VBox SVN:

http://www.virtualbox.org/browser/trunk ... box_x11.te

This is the policy needed to let X use the required device node. It's actually a bit broad since it allows X to access any device_t (it would be better to create a label for vbox).

Copy the content to a file (vbox_x11.te).

Then you must compile the policy: And install it (as root): (you'll need at least selinux-devel package)

That works undoubtedly well! For those who need a little extra hand-holding (like me), here are some minor details:

-Install selinux-devel if necessary ("sudo yum install libselinux-devel")
-Create a new folder for the vbox_x11 files.
-Copy the contents from Luca's link into a file and name it "vbox_x11.te" (remove line numbers, of course).
-Run the policy compilation command from within the folder, which will create vbox_x11.pp.
-Run "sudo /usr/sbin/semodule -i vbox_x11.pp"

See this link from the .te file for more information:
http://docs.fedoraproject.org/selinux-f ... y-local.te

Mouse pointer integration should now work even with SELinux set to Enforcing mode.

Thanks Luca for pointing out this policy!

Thank you everybody.

You really helped me a lot.

It's nice to be able to flip between host<-->guest smoothly again!