You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2019-04-11 20:18:15
VirtualBox automount problem
This topic may belong with configuration, but it arises in migration from Debian stretch to Devuan. I am running Devuan in a VirtualBox machine set up on Windows 10. The virtual machine was cloned from a Debian machine, and converted using the migration procedure. After one minor problem with adapter names, everything now works as before, except for the automatic mounting of a shared folder with the host machine.
The shared folder is not mounted by the boot process on Devuan, but it can be mounted manually without any problem. In the original machine, before migration, the folder was mounted automatically as specified in the VirtualBox settings. One solution to the problem would be to include the mount in /etc/fstab but it should be handled by VirtualBox Guest Additions.
Is it possible that some systemd debris, that has not been cleaned out of the virtual machine, is getting in the way?
Offline
#2 2019-04-12 04:08:34
Re: VirtualBox automount problem
As a follow-up, checking for reports on this problem elsewhere, it seems the cause is that in the boot process file systems are mounted before the VirtualBox Guest Additions kernel module is loaded. This sequence of events is verified by examination of kern.log
Ironically systemd has a mechanism to deal with this, but it is much simpler to run a mount command on infrequent occasions where the shared folder is required.
In any case, the problem won't arise on a real machine; the virtual machine was used for testing the migration process.
Offline
Pages: 1
