Applies to openSUSE LEAP 15.0 and 15.1 Guests running Virtualbox 6.0 running on Windows (Last I heard, do not know if anything has changed about issues installing VBox 6.0 on openSUSE as the HostOS). Assume that running TW as a VBox Guest is not different than LEAP.

VBox users should know that VBox 6.0 is a major upgrade with new features and slightly different configurations compared to earlier VBox versions.

A good starting point is the current Virtualbox Guest Additions documentation

https://www.virtualbox.org/manual/ch04.html

A few highlights I notice...
  • I seem to remember shared folders automatically mounted in the same place as the optical disk (or was that my imagination?). Auto mounted folders are now located in

Code:
/media/sf_Sharename
  • A special (proprietary?) USB driver that is separate from Extensions is installed
  • Extensive new support for 2D and 3D hardware acceleration, but mostly for Windows Guests (Unsaid in the documentation if these new capabilities are possible on non-Windows HostOS)
  • I haven't had the opportunity to try "Seamless Windows" but it looks interesting and that may be related to a new way of file sharing between the Guest and Host, no longer requiring setting up Shared Folders there is a new Virtualbox File manager which is much like Midnight Commander or the old Konqueror File Manager enabling files to be transferred between any file location in the Guest and any location on the HostOS.
  • Some general management functions like snapshot management and the main buttons for Run, Stop, Settings and New have been re-located to more efficiently use display space.
  • Some new overcommit capabilities commonly found elsewhere. Virtualbox claims the way it does memory page sharing is more efficient and less resource intensive. Could mean more virtual machines running simultaneously.


Some of the "new" features like Guest Properties look like a re-packaging of VBoxManage APIs. May look more closely sometime to see if there is indeed anything really new.

Some adventures in Guest Additions...
I found that for 15.0, the existing Vbox 5.2.2 extensions sort of worked when the Guest was first opened after upgrading to 6.0. But you could see something was likely wrong like jittery graphic movements. Configured Shared Folders worked and auto display re-sizing worked.

My first attempt to upgrade Guest additions in this 15.0 Guest was to build using the Guest Additions ISO. The Guest Additions ISO failed to build and wrecked existing installed Guest Additions... I would suggest being wary if you try to install Guest Additions from the VBox application. But! -- The pre-built Guest Additions from openSUSE work just fine!

So, bottom line for openSUSE 15.0 Guests, I recommend upgrading Guest Additions by simply doing a forced re-install of the pre-built Guest Additions as follows, and if you did a mis-step like I did, can fix those problems too
Code:
zypper in -f virtualbox-guest-tools virtualbox-guest-x11
On the other hand, with openSUSE 15.1 so far (I've only run a few tests up to now),
Although Guest Additions should install automatically in most cases during the install due to the install detecting being installed in a virtual machine, a Guest I created running only the awesome WM did not install Guest Additions. I then attempted to install the openSUSE Additions from openSUSE, but although the installations did not error, there was no functionality. I then uninstalled the Additions packages and installed using the VBox app's ISO file, and that worked perfectly, the virtual machine has full Additions functionality including display re-sizing, seamless mouse between Host and Guest. Shared folders does not work right away, but that is likely because of an idiosyncrasy of awesome that there is no /media/ folder by default so automounting likely failed when the parent folder doesn't exist.

As Virtualbox 6.0 is used more, I'm sure that more new features will be discovered.

Probably not specific to VBox 6.0, I now see a libvirt Virtualbox daemon package in the OSS, and online documentation verifies that Virtualbox can now be managed using libvirt if you prefer over Virtualbox's own virtual machine manager. Can Virtualbox have dreams of being used as an Enterprise solution instead of only as a personal solution?

TSU


-