-
-
Notifications
You must be signed in to change notification settings - Fork 604
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
Don't use qemu's "-redir" option in run.py #781
Comments
OSv does not include by default (or at all) an SSH server for a long time, so the forwarding of the guest's port 22 to port 2222 on the guest is pretty pointless. And generates the annoying message of issue #781. Signed-off-by: Nadav Har'El <nyh@scylladb.com>
OSv does not include by default (or at all) an SSH server for a long time, so the forwarding of the guest's port 22 to port 2222 on the guest is pretty pointless. And generates the annoying message of issue cloudius-systems#781. Signed-off-by: Nadav Har'El <nyh@scylladb.com>
Dear @nyh , I have played for a while with it today and it turns out, According to the documentation [1], we should set something like this:
So, I tried this:
But because we set netdev before handling "--api" or "--forward", qemu fails with the following message:
It's strange that it fails because the same documentation says it can handle multiple -netdev entries... [1] https://wiki.qemu.org/Documentation/Networking Kind Regards, |
@geraldo-netto I think the redirection options ("api" and "forward") are only relevant to the emulated network (qemu's "user" network), not to bridging mode, so I think the solution is to do something like your above code, but only in the one specific case (an "else:" section of if options.networking) where the "user" netdev is being set up by run.py. So it's more or less what you suggested, just that you need to do it only for the user netdev, not the bridge ones. Looks pretty straightforward. |
QEMU's "-redir" option has been deprecated for at least 5 years now, but silently supported. Since QEMU 2.6, it started to be annoyingly loud about it:
We can probably fix it exactly as the message suggests.
The text was updated successfully, but these errors were encountered: