[Qemu-devel] [Bug 717929] [NEW] Serial communication between VMs problematic

[jiribb]

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
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:
  New

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.