From: Launchpad Bug Tracker <717929@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 717929] Re: Serial communication between VMs problematic
Date: Mon, 21 Jun 2021 04:17:32 -0000 [thread overview]
Message-ID: <162424905240.11837.12752395415846285033.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20110212234034.2762.77476.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/717929
Title:
Serial communication between VMs problematic
Status in QEMU:
Expired
Bug description:
Hello,
I want to setup serial communication between VM hosts but I have found
it quite difficult...:
...because when trying unix sockets:
- host A has serial device as unix socket (bind)
- host B has serial device as client of unix socket
- host A is down thus not unix socket does exist
- host B can't be started because cannot read the socket:
error: Failed to start domain opd1s02
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/0
connect(unix:/tmp/test.sock): Connection refused
chardev: opening backend "socket" failed
Can that work like the cable is not plugged in? So host B can start
and when the socket would exist it would connect to it?
...and when using pty and host device combination one cannot predict
pty device under /dev/pts, it would be nice if would be possible to
define exact device name.
Tested on Fedora 14.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/717929/+subscriptions
prev parent reply other threads:[~2021-06-21 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 23:40 [Qemu-devel] [Bug 717929] [NEW] Serial communication between VMs problematic jiribb
2020-08-07 7:59 ` [Bug 717929] " Thomas Huth
2021-04-22 3:53 ` Thomas Huth
2021-06-21 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162424905240.11837.12752395415846285033.malone@loganberry.canonical.com \
--to=717929@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.