Preparing a CentOS 7 minimal installation for use in a VMware vSphere environment:
Install CentOS7
Net-tools includes ifconfig which is required to take advantage of the Customization Specification Templates
bzip2 is required by the VirtualBox Guest Additions
cifs-utils is required to mount Samba shares
yum install -y cifs-utils net-tools bzip2
If you are using Windows as a host, and plan to use smb shares to get files to the the client vm, install the vagrant-vbguest plugin:
vagrant plugin install vagrant-vbguest
If you are getting vboxsf errors, ensure you installed the VirtualBox Guest Additions. This goes for VMware based deployments as well for some reason.
#This is buggy as hell be sure to install the shared folders stuff.
#rpm -Uvh http://dl.fedoraproject.org/pub/epel/beta/7/x86_64/epel-release-7-0.2.noarch.rpm;
#yum -y install dkms kernel-devel-$(uname -r) kernel-headers-$(uname -r);
#wget http://download.virtualbox.org/virtualbox/4.3.14/VBoxGuestAdditions_4.3.14.iso;
#mount -o loop VBoxGuestAdditions_4.3.14.iso /media/;
#/media/VBoxLinuxAdditions.run;
#Yolo Style:
rpm -Uvh http://download.virtualbox.org/virtualbox/5.0.10/VirtualBox-5.0-5.0.10_104061_el7-1.x86_64.rpm
If shared folders is still giving you problems, reinstall the vmware tools:
If you’re still having challenges, you’re using Windows 10. There are some existing issues with SMB fileshares that I have not pinned down. Server 2012 R2/Windows 8 are the currently working versions. Windows 7 has a challenge with regard to missing powershell ip functionality. I tested these steps on the Windows 8 box with no challenges, but I could only get the VM started – but not SMB share working.
Further details have been discovered – to resolve the issues with Windows 10, navigated to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Right click on Parameters key name, and select New -> DWORD (32-bit) Value.
Name the value AllowInsecureGuestAuth and set the value to 1 hex. This effectively makes it so you can guest your way into the shared folders – this is highly insecure. It’s outlined here: https://techjourney.net/cannot-connect-to-cifs-smb-samba-network-shares-shared-folders-in-windows-10/ It’s a known issue in windows, and is outlined by the folks at vagrant here: https://github.com/mitchellh/vagrant/issues/6222
If it’s still, STILL giving you errors, or if you have a space in your username provided to vagrant for access to your SMB share, it breaks the command running on linux, and provides a really odd error, proving once again it’s always the last thing you try:
