Hi I have just downloaded an Ubuntu Box and installed all web dev tools I need. Now I want to get a copy of this settings as is and use it from a place without internet connection.
What should I do to get a complete backup of my virtual box so I can use it at home? What files I need to copy.
Note: I am using Virtualbox and Vagrant.
Virtual box has export and import appliance features. Use them.
Related
I need a virtual desktop to access chrome on the go via the Chrome Remote Desktop app on IOS.
The virtual desktop should be the usual GUI where I can open / install programs like a normal PC.
I know Windows is not free hence I am stuck with linux.
I created account and I know I need to create an instance.
What instance? How to get GUI? How to setup and access using Chrome Remote Desktop? Etc
Totally clueless.
What I Did:
1) I installed a Ubantu instance with a disk space of 30G.
2) I went into the shell and tried to run commands for installing a standard GUI.
sudo apt-get install ubuntu-desktop
3) Immediately received errors of missing dependencies.
I am new to Docker, using windows 10 home edition, and want to create a docker image for my C++ project developed with visual studio. As far as I understand, the image I need to create is going to be a windows image, and therefore I need to install “Docker for windows” and enable the Hyper-V feature. This is not possible with my windows home edition, as Hyper-V is available for windows 10 pro only. The other alternative, using “Docker toolbox” and a virtualbox linux VM, does not support creating or pulling windows containers. Did I miss something? Is there a workaround?
You could use the Windows Linux Subsystem: https://medium.com/#sebagomez/installing-the-docker-client-on-ubuntus-windows-subsystem-for-linux-612b392a44c4
EDIT: On second read of your question you probably want to have a windows-container for visual studio. This solutions makes Linux-containers possible, but doesn't help with windows images...
As you know, you are unable to install Docker for Windows Home edition, as it requires Hyper V virtualization.
So these are your options:
You will need to install Docker Toolbox which uses VirtualBox instead.
Docs and setup info available here:
https://docs.docker.com/toolbox/toolbox_install_windows/
Release downloads available here:
https://github.com/docker/toolbox/releases
Toolbox will install everything you need including VirtualBox.
You may also need to enable virtualization in your computer's BIOS settings. This will be different for each manufacturer, please refer to their documentation on which keys to use to access these settings on reboot.
After Toolbox is finished installing, open the Docker Quickstart Terminal. This will complete the setup and provision your VirtualBox machine.
Check your install:
Launch the Docker QuickStart terminal and type the command:
docker run hello-world
This should pull down the test container and print hello-world to your screen.
I downloaded a VM instance from the web and launched / modified it using it using VMware Workstation 12 Player
I would now like to transfer this image onto an ESXi host running VMware ESXi Version 5.5.0.
I have tried copying the working directory "C:\Users\xxxx\Downloads\Kali-Linux-2.0.0-vm-amd64\Kali-Linux-2.0.0-vm-amd64" to the ESXi datastore and have tried to import it using a couple of methods:
I tried browsing to the Datastore, right clicking the "Kali-Linux-2.0.0-vm-amd64.vmx" file and selecting "add to inventory"
I tried creating a virtual machine, selecting the option to use and existing disk and pointed it at the VMDK file.
Both methods allow me to create the machine, but fail with the following error when I try to power it up.
Failed to start the virtual machine.
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/4dc219c6-2eb825c6-0119-d8d3855f4a40/Kali-Linux-2.0.0-vm-amd64/Kali-Linux-2.0.0-vm-amd64.vmdk' or one of the snapshot disks it depends on.
The system cannot find the file specified
VMware ESX cannot find the virtual disk "/vmfs/volumes/4dc219c6-2eb825c6-0119-d8d3855f4a40/Kali-Linux-2.0.0-vm-amd64/Kali-Linux-2.0.0-vm-amd64.vmdk". Verify the path is valid and try again.
I have checked and I can see the VMDK file on the Datastore.
I don't know if it of any significance, but the files on my desktop are broken down into multiple VMDK files and when I copied it to the Datastore, it turned them into one large VMDK file.
It might be best to use vmware converter to import the vm into your esxi host and/or even try an export to OVF from workstation and then an import (deploy OVF) to ESXi host.
From the error generated it looks like the original VM may still have some snapshots. Try and remove any snapshots, then take note of the disk controller and disk type of the workstation vm and check that it is supported for ESXi vm (for example IDE etc.), ESXi likes SCSI.
I am trying to create custom vagrant box file. I plan to use VirtualBox and I am reading this documentation: https://docs.vagrantup.com/v2/virtualbox/boxes.html
When the doc says,"VirtualBox Guest Additions must be installed so that things such as shared folders can function. Installing guest additions also usually improves performance since the guest OS can make some optimizations by knowing it is running within VirtualBox.
Before installing the guest additions, you'll need the linux kernel headers and the basic developer tools ...", but it doesn't say if this is to be done on the guest OS or host OS where I installed vargant and VirtualBox.
So I am guessing that I need to install a VM on VirtualBox and install the "VirtualBox Guest Addtitions" on this VM. Am I right?
The guest additions need to be installed on the guest OS. The host operating system only needs Virtualbox and vagrant installed. There are various descriptions out there for different operating systems and versions. It depends a bit on what your guest os looks like, so without a hint on what guest OS you are installing, I cannot provide more information.
Just FYI: You can use the boxes from vagrantcloud.com as a base, boot it and install softwareon top, exporting it to create "your" base box. In most cases, this works pretty well and you don't need to set up a whole new box. Take a look at the featured boxes, e.g. from chef. Chef boxes are the most basic setup one can create with really just the OS and the things vagrant need (ssh key, guest additions and so on).
I got a repo where I take a chef box and add some of my standard software stack (using chef) and export it as a new box. Have a look at Sgoettschkes/va for more information.
I am trying to load a VM that was created by someone else using VMware vSphere into virtualbox. I got these 3 files, the first one being an xml ovf file, the second one containing the SHA1 sums and the last one being a 3.2GB vmdk:
myVM.ovf
myVM.mf
myVM-disk1.vmdk
When I try Import an Appliance choosing the ovf file, I get this error:
Failed to import appliance /home/username/VirtualBox VMs/blah/blah/myVM.ovf.
<vbox:Machine> element in OVF contains a medium attachment for the disk image 58d8e82a-37a1-4c10-b3be-b53cdb213fbe but the OVF describes no such image.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}
I made sure the menu is pointing to the right vmdk file, but still there is something wrong.
Any ideas?
At the Import dialog, try to uncheck USB controller and CD/DVD devices.
If that will help, You can enable them afterwards. In fact, You will need them to install Guest Additions later.
This helped for me, to install Microsoft prepared Virtual machines for different Internet Explorer tests from http://dev.modern.ie/tools/vms/windows/
I received a similar issue today when doing a simple export / import of a windows 7 vm running Oracle VM 4.3.1 on linux mint. I exported in OVF 2.0 and it generated an .ova file. I had nearly identical error message when importing the image. I am assuming the image was made with Oracle VM.
"Failed to import appliance /home/val/Desktop/win7.ova"... "the OVF describes no such image"
THE FIX: All I had to do was rename the .ova file to .ovf; you may have to change the .ovf extension to .ova as well. Also ensure you are the owner of the file (chown) and you have correct permissions(chmod). This worked for me it may work for you.
I found this fix here: https://www.virtualbox.org/ticket/9414