<tt>libvirt-cim-bounces@redhat.com wrote on 2008-06-11 23:29:08: > yunguol@cn.ibm.com wrote: > > # HG changeset patch > > # User Guolian Yun <yunguol@cn.ibm.com> > > # Date 1213266000 -28800 > > # Node ID a69394e8052f65132dce5886e0a8670717133bf1 > > # Parent 254bc5464030a03b6f791fd49acd208f6ec1db23 > > [TEST] Update SettingsDefineCapabilities.03 for LXC support > > > > Signed-off-by: Guolian Yun <yunguol@cn.ibm.com> > > > > diff -r 254bc5464030 -r a69394e8052f suites/libvirt- > cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py > > I saw the following failure: > > Testing LXC hypervisor > SettingsDefineCapabilities - 03_forward_errs.py: FAIL > ERROR - Unexpected rc code 4 and description > CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0" > > ERROR - ------ FAILED: Invalid CCName Key Name.------ > > I also saw the same issue on Xen, XenFV, and KVM. > </tt> <tt> Do you test it with Pegasus or SFCB? It passes with Pegasus when I</tt> <tt> test on your machine, and pass on Deepti's cimtest report. </tt> <tt> </tt> <tt> I think it fails with sfcb because that the WrongClassName can't</tt> <tt> be parsed by sfcb, so there is none output with the wrongclassname</tt> <tt> querying as follows:</tt> <tt> wbemcli ain -ac LXC_SettingsDefineCapabilities http://root:password@localhost/root/virt:WrongClassName.InstanceID="MemoryPool/0"</tt> <tt> However, we can get output with Pegasus.</tt> <tt> wbemcli ain -ac LXC_SettingsDefineCapabilities http://root:password@localhost/root/virt:WrongClassName.InstanceID="MemoryPool/0"</tt> <tt> *</tt> <tt> * wbemcli: Cim: (4) CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0"</tt> <tt> *</tt> <tt> </tt> <tt> </tt> <tt> > -- > 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 </tt>