[pve-devel] qemu-server : drive-mirror : die if stats are empty.

[Alexandre DERUMIER]

>>IMHO, A block job should store the error somewhere, so that we can query it later. 
>>(like I do it for the backup task). 

OH, ok, so indeed if it's possible to retrieve them, it could be great. I'll try to read the qemu code.

>>Everything is possible ;-) But we now have a simple, stateless interface. I am not really keen 
>>to make that more complex. At least I would wait until we really need it. 
Yes, it was just an idea ;) I agree to keep things simple :) 

----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 7 Mai 2013 08:02:54 
Objet: RE: [pve-devel] qemu-server : drive-mirror : die if stats are empty. 

> >>What for? Just to log event messages? 
> no ;), of course,that was just an example. Maybe something like a shared 
> memory with last qmp events, to be able to use them from proxmox code 
> 
> it should great to be able to known if a block job have die and the block job error 
> detail, if a bad sector exist by example (for drive-mirror, can be usefull for 
> backup too). 

IMHO, A block job should store the error somewhere, so that we can query it later. 
(like I do it for the backup task). 

> Maybe it could be usefull too for other things in the future, like spice qmp events 
> (client connect/disconnectd events). 
> 
> 
> Another idea, maybe it should be possible to stream events to extjs (websocket 
> ?), to instant update running vm status in the gui, without need to pool the 
> status. (It's just an idea ;) 

Everything is possible ;-) But we now have a simple, stateless interface. I am not really keen 
to make that more complex. At least I would wait until we really need it.