qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Prem Anand <1544524@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1544524] Re: "info chardev" not showing the real port in use
Date: Thu, 11 Feb 2016 15:21:31 -0000	[thread overview]
Message-ID: <20160211152131.4966.9305.malone@gac.canonical.com> (raw)
In-Reply-To: 20160211115903.17778.55276.malonedeb@soybean.canonical.com

Also on quickly connecting to the ports via the netcat tool (hoping that it would make qemu to change its state from disconnected)
I see the following error "Error in getpeername: Transport endpoint is not connected"

pharidos@uks2:~/$ qemu-system-x86_64 --enable-kvm -hda Sisk.qcow2 -serial telnet::0,server,nowait -serial telnet::0,server,nowait -nographic 
QEMU 2.5.0 monitor - type 'help' for more information
(qemu) info chardev
parallel0: filename=null
serial1: filename=disconnected:telnet::0,server
serial0: filename=disconnected:telnet::0,server
compat_monitor0: filename=stdio
(qemu) 

# COnnect quickly to the serial ports via netcat
pharidos@kvm:~/$ netstat -tupan 2>/dev/null | grep "LISTEN.* $(pgrep -f qemu)/qemu" | cut -d: -f2 | cut -d' ' -f1
45814
42522
pharidos@kvm:~/$ ports=$(netstat -tupan 2>/dev/null | grep "LISTEN.* $(pgrep -f qemu)/qemu" | cut -d: -f2 | cut -d' ' -f1)
pharidos@kvm:~/$ for p in $ports; do echo | nc -w0 kvm $p >/dev/null; done

# Check the port status again. We see the the error "Error in getpeername: Transport endpoint is not connected"
(qemu) info chardev
parallel0: filename=null
serial1: filename=Error in getpeername: Transport endpoint is not connected

serial0: filename=Error in getpeername: Transport endpoint is not
connected

compat_monitor0: filename=stdio
(qemu)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1544524

Title:
  "info chardev" not showing the real port in use

Status in QEMU:
  New

Bug description:
  With Qemu 2.1.2
  ===============
  pharidos@uks2:~$ qemu-system-x86_64 -hda Disk.qcow2 -serial telnet::0,server,nowait -nographic
  QEMU 2.1.2 monitor - type 'help' for more information
  (qemu) info chardev
  parallel0: filename=null
  serial0: filename=telnet:0.0.0.0:44189,server
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^ serial console is using port 44189
  compat_monitor0: filename=stdio
  (qemu)

  With Qemu 2.5.0
  ===============
  pharidos@uks2:~$ qemu-system-x86_64 -hda Disk.qcow2 -serial  telnet::0,server,nowait -nographic
  QEMU 2.5.0 monitor - type 'help' for more information
  (qemu) info chardev
  parallel0: filename=null
  serial0: filename=disconnected:telnet::0,server
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ serial console port not shown
  compat_monitor0: filename=stdio
  (qemu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1544524/+subscriptions

  reply	other threads:[~2016-02-11 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 11:59 [Qemu-devel] [Bug 1544524] [NEW] "info chardev" not showing the real port in use Prem Anand
2016-02-11 15:21 ` Prem Anand [this message]
2019-04-16  5:42 ` [Qemu-devel] [Bug 1544524] " Thomas Huth
2019-04-16  5:42   ` Thomas Huth
2019-04-16 10:37 ` Prem Anand
2019-04-16 10:37   ` Prem Anand

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=20160211152131.4966.9305.malone@gac.canonical.com \
    --to=1544524@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).