Leap 42.1 and Virtualbox 5.0.18

English Virtualization
#1

Upgrading to Virtualbox 5.0.18 makes openSUSE Leap 42.1 fail to load a graphical screen, and results in a blank black screen. Terminai access is fine, but there is no GUI session. This has only happened since 5.0.18. Upgrading the guest additions to the Virtualbox supplied 5.0.18 version has no effect. Furthermore, the screen size is limited to 640x800 (or whatever - about that).

Any ideas?

Andrew

#2

Everything OK here with the upstream (Oracle) 5.0.18 version with matching Extension pack and Guest Additions: something crippled in your configuration?

#3

I had a similar issue and I hope I can help.

After many trial and error changes I finally pinpointed to the settings option on the host. By changing the option ‘system->acceleration->paravirtualization interface’ to legacy the problem disappeared.

Cheers

Jerome

#4

I’m seeing the same issue too . Using a Windows 7 64-bit host OS and Linux 64-bit OpenSuse Leap.
After upgrading Virtualbox to I can’t seem to get the auto-resize to work even after getting the guest additions installed. Initially I didn’t
have the kernel headers and make utilities , and got it installed.

Also I changed the para-virtualization to “Legacy” from “Default”, it didn’t help either. I think something else if wrong.

Anytime we update the VirtualBox software, we recompile the VirtualBox guest additions and it works fine. Not sure
about the problem with OpenSuse, since this is a very basic step.

Thanks

#5

Pls verify whether what you’re seeing is the same as what I’ve already reported to bugzilla.
https://bugzilla.opensuse.org/show_bug.cgi?id=976965

  1. If this is an upgrade of an existing Guest VM, the problem is more clear. If this is a brand new Guest VM, you may not be able to verify the same way I did my troubleshooting.
  • On any Guest, inspect the Guest Additions or Tools before you upgrade. Or, if you have any Guests which have not yet been upgraded, determine the version <before> upgrading. How you do this determined by the virtualization you’re using.
  • On any Guest <before> upgrading, run the following to get the kernel version
uname -a
  • Run the same tests determining the kernel and Additions/Tools version <after> upgrading and compare.
  1. I found the problem appeared in VMware. Your post is about Virtualbox. I haven’t yet investigated Virtualbox, but the problem <may> be the same.

Anyone who determines that their auto-fit does not work should add to the bug I posted above, be sure to describe the Additions or Tools versions and the kernel versions of your Guests.

TSU

#6

The got reproduces after VirtualBox upgrade from 5.0.16 -> 5.0.18 . The kernel version is Linux linux-rb30.suse 4.1.20-11-default.
I didn’t see any errors while compiling the guest addition kernel modules.

Compilation logs :

Verifying archive integrity… All good.
Uncompressing VirtualBox 5.0.18 Guest Additions for Linux…
VirtualBox Guest Additions installer
Removing installed version 5.0.18 of VirtualBox Guest Additions…
Removing existing VirtualBox non-DKMS kernel modudone
Copying additional installer modules …
Installing additional modules …
Removing existing VirtualBox non-DKMS kernel modudone
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module done
Building the shared folder support module done
Building the graphics driver module done
Doing non-kernel setup of the Guest Additions done
You should restart your guest to make sure the new modules are actually used

Press Return to close this window…

Below is from the dmesg logs :
r@linux-rb30:~/Desktop> dmesg | grep -i vbox
0.000000] ACPI: RSDP 0x00000000000E0000 000024 (v02 VBOX )
0.000000] ACPI: XSDT 0x000000007FFF0030 00003C (v01 VBOX VBOXXSDT 00000001 ASL 00000061)
0.000000] ACPI: FACP 0x000000007FFF00F0 0000F4 (v04 VBOX VBOXFACP 00000001 ASL 00000061)
0.000000] ACPI: DSDT 0x000000007FFF0470 002106 (v01 VBOX VBOXBIOS 00000002 INTL 20100528)
0.000000] ACPI: APIC 0x000000007FFF0240 000054 (v02 VBOX VBOXAPIC 00000001 ASL 00000061)
0.000000] ACPI: SSDT 0x000000007FFF02A0 0001CC (v01 VBOX VBOXCPUT 00000002 INTL 20100528)
1.193940] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
1.194462] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK 1.0 PQ: 0 ANSI: 5
1.506195] vboxguest: misc device minor 58, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
1.506197] vboxguest: Successfully loaded version 5.0.16_SUSE (interface 0x00010004)
1.512749] [drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0
1.738344] ata3.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133
1.738990] scsi 2:0:0:0: CD-ROM VBOX CD-ROM 1.0 PQ: 0 ANSI: 5
5.728420] vboxsf: Successfully loaded version 5.0.18 (interface 0x00010004)
6.766967] VBoxService 5.0.18 r106667 (verbosity: 0) linux.amd64 (Apr 18 2016 15:31:59) release log
6.767168] 00:00:00.000293 main Executable: /opt/VBoxGuestAdditions-5.0.18/sbin/VBoxService

Not sure why it still says “vboxguest: Successfully loaded version 5.0.16_SUSE” , though its for the 5.0.18 virtual box additions.

r@linux-rb30:~/Desktop> lsmod | grep -i vbox
vboxsf 49152 0
vboxguest 299008 5 vboxsf
vboxvideo 16384 0
drm 385024 2 vboxvideo

The “Used By” field reports as 0 for some reason for the vboxvideo module , not sure why.

Is there some other way of installing the guest additions on OpenSUSE. I’m new to the distribution , please guide.

Thanks.

#7

I assume you installed virtualbox from the openSUSE repos and not from the Oracle Virtualbox website.

If so, you should post the version of Virtualbox you currently have installed, run the following command in a console

zypper info virtualbox

The reason why it’s important to check your current virtualbox version is because Guest Tools and Additions 5.18 should only be applied to Virtualbox 5.18, not to 5.16.

TSU

#8

The host is a Windows 7 machine and the guest is OpenSUSE Leap 42.1 distribution.

This is the output as requested.
$ zypper info virtualbox
Loading repository data…
Reading installed packages…

Information for package virtualbox:

Repository: Main Update Repository
Name: virtualbox
Version: 5.0.16-13.1
Arch: x86_64
Vendor: openSUSE
Installed: No
Status: not installed
Installed Size: 30.0 MiB
Summary: VirtualBox is an Emulator
Description:
VirtualBox is an extremely feature rich, high performance product
for enterprise customers, it is also the only professional solution
that is freely available as Open Source Software under the terms of the
GNU Public License (GPL).

The problem is that the “Auto-resize guest display” is greyed out even after installing the guest additions from the mounted CD within the OpenSUSE VM. I’ve never faced anything similar in any of the other
distributions , so not sure why it should be different for OpenSUSE.

Below is the log from a manual compilation of GA :

./VBoxLinuxAdditions.run
Verifying archive integrity… All good.
Uncompressing VirtualBox 5.0.20 Guest Additions for Linux…
VirtualBox Guest Additions installer
Removing installed version 5.0.20 of VirtualBox Guest Additions…
Removing existing VirtualBox non-DKMS kernel modules done
Copying additional installer modules …
Installing additional modules …
Removing existing VirtualBox non-DKMS kernel modules done
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module done
Building the shared folder support module done
Building the graphics driver module done
Doing non-kernel setup of the Guest Additions done
You should restart your guest to make sure the new modules are actually used

#9

Post:

zypper se -si vbox virtualbox
#10

First, it should be known that over the past 48 hrs or so, Virtualbox released another version, 5.0.20.

The virtualbox version I requested actually should be the main app, so should be Host and since you’re running on Windows, you won’t be able to get a package rpm info. Instead, you would open from the menu bar
Help > About Virtualbox…

So, your Virtualbox app might be 5.0.16, 5.0.18 or 5.0.20 depending on when you installed Virtualbox, today you should update to 5.0.20.

The Virtualbox Extensions should be the same version as your Virtualbox app, so again should likely be 5.0.20. To inspect your Extensions version, again from the menu bar
File > Preferences > Extensions

Now, the Guest Additions which are installed within <each> Guest (not on the Host). It seems that VBox currently is experiencing some confusing version mis-matches, it should be known that Guest Additions 5.0.16 seems to be the version for VBox versions 5.0.16, 5.018 and 5.0.20.

