-
Notifications
You must be signed in to change notification settings - Fork 659
Revert virtserialport back to unix socket for QEMU guest agent communication #2112
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
Revert virtserialport back to unix socket for QEMU guest agent communication #2112
Conversation
@@ -128,7 +128,8 @@ func New(instName string, stdout io.Writer, sigintCh chan os.Signal, opts ...Opt | |||
} | |||
vSockPort = port | |||
} else if *y.VMType == limayaml.QEMU { | |||
virtioPort = filenames.VirtioPort | |||
// virtserialport doesn't seem to work reliably: https://github.com/lima-vm/lima/issues/2064 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you report this to https://gitlab.com/qemu-project/qemu/-/issues ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what exactly I would report; I have no more information beyond that the code in Lima sometimes fails. It doesn't even fail reliably, which is why the bisect script restarts the VM up to 100 times before accepting that the code works properly.
I haven't checked if the problem happens on the sending or the receiving side, as we are not getting any errors.
So I feel this would need some more investigation before reporting to upstream, but unfortunately I'm out of time right now. 😞
a8ef354
to
61cf141
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Shall we release a new version after merging this? |
Converted to draft because it only works properly with Ubuntu, but not with Alpine. Will investigate... |
…ication The serial port sometimes doesn't seem to work: lima-vm#2064 Signed-off-by: Jan Dubois <[email protected]>
61cf141
to
9e1a07a
Compare
I think I fixed it now (just some quoting issues in |
Seems to work fine with Alpine as well now.
I think so, as running into the flakiness is annoying, and not immediately obvious if it is your fault or not. Don't really care about the version 0.19.2 vs. 0.20.0; either one works for me. |
@@ -128,7 +128,8 @@ func New(instName string, stdout io.Writer, sigintCh chan os.Signal, opts ...Opt | |||
} | |||
vSockPort = port | |||
} else if *y.VMType == limayaml.QEMU { | |||
virtioPort = filenames.VirtioPort | |||
// virtserialport doesn't seem to work reliably: https://github.com/lima-vm/lima/issues/2064 | |||
virtioPort = "" // filenames.VirtioPort |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-assigning the empty string here to satisfy the linter; couldn't get it to shut up blathering about empty branches and empty blocks if I left everything commented out...
@balajiv113 LGTY? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
The serial port sometimes doesn't seem to work: #2064.
The vsock implementation used for VZ doesn't seem to have this problem.
It makes sense to revert to the old mechanism for QEMU until the serialport has been fixed (if possible).
Just commenting out the virtioPort will fall back to the old socket method thanks to #2006.