virtualbox.org

Did an update today and a new kernel was installed... I think 3.1.1-2 from 3.1.1-1 and
the new system will not boot...

I get a signal 15 while udev is doing a mod probe...

Strange thing is that the previous kernel still boots ok...

I erased the newest kernel and updated again with the same problem...

Any suggestions?

Jerr

I saw this as well and am working on finding out why.

This is weird...

Just for the heck of it I stuck a "-S" on the kernel line at the boot screen hoping to get into
single user mode and perhaps do a fsck...

But I did not go into single user mode ( I do not understand how grub 2 works evidently ) but the
rascal booted.

I had to manually run the VBoxLinuxAdditions.run thingee because the auto run did nothing.

I rebooted after the additions and the VM booted again...go figure...

Jerry

A little off topic...

With Fedora 15 I get the Gnome 3 Shell.

With Fedora 16 I get the "Fall Back" Shell.

Does anyone get the Gnome 3 Experience with Fedora 16?

Jerry

Yes. I did that on the last update to Fedora, just before this one. I found that I could turn off the 3D in the guest settings and then boot Fedora and install the guest additions (even though I had dmks installed) and the shutdown turn 3D back on and it worked. This time however it is not working. I even used the Ctrl+Atl+Backspace and that does not shake it loose. Looking at the logs Fedora is doing a lot of debugging when booting and having a really hard time finding the proper gnome.session and also having issues with freedesktop trying got start sessions.

Does anyone get the Gnome 3 Experience with Fedora 16?

Yes and no. I did before this update. That is why I am trying to find what the issue really is.

I finally got F16 to boot in Gnome3 using the (Ctrl+Alt+Backspace) enough times but there is defiantly something wrong in how Fedora is handling the Gnome3 desktop as indicated in the Fedora log files.

Sigh...

I turned off selinux and rebooted and viola, gnome 3 magically appeared.

There appears to some instability in VB....

I specified my home directory on the mac to be a shared directory. Booting the Fedora VM shows
the mac home directory to be mounted under media but if I attempt to copy a file from the
mac directory ( in /media ) to a 'File' window in Fedora, I get a 'splice' error, the icon appears
but no data is transferred.

I note the all of the files in sf_media are owned by root and group vboxsf, I added myself (in fedora )
to the vboxsf group but I still could not copy files *to* the fedora side...

Jerry

I stopped using the auto-mount feature of the shared resources due to the same issue in Fedora and openSUSE.
Seems to be a problem with auto-mount and RPM distros.

Oh well,

I just discovered (again) that VB does not like restoring a 'saved' image from Gnome 3, did not
have that problem when the fallback mode was being used...

Do you know where I can file a bug about some of these problems?

Jerry