Closed fatganz closed 11 years ago
Checked VirtualBox virtual machines directory and seems that vm exists there - UIDs from .vagrant
file and VM are matching.
This machine wasn't visible in Virtual Box Manager after I've imported it - status became poweroff. I've discovered that for me when new machine is imported by vagrant they do not appear in Virtual Box Manager. Is that expected behavior?
I think this is fixed now in 1.1. Can you verify?
After boot and provisioning my VM appears not created. Vagrant 1.0.3 Virtualbox 4.1.16, 4.1.20 MS Windows 7 Enterprise
Steps to reproduce: 1) Init new project with recipes (puppet or chef) 2)
vagrant up
(will boot Vm and provision it) - everything is ok at this step and machine is working 3)vagrant halt
4)vagrant status
Current VM states:default not created
The environment has not yet been created. Run
vagrant up
to create the environment.This is not always reproducible - working to get more information. Please suggest me what I can do to improve issue description.