Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant does not recognise the machine anymore #39

Open
royteeuwen opened this issue Jun 9, 2016 · 1 comment
Open

Vagrant does not recognise the machine anymore #39

royteeuwen opened this issue Jun 9, 2016 · 1 comment

Comments

@royteeuwen
Copy link

I created a vagrant box, and when it is done, I made a snapshot. The next day after I have shutdown my macbook and brought it back up, I get the following error when trying to bring up the machine:

Bringing machine 'publish1' up with 'virtualbox' provider...
==> publish1: Importing base box 'publish'...
==> publish1: Matching MAC address for NAT networking...
==> publish1: Checking if box 'publish' is up to date...
A VirtualBox machine with the name 'publish1' already exists.
Please use another name or delete the machine with the existing
name, and try again.

It seems it does not know the machine anymore after making a snapshot, this does not ever happen when I don't make a snapshot. I have tried it a few times already now and it keeps happening.

Any thoughts? I manually tried to edit the uuid in .vagrant/machines/virtualbox/publish1/id back to the id found by VBoxManage showhdinfo on the specific box, but that sadly doesn't fix the problem, it wont come up again

@dergachev
Copy link
Owner

The error message suggests that it's trying to create another machine
"publish1" anew, instead of re-starting your existing one.
Maybe "vagrant global-status" can help.

I don't think it's likely to be related to snapshots, but I guess you never
know.
Here's a random vagrant ticket that seems related, maybe there's debug
hints there for you: hashicorp/vagrant#1755

Keep in mind that vagrant-vbox-manage is just a simple wrapper around
VBoxManage, so I guess I'd recommend debugging using VBoxManage to see
what's actually happening. Perhaps if you can reproduce the bug and
identify an exact set of commands that triggers it, I'll take another look.

Sorry I can't be of more help, and good luck!!


Alex Dergachev Evolving Web
Lead developer web design & development
alex@evolvingweb.ca http://evolvingweb.ca
phone 514.844.4930 300 St Sacrement, #204

fax 514.807.7499 Montreal, QC, H2Y 1X4

On Thu, Jun 9, 2016 at 10:35 AM, Roy Teeuwen notifications@github.com
wrote:

I created a vagrant box, and when it is done, I made a snapshot. The next
day after I have shutdown my macbook and brought it back up, I get the
following error when trying to bring up the machine:

Bringing machine 'publish1' up with 'virtualbox' provider...
==> publish1: Importing base box 'publish'...
==> publish1: Matching MAC address for NAT networking...
==> publish1: Checking if box 'publish' is up to date...
A VirtualBox machine with the name 'publish1' already exists.
Please use another name or delete the machine with the existing
name, and try again.

It seems it does not know the machine anymore after making a snapshot,
this does not ever happen when I don't make a snapshot. I have tried it a
few times already now and it keeps happening.

Any thoughts? I manually tried to edit the uuid in
.vagrant/machines/virtualbox/publish1/id back to the id found by VBoxManage
showhdinfo on the specific box, but that sadly doesn't fix the problem, it
wont come up again


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#39, or mute
the thread
https://github.com/notifications/unsubscribe/AAIS4PpCowZFec8m52aN60JyK2d3hm6Wks5qKCSvgaJpZM4IyCmz
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants