[Qemu-devel] [Bug 1612908] [NEW] qom-[list, tree, get, set] don't accept tcp endpoint arg

[Qemu-devel] [Bug 1612908] [NEW] qom-[list, tree, get, set] don't accept tcp endpoint arg

[Carl Allendorph]

Public bug reported:

Hi,

I'm using origin/master [6bbbb0ac13...]. When I run any of the commands
in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text says that
it can connect to a QEMU instance by passing either a path to a unix
socket or a tcp endpoint in the format "host:port". The unix socket
variant works but the tcp endpoint variant does not. QEMUMonitorProtocol
accepts either a string (unix socket) or a tuple (host,port). None of
the qom-* scripts actually massage the '-s' argument into a tuple.

I have a patch to fix this issue that I can submit to the developer
list.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: python qom qom-list qom-tree scripts

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

Title:
  qom-[list,tree,get,set] don't accept tcp endpoint arg

Status in QEMU:
  New

Bug description:
  Hi,

  I'm using origin/master [6bbbb0ac13...]. When I run any of the
  commands in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text
  says that it can connect to a QEMU instance by passing either a path
  to a unix socket or a tcp endpoint in the format "host:port". The unix
  socket variant works but the tcp endpoint variant does not.
  QEMUMonitorProtocol accepts either a string (unix socket) or a tuple
  (host,port). None of the qom-* scripts actually massage the '-s'
  argument into a tuple.

  I have a patch to fix this issue that I can submit to the developer
  list.

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

[Bug 1612908] Re: qom-[list, tree, get, set] don't accept tcp endpoint arg

[Thomas Huth]

Hi! Triaging old bug tickets ... is this still an issue with the latest
version of QEMU? If you've got a patch for this ready, please send it to
the qemu-devel mailing list!

** 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/1612908

Title:
  qom-[list,tree,get,set] don't accept tcp endpoint arg

Status in QEMU:
  Incomplete

Bug description:
  Hi,

  I'm using origin/master [6bbbb0ac13...]. When I run any of the
  commands in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text
  says that it can connect to a QEMU instance by passing either a path
  to a unix socket or a tcp endpoint in the format "host:port". The unix
  socket variant works but the tcp endpoint variant does not.
  QEMUMonitorProtocol accepts either a string (unix socket) or a tuple
  (host,port). None of the qom-* scripts actually massage the '-s'
  argument into a tuple.

  I have a patch to fix this issue that I can submit to the developer
  list.

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

[Bug 1612908] Re: qom-[list, tree, get, set] don't accept tcp endpoint arg

[Launchpad Bug Tracker]

[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/1612908

Title:
  qom-[list,tree,get,set] don't accept tcp endpoint arg

Status in QEMU:
  Expired

Bug description:
  Hi,

  I'm using origin/master [6bbbb0ac13...]. When I run any of the
  commands in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text
  says that it can connect to a QEMU instance by passing either a path
  to a unix socket or a tcp endpoint in the format "host:port". The unix
  socket variant works but the tcp endpoint variant does not.
  QEMUMonitorProtocol accepts either a string (unix socket) or a tuple
  (host,port). None of the qom-* scripts actually massage the '-s'
  argument into a tuple.

  I have a patch to fix this issue that I can submit to the developer
  list.

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