VirtualBox

[Caltrop]

VirtualBox will NOT share folders.

Installed full package.

downloaded Guest Additions ISO and installed it as well

no network
no shared folders
NO WAY TO GET DATA IN & OUT!

[Pjotr]

What do you mean "no network"? Your VM's should use the network of the host.

[Caltrop]

I set the network in VirtualBox to different settings and it still does not show in the guest.

No shared folders show in the guest.

VirtualBox tells me Guest Additions are not installed but I just installed from the ISO & re-booted.

VirtualBox says to talk to Mint. Mint tells me to talk to VirtualBox. No one knows anything!!!

ALL Virtual Machines are broken on my computer with Mint 18.2.

[Flemur]

VirtualBox says to talk to Mint. Mint tells me to talk to VirtualBox. No one knows anything!!!

What does that mean?

[o-l-d]

To share folders with Virtualbox it has to be started with root privileges. You can run Virtualbox as root by opening terminal and use su or sudo virtualbox command to open it as root. Once opened you can then share folders and make settings to network if necessary. Once the folders are shared or network fixed you can close and open Virtualbox normally and your settings should be saved. The lack of information makes it difficult to be able to give specific tips/help.

[catweazel]

To share folders with Virtualbox it has to be started with root privileges.

That is not correct. Shared folders work fine without root privilege. That is the case because VirtualBox shares folders via a network connection.

[o-l-d]

To share folders with Virtualbox it has to be started with root privileges.

That is not correct. Shared folders work fine without root privilege. That is the case because VirtualBox shares folders via a network connection.

Thanks for the correction it is actually VMware where you have to sudo to change settings or share folders upon rethink. This is from Virtualbox blog:

For VirtualBox with a Linux guest, these are the steps to mount a shared folder:

Use the VirtualBox host's application, VirtualBox Manager, to specify host folders to share.
Make sure VirtualBox Guest Additions are installed in the VirtualBox guest.
In the Linux guest, the mount command should show a line that the share was mounted. This is indicated by type vboxsf. The issue becomes that the mount point may not be where desired, and the permissions are root only. The default mount location is in /media/sf_.
You can access the share by making the user, or group id of 1000, a member of group vboxsf. This is done by changing the vboxsf line in the /etc/group file. May require reboot.
You can change where the folder is mounted by using the VBoxControl command. The command is installed when Guest Additions is installed. May require reboot. For example, to change the mount point from /media/sf_... to /home/toto/sf_... use the following command to set the VirtualBox shared folder guestproperty:
sudo VBoxControl guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir /home/toto/
To confirm the change, use get:

sudo VBoxControl guestproperty get /VirtualBox/GuestAdd/SharedFolders/MountDir

Please excuse me for posting wrongly.

[deleted]

Nope. Not vmware either.

To recap... Neither VirtualBox nor VMWare are required to run as root (or sudo) for anything.
And you definitely should not run them as root (or sudo)

You're referring to mounting shared folders in while in the Linux guest, not the Linux host, which is no different than mounting shares in Linux.
-Hinto

[Pierre]

when sharing some picture / document between the Host & the Guest,
it's a usb stick that seems to work the best between the two,
although it should be possible to specify a fat32 partition on the actual HDD itself,
but I've never successfully got that method to work and generally the information
has come from a 3rd source anyway & so is on the usb stick , for starters.
so, using that usb stick, as the shared folder does work for me.

you have to specify where / what the shared folder is via the settings area of the Guest VM.
- and No, you don't need to be Admin / Root in order to specify that setting,
although it's best if the actual Guest VM is not running, when changing it's VB settings.

[Flemur]

it's a usb stick that seems to work the best between the two,
although it should be possible to specify a fat32 partition on the actual HDD itself,
but I've never successfully got that method to work and generally the information

I share an ext4 partition with Mint 18 host and Win 7 guest, and it works fine for everything except Adobe software running on Win 7.

Code: Select all

$ dpkg -l "*virtu*" | grep ii
ii  virtualbox-5.1                 5.1.12-112440~Ubuntu~xenial  amd64     
ii  virtualbox-guest-dkms          5.0.40-dfsg-0ubuntu1.16.04.1 all     
ii  virtualbox-guest-utils         5.0.40-dfsg-0ubuntu1.16.04.1 amd64    
ii  virtualbox-guest-x11           5.0.40-dfsg-0ubuntu1.16.04.1 amd64   

[bob466]

Both Shared Folders and Flash Drives work perfectly in Virtualbox...you just need to be shown...

https://www.youtube.com/watch?v=TSpXn1rWlM8
https://www.youtube.com/watch?v=flehCcMzO30

As for Network...Go to Network...in VM Settings tick...Enable Network Adapter...Attached To:...then make your selection - Done. Hope this helps.

[Caltrop]

see my post here:

https://forums.virtualbox.org/viewtopic ... 82#p399379

The problem is libqt5core5a not being the newest version.

[deleted]

If I read your post correctly, you installed VirtualBox from the Software Manager.
You'll always find here that you should install the version from virtualbox.org.

Normally you do only install from the Software Manager, this is an exception.
Not sure if it solves your problem, but I know I don't have a problem with VB and Mint 18.2.
-H

[Caltrop]

I have nothing but the CD/DVD drive and the virtual C: Drive.

There is NO USB, no Shared Folder/Directory, NOTHING!

VirtualBox says to ask Mint.
Then Mint says ask VirtualBox.

see my post:
https://forums.virtualbox.org/viewtopic ... 82#p399465

About ready to switch Distro!

[deleted]

They said install virtualbox from their site.
You should do that.
-H

[Caltrop]

If I read your post correctly, you installed VirtualBox from the Software Manager.
You'll always find here that you should install the version from virtualbox.org.

Normally you do only install from the Software Manager, this is an exception.
Not sure if it solves your problem, but I know I don't have a problem with VB and Mint 18.2.
-H

Tried to install direct from VirtualBox but the latest version has a dependency that can not be resolved.
Error: Dependency is not satisfiable: libqt5core5a (>=5.70)
I have v5.5 and it will not update to the beta version or whatever it is.

[deleted]

http://ubuntuhandbook.org/index.php/201 ... -released/

[Caltrop]

OK, I downloaded the ISO image, mounted it, went to it and ran it and...

Verifying archive integrity... All good.
Uncompressing VirtualBox 5.0.40 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 5.0.40 of VirtualBox Guest Additions...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
update-initramfs: Generating /boot/initrd.img-4.10.0-30-generic
update-initramfs: Generating /boot/initrd.img-4.8.0-53-generic
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
Starting the VirtualBox Guest Additions ...fail!
(modprobe vboxguest failed)
Press Return to close this window...

[deleted]

https://forums.virtualbox.org/viewtopic.php?f=7&t=55354

[Caltrop]

WOW, what a fun couple of days!

It was unclear that you had to install VirtualBox in the Guest as well as the Host.
I mounted the ISO and nothing showed in the Guest.
So I finally burned a CD, the only thing REAL that shows in the Guest.
Installed, saying OK several times when told I was doing something questionable.
Now...

IT WORKS!