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

serial/console access functionality #37

Open
leifliddy opened this issue Apr 25, 2023 · 1 comment
Open

serial/console access functionality #37

leifliddy opened this issue Apr 25, 2023 · 1 comment

Comments

@leifliddy
Copy link

leifliddy commented Apr 25, 2023

Is there a convenient way to associate a VM with its socket_path?
The vagrant paths are not logically named.

[leif.liddy@mac ~]$ find .vagrant.d/ | grep socket_serial
.vagrant.d//tmp/vagrant-qemu/UVg8j53wuBs/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/wNR_5RUixTs/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/1TTkvUQgz6Q/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/5wbGTEzltJM/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/g8P2n_5CawA/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/wNwtgWiaMxs/qemu_socket_serial
.vagrant.d//tmp/vagrant-qemu/zABVz-znJlA/qemu_socket_serial

Having an equivalent function to vagrant ssh-config or vagrant-ssh would be a really useful feature
Where you would run something like
vagrant serial-config to list the qemu_socket_serial paths for each VM.

and/or maybe something like
vagrant console [vm_name] or vagrant serial [vm_name] to serial/console in to a specific VM.

Anyone of these features would be extremely useful. Anyways, just a thought.
Thank you for such a cool project!

@leifliddy leifliddy changed the title console access serial/console access functionality Apr 25, 2023
@ppggff
Copy link
Owner

ppggff commented Apr 26, 2023

Thanks, I will try to add these custom commands.

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