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

Improve "VM limit exhausted" message #62

Closed
fmoc opened this issue May 9, 2023 · 0 comments · Fixed by #66
Closed

Improve "VM limit exhausted" message #62

fmoc opened this issue May 9, 2023 · 0 comments · Fixed by #66
Assignees
Labels
enhancement New feature or request

Comments

@fmoc
Copy link

fmoc commented May 9, 2023

Right now, this is the log output when trying to build a new VM with Packer when two are already running:

% packer build [...]
tart-cli.tart: output will be in this color.

==> tart-cli.tart: Cloning virtual machine...
==> tart-cli.tart: Updating virtual machine resources...
==> tart-cli.tart: Inspecting machine disk image...
==> tart-cli.tart: Getting partition table...
==> tart-cli.tart: Starting the virtual machine...
==> tart-cli.tart: Waiting for the VNC server credentials from Tart...
==> tart-cli.tart: Retrieved VNC credentials, connecting...
==> tart-cli.tart: Failed to connect to the Tart's VNC server: dial tcp 127.0.0.1:60993: connect: connection refused
==> tart-cli.tart: Waiting for the tart process to exit...
Build 'tart-cli.tart' errored after 1 second 61 milliseconds: Failed to connect to the Tart's VNC server: dial tcp 127.0.0.1:60993: connect: connection refused

It took me a while to figure out it's the 2 VMs limit which is responsible for this log output. Is there a way to catch the limit earlier and log this appropriately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
3 participants