search for: qemumonitorioprocess

Hi folks, I need to trace how libvirt talk with qemu monitor, log everything when give command, but does anyone know what the format, and how to read the log file? for example: 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 : QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds": 1406049922, "microseconds": 983916}, "event": "STOP"} where to find the qemuMonitorIOProcess function, and what :356 means? Thanks very much! Best, Yuanzhen

...01:48 PM, Yuanzhen Gu wrote: > Hi folks, > > > I need to trace how libvirt talk with qemu monitor, log everything when > give command, but does anyone know what the format, and how to read the log > file? > > for example: > 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 : > QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds": > 1406049922, "microseconds": 983916}, "event": "STOP"} > > where to find the qemuMonitorIOProcess function, and what :356 means? > Thanks very much!...

...quot;} 2013-03-22 21:13:45.523+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d6c1789e0 buf={"execute":"balloon","arguments":{"value":8589934592},"id":"libvirt-9"} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMon...

...0+0000: 13278: info : qemuMonitorIOWrite:503 : QEMU_MONITOR_IO_WRITE: mon=0x7fa62801cbf0 buf={"execute":"qom-list","arguments":{"path":"/machine/unattached/device[0]"},"id":"libvirt-5"} 2015-02-11 14:10:33.261+0000: 13278: info : qemuMonitorIOProcess:399 : QEMU_MONITOR_IO_PROCESS: mon=0x7fa62801cbf0 buf={"id": "libvirt-5", "error": {"class": "CommandNotFound", "desc": "The command qom-list has not been found", "data": {"name": "qom-list"}}} 2015-...

On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >I've upgraded from Fedora 20; probably missed a merge of rpmnew with >existing .conf; permission problem, some other mistake along the way to >Fedora 25. > Yeah, probably some 'rpm -qV' (or whatever the command to verify all packages is) could help as well. >Is there a "how to" similar to [1]

.../qemu-*) > >2017-06-05 23:06:39.884+0000: 15559: info : >virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 >events=1 >2017-06-05 23:06:39.884+0000: 15559: info : virObjectRef:296 : >OBJECT_REF: obj=0x7f0a603d33b0 >2017-06-05 23:06:39.884+0000: 15559: info : qemuMonitorIOProcess:429 : >QEMU_MONITOR_IO_PROCESS: mon=0x7f0a603d33b0 buf={"id": "libvirt-41", >"error": {"class": "GenericError", "desc": "this feature or command is >not currently supported"}}^M > len=120 Well, at least QEMU_MONITOR...

...source (in /usr/local/bin/qemu-*) 2017-06-05 23:06:39.884+0000: 15559: info : virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 events=1 2017-06-05 23:06:39.884+0000: 15559: info : virObjectRef:296 : OBJECT_REF: obj=0x7f0a603d33b0 2017-06-05 23:06:39.884+0000: 15559: info : qemuMonitorIOProcess:429 : QEMU_MONITOR_IO_PROCESS: mon=0x7f0a603d33b0 buf={"id": "libvirt-41", "error": {"class": "GenericError", "desc": "this feature or command is not currently supported"}}^M len=120 2017-06-05 23:06:39.884+0000: 15559: debu...

...-05 23:06:39.884+0000: 15559: info : >> virEventPollDispatchHandles:506 : EVENT_POLL_DISPATCH_HANDLE: watch=11 >> events=1 >> 2017-06-05 23:06:39.884+0000: 15559: info : virObjectRef:296 : >> OBJECT_REF: obj=0x7f0a603d33b0 >> 2017-06-05 23:06:39.884+0000: 15559: info : qemuMonitorIOProcess:429 : >> QEMU_MONITOR_IO_PROCESS: mon=0x7f0a603d33b0 buf={"id": "libvirt-41", >> "error": {"class": "GenericError", "desc": "this feature or command is >> not currently supported"}}^M >> len=120 > >...