So, it seems that if you have a problem with Guest Additions, at the moment if you updated Guest Additions relatively recently in the Guest, the most you’re likely going to be able to do to fix any anomalies is to force re-installing the Guest Additions.

Now, regarding the inability to auto-fit the Guest display whenever the overall window is re-sized…
IMO the easiest way to verify whether you’re seeing the same bug I reported for VMware…

  1. You must verify the kernel version <before> you do a kernel upgrade (or any other action like re-installing Guest Additions). You can get your kernel version by running the following command. And, of course verify that you <don’t> have the autofit problem. Re-size the window and the Guest display inside should automatically re-size to fill the newly re-sized window (default setting).
uname -r
  1. Now you can upgrade your kernel, most likely simply by updating your system
zypper up
  1. Now, verify that the display auto-fit problem has appeared. Re-size your window but the Guest display inside will stay the same as before and will <not> re-size to fit the window. Now, verify that
  • The VBox application on the Host has not changed since you ran “zypper up” in the Guest.
  • The VBox Extensions has not changed.
  • The Guest Additions has not changed… Although if you have DKMS installed, your VBox Guest kernel modules almost certainly have been re-built because of the kernel upgrade. Or, if you want to be absolutely certain your Guest Additions should be working, don’t take the kernel module re-build for granted, re-install Guest Additions.
  • Run “uname -r” again to verify that the only significant change has been the updated kernel.

TSU

#11

FYI =
Running a VBox 5.0.18 (I’m about to upgrade to 5.0.20),
A LEAP Guest with Guest Additions originally installed from Oracle, fully updated is able to auto-fit (re-size) its display.

So,
No problem at least with that combination.

TSU

#12

After upgrading to VBox 5.0.20 (with same version Extensions installed),
And running a LEAP Guest(fully updated) with Guest Additions 5.0.16 (using the iso downloadable from VBox but should also be included in any VBox install),

No auto-fit issue is seen.
You can “Full Screen” the Guest window and the display auto-fits (expands) to fill the window.

So, if anyone is still seeing an auto-fit problem running a current version of VBox 5.0, it’s not normal.

TSU

#13

Important update for anyone who has updated to Virtualbox 5.0.20 (as this OP seems to have done)…

Upon further investigation and despite what you might see on the Oracle VBox Downloads page, Guest Additions 5.0.16 is not fully functional.

VBox 5.0.20 when installed ships with VBox Guest Additions 5.0.20 which will provide full Guest Additions functionality.

Full Instructions to install Guest Additions 5.0.20 follows (if you don’t want to wait for openSUSE maintainers to provide a pre-compiled Guest Additions)…

  1. Uninstall your Guest Additions if they are provided by the OSS with the following command
zypper rm virtualbox-guest-kmp-default virtualbox-guest-tools virtualbox-guest-x11
  1. Install dependencies to build your KLM using the Oracle Guest additions ISO (which is automatically included in your VBox install. DO NOT try to download the Guest Additions ISO separately, it’s not easily available).
zypper in make gcc kernel-devel

  1. Mount the Guest Additions ISO. To do so easily, “Run” your Guest so that it boots up fully. From the Guest Window,
    Devices > Insert Guest Additions CD Image…

  2. From within the Guest, I recommend copying the Guest Additions installer to your virtual disk instead of running from the CD so that if you have to run it again you don’t have to remount the image (but it’s your choice). You can either run the installer from the following location or run the command as shown to copy the file to your ~/Downloads folder.

cp /run/media/$USER/VBOXADDITIONS_5.0.20_106931/VBoxLinuxAdditions.run ~/Downloads
  1. Assuming you copied the Install file to your Downloads file as I described in the previous step, you should now be able to open a root console to your Downloads directory and execute the install file as follows
cd ~/Downloads && ./VBoxLinuxAdditions.run

After it completes, you should be golden!

TSU

#14

Addendum to the previous post updating to Guest Additions 5.0.20 (on a Virtualbox 5.0.20),
After a few reboots,
It seems that the autofit problem has re-appeared…
But, at least everything else that the Guest Additions provides seems to be working properly…

TSU