On 06/09/2010 10:18 AM, Luiz Capitulino wrote:
The big problem is things like the block io error events. I don't see
how we can support that given what we have in 0.13. Putting errno on
the wire is a bad idea. We need to marshal a QError object using the
__class__ memory to identify it as QError and pass that with the event.
It could potentially be made to work for 0.13 but it'll be ugly.
Yes, that's the main problem of the whole thing I think.
From QEMU pov, the best thing to do would be to let this event as it's
today and wait for the new QError (it's a compatible change, anyway).
I'd prefer that we just send the event with an embedded qerror (using
__class__). We can generate it directly instead of using
qerror_report/qerror_new. It's ugly but it'll work and be future
compatible. For now, let's just support a few types of qerror to
basically distinguish between an unknown io error and ENOSPC.
However, libvirt was counting on this feature and on the snapshot commands
to switch from the text Monitor. We have two options:
I don't think snapshots are actually usable by libvirt in the current form.
Regards,
Anthony LIguori
1. Ask them to wait one more release (not so good for us)
2. Try to find a way to have those features in for 0.13
Daniel has commented to me that making the snapshot commands synchronous
for 0.13 wouldn't be that bad, what do you think?
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
