Hi I have about 20 Vagrant VM in my laptop ( Windows OS) , however disk space is almost full. Hence I would like to know if I can use external SSD disk as Vagrant "Default Machine Folder" in Oracle VM VirtualBox.
Anybody have done this before ? Any issue in performance of Vagrant or memory if use external disk as storage for Vagrant VM ?
Thanks
Related
I always SSH into my virtual machine and don't use VMWare's virtual machine window/terminal after I am done setting up the VM. I find it annoying to always have the VMWare Fusion application open as well as the VM window, thus, I want to be able to silently start the VM from my terminal and do all other actions only through terminal.
I saw this page on the VMWare website that talks of starting a VM with the command:
/Applications/VMware\ Fusion.app/Contents/Library/vmrun start full/path/of/your/virtual/machine/bundle
That is a step in the right direction as I don't need to click anything to start my VM, however, it still opens the application and VM in windows.
When I used Virtual Box, I remember being able to do this with a command like:
VBoxManage startvm "VM name" --type headless
Is there a similar command that for VMWare that would allow me to run my VM headless?
You can try :
vmrun start full/path/of/your/virtual/machine/bundle nogui
Our linux server has been rebooted after server crash/freeze.
Trying to use a virtual machine (using vagrant up) , I've noticed the VM (created with vagrant) reverted to a prior version (version of the first week since vm creation).
I 'm now trying to recover the data (important data).
I've got the original files of the vm in "VirtualBox VMs folder" and the same files backuped on ftp server (the backup were created 1 day before crash) :
The Folders contain :
**- vm.vbox ,
vm.vbox-prev ,
vm.vmdk ,
vm.vdi**
I tried to mount each of the "vm.vdi" ("qemu-nbd -c ...")(the backup "vm.vdi" and the original one).
I then tried to clone the vm ("VBoxManage clonevm ...") and check for new files in the cloned vm , clone the vdis ("VBoxManage clonehd") and mount the cloned ones, package the box and create a new vagrant box from the original one packaged , but nothing to do, the data has been reverted to the creation of the virtual machine.
In the past, we've shutdown the host and the vm many times without troubles (gracefull shutdown ).
**Host and VM : ubuntu bionic 18.04 ,
Virtualbox : 5.2.18 ,
Vagrant : 2.0.3**
Any suggestions ?
During vagrant up command I saw that it is generating settler_default_xxxxx folder in my virtual machines folder, and then it renames the folder to homestead-7, and then tries to run the machine and fails with:
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state.
When I look at the machine, I see that it has wrong hard disk attachment. The disk still points to the path in settler_ folder which no longer exists. I have to manually remove the attached disk and attach the right one in the homestead-7 folder instead.
Why doesn't Vagrant rename the disk attachment to homestead-7? Am I doing something wrong? If it's a bug, then is it Vagrant's, Laravel's or VirtualBox's bug?
My config:
Vagrant 1.8.1
VirtualBox 5.0.14
VAGRANT_HOME points to V:\VAGRANT_HOME
VirtualBox File -> Preferences -> Default Machine Folder points to V:\
Computer:
Windows 10 64-bit
8GB RAM
I have a number of windows VMs running on my hyper-v instance I want to turn into vagrant boxes. Its there a tool out there that can do this for me or a clear guide on what needs to be enabled on the machine and how to create the config files that go into the box?
The documentation for windows VMs coming from hyper-v seem to be lacking with most guides focusing on virtual box.
TIA
There is no direct approach to achieve what you want.
NOTE: remove the hyper-v integration tools (agent, PV drivers etc...).
First, you need to convert VHD to VMDK or VDI format using VBoxManage, for example from VHD to VDI -> VBoxManage clonehd source.vhd target.vdi --format VDI
Once done, create a VM in VirtualBox with a proper spec (# of vCPUs, Memory, etc.), use the existing converted .vdi file as its virtual disk.
Try to boot the VM and see if everything works as expected. Install the VirtualBox Guest Additions (recommended).
Configure the VM as per Vagrant Documentation (e.g. NAT port forwarding rules, disabling UAC etc., refer to Creating a Base Box)
Package it as Vagrant box vagrant package --base vbox_vm_name --output /file/to/name.box
I want to take a dump of the entirety of the physical memory of a virtual machine running on VBox on vagrant. I was wondering if vagrant can do that for me? It seems like the vagrant commands are pretty limited. Thanks
You can do it inside of VM:
sudo dd if=/dev/fmem of=/tmp/fmem_dump.dd bs=1MB count=10
If you want to dump the memory of one process you can use:
$ cat /proc/[pid]/maps