Bug 25577

and kmods:

SRPM:
kmod-virtualbox-6.0.14-1.mga7.src.rpm


i586:
virtualbox-kernel-5.3.6-desktop-2.mga7-6.0.14-1.mga7.i586.rpm
virtualbox-kernel-5.3.6-desktop586-2.mga7-6.0.14-1.mga7.i586.rpm
virtualbox-kernel-5.3.6-server-2.mga7-6.0.14-1.mga7.i586.rpm
virtualbox-kernel-desktop586-latest-6.0.14-1.mga7.i586.rpm
virtualbox-kernel-desktop-latest-6.0.14-1.mga7.i586.rpm
virtualbox-kernel-server-latest-6.0.14-1.mga7.i586.rpm


x86_64:
virtualbox-kernel-5.3.6-desktop-2.mga7-6.0.14-1.mga7.x86_64.rpm
virtualbox-kernel-5.3.6-server-2.mga7-6.0.14-1.mga7.x86_64.rpm
virtualbox-kernel-desktop-latest-6.0.14-1.mga7.x86_64.rpm
virtualbox-kernel-server-latest-6.0.14-1.mga7.x86_64.rpm

Mageia 7, x86_64

Desktop version installed.  Launched two guests successfully.  Received a popup message about the Oracle guest additions pack.
Tried to install the Oracle extension pack via the help menu -> Virtualbox site -> Downloads.  This always fails to install via the Virtualbox Manager.  It failed again, which means the USB interface is not available.  Unsure how to proceed at this point.

CC: (none) => tarazed25

(In reply to Len Lawrence from comment #2)
> Mageia 7, x86_64
> 
> Desktop version installed.  Launched two guests successfully.  Received a
> popup message about the Oracle guest additions pack.
> Tried to install the Oracle extension pack via the help menu -> Virtualbox
> site -> Downloads.  This always fails to install via the Virtualbox Manager.
> It failed again, which means the USB interface is not available.  Unsure how
> to proceed at this point.

Download it manually, and install it then

Thanks Thomas, that is what I was trying to avoid because I could not remember how to do that.  Found a note eventually and installed it OK.

For the record:
$ su -
# cd /home/<user>/Downloads
# VBoxManage extpack cleanup
# VBoxManage extpack install <extpack>
# exit

I would still like to know why it never installs from the gui.

Weird, I just downloaded the extpack with firefox, then in VirtualBox I used:

File -> Preferences -> Extensions -> Click on '+' to select the extension pack -> got asked for Administrator password -> plugin installed nicely.

virtualbox has always behaved weirdly here.  See this:

Logged in to the virtualbox client.  Noticed that there was a popup on the host desktop saying 'Creating process for virtual machine "hatysa" (GUI/Qt) ... (1/2)' and that hangs forever at 0%.  Logged out and closed down and the popup disappeared but then VBox Manager reported "Failed to open a session for the virtual machine hatysa.", exit code 0.

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

The "creating process" popup appears again.

The USB settings dialogue is greyed-out although USB controller for 3.0 is enabled and a default filter is set.  There may be some relation between these two things.

Just checked that and can say that there is not, so there are two problems, the strange popup which triggers shortly after logging in, this time after typing 'ls' in a terminal, and the fact that USB is disabled.

Note that USB has sometimes worked in the past.  I am wondering if there are some software components missing or mismatched.
$ rpm -qa | egrep "virtualbox|vbox"
virtualbox-devel-6.0.14-1.mga7
virtualbox-guest-additions-6.0.14-1.mga7
virtualbox-kernel-5.3.6-desktop-2.mga7-6.0.14-1.mga7
dkms-vboxadditions-6.0.14-1.mga7
python-virtualbox-6.0.14-1.mga7
x11-driver-video-vboxvideo-1.0.0-5.mga7
virtualbox-6.0.14-1.mga7
virtualbox-kernel-5.2.16-desktop-2.mga7-6.0.12-1.mga7
virtualbox-kernel-desktop-latest-6.0.14-1.mga7
dkms-virtualbox-6.0.14-1.mga7
virtualbox-kernel-5.3.2-desktop-1.mga7-6.0.12-2.mga7

What else should I look for?

@Thomas, in reply to comment 3;
Thanks, I did not know about that installation method (aka forgotten).
My reference to "from the gui" meant using the popup when downloading from the website, install or file.
From memory, the extension pack was never listed under extensions, even after an apparently successful installation.
Cleaned up and used the gui method.
Noted that this time the plugin was listed.  Tried to remove it and reinstall and that failed.

Have to give up on this.  Tried to uninstall the extension pack via the gui and nothing happened.
Used the command line and that failed with the complaint "Invalid extension pack name specified".  That happened with or without the vbox-extpack extension.
Tried uninstalling and reinstalling virtualbox from updates testing, including dkms-virtualbox.  No progress.  The "creating process" popup appears as soon as any desktop operation is executed.

Enough.

Tried a different machine and installed the updates.  Noticed a large number of "broken pipe" errors when dkms was working.  A vbox client launched OK, worked normally, logged out.  Shutdown the machine.  Downloaded the extension pack.  Installed it via File->preferences->extensions-> +  ->  failed.

Umm.  Just noticed that aforesaid machine is running the server kernel.  Would that cause problems - like "broken pipe"?

Switched to the desktop kernel and saw vboxadditions being rebuilt on the fly.
Still no luck installing the plugin.  Tried removing then reinstalling dkms-virtualbox.  No errors reported.  Could not install the plugin.  tried disabling the USB controller entirely.  Tried the plugin again.  Still fails to install.

Cannot think of anything else to try.

Back on the hatysa virtual machine.  It seems to have settled down - no more annoying popups - extension pack installed - but still no USB; all options greyed out aka disabled.
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The mouse and keyboard are both wifi, connected through a USB dongle on the host and they both work.  NFS shares work.

So what is the magic to enable access to USB devices on the host?  Beats me.

Still on hatysa.  There is a 2TB USB disk drive plugged in to the 3.0 bus.  Tried disabling 3.0 and enabling 2.0.  Launched the client then plugged in another USB drive.  Not able to see the device in virtualbox but it mounted on the host then dismounted.  It kept on bouncing like that as long as the client was up.  Closed down the client.  The drive mounted on the host and stayed mounted.  This situation happened in the past I now remember, with much earlier versions of vbox so it looks like a longstanding contention issue.  Tried unmounting the USB drive and plugged it in again and checked devices in vbox.  No listed USB devices but thunar kicked in a little later and displayed the contents of the disk (in the guest); the anomalous "creating process.... 0%" popup appeared and remained for the rest of the session.  Still nothing listed in devices.  Closed the gui.  No icon on the desktop.  Closed down at that point because the devices entry had disappeared from the menu.

on mga7-64  kernel-desktop  plasma

packages installed cleanly:

- dkms-virtualbox-6.0.14-1.mga7.noarch
- virtualbox-6.0.14-1.mga7.x86_64
- virtualbox-kernel-5.3.6-desktop-2.mga7-6.0.14-1.mga7.x86_64
- virtualbox-kernel-desktop-latest-6.0.14-1.mga7.x86_64

# dkms status
virtualbox, 6.0.14-1.mga7, 5.3.6-desktop-2.mga7, x86_64: installed 
virtualbox, 6.0.14-1.mga7, 5.3.6-desktop-2.mga7, x86_64: installed-binary from 5.3.6-desktop-2.mga7

extension pack upgraded cleanly

vbox and clients (winxp, win7 and mga7-32) launched normally

Updated additions in all 3 clients. As usual the download of the additions iso  for the Windows clients, failed part way. I had to download and insert the iso manually.

"Attached" my USB printer to the mga7-32 client, configured it in the client and printed a test page. 

No regressions observed. OK for mga7-64 on this system:

Desktop System: Dell product: Precision Tower 3620
Quad Core model: Intel Core i7-6700
Intel HD Graphics 530

CC: (none) => jim

At last; found the solution on a web forum: add user to vboxusers group.  I have forgotten that small step countless times.  Looks like everything is working properly now.

On real hardware, M7.1, Plasma, 64-bit

Package(s) under test:
virtualbox

default install of packages:
kernel-desktop-latest virtualbox
virtualbox-guest-additions virtualbox-kernel-desktop-latest
x11-driver-video-vboxvideo kernel-desktop-devel-latest
cpupower

[root@localhost wilcal]# uname -a
Linux localhost 5.3.6-desktop-2.mga7 #1 SMP Sun Oct 13 18:22:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-5.3.6-2.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox
Package virtualbox-6.0.12-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox-guest-additions
Package virtualbox-guest-additions-6.0.12-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest
Package virtualbox-kernel-desktop-latest-6.0.12-4.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi x11-driver-video-vboxvideo
Package x11-driver-video-vboxvideo-1.0.0-5.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi kernel-desktop-devel-latest
Package kernel-desktop-devel-latest-5.3.6-2.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi cpupower
Package cpupower-5.3.6-2.mga7.x86_64 is already installed
[root@localhost wilcal]# lspci -k
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 3518
        Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia390

Mageia-7-Live-Xfce-i586.iso
Runs as a Vbox client.
Boots to a working desktop. Common apps work.
Screen sizes are correct.


install from updates testing:

virtualbox
virtualbox-guest-additions virtualbox-kernel-desktop-latest
x11-driver-video-vboxvideo kernel-desktop-devel-latest
cpupower

[root@localhost wilcal]# uname -a
Linux localhost 5.3.6-desktop-2.mga7 #1 SMP Sun Oct 13 18:22:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-5.3.6-2.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox
Package virtualbox-6.0.14-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox-guest-additions
Package virtualbox-guest-additions-6.0.14-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest
Package virtualbox-kernel-desktop-latest-6.0.14-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi x11-driver-video-vboxvideo
Package x11-driver-video-vboxvideo-1.0.0-5.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi kernel-desktop-devel-latest
Package kernel-desktop-devel-latest-5.3.7-1.mga7.x86_64 is already installed
[root@localhost wilcal]# urpmi cpupower
Package cpupower-5.3.7-1.mga7.x86_64 is already installed
[wilcal@localhost ~]$ lspci -k
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 3518
        Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia390

Mageia-7-Live-Xfce-i586.iso
Runs as a Vbox client.
Boots to a working desktop. Common apps work.
Screen sizes are correct.

Mageia-7-Live-GNOME-x86_64.iso
Runs as a Vbox client.
Boots to a working desktop. Common apps work.
Screen sizes are correct.

Mageia-7-x86_64.iso
Runs as a Vbox client
Boots to a working desktop. Common apps work.
Screen sizes are correct.
Installs without error. Updates without error.
Reboots to a working desktop without error.

CC: (none) => wilcal.int

Tested on a 64-bit Plasma host - Probook 6550b, i3, 8GB, Intel graphics and wifi.

This system does not have dkms-virtualbox installed, to assure that tests will use the Mageia kmods rather than locally-built ones.

Packages installed cleanly. Ran vbox and upgraded the extension pack using the gui's "File/Check for updates" function. Ran a Mageia 7 guest and updated it, including the 6.0.14 guest additions. Rebooted, and everything seemed to work.

Ran a Windows XP guest, and as usual the guest additions download failed when using the gui's "Devices/Insert guest additions CD image" to try to get it. Bug 24696. Guest additions had to be manually downloaded and mounted as a CD image. Other than that ongoing problem, all is good with the XP guest, too.

CC: (none) => andrewsfarm

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2019-0303.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED