Displaying 3 results from an estimated 3 matches for "983916".
2014 Jul 23
2
how to read the libvirt log file
...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
2014 Jul 23
0
Re: how to read the libvirt log file
...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!
If you have libvirt.git checked out:
$ git grep -l qemuMonitorIOProcess | cat
src/qemu/qemu_monitor.c
Now look at line 356 of that file (assuming you hav...
2015 Feb 13
4
libvirt live migration, qcow2 image, nbd server
Hi all,
When I live migrate a vm using
"migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system
tcp://192.168.1.3"
I got the following error
WARNING: Image format was not specified for
'nbd://node2:49155/drive-virtio-disk0' and probing guessed raw.
258 Automatically detecting the format is dangerous for raw
images, write operations on