heketi / vagrant-heketi

Demos of Heketi
30 stars 16 forks source link

Unable to run ./up.sh for virtualbox provider #22

Open gnufied opened 8 years ago

gnufied commented 8 years ago

I tried using standalone provider but resulted in following error:

client: /vagrant => /home/shared/redhat/vagrant-heketi/standalone
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attemped was:

set -e
mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

I am yet to investigate further but from a quick glance it looks like Guest Additions module failed to compile in the guest because of missing kernel sources. I am using vbguest addition plugin.

It could be just my environment, but I will keep investigating in case someone else runs into same problem.

lpabon commented 7 years ago

I'll take a look, thanks @gnufied