Jim Fehlig
2009-Feb-03 20:58 UTC
[Xen-devel] [PATCH] XendAPIStore - do not remove non-existent item
If list is searched and item not found, then don''t attempt to delete the item. I''ve seen this bug manifest as xen81:~/bin # xm li Name ID Mem VCPUs State Time(s) Domain-0 0 3151 16 r----- 1240.8 pxe 3 256 1 -b---- 26.4 xen81:~/bin # xm des 3 Error: (''d59cd309-80cd-66b3-d4f3-cff439eadc8a'', ''VM_metrics'') Usage: xm destroy <Domain> Terminate a domain immediately. I''m not sure why this vm had no metrics object associated with it but nonetheless I don''t think we should be throwing exceptions by removing non-existent objects from XendAPIStore. Signed-off-by: Jim Fehlig <jfehlig@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Apparently Analagous Threads
- Successfully running VM, subsequently startup gives this error -- VmError: Boot loader didn''t return any data!
- XenAPI: why we implement VM_metrics.VCPUs_utilisation as proportion?
- [PATCH]xend: fix dual destroy
- VM creation failure using passthrough with latest unstable
- xm in xen-api mode problem after failure to start domain (vbd in use)