Skip to content

Vagrant SSH connections with Parallels #18

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

Open
Jaymon opened this issue Jan 30, 2023 · 0 comments
Open

Vagrant SSH connections with Parallels #18

Jaymon opened this issue Jan 30, 2023 · 0 comments

Comments

@Jaymon
Copy link
Owner

Jaymon commented Jan 30, 2023

I have notes on my findings in sysadmin/vagrant/parallels-configuration/_NOTES.md

The biggest problem is it seems bento boxes seem to share the same machine-id which messes up the DHCP leases that parallels gives you and puts Vagrant in a bad state. For example, I can run:

$ cat /Library/Preferences/Parallels/parallels_dhcp_leases
[vnic0]
10.211.55.3="1675109922,1800,001c42cc5e4c,ff0824450a00020000bb113754a24acdf09cbb"

But I actually have two bento 20.04 boxes up and running. And they both seem to be running, because I can talk to the db of the second box through the forwarded port, but I can't ssh into it, in fact, I can't run vagrant ssh in either of the directories and ssh into the boxes, I have to ssh into them directly:

And that's only for the first box, as far as I can tell, I can't ssh into the second box at all, it's just up and running with no way to get into it.

I need to get sshv working for parallels, basically parsing the parallels_dhcp_leases file for the ip addresses. ff0824450a00020000bb113754a24acdf09cbb doesn't seem to correspond to the box ids found running vagrant status though, so I'll have to poke around and see what I can find

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

1 participant