Bug 24141 - Mageia 7 guests not auto-mounting shared folders in VirtualBox
Summary: Mageia 7 guests not auto-mounting shared folders in VirtualBox
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: 7beta2
Depends on:
Blocks:
 
Reported: 2019-01-05 22:54 CET by Thomas Andrews
Modified: 2019-01-06 17:10 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Thomas Andrews 2019-01-05 22:54:01 CET
Description of problem:

Host system: 64-bit Mageia 6 Plasma, using 64-bit VirtualBox 5.2.22 as installed from the Mageia 6 repositories, with the 5.2.22 extension pack installed.

Guest system: Mageia 7 Plasma system, as installed from the test Round 1 of the Beta 2 LiveDVD iso.

The guest system is not auto-mounting shared folders from the host, or if it is I can't find them. 

The guest user is part of the vboxsf group, and the host user belongs to the vboxusers group. Shared folders do work in other guests, including Mageia 6 and Windows XP.

virtualbox-guest-additions was installed by the iso. dkms-vboxadditions was not.

I first saw this after an install from the beta 1 iso, but attributed it to /media, where shared folders are typically mounted, not being created. That has been corrected in the beta 2 isos.
Thomas Andrews 2019-01-05 22:54:25 CET

Priority: Normal => High

Thomas Andrews 2019-01-05 22:54:47 CET

Keywords: (none) => 7beta1

Comment 1 Marja Van Waes 2019-01-05 23:38:35 CET
Assigning to tmb.

CC: (none) => marja11
Assignee: bugsquad => tmb

Comment 2 William Kenney 2019-01-06 07:03:43 CET
I believe this is the same as:

Summary: Timing of the nfs mount not working?
https://bugs.mageia.org/show_bug.cgi?id=23863

We've seen this before in  previous releases.

CC: (none) => wilcal.int

Thomas Andrews 2019-01-06 17:10:59 CET

Keywords: 7beta1 => 7beta2


Note You need to log in before you can comment on or make changes to this bug.