[libvirt] virGetLastError() disagrees with virConnGetLastError()

John Levon levon at movementarian.org
Tue Feb 3 16:16:20 UTC 2009


On Tue, Feb 03, 2009 at 11:14:24AM +0000, Daniel P. Berrange wrote:

> I can't reproduce this problem with current CVS.
> 
> I made the following change to the 'dump' method in virsh.c

The difference is I have it /after/ the virDomainFree (actually in
virCommandRun). I hadn't noticed this before.

error: Failed to core dump domain Domain-0 to /var/tmp/a
0 80a90ac
11 POST operation failed: xend_post: error from xen daemon: (xend.err 'Cannot dump core for privileged domain 0')
virsh: error: POST operation failed: xend_post: error from xen daemon: (xend.err 'Cannot dump core for privileged domain 0')

Perhaps it's the case that there's no guarantees as to the error state
after a successful call.

I'm trying to "save" the error messages in virsh until a command
actually failed. That way any incidental errors along the way aren't
shown. It looks like I might need to save the last error in the error
handler with virCopyLastError(), then use that in vshCommandRun().

regards
john




More information about the libvir-list mailing list