May 11, 2006
Configuration:
Unisys ES7000/one
x86_64
32 processors
32 GB RAM
SLES 10 Beta 11 with
xen-unstable changeset 9960
Issues: Multiple failures of network tests. We get the exact same results on
an x86_64 Dell 4X with 2GB RAM. The xm-test output file shows attempts to
create domUs fail with Device 0 (vif) could not be connected. Backend device not
found. We noticed that doing ifconfig in dom0 only shows eth0 and lo devices.
ifconfig no longer shows peth0 and xenbr0 devices as it did with earlier
changesets. Do we now need to include other modules to get networking to work?
Xm-test execution summary:
PASS: 100
FAIL: 15
XPASS: 0
XFAIL: 3
Details:
FAIL: 13_create_multinic_pos
(0 nics) Failed to create domain
FAIL: 01_enforce_dom0_cpus_basic_pos
/proc/cpuinfo says xend didn''t enforce dom0_cpus (31 != 1)
XFAIL: 02_network_local_ping_pos
Failed to create domain
FAIL: 03_network_local_tcp_pos
Failed to create domain
FAIL: 04_network_local_udp_pos
Failed to create domain
XFAIL: 05_network_dom0_ping_pos
Failed to create domain
FAIL: 06_network_dom0_tcp_pos
Failed to create domain
FAIL: 07_network_dom0_udp_pos
Failed to create domain
XFAIL: 11_network_domU_ping_pos
Failed to create domain
FAIL: 12_network_domU_tcp_pos
Failed to create domain
FAIL: 13_network_domU_udp_pos
Failed to create domain
FAIL: 01_network_attach_pos
xm network-attach returned invalid 256 != 0
FAIL: 02_network_attach_detach_pos
xm network-attach returned invalid 256 != 0
FAIL: 03_network_attach_detach_multiple_pos
xm network-attach returned invalid 256 != 0
FAIL: 04_restore_withdevices_pos
Failed to create domain
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
FAIL: 01_enforce_dom0_cpus_basic_pos
/proc/cpuinfo says xend didn''t enforce dom0_cpus (31 != 1)
This issue happens because it takes a few seconds for the /proc/cpuinfo
to be reduced from 32 to 1 after dom0_cpus have been reset to 1. We will
be sending in a path shortly to monitor /proc/cpuinfo in a loop with a
20 second timeout.
Raj
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
May 22, 2006
Configuration:
Unisys ES7000/one
x86_64
16 processors
16 GB RAM
SLES 10 RC1 with xen-unstable changeset 10058
Issues: We ran with a workaround for multiple failures of network tests (see
our previous xm-test run on 5/11). The multiple network test failures also
happen on an x86_64 Dell 4X with 2GB RAM. The failures are related to the fact
that ifconfig shows dom0 is only configured with eth0 and lo and is missing
multiple other entries, one of which is xenbr0. We edited
/etc/xen/xend-config.sxp to change the statement (network-script network-bridge)
to (network-script ''network-bridge vifnum=0'') and then
restarted xend. This caused xenbr0 and other entries to be configured. Then,
since xm-test looks in the xend-config.sxp file for the original network-script
statement, we had to change the statement back to (network-script
network-bridge) and restart xend in order to get xm-test to run.
We have created bugzilla # 656 for this problem.
Xm-test execution summary:
PASS: 111
FAIL: 4
XPASS: 0
XFAIL: 3
Details:
FAIL: 03_memset_random_pos
Timed out waiting for console
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
May 30, 2006
Configuration:
Unisys ES7000/one
x86_64
16 processors
8 GB RAM
SLES 10 RC1 with xen-unstable changeset 10172
Issues: We ran with a workaround for multiple failures of network tests (see
our previous xm-test run on 5/11). The multiple network test failures also
happen on an x86_64 Dell 4X with 2GB RAM. The failures are related to the fact
that ifconfig shows dom0 is only configured with eth0 and lo and is missing
multiple other entries, one of which is xenbr0. We edited
/etc/xen/xend-config.sxp to change the statement (network-script network-bridge)
to (network-script ''network-bridge vifnum=0'') and then
restarted xend. This caused xenbr0 and other entries to be configured. Then,
since xm-test looks in the xend-config.sxp file for the original network-script
statement, we had to change the statement back to (network-script
network-bridge) and restart xend in order to get xm-test to run.
We have created bugzilla # 656 for this problem.
Xm-test execution summary:
PASS: 110
FAIL: 5
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_memset_basic_pos
DomU reported incorrect memory amount 59 MB
FAIL: 03_memset_random_pos
Timed out waiting for console
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel