Virtualbox - folder does not automatically mount, Windows 7 host Ubuntu 17.10 guest
I'm trying to use Virtualbox's shared folder functionality, and I can't get the automount folder feature to work.
I've followed directions in various SO/AskUbuntu questions, and it seems like I set up shared folders correctly.
More details:
Mounting the folder with sudo mount -t vboxsf vbox_shared /media/vbox_shared works, including write access.
I've installed Virtualbox Guest Additions, and lsmod | grep vboxguest returns vboxguest 294912 2 vboxsf,vboxvideo.
I've run sudo usermod -G vboxsf -a <username> to add myself to the group.
I've restarted the virtual machine.
In Virtualbox settings, I've set Folder Path: C:Users<myusername>vbox_shared, Folder Name: vbox_shared, Auto-mount and Make Permanent are checked.
Host is Windows 7 Enterprise, Guest is Ubuntu Server 17.10, Virtualbox 5.2.6.
What else could be the cause of this?
network-shares virtualbox
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
migrated from serverfault.com Feb 14 '18 at 20:40
This question came from our site for system and network administrators.
add a comment |
I'm trying to use Virtualbox's shared folder functionality, and I can't get the automount folder feature to work.
I've followed directions in various SO/AskUbuntu questions, and it seems like I set up shared folders correctly.
More details:
Mounting the folder with sudo mount -t vboxsf vbox_shared /media/vbox_shared works, including write access.
I've installed Virtualbox Guest Additions, and lsmod | grep vboxguest returns vboxguest 294912 2 vboxsf,vboxvideo.
I've run sudo usermod -G vboxsf -a <username> to add myself to the group.
I've restarted the virtual machine.
In Virtualbox settings, I've set Folder Path: C:Users<myusername>vbox_shared, Folder Name: vbox_shared, Auto-mount and Make Permanent are checked.
Host is Windows 7 Enterprise, Guest is Ubuntu Server 17.10, Virtualbox 5.2.6.
What else could be the cause of this?
network-shares virtualbox
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
migrated from serverfault.com Feb 14 '18 at 20:40
This question came from our site for system and network administrators.
add a comment |
I'm trying to use Virtualbox's shared folder functionality, and I can't get the automount folder feature to work.
I've followed directions in various SO/AskUbuntu questions, and it seems like I set up shared folders correctly.
More details:
Mounting the folder with sudo mount -t vboxsf vbox_shared /media/vbox_shared works, including write access.
I've installed Virtualbox Guest Additions, and lsmod | grep vboxguest returns vboxguest 294912 2 vboxsf,vboxvideo.
I've run sudo usermod -G vboxsf -a <username> to add myself to the group.
I've restarted the virtual machine.
In Virtualbox settings, I've set Folder Path: C:Users<myusername>vbox_shared, Folder Name: vbox_shared, Auto-mount and Make Permanent are checked.
Host is Windows 7 Enterprise, Guest is Ubuntu Server 17.10, Virtualbox 5.2.6.
What else could be the cause of this?
network-shares virtualbox
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
I'm trying to use Virtualbox's shared folder functionality, and I can't get the automount folder feature to work.
I've followed directions in various SO/AskUbuntu questions, and it seems like I set up shared folders correctly.
More details:
Mounting the folder with sudo mount -t vboxsf vbox_shared /media/vbox_shared works, including write access.
I've installed Virtualbox Guest Additions, and lsmod | grep vboxguest returns vboxguest 294912 2 vboxsf,vboxvideo.
I've run sudo usermod -G vboxsf -a <username> to add myself to the group.
I've restarted the virtual machine.
In Virtualbox settings, I've set Folder Path: C:Users<myusername>vbox_shared, Folder Name: vbox_shared, Auto-mount and Make Permanent are checked.
Host is Windows 7 Enterprise, Guest is Ubuntu Server 17.10, Virtualbox 5.2.6.
What else could be the cause of this?
network-shares virtualbox
network-shares virtualbox
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
edited Feb 14 '18 at 21:11
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
asked Feb 14 '18 at 20:38
AnonymousCowherd
34
34
migrated from serverfault.com Feb 14 '18 at 20:40
This question came from our site for system and network administrators.
migrated from serverfault.com Feb 14 '18 at 20:40
This question came from our site for system and network administrators.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Automount performed by appropriate systemd unit service:
virtualbox-guest-utils.service - if you have installed virtualbox-guest-dkms and virtualbox-guest-utils
or
vboxadd-service.service - if you have installed VBoxLinuxAdditions.run from VirtualBox virtual CD.
In the both of the cases appropriate service possible failure to start caused by unit dependecies.
Possible solution:
sudo systemctl edit --full vboxadd-service
or
sudo systemctl edit --full virtualbox-guest-utils
and remove "systemd-timesync.service" from "Conflicts=" line in [Unit] section. Then reboot.
UPDATED
If you'll update Virtual Guest Additions you'll possible have to change manually version number in the vboxadd-service. See also selectstriker2 comment below.
answered Aug 17 '18 at 11:44
Final12345
113
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1295025%2fvirtualbox-folder-does-not-automatically-mount-windows-7-host-ubuntu-17-10-gu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Automount performed by appropriate systemd unit service:
virtualbox-guest-utils.service - if you have installed virtualbox-guest-dkms and virtualbox-guest-utils
or
vboxadd-service.service - if you have installed VBoxLinuxAdditions.run from VirtualBox virtual CD.
In the both of the cases appropriate service possible failure to start caused by unit dependecies.
Possible solution:
sudo systemctl edit --full vboxadd-service
or
sudo systemctl edit --full virtualbox-guest-utils
and remove "systemd-timesync.service" from "Conflicts=" line in [Unit] section. Then reboot.
UPDATED
If you'll update Virtual Guest Additions you'll possible have to change manually version number in the vboxadd-service. See also selectstriker2 comment below.
answered Aug 17 '18 at 11:44
Final12345
113
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
add a comment |
Automount performed by appropriate systemd unit service:
virtualbox-guest-utils.service - if you have installed virtualbox-guest-dkms and virtualbox-guest-utils
or
vboxadd-service.service - if you have installed VBoxLinuxAdditions.run from VirtualBox virtual CD.
In the both of the cases appropriate service possible failure to start caused by unit dependecies.
Possible solution:
sudo systemctl edit --full vboxadd-service
or
sudo systemctl edit --full virtualbox-guest-utils
and remove "systemd-timesync.service" from "Conflicts=" line in [Unit] section. Then reboot.
UPDATED
If you'll update Virtual Guest Additions you'll possible have to change manually version number in the vboxadd-service. See also selectstriker2 comment below.
answered Aug 17 '18 at 11:44
Final12345
113
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
add a comment |
Automount performed by appropriate systemd unit service:
virtualbox-guest-utils.service - if you have installed virtualbox-guest-dkms and virtualbox-guest-utils
or
vboxadd-service.service - if you have installed VBoxLinuxAdditions.run from VirtualBox virtual CD.
In the both of the cases appropriate service possible failure to start caused by unit dependecies.
Possible solution:
sudo systemctl edit --full vboxadd-service
or
sudo systemctl edit --full virtualbox-guest-utils
and remove "systemd-timesync.service" from "Conflicts=" line in [Unit] section. Then reboot.
UPDATED
If you'll update Virtual Guest Additions you'll possible have to change manually version number in the vboxadd-service. See also selectstriker2 comment below.
answered Aug 17 '18 at 11:44
Final12345
113
Automount performed by appropriate systemd unit service:
virtualbox-guest-utils.service - if you have installed virtualbox-guest-dkms and virtualbox-guest-utils
or
vboxadd-service.service - if you have installed VBoxLinuxAdditions.run from VirtualBox virtual CD.
In the both of the cases appropriate service possible failure to start caused by unit dependecies.
Possible solution:
sudo systemctl edit --full vboxadd-service
or
sudo systemctl edit --full virtualbox-guest-utils
and remove "systemd-timesync.service" from "Conflicts=" line in [Unit] section. Then reboot.
UPDATED
If you'll update Virtual Guest Additions you'll possible have to change manually version number in the vboxadd-service. See also selectstriker2 comment below.
answered Aug 17 '18 at 11:44
Final12345
113
edited Dec 12 '18 at 12:12
answered Aug 17 '18 at 11:44
Final12345
113
answered Aug 17 '18 at 11:44
Final12345
113
answered Aug 17 '18 at 11:44
Final12345
113
113
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
add a comment |
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
So I ran into an issue when updating from 5.2.18 to 5.2.22 which caused the vboxadd-service configuration to not update from .18 to .22. This caused vboxadd-service to fail to start. I fixed those lines in the file using this method and was able to get the vboxadd-service to actually start
– selectstriker2
Dec 7 '18 at 23:06
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1295025%2fvirtualbox-folder-does-not-automatically-mount-windows-7-host-ubuntu-17-10-gu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
