1:12 a.m.
stro: Fedora 9 Beta
kernel-2.6.25-0.218.rc8.git7.fc9.x86_64
CIMOM: tog-pegasus-2.7.0-6.fc9.x86_64
cimtest: changeset-218
==================================================================
PASS : 87
FAIL : 1
XFAIL : 1
SKIP : 40
-----------------
Total : 129
===================== CIMTEST REPORT===============================
AllocationCapabilities - 01_enum.py: PASS
AllocationCapabilities - 02_alloccap_gi_errs.py: PASS
ComputerSystem - 01_enum.py: PASS
ComputerSystem - 02_nosystems.py: PASS
ComputerSystem - 03_defineVS.py: PASS
ComputerSystem - 04_defineStartVS.py: FAIL
ERROR - Error: property values are not set for VS domguest
ComputerSystem - 05_activate_defined_start.py: XFAIL Bug: 00002
ERROR - ERROR: VS DomST1 transition from Defined State to Activate state
was not Successful
Bug:<00002>
ComputerSystem - 06_paused_active_suspend.py: SKIP
ComputerSystem - 22_define_suspend.py: PASS
ComputerSystem - 23_suspend_suspend.py: SKIP
ComputerSystem - 27_define_suspend_errs.py: PASS
ComputerSystem - 32_start_reboot.py: SKIP
ComputerSystem - 33_suspend_reboot.py: SKIP
ComputerSystem - 35_start_reset.py: SKIP
ComputerSystem - 40_RSC_start.py: SKIP
ComputerSystem - 41_cs_to_settingdefinestate.py: SKIP
ComputerSystem - 42_cs_gi_errs.py: PASS
ComputerSystemIndication - 01_created_indication.py: SKIP
ElementAllocatedFromPool - 01_forward.py: SKIP
ElementAllocatedFromPool - 02_reverse.py: SKIP
ElementAllocatedFromPool - 03_reverse_errs.py: SKIP
ElementAllocatedFromPool - 04_forward_errs.py: SKIP
ElementCapabilities - 01_forward.py: PASS
ElementCapabilities - 02_reverse.py: PASS
ElementCapabilities - 03_forward_errs.py: PASS
ElementCapabilities - 04_reverse_errs.py: PASS
ElementCapabilities - 05_hostsystem_cap.py: PASS
ElementConforms - 01_forward.py: PASS
ElementConforms - 02_reverse.py: PASS
ElementConforms - 03_ectp_fwd_errs.py: PASS
ElementConforms - 04_ectp_rev_errs.py: PASS
ElementSettingData - 01_forward.py: PASS
ElementSettingData - 03_esd_assoc_with_rasd_errs.py: PASS
EnabledLogicalElementCapabilities - 01_enum.py: PASS
EnabledLogicalElementCapabilities - 02_elecap_gi_errs.py: PASS
HostSystem - 01_enum.py: PASS
HostSystem - 02_hostsystem_to_rasd.py: SKIP
HostSystem - 03_hs_to_settdefcap.py: SKIP
HostSystem - 04_hs_to_EAPF.py: SKIP
HostSystem - 05_hs_gi_errs.py: PASS
HostSystem - 06_hs_to_vsms.py: PASS
HostedDependency - 01_forward.py: PASS
HostedDependency - 02_reverse.py: PASS
HostedDependency - 03_enabledstate.py: SKIP
HostedDependency - 04_reverse_errs.py: PASS
HostedResourcePool - 01_forward.py: PASS
HostedResourcePool - 02_reverse.py: PASS
HostedResourcePool - 03_forward_errs.py: PASS
HostedResourcePool - 04_reverse_errs.py: PASS
HostedService - 01_forward.py: PASS
HostedService - 02_reverse.py: PASS
HostedService - 03_forward_errs.py: PASS
HostedService - 04_reverse_errs.py: PASS
LogicalDisk - 01_disk.py: SKIP
LogicalDisk - 02_nodevs.py: SKIP
LogicalDisk - 03_ld_gi_errs.py: SKIP
Memory - 01_memory.py: PASS
Memory - 02_defgetmem.py: PASS
Memory - 03_mem_gi_errs.py: PASS
NetworkPort - 01_netport.py: SKIP
NetworkPort - 02_np_gi_errors.py: SKIP
NetworkPort - 03_user_netport.py: SKIP
Processor - 01_processor.py: SKIP
Processor - 02_definesys_get_procs.py: SKIP
Processor - 03_proc_gi_errs.py: SKIP
Profile - 01_enum.py: PASS
Profile - 02_profile_to_elec.py: SKIP
Profile - 03_rprofile_gi_errs.py: PASS
RASD - 01_verify_rasd_fields.py: PASS
RASD - 02_enum.py: PASS
RASD - 03_rasd_errs.py: PASS
ReferencedProfile - 01_verify_refprof.py: PASS
ReferencedProfile - 02_refprofile_errs.py: PASS
ResourceAllocationFromPool - 01_forward.py: SKIP
ResourceAllocationFromPool - 02_reverse.py: PASS
ResourceAllocationFromPool - 03_forward_errs.py: PASS
ResourceAllocationFromPool - 04_reverse_errs.py: PASS
ResourceAllocationFromPool - 05_RAPF_err.py: SKIP
ResourcePool - 01_enum.py: PASS
ResourcePool - 02_rp_gi_errors.py: PASS
ResourcePoolConfigurationCapabilities - 01_enum.py: PASS
ResourcePoolConfigurationCapabilities - 02_rpcc_gi_errs.py: PASS
ResourcePoolConfigurationService - 01_enum.py: PASS
ResourcePoolConfigurationService - 02_rcps_gi_errors.py: PASS
ResourcePoolConfigurationService - 03_CreateResourcePool.py: SKIP
ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: SKIP
ResourcePoolConfigurationService - 05_AddResourcesToResourcePool.py: SKIP
ResourcePoolConfigurationService - 06_RemoveResourcesFromResourcePool.py:
SKIP
ResourcePoolConfigurationService - 07_DeleteResourcePool.py: SKIP
SettingsDefine - 01_forward.py: PASS
SettingsDefine - 02_reverse.py: PASS
SettingsDefine - 03_sds_fwd_errs.py: PASS
SettingsDefine - 04_sds_rev_errs.py: PASS
SettingsDefineCapabilities - 01_forward.py: PASS
SettingsDefineCapabilities - 03_forward_errs.py: PASS
SettingsDefineCapabilities - 04_forward_vsmsdata.py: PASS
SettingsDefineCapabilities - 05_reverse_vsmcap.py: PASS
SystemDevice - 01_forward.py: PASS
SystemDevice - 02_reverse.py: PASS
SystemDevice - 03_fwderrs.py: PASS
VSSD - 01_enum.py: PASS
VSSD - 02_bootldr.py: SKIP
VSSD - 03_vssd_gi_errs.py: PASS
VSSD - 04_vssd_to_rasd.py: PASS
VirtualSystemManagementCapabilities - 01_enum.py: PASS
VirtualSystemManagementCapabilities - 02_vsmcap_gi_errs.py: PASS
VirtualSystemManagementService - 01_definesystem_name.py: PASS
VirtualSystemManagementService - 02_destroysystem.py: PASS
VirtualSystemManagementService - 03_definesystem_ess.py: PASS
VirtualSystemManagementService - 04_definesystem_ers.py: PASS
VirtualSystemManagementService - 05_destroysystem_neg.py: PASS
VirtualSystemManagementService - 06_addresource.py: SKIP
VirtualSystemManagementService - 07_addresource_neg.py: PASS
VirtualSystemManagementService - 08_modifyresource.py: SKIP
VirtualSystemMigrationCapabilities - 01_enum.py: PASS
VirtualSystemMigrationCapabilities - 02_vsmc_gi_errs.py: PASS
VirtualSystemMigrationService - 01_migratable_host.py: SKIP
VirtualSystemMigrationService - 02_host_migrate_type.py: SKIP
VirtualSystemMigrationService - 05_migratable_host_errs.py: SKIP
VirtualSystemMigrationSettingData - 01_enum.py: PASS
VirtualSystemMigrationSettingData - 02_vsmsd_gi_errs.py: PASS
VirtualSystemSettingDataComponent - 01_forward.py: SKIP
VirtualSystemSettingDataComponent - 02_reverse.py: PASS
VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: PASS
VirtualSystemSettingDataComponent - 04_vssdc_rev_errs.py: PASS
VirtualSystemSnapshotService - 01_enum.py: PASS
VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py: PASS
VirtualSystemSnapshotServiceCapabilities - 01_enum.py: PASS
VirtualSystemSnapshotServiceCapabilities - 02_vs_sservicecap_gi_errs.py:
PASS
Best,
Regards
Daisy (运国莲)
VSM Team, China Systems & Technology Labs (CSTL)
E-mail: yunguol(a)cn.ibm.com
TEL: (86)-21-60922144
Building 10, 399 Ke Yuan Rd, Pudong Shanghai, 201203
10:46 a.m.
GY> ComputerSystem - 04_defineStartVS.py: FAIL
GY> ERROR - Error: property values are not set for VS domguest
Do you know if your container is actually starting? Grabbing the XML,
defining it manually, and then starting it would be good. If it
transitions to the running state, then it should be okay, but check
the console to be sure.
GY> ComputerSystem - 05_activate_defined_start.py: XFAIL Bug: 00002
GY> ERROR - ERROR: VS DomST1 transition from Defined State to Activate state was
GY> not Successful
GY> Bug:<00002>
What is this test doing that is expected to fail?
Thanks!
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
10:15 p.m.
libvirt-cim-bounces(a)redhat.com wrote on 2008-06-19 23:46:52:
GY> ComputerSystem - 04_defineStartVS.py: FAIL
GY> ERROR - Error: property values are not set for VS domguest
Do you know if your container is actually starting? Grabbing the XML,
defining it manually, and then starting it would be good. If it
transitions to the running state, then it should be okay, but check
the console to be sure.
Kaitlin - Would you please test ComputerSystem.04 on your machine? I
can't run the cimtest on your machine although I can login today.
And if it still fails for you, would you please check it manually?
This tc pass for me on sfcb.
GY> ComputerSystem - 05_activate_defined_start.py: XFAIL Bug:
00002
GY> ERROR - ERROR: VS DomST1 transition from Defined State to
Activate state was
GY> not Successful
GY> Bug:<00002>
What is this test doing that is expected to fail?
Thanks!
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
[attachment "attycree.dat" deleted by Guo Lian Yun/China/IBM]
_______________________________________________
Libvirt-cim mailing list
Libvirt-cim(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim
12:16 a.m.
libvirt-cim-bounces(a)redhat.com wrote on 2008-06-20 11:15:43:
libvirt-cim-bounces(a)redhat.com wrote on 2008-06-19 23:46:52:
> GY> ComputerSystem - 04_defineStartVS.py: FAIL
> GY> ERROR - Error: property values are not set for VS domguest
>
> Do you know if your container is actually starting? Grabbing the XML,
> defining it manually, and then starting it would be good. If it
> transitions to the running state, then it should be okay, but check
> the console to be sure.
>
Kaitlin - Would you please test ComputerSystem.04 on your machine? I
can't run the cimtest on your machine although I can login today.
And if it still fails for you, would you please check it manually?
Below is the domain dumpxml.
<?xml version="1.0" ?>
<domain
type="lxc"><name>domguest</name><uuid>d03a0a52-3e85-11dd-b7d1-0011259da336</uuid><os><init>/tmp/cimtest_lxc_init</init></os><memory>131072</memory><vcpu>1</vcpu><on_poweroff>destroy</on_poweroff><on_reboot>restart</on_reboot><on_crash>destroy</on_crash><devices><console>/dev/ptmx</console></devices></domain>
With it I can define and start the domain successfully on SFCB.
virsh # list
Id Name State
----------------------------------
9134 domguest running
However, on Pegasus with Kaitlin's system, I can only define the
domain. Although
it report 'Domain domguest started' by starting the domain, actually
there is none
in virsh list.
This tc pass for me on sfcb.
> GY> ComputerSystem - 05_activate_defined_start.py: XFAIL Bug: 00002
> GY> ERROR - ERROR: VS DomST1 transition from Defined State to
> Activate state was
> GY> not Successful
> GY> Bug:<00002>
>
> What is this test doing that is expected to fail?
>
I think this is the same issue with 04_defineStartVS.py, a defined
domain
can't transit to running state. Below is the bug:<00002> description
in wiki.
00002
RequestedState property in ComputerSystem is not getting populated
Xem, KVM (?)
No
> Thanks!
>
> --
> Dan Smith
> IBM Linux Technology Center
> Open Hypervisor Team
> email: danms(a)us.ibm.com
> [attachment "attycree.dat" deleted by Guo Lian Yun/China/IBM]
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim
_______________________________________________
Libvirt-cim mailing list
Libvirt-cim(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim
12:36 a.m.
libvirt-cim-bounces(a)redhat.com wrote on 2008-06-20 13:16:53:
libvirt-cim-bounces(a)redhat.com wrote on 2008-06-20 11:15:43:
>
> libvirt-cim-bounces(a)redhat.com wrote on 2008-06-19 23:46:52:
>
> > GY> ComputerSystem - 04_defineStartVS.py: FAIL
> > GY> ERROR - Error: property values are not set for VS domguest
> >
> > Do you know if your container is actually starting? Grabbing the
XML,
> > defining it manually, and then starting it would be good.
If it
> > transitions to the running state, then it should be okay, but check
> > the console to be sure.
> >
> Kaitlin - Would you please test ComputerSystem.04 on your machine? I
> can't run the cimtest on your machine although I can login
today.
> And if it still fails for you, would you please check it manually?
>
Below is the domain dumpxml.
<?xml version="1.0" ?>
<domain
type="lxc"><name>domguest</name><uuid>d03a0a52-3e85-11dd-
b7d1-0011259da336</uuid><os><init>/tmp/cimtest_lxc_init</init></os><memory>131072</memory><vcpu>1</vcpu><on_poweroff>destroy</on_poweroff><on_reboot>restart</on_reboot><on_crash>destroy</on_crash><devices><console>/dev/ptmx</console></devices></domain>
With it I can define and start the domain successfully on SFCB.
virsh # list
Id Name State
----------------------------------
9134 domguest running
However, on Pegasus with Kaitlin's system, I can only define the
domain. Although
it report 'Domain domguest started' by starting the domain,
actually there is none
in virsh list.
May I say the issue related with linux kernel?
The domain can be start successfully with
kernel-2.6.25-0.121.rc5.git4.fc9.i686,
and the other test on Pegaus with kernel
2.6.25-0.218.rc8.git7.fc9.x86_64.
> This tc pass for me on sfcb.
>
> > GY> ComputerSystem - 05_activate_defined_start.py: XFAIL Bug:
00002
> > GY> ERROR - ERROR: VS DomST1 transition from Defined
State to
> > Activate state was
> > GY> not Successful
> > GY> Bug:<00002>
> >
> > What is this test doing that is expected to fail?
> >
I think this is the same issue with 04_defineStartVS.py, a defined
domain
can't transit to running state. Below is the
bug:<00002>
description in wiki.
00002
RequestedState property in ComputerSystem is not getting populated
Xem, KVM (?)
No
> > Thanks!
> >
> > --
> > Dan Smith
> > IBM Linux Technology Center
> > Open Hypervisor Team
> > email: danms(a)us.ibm.com
> > [attachment "attycree.dat" deleted by Guo Lian Yun/China/IBM]
> > _______________________________________________
> > Libvirt-cim mailing list
> > Libvirt-cim(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/libvirt-cim
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim
_______________________________________________
Libvirt-cim mailing list
Libvirt-cim(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim
12:18 p.m.
>
May I say the issue related with linux kernel?
The domain can be start successfully with
kernel-2.6.25-0.121.rc5.git4.fc9.i686,
and the other test on Pegaus with kernel
2.6.25-0.218.rc8.git7.fc9.x86_64.
You're using a recent version of libvirt from cvs, correct? When did
you check it out? I checked out a version on 6-12.
Dan - are you seeing similar problems? The contain fails to start.
It's attempting to launch a script that just runs "exec /bin/bash", so
the script shouldn't be immediately failing.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
2:14 p.m.
KR> Dan - are you seeing similar problems? The contain fails to
KR> start. It's attempting to launch a script that just runs "exec
KR> /bin/bash", so the script shouldn't be immediately failing.
Well, the lxc driver is pretty fragile, so I'm sure there's just
something blocking it.
Daisy, you might want to run libvirtd in non-daemon mode. Also, if
you --enable-debug=yes on the libvirt build and then run the daemon
with LIBVIRT_DEBUG=1 you'll get more information.
You can also just use <init>/bin/bash</init> to take one of the
variables out of the equation.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
3:43 p.m.
Dan Smith wrote:
KR> Dan - are you seeing similar problems? The contain fails to
KR> start. It's attempting to launch a script that just runs "exec
KR> /bin/bash", so the script shouldn't be immediately failing.
Well, the lxc driver is pretty fragile, so I'm sure there's just
something blocking it.
Daisy, you might want to run libvirtd in non-daemon mode. Also, if
you --enable-debug=yes on the libvirt build and then run the daemon
with LIBVIRT_DEBUG=1 you'll get more information.
You can also just use <init>/bin/bash</init> to take one of the
variables out of the equation.
Also, I forgot to verify this on Friday - can you make sure the script
has the proper execute permissions.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
6025
days inactive
6029
days old
7 comments
3 participants
participants (3)
-
Dan Smith -
Guo Lian Yun -
Kaitlin Rupert