Hello,
Am Donnerstag 20 Januar 2011 04:05:46 schrieb Jim Fehlig:
> I think a patch addressing the issue in the JSON monitor, where we can
> reliably detect the error, is a good start. Would that be okay? Also,
> recall that I cannot reproduce the issue with qemu 0.13.
We can reliably reproduct
On 01/19/2011 10:05 PM, Jim Fehlig wrote:
I think a patch addressing the issue in the JSON monitor, where we can
reliably detect the error, is a good start. Would that be okay?
Agreed.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Jim Fehlig wrote:
> Agreed. What error do you get back from the text monitor when cont cmd
> fails? I'd be interested in the following output from
> $root/src/qemu/qemu_monitor_text.c:qemuMonitorCommandWithHandler()
>
> VIR_DEBUG("Receive command reply ret=%d errno=%d %d bytes '%s'",
>
On 01/18/2011 01:15 PM, Jim Fehlig wrote:
Laine Stump wrote:
On 01/14/2011 04:26 PM, Jim Fehlig wrote:
Laine Stump wrote:
On 01/13/2011 04:29 PM, Jim Fehlig wrote:
Daniel P. Berrange wrote:
Yep, it wasn't really intended as a fix. It was intended to make
the error scenario clearly dete
Laine Stump wrote:
> On 01/14/2011 04:26 PM, Jim Fehlig wrote:
>> Laine Stump wrote:
>>> On 01/13/2011 04:29 PM, Jim Fehlig wrote:
Daniel P. Berrange wrote:
>> Yep, it wasn't really intended as a fix. It was intended to make
>> the error scenario clearly detectable, which has succe
On 01/14/2011 04:26 PM, Jim Fehlig wrote:
Laine Stump wrote:
On 01/13/2011 04:29 PM, Jim Fehlig wrote:
Daniel P. Berrange wrote:
Yep, it wasn't really intended as a fix. It was intended to make
the error scenario clearly detectable, which has succeeded as per
Jim's report. The fact that
Laine Stump wrote:
> On 01/13/2011 04:29 PM, Jim Fehlig wrote:
>> Daniel P. Berrange wrote:
>>> >
>>> > Yep, it wasn't really intended as a fix. It was intended to make
>>> > the error scenario clearly detectable, which has succeeded as per
>>> > Jim's report. The fact that QMP returned an error
On 01/13/2011 04:29 PM, Jim Fehlig wrote:
Daniel P. Berrange wrote:
>
> Yep, it wasn't really intended as a fix. It was intended to make
> the error scenario clearly detectable, which has succeeded as per
> Jim's report. The fact that QMP returned an error in this way,
> means we can now rel
Daniel P. Berrange wrote:
> On Wed, Jan 12, 2011 at 11:29:27PM -0500, Laine Stump wrote:
>
>> On 01/12/2011 05:13 PM, Jim Fehlig wrote:
>>
>>> libvirt 0.8.7
>>> qemu 0.13
>>>
>>> I'm looking into a problem with qemu save/restore via JSON monitor. On
>>> restore, the vm is left in a paused
On Wed, Jan 12, 2011 at 11:29:27PM -0500, Laine Stump wrote:
> On 01/12/2011 05:13 PM, Jim Fehlig wrote:
> >libvirt 0.8.7
> >qemu 0.13
> >
> >I'm looking into a problem with qemu save/restore via JSON monitor. On
> >restore, the vm is left in a paused state with following error returned
> >for 'co
On 01/12/2011 05:13 PM, Jim Fehlig wrote:
libvirt 0.8.7
qemu 0.13
I'm looking into a problem with qemu save/restore via JSON monitor. On
restore, the vm is left in a paused state with following error returned
for 'cont' command
An incoming migration is expected before this command can be execu
libvirt 0.8.7
qemu 0.13
I'm looking into a problem with qemu save/restore via JSON monitor. On
restore, the vm is left in a paused state with following error returned
for 'cont' command
An incoming migration is expected before this command can be executed
I was trying to debug the issue in gdb,
12 matches
Mail list logo
