Displaying 9 results from an estimated 9 matches for "qemumonitorjsonioprocessline".
2013 Mar 25
0
Bug in DOMINFO command when balloon driver is used on a vm with more then 8 GB of MaxMemory ?
...Process: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 :
qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds":
1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data":
{"actual": 12883853312}}]
2013-03-22 21:13:45.528+0000: 23179: debug : virJSONValueFromString:975 :
string={"times...
2018 Feb 27
2
Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
...Write:553 :
QEMU_MONITOR_IO_WRITE: mon=0x7f728c07f260
buf={"execute":"eject","arguments":{"device":"drive-ide0-1-0","force":false}
,"id":"libvirt-78"}
len=93 ret=93 errno=0
2018-02-26 13:09:13.669+0000: 50514: debug :
qemuMonitorJSONIOProcessLine:193 : Line [{"return": {}, "id": "libvirt-78"}]
2018-02-26 13:09:13.669+0000: 50514: info : qemuMonitorJSONIOProcessLine:213
: QEMU_MONITOR_RECV_REPLY: mon=0x7f728c07f260 reply={"return": {}, "id":
"libvirt-78"}
2018-02-26 13:09:13.669+0...
2015 Feb 11
0
Re: libvirt 1.2.10 and latest EL6 qemu-kvm
...a62801cbf0 buf={"id": "libvirt-5",
"error": {"class": "CommandNotFound", "desc": "The command qom-list
has not been found", "data": {"name": "qom-list"}}}
2015-02-11 14:10:33.261+0000: 13278: debug :
qemuMonitorJSONIOProcessLine:183 : Line [{"id": "libvirt-5", "error":
{"class": "CommandNotFound", "desc": "The command qom-list has not
been found", "data": {"name": "qom-list"}}}]
2015-02-11 14:10:33.261+0000: 13278: debug :
v...
2020 Oct 12
3
unable to migrate: virPortAllocatorSetUsed:299 : internal error: Failed to reserve port 49153
...emu+tls://ratchet.lan/system --live
--persistent --undefinesource --copy-storage-all --verbose
error: internal error: Failed to reserve port 49153
virsh #
On target host with debug logs, nothing interesting but the error
itself is found in the logs
...
2020-10-12 02:11:33.852+0000: 6871: debug :
qemuMonitorJSONIOProcessLine:220 : Line [{"return": {}, "id":
"libvirt-373"}]
2020-10-12 02:11:33.852+0000: 6871: info :
qemuMonitorJSONIOProcessLine:239 : QEMU_MONITOR_RECV_REPLY:
mon=0x7fe784255020 reply={"return": {}, "id": "libvirt-373"}
2020-10-12 02:11:33.852+00...
2017 May 16
3
Re: Duplicate reboot events
> On May 16, 2017, at 3:49 PM, Martin Kletzander <mkletzan@redhat.com> wrote:
>
> On Tue, May 16, 2017 at 06:41:05PM +0000, Innus, Martins wrote:
>> Hi,
>>
>> Running on:
>>
>> $ cat /etc/redhat-release
>> CentOS Linux release 7.3.1611 (Core)
>>
>> And:
>>
>> $ rpm -qa |grep libvirt
>>
2017 Jun 05
2
Re: libvirtd not accepting connections
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]
2017 Jun 06
3
Re: libvirtd not accepting connections
...ds. Like
'query-commands' which we need to know which commands we can run (bit of
a catch 22 right there). But these should not happen with x86, x86_64,
arm, arm64 (or aarch64), and few others. Those are being maintained
continuously.
>2017-06-05 23:06:39.884+0000: 15559: debug :
>qemuMonitorJSONIOProcessLine:191 : Line [{"id": "libvirt-41", "error":
>{"class": "GenericError", "desc": "this feature or command is not
>currently supported"}}]
>2017-06-05 23:06:39.884+0000: 15559: debug : virJSONValueFromString:1604
>: string...
2017 Jun 05
0
Re: libvirtd not accepting connections
...:
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: debug :
qemuMonitorJSONIOProcessLine:191 : Line [{"id": "libvirt-41", "error":
{"class": "GenericError", "desc": "this feature or command is not
currently supported"}}]
2017-06-05 23:06:39.884+0000: 15559: debug : virJSONValueFromString:1604
: string={"id&qu...
2017 Jun 06
0
Re: libvirtd not accepting connections
...64,
> arm, arm64 (or aarch64), and few others. Those are being maintained
> continuously.
The messages only show when qemu is "sudo make install" from sources.
In case it matters, all my existing VM's are x86_64.
>> 2017-06-05 23:06:39.884+0000: 15559: debug :
>> qemuMonitorJSONIOProcessLine:191 : Line [{"id": "libvirt-41", "error":
>> {"class": "GenericError", "desc": "this feature or command is not
>> currently supported"}}]
>> 2017-06-05 23:06:39.884+0000: 15559: debug : virJSONValueFromString:16...