Luiz Capitulino writes:
> On Tue, 04 May 2010 16:56:19 -0500
> Anthony Liguori wrote:
>
>> On 05/04/2010 03:30 PM, Luiz Capitulino wrote:
>> >
>> > StateVmSaveFailed is not like CommandFailed, there are five errors
>> > in do_savevm() and StateVmSaveFailed happens to be one of them.
>> >
>> >
Anthony Liguori writes:
> On 05/03/2010 08:06 AM, Markus Armbruster wrote:
>> Luiz Capitulino writes:
>>
>>
>>> We need to expose errno in QMP, for three reasons:
>>>
>>>1. Some error handling functions print errno codes to the user,
>>> while it's debatable whether this is good or
On Tue, 04 May 2010 16:56:19 -0500
Anthony Liguori wrote:
> On 05/04/2010 03:30 PM, Luiz Capitulino wrote:
> >
> > StateVmSaveFailed is not like CommandFailed, there are five errors
> > in do_savevm() and StateVmSaveFailed happens to be one of them.
> >
> > But I understand what you mean and
On 05/04/2010 03:30 PM, Luiz Capitulino wrote:
StateVmSaveFailed is not like CommandFailed, there are five errors
in do_savevm() and StateVmSaveFailed happens to be one of them.
But I understand what you mean and I have considered doing something
like it, one of the problems though is that
On Tue, 04 May 2010 09:03:47 -0500
Anthony Liguori wrote:
> On 05/04/2010 08:56 AM, Luiz Capitulino wrote:
> > On Mon, 03 May 2010 08:16:35 -0500
> > Anthony Liguori wrote:
> >
> >
> >> On 05/03/2010 08:06 AM, Markus Armbruster wrote:
> >>
> >>> Luiz Capitulino writes:
> >>>
> >>>
>
On Mon, 03 May 2010 08:16:35 -0500
Anthony Liguori wrote:
> On 05/03/2010 08:06 AM, Markus Armbruster wrote:
> > Luiz Capitulino writes:
> >
> >
> >> We need to expose errno in QMP, for three reasons:
> >>
> >>1. Some error handling functions print errno codes to the user,
> >> whi
On 05/04/2010 08:56 AM, Luiz Capitulino wrote:
On Mon, 03 May 2010 08:16:35 -0500
Anthony Liguori wrote:
On 05/03/2010 08:06 AM, Markus Armbruster wrote:
Luiz Capitulino writes:
We need to expose errno in QMP, for three reasons:
1. Some error handling functions pri
On 05/03/2010 08:06 AM, Markus Armbruster wrote:
Luiz Capitulino writes:
We need to expose errno in QMP, for three reasons:
1. Some error handling functions print errno codes to the user,
while it's debatable whether this is good or not from a user
perspective, sometimes it
Luiz Capitulino writes:
> We need to expose errno in QMP, for three reasons:
>
> 1. Some error handling functions print errno codes to the user,
> while it's debatable whether this is good or not from a user
> perspective, sometimes it's the best we can do because it's
> what sys
We need to expose errno in QMP, for three reasons:
1. Some error handling functions print errno codes to the user,
while it's debatable whether this is good or not from a user
perspective, sometimes it's the best we can do because it's
what system calls and libraries return
2.
10 matches
Mail list logo
