-
Notifications
You must be signed in to change notification settings - Fork 42
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
Console wont connect to VMs on external HOST #28
Comments
That's exactly what is done but address must be set to 0.0.0.0 as 127.0.0.1 won't allow remote connections: |
seems it doesnt work in my case, in logs i can see: in XML of a VM I had set: and on a HOST system, port is open and listening Virtlyst is using QEMU+SSH to a host 192.168.4.10 |
This is fixed in git master, I haven't tagget a Virtlyst release after that yet |
Is it possible to use ssh to redirect if 127.0.01 is used? I'm using localhost and virt-manager can do this with ssh without any problems. Maybe libvirt already supports it? |
Both use libvirt under the hood so likely possible, the main issue with SSH is if it want's to prompt for password, you better use ssh-keys then |
Yeah, I already added ssh key and it works perfect. Just the console is not working because I like to use localhost and authorization over ssh. |
hmm don't know exactly what you want, but likely https://github.com/cutelyst/Virtlyst/blob/master/src/lib/connection.cpp |
As in topic, WebConsole aquires IP address from VMS config and tries to connect to 127.0.0.1 or 0.0.0.0 on port 5900 (for the first VM). To be able to connect I was forced to manualy edit XML and set the address to some routable address.
A good starting pooint would be to take an IP from the Host's Connection details (when used as a qemu+ssh/tcp/tls)
The text was updated successfully, but these errors were encountered: