Check the VirtualBox gui if there is any VM in the GUI left, and in the
media manager is there is any orphan disk.
Be sure to be running Vagrant as your normal user, and not as Administrator.
Alvaro.
On Wed, Feb 3, 2016 at 8:46 PM, Rob Woerner
wrote:
> My apologies
I have a Windows 8.1 machine. I have installed Vagrant and VirtualBox. If I
start an Ubuntu VM (ubuntu/trusty32) up using VirtualBox it seems to start
fine. I can then use the following command to connect:
> vagrant ssh
However, if I instead use Vagrant to start the VM, it times out. The
Hello,
Can you try using vagrant package?
z2-3:~ kikitux$ vagrant package -h
Usage: vagrant package [options] [name]
Options:
--base NAME Name of a VM in virtualbox to package
as a base box
--output NAMEName of the file to output
Hi,
I did use vagrant package to create the box.
And the vagrant file got packaged correctly (./include/Vagrantfile and
./Vagrantfile (which points to the former)) as the above files show.
But when I use the box, the embedded vagrant file is not getting run -
that's my issue.
If I do a
>
>
> Problem resolved by running this command in an elavated command prompt
bcdedit /set hypervisorlaunchtype off
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may
Figured it out. There was an error in my Vagrantfile. It was being run, but
the section of config I used to configure my ssh settings was not getting
reached.
Thanks,
||Rich
On Wednesday, February 3, 2016 at 8:32:01 AM UTC-5, Richard Wellum wrote:
>
> Hi,
>
> I did use vagrant package to
That's an important item to note. If the Windows machine has Hyper-V
running it has to be turned off in order for VirtualBox to run correctly,
especially when run through Vagrant. This applies to Windows 8.x and 10.
On Wednesday, February 3, 2016 at 6:04:22 AM UTC-8, Paul Davidson wrote:
>
>
>>