On Thu, 10 Jun 2010 09:27:34 -0500
Anthony Liguori anth...@codemonkey.ws wrote:
On 06/10/2010 08:08 AM, Kevin Wolf wrote:
Am 10.06.2010 14:53, schrieb Anthony Liguori:
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh, why this? Seems I still haven't understood all of qcow2
On 06/11/2010 07:55 AM, Luiz Capitulino wrote:
On Thu, 10 Jun 2010 09:27:34 -0500
Anthony Liguorianth...@codemonkey.ws wrote:
On 06/10/2010 08:08 AM, Kevin Wolf wrote:
Am 10.06.2010 14:53, schrieb Anthony Liguori:
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh,
Am 09.06.2010 18:22, schrieb Anthony Liguori:
On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
However, libvirt was counting on this feature and on the snapshot commands
to switch from the text Monitor. We have two options:
1. Ask them to wait one more release (not so good for us)
2.
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh, why this? Seems I still haven't understood all of qcow2 then... I
always thought that there's just a specific offset where VM state
starts, but no explicit end.
A live snapshot can last for a very long time. What happens if you need
to
Am 10.06.2010 14:53, schrieb Anthony Liguori:
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh, why this? Seems I still haven't understood all of qcow2 then... I
always thought that there's just a specific offset where VM state
starts, but no explicit end.
A live snapshot can last for a
On 06/10/2010 04:08 PM, Kevin Wolf wrote:
It's just not seen by the guest because
it's saved at a high offset that is after the end of the real disk
content, but otherwise it should behave the same as guest data.
That's very unfriendly towards extending the guest-visible portion of
the
Am 10.06.2010 16:11, schrieb Avi Kivity:
On 06/10/2010 04:08 PM, Kevin Wolf wrote:
It's just not seen by the guest because
it's saved at a high offset that is after the end of the real disk
content, but otherwise it should behave the same as guest data.
That's very unfriendly towards
On 06/10/2010 08:08 AM, Kevin Wolf wrote:
Am 10.06.2010 14:53, schrieb Anthony Liguori:
On 06/10/2010 04:43 AM, Kevin Wolf wrote:
Huh, why this? Seems I still haven't understood all of qcow2 then... I
always thought that there's just a specific offset where VM state
starts, but no
On Tue, 08 Jun 2010 16:13:37 -0500
Anthony Liguori anth...@codemonkey.ws wrote:
On 06/08/2010 03:59 PM, Luiz Capitulino wrote:
Now, QError.
This is something I think we should fix for 0.13. However, I still don't
know how to get it right: most of what you say in the wiki page has
On Wed, Jun 09, 2010 at 12:18:20PM -0300, Luiz Capitulino wrote:
On Tue, 08 Jun 2010 16:13:37 -0500
Anthony Liguori anth...@codemonkey.ws wrote:
On 06/08/2010 03:59 PM, Luiz Capitulino wrote:
Now, QError.
This is something I think we should fix for 0.13. However, I still don't
On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
However, libvirt was counting on this feature and on the snapshot commands
to switch from the text Monitor. We have two options:
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
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
On Wed, Jun 09, 2010 at 11:22:55AM -0500, Anthony Liguori wrote:
On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
However, libvirt was counting on this feature and on the snapshot
commands
to switch from the text Monitor. We have two options:
1. Ask them to wait one more release
On Tue, 08 Jun 2010 11:01:19 -0500
Anthony Liguori anth...@codemonkey.ws wrote:
On 06/08/2010 10:05 AM, Chris Wright wrote:
[...]
migration events?
- QMP (wire protocol) has nice async events
- QError reasonable
- migration is async command, can complete w/ error or success
-
On 06/08/2010 03:59 PM, Luiz Capitulino wrote:
Now, QError.
This is something I think we should fix for 0.13. However, I still don't
know how to get it right: most of what you say in the wiki page has already
been discussed before.
For example, you suggest the error object should be
15 matches
Mail list logo
