libvirt-cim-bounces@redhat.com wrote on 2009-02-26 06:45:02:

> >  > > FAIL Test Summary:
> >  > > ComputerSystem - 01_enum.py: FAIL
> >  > Passed when run manually.
> >  > > ElementAllocatedFromPool - 02_reverse.py: FAIL
> >  > Need to investigate further
> >  > > ElementCapabilities - 01_forward.py: FAIL
> >  > The virsh on the machine is throwing the following error on the stderr
> >  >
> >  > virsh -c xen:/// list --all | sed -e '1,2 d' -e '$ d'
> >  > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID
> >  > libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID
> >  >
> >  > because of this the test case is not able to parse the values properly
> >  > and hence fails.
> >
> >   Kaitlin - Does Richard Maciel's patches of
> >   "This series of patches exposes errors provided from executions of
> > libvirt functions"
> >   fix this issue?
> >
> >   Thanks!
>
> No, Richard is working on enhancing the error messages returned by the
> providers.  Right now, we don't include libvirt's error messages in the
> error messages returned by the providers (in most cases, anyway).
>
> However, this is a different issue.  virsh is returning an error, which
> means it's this issue is happening outside of the providers.
>
> I have seen something similar happen before - a guest gets into a bad
> state and libvirt is aware of the guest, but xend doesn't know about the
> guest.  Usually, this guest will have "no state" for it's state.
>
> You can try restarting xend and libvirtd and then undefining the invalid
> guest. That resolve the error messages.  If it doesn't, try rebooting
> the box (sadly).

  I restarted the box and fixed these virsh issues. There are total 8 tests fail
  now =)
 
  Thanks!

> --
> Kaitlin Rupert
> IBM Linux Technology Center
> kaitlin@linux.vnet.ibm.com
>
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim