Fedora 16 as VirtualBox guest

[Palooka]

Hi,

I have Fedora 16 (kernel 3.1.0-0.rc4.git0.0.fc16.x86_64) installed in a VirtualBox VM (Version 4.1.2 r73507 from the VirtualBox site). The host is also Linux.

The Guest Additions compile and install successfully, except that I see the following message:

Warning: unsupported pre-release version of X.Org Server installed. Not installing the X.Org drivers

I am guessing that this is the reason my screen resolution does not follow resizing properly, and that mouse integration does not work. I notice that there is no /etc/X11/xorg.conf.

Is this assumption correct? And is there a workaround?

Thanks,
Palooka

[skytux]

I also have the same problem, and I don't know a workaround, but you don't need an xorg.conf file. And yes, that is the reason you don't get full screen in your virtual machine.

Germán.

[kkshethin]

I have similar error. Difference is gnome 3 gnome-cell is not working. falls to fallback mode.

[Dutchy]

We probably need to wait for updated guest additions.

[meanpt]

Same problem here with F16 alfa updated daily, on the 4.0.12. On Fedora 15 and Ubuntu 11.10 guest additions installs fine and Gnome shell 3 works on both.

[AdamW]

F16 uses a newer version of X compared to F15 and Ubuntu 11.10, and Oracle haven't updated VBox Guest Additions to build against the newer X yet. Not much you can do but wait on Oracle.

[meanpt]

Now with the VB 414 guest additions supporting xorg 1.11, I can't still open a gnomeshell 3 desktop and I'm still left in the fallback mode, despite already getting a full screen with the correct resolution.

So, how can I have this thing working?

[cazo]

Opening a terminal window & entering:

gnome-shell --replace &


works. However, like you, I still can't get gnome to start in 'standard experience' even after a reboot.

[meanpt]

Thanks. I wonder why this still happens. I tried it with your tip. Looks nice ot have gs3 running. But It gets really messy and everything freezes - not a good experience:

[meanpt@fed16AVB ~]$ gnome-shell --replace &
[1] 1670
[meanpt@fed16AVB ~]$ Gtk-Message: Failed to load module "pk-gtk-module"
Window manager warning: 0 stored in GConf key /desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
OpenGL Info: Using XSHM for GLX_EXT_texture_from_pixmap
Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Faile d: An authentication agent already exists for the given subject
Window manager warning: Log level 16: Error registering polkit authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Faile d: An authentication agent already exists for the given subject (polkit-error-quark 0)
JS LOG: GNOME Shell started at Tue Oct 04 2011 20:38:35 GMT+0100 (WEST)
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0xb764f860
OpenGL Warning: Retry with 0x8002 returned 0 visuals

[AdamW]

none of those look like fatal errors to me...

[mightyvoid]

You need to install Virtualbox 4.1.4, works for me.

[mr.erdk]

I've dig through logs and find this:
fedora setroubleshoot: SELinux is preventing /usr/libexec/gnome-session-check-accelerated-helper from execute access on the file /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so. For complete SELinux messages...

Apparently it's VirtualBox Driver/SELinux problem. After:

# grep gnome-session-c /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
and rebooting system everything work like a charm :)

[meanpt]

Hi, mr.erdk

Seems the problems here between VBox and Selinux are worse and bigger than the one you report. Went to the logs of Selinux, applied all the troubleshooting listed there and still don't get gnome shell 3 working. I hope developpers can take care of this in the next release candidate for the release candidate. These are the things where selinux needs some fixing:

SELinux is preventing /usr/libexec/gnome-session-check-accelerated-helper from execute access on the file /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so.

Plugin: restorecon
SELinux denied access requested by gnome-session-c.
/opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so may be a mislabeled.
/opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so default SELinux type is
textrel_shlib_t, but its current type is usr_t. Changing this file back to the
default type, may fix your problem.

File contexts can be assigned to a file in the following ways.

* Files created in a directory receive the file context of the parent
directory by default.
* The SELinux policy might override the default label inherited from the
parent directory by specifying a process running in context A which creates
a file in a directory labeled B will instead create the file with label C.
An example of this would be the dhcp client running with the dhclient_t type
and creating a file in the directory /etc. This file would normally receive
the etc_t type due to parental inheritance but instead the file is labeled
with the net_conf_t type because the SELinux policy specifies this.
* Users can change the file context on a file using tools such as chcon, or
restorecon.

This file could have been mislabeled either by user error, or if an normally
confined application was run under the wrong domain.

However, this might also indicate a bug in SELinux because the file should not
have been labeled with this type.

If you believe this is a bug, please file a bug report against this package.If you want to fix the label.
/opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so default label should be textrel_shlib_t.
you can run restorecon.
# /sbin/restorecon -v /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so


SELinux is preventing /usr/libexec/gnome-session-check-accelerated-helper from execute access on the file /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so.

Plugin: catchall_labels
you want to allow gnome-session-check-accelerated-helper to have execute access
on the VBoxOGL.so fileIf you want to allow gnome-session-check-accelerated-helper to have execute access on the VBoxOGL.so file
You need to change the label on /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so
# semanage fcontext -a -t FILE_TYPE '/opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so'
where FILE_TYPE is one of the following: dbusd_exec_t, textrel_shlib_t, loadkeys_exec_t, plymouth_exec_t, ssh_agent_exec_t, xauth_exec_t, mount_exec_t, shell_exec_t, rpm_exec_t, pulseaudio_exec_t, pam_exec_t, oddjob_mkhomedir_exec_t, systemd_systemctl_exec_t, fusermount_exec_t, updpwd_exec_t, xdm_tmp_t, chkpwd_exec_t, hostname_exec_t, gkeyringd_exec_t, init_exec_t, shutdown_exec_t, alsa_exec_t, consoletype_exec_t, xdm_exec_t, policykit_auth_exec_t, lib_t, bin_t, lib_t, abrt_helper_exec_t, pam_console_exec_t, ld_so_t, xserver_exec_t, etc_t, systemd_systemctl_exec_t, xsession_exec_t.
Then execute:
restorecon -v '/opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so'



SELinux is preventing /usr/libexec/gnome-session-check-accelerated-helper from execute access on the file /opt/VBoxGuestAdditions-4.1.4/lib/VBoxOGL.so.

Plugin: catchall
you want to allow gnome-session-check-accelerated-helper to have execute access
on the VBoxOGL.so fileIf you believe that gnome-session-check-accelerated-helper should be allowed execute access on the VBoxOGL.so file by default.
You should report this as a bug.
You can generate a local policy module to allow this access.
Allow this access for now by executing:
# grep gnome-session-c /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp




SELinux is preventing /lib/systemd/systemd-logind from unlink access on the file user.

Plugin: catchall
you want to allow systemd-logind to have unlink access on the user fileIf you believe that systemd-logind should be allowed unlink access on the user file by default.
You should report this as a bug.
You can generate a local policy module to allow this access.
Allow this access for now by executing:
# grep systemd-logind /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp



SELinux is preventing /usr/bin/python from read access on the file online.

Plugin: catchall
you want to allow python to have read access on the online fileIf you believe that python should be allowed read access on the online file by default.
You should report this as a bug.
You can generate a local policy module to allow this access.
Allow this access for now by executing:
# grep sealert /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

[mr.erdk]

@meanpt

Hmm, interesting... Are you using fresh install of Fedora 16 Beta, or you updated from alpha release?

[rhatdan]

I've dig through logs and find this:


Apparently it's VirtualBox Driver/SELinux problem. After:

# grep gnome-session-c /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
and rebooting system everything work like a charm :)

This is a labeling problem, No need to add a policy module.

restorecon -R - v /opt

Would fix the labels and then everything should work fine.

---------- Post added at 04:31 PM ---------- Previous post was at 04:29 PM ----------

This is a labeling problem, No need to add a policy module.

restorecon -R - v /opt

Would fix the labels and then everything should work fine.

Not only that but the alert told you exactly how to fix the issue.

[meanpt]

@mr.erdk

@meanpt

Hmm, interesting... Are you using fresh install of Fedora 16 Beta, or you updated from alpha release?

I'm running an updated alfa because the beta can't update due to a maformed disk database ... I just grabed it from the Distrowatch link ...

Edit: problem solved on the Beta not being able to update; instead of choosing "use all the space", I used the installer's second option (don't remember the corresponding text).

I can run GS3 with the trick mentioned before but when logging out or shuttingdown, everything freezes and the virtual machine needs to be closed.on virutalbox.

[Bazu135]

This is a labeling problem, No need to add a policy module.

restorecon -R - v /opt

Would fix the labels and then everything should work fine.
I've tried this, but upon restarting, my VM loads as far as displaying the wallpaper, but doesn't show the login window. At the moment, the cursor is just sat showing the 'loading' status, and has been for about five minutes.

Is this an expected outcome, or has my VM just borked - and if it's the latter, any suggestions as to how I would go about fixing it without a full restart? It was a clean F16 Beta install, with the guest additions installed, if that makes any difference.

[Palooka]

F16 uses a newer version of X compared to F15 and Ubuntu 11.10, and Oracle haven't updated VBox Guest Additions to build against the newer X yet. Not much you can do but wait on Oracle.

Thanks. Yes, it works perfectly now with VirtualBox 4.1.4 on the host, and the corresponding Guest Additions in the Fedora 16 guest.

Palooka

[Dutchy]

I've tried this, but upon restarting, my VM loads as far as displaying the wallpaper, but doesn't show the login window. At the moment, the cursor is just sat showing the 'loading' status, and has been for about five minutes.

Is this an expected outcome, or has my VM just borked - and if it's the latter, any suggestions as to how I would go about fixing it without a full restart? It was a clean F16 Beta install, with the guest additions installed, if that makes any difference.

I had to install the latest updates or it wouldn't even let me install them no matter what I tried.
So try to update the system by CLI, reboot, try to logon and look if the guest additions are still enabled.

[Bazu135]

Unfortunately, that didn't fix the issue, so I've had to go for a completely fresh start.

My approach this time has been to run yum update and install guests additions, after which gnome-shell --replace & was able to bring up Gnome Shell, though it still didn't appear at start-up. So I now run this script at start-up:

#!/bin/bash
sleep 5;
gnome-shell --replace &
and I get my Gnome Shell :)

(After all that, I may well end up using LXDE or KFCE anyway, but I want to give Gnome3 a fair chance!)

[chrismurphy]

I am still having this problem with VirtualBox 4.1.6 and Fedora 16 RC5, even after installing Guest Additions. If I set kernel parameter to enforcing=0 the problem, Fallback experience, does not occur and I get Standard experience consistently. If I reboot normally and SELinux is enforcing, I get Fallback experience.

restorecon -R -v /opt

fixes the problem such that I can leave SELinux set to enforcing.

However I'd say roughly 50% of the time on a reboot, I get wallpaper but no login and a circular mouse arrow and nothing happens. If I control-alt-delete to restart gnome-shell, 100% of the time so far I now get a login window.