be
great to store last X events in central memory location)
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mardi 19 Mars 2013 18:13:36
Objet: RE: [pve-devel] how to catch qmp events ?
mmm, doc
It could be great to store last X events in central memory location
I think we should not depend on such async information in any way.
Instead, qemu command should store that info if it is really needed.
___
pve-devel mailing list
diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 20 Mars 2013 08:35:45
Objet: RE: [pve-devel] how to catch qmp events ?
It could be great to store last X events in central memory location
I think we should not depend on such async
and qmp block-job-status say no block-job running.
So I really don't know how to retrieve error of the block-job-mirror.
How do you manage this kind of error with backups ? (I think it's also a
block-job
?)
I have an extra command 'backup' which starts the block-job and stores any
mirror block-job simply stop itself, but I don't have the error message.
There was some recent patches on the qemu-devel list to improve logging, but
AFAIK
many error messages are still sent to /dev/null when you run with --damonize.
___
pve-devel
: [pve-devel] how to catch qmp events ?
mirror block-job simply stop itself, but I don't have the error message.
There was some recent patches on the qemu-devel list to improve logging, but
AFAIK
many error messages are still sent to /dev/null when you run with --damonize
to add this in qmpclient.pm
- Mail original -
De: Alexandre DERUMIER aderum...@odiso.com
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mardi 19 Mars 2013 18:01:23
Objet: Re: [pve-devel] how to catch qmp events ?
documentation
http://wiki.qemu.org/Features
