The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state
back to "New" within the next 60 days, otherwise this report will be marked as
"Expired". Or mark it as "Fix Released" if the problem has been solved with a
newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
