vagrant 1.9
virtualbox 5.1.12
base box: https://github.com/CommanderK5/packer-centos-template/releases/download/0.7.2/vagrant-centos-7.2.box
Current Laptop: Windows7 on Dell Latitude E7270 with 250gb ssd on bitlocker.
So with that out of the way, I was previously using vagrant with the same version of vagrant, virtualbox and base box on a different computer with a mechanical hdd without bitlocker. Everything is ok until I upgraded my laptop.
In vagrant if we do vagrant init in a folder and launch vagrant it will mount the folder with the VagrantFile to the /vagrant on the guest machine. On the current laptop it takes a loong time for vagrant to mount this shared folder.
Do you think its bitlocket that might be causing this issue?
Thanks
Related
I have been using ubuntu 14.x from windows using virtual box.but suddenly ubuntu instance stopped working and when i start the virtual machine using vagrant up command it is saying
Couldn't remount RDWR because of unprocessed orphan inode list.
Does anyone knows how to boot virtual machine and solve mounting issue.?
I'm trying to run a CentOS distribution on VMWare. Because the Linux is running calculations, i need this machine to never stop.
I've tried to run it in VMWare player, after 20 minutes of "innactivity", the session logout. I've tried to run it in VMWare Workstation, it does the same.
How do i manage the Linux or VMWare to prevent this logout ?
Thank you.
I had the same problem a while ago, if I can remember correctly, you need to do the following:
Shutdown the Virtual Machine.
Locate the Virtual Machine .vmx File.
Open The .vmx file in any text Editor.
Add This line: suspend.disabled = "TRUE"
Start the Virtual Machine again.
Hope this helps.
Note: For creating clone of Vagrant Box
I have created vagrant box for centos from atlas.hasicorp.
`https://atlas.hashicorp.com/matyunin/boxes/centos7'
`[user#localhost vagrant_ssh]$ vagrant init matyunin/centos7' This command creates VagrantFile in vagrant_ssh directory.
[user#localhost vagrant_ssh]$ vagrant up --provider virtualbox. Now this will download this vagrant box.
Now I want to create clone of this vagrant box. I can easy to by doing transfer the .box file to the other machine, add the box and run vagrant up. But I am not able to find the location of vagrant box in Centos 7. In this link, someone mentioned path for vagrant in Mac/linux is ~/.vagrant.d/boxes, but I didn't find this path on Centos7
The box is not stored in the vm but on the host machine, so search for the files on your system
The default path is :
Mac OS / Linux: ~/.vagrant.d/boxes
Windows: C:/Users/USERNAME/.vagrant.d/boxes
I have been trying maybe weeks now to figure out how to configure VirtualBox to have 1366x768 resolution on a linux guest, which is on a windows 8.1 host.
My configuration:
Windows 8.1 as host
Linuxmint 17.1 as guest (tried ubuntu and debian too but no luck)
Virtualbox 4.3.26 and its extension pack
Laptop is powerful with 16GB ram and 4GB Nvdia
My problem is that it doesn't matter what I used, nothing worked.
Please do not post the answers on most known websites, I tried them already.
Once your VM is started, you need to run the VBox Linux Guest Additions.
First try to run it from the VirtualBox window's menu:
Devices >> Insert guest Additions CD image...
and follow the instructions.
If that fails, open a terminal and go to the directory where you CD reader is mounted (/run/media/ on Fedora or /media/ on Ubuntu for example).
Then type command sudo ./VBoxLinuxAdditions.run
Complete instructions can be found on the VirtualBox user manual
Once Guest Additions are installed, reboot your virtual machine. You should be able to resize your screen to your heart's content.
I installed the new VirtualBox 5.0.0_BETA2 and it solved my all problems. Great product is getting ready! Cant wait the latest release. more than a PERFECT software. Now you can remove top bar and/or bottom bar easily. Show what you need.
If you are having problem like me with 1366x768 I recommend you to install latest versin of VB even if it is Beta!
Problem description:
When I boot my VirtualBox Guest OS, the mounting of the shared file-system - which is referenced in /etc/fstab - fails.
However, after login - mount -a succeeds.
Details:
The boot process gets stuck here ...
... and pressing s continues the boot process, which finishes.
In the shell, I verify that my shared directory is not mounted:
But now, from the shell, the mount of the shared file-system succeeds:
What should I do to make my mount succeed during start-up?
Environment:
VirtualBox: 4.3.12.r93733
Host OS: Windows 7
Guest OS: Linux ubuntu 3.13.0-32-generic #57~precise1-Ubuntu x86_64 GNU/Linux
/etc/fstab
Relevant lines in /var/log/boot.log
You don't have to mount it, VitrualBox will make it for you. For me,these steps worked on my System (VirtualBox 5.0.10 on Windows 7 and Kubuntu 14.04 guest system):
In VirtualBox, configure your shared folder for your machine under 'Shared Folder'. Pick up the directory on your host system (e.g. D:\shared) and set a name for your guest system (e.g. shared).
Boot the guest system. Now you should have a mounted folder under \media\sf_shared.
Thats all. VirtualBox manages this for you.
You need to install VirtualBox Guest Additions properly and use VirtualBox Manager to specify share folders. The issue happens because the mount point is in place with root permissions. The default mount location is in /media/sf_.
You can change mount point with VBoxControl command. To change the mount point from /media/sf_... to /home/user/sf_... use the command:
sudo VBoxControl guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir /home/user/
To check if that's working:
sudo VBoxControl guestproperty get /VirtualBox/GuestAdd/SharedFolders/MountDir