top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Fedora 23 and VirtualBox: VBox Guest Additions not working properly

+2 votes
2,243 views

I have just upgraded to 23 from 22 in a virtual machine using dnf as described in the Fedora Wiki, which went rather smoothly for me.

After manually installing the Guest Additions, the features "seemless windows" and "automatic resize of the guest desktop" don't work (the respective options in the views menu are greyed out).

The VBox kernel modules are built ok, but I get a warning saying: "unsupported pre-release version of X.Org server installed. Not
installing the X.Org drivers."

The X log says that there is X.Org X Server 1.17.99.902 installed, which is a pre-release. I guess downgrading might cure the problem, but how?

Any advice?

posted Nov 5, 2015 by Anderson

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
Are you using VirtualBox from the virtualbox repos or from rpmfusion?  I'm using the VirtualBox repo version (Oracle version) and it's working for me.
commented Nov 5, 2015 by Garima Jain
I am using the VBox repo version as well (to be precise:  VirtualBox-5.0-5.0.8_103449_fedora22-1.x86_64).
commented Nov 5, 2015 by anonymous

Similar Questions
+1 vote
Virtualbox guest additions kill X in Ubuntu

I had Ubuntu 12.04 installed in Virtualbox which ran OK, if a bit slow, until recently when I did a bunch of updates. As is usually the case after kernel updates, I had to reinstall the guest additions to get
back full screen and auto-resize. However, what I got instead when I restarted, was the following message:

"The system is running in low graphics mode Your screen, graphics card and input device settings could not be detected correctly. You will need to configure these yourself"

It then drops into a menu with buttons where most of the options don't seem to work and eventually bring me to a command line login. I've tried a complete reinstall followed by an upgrade to 12.10 but
again the installation of guest additions bring me to the same point If the graphics settings can be configured I'll need some advice on how to go about it

I don't think I can provide log output as cutting/pasting between guest and host no longer functions.

This is Virtualbox 4.2.12. The kernel is 3.2.0-43-generic-pae i686

+1 vote
Can not start VirtualBox on Fedora19

I am getting the error message below on a Fredora 19 system when attempt to start VirualBox Any help will be greatly appreciated :

Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' as root.

+7 votes
Controlling VirtualBox machine settings from guest system

As I found from documentation and source code, theres no possibility to modify machine settings from guest system.

I want to patch VB to treat certain guestproperties as settings - hence well have ability (using VBoxControl) to change RAM amount for example, from guest system (now instantly of course, but after reboot).

Do I think right way about guestproperties? Maybe there exists some more appropriate way to do it?

+2 votes
Accessing serial port output of guest OS in VirtualBox in Mac

I am using VirtualBox in Mac OSX. I have a guest OS that writes to serial port. I want to view the output on the serial port. Since I do not have physical COM1, I have enabled host-pipe to write to a local domain socket. What tool can I use to view the serial port output?

+1 vote
How to shut down a fedora 20 virtual machine?

I am currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, I selected "Virtual Machine" -> "Shut Down" -> "Shut Down".

Where it *looks* like the VM shuts down, but the VMM window shows "f20 Running"

Should I expect a different result? I was expecting the VMM window to show that that VM was Stopped or something.

...