We have tested the latest xen on VT platform with Intel 915/E8500
chipset.
Three platforms(32/PAE/32E) test all are based on SMP, It means that we
boot up SMP guest OS in VMX.
Here is the test summary:
Issues:
1).IA32: Build linux 2.6.16 kernel in IA32 non-pae SMP VMX domain
succeed about 30% of the time.
2).Create eight VMX domains simultaneously, usually, not all four VMX
domains can start successfully. only part of them can start, but two or
one will failed with the following messages " Error: Device 768 (vbd)
could not be connected. Hotplug scripts not working." or "Error:
Device
5632 (vbd) could not be connected. Hotplug scripts not working."or "
Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.".
I use following script to create four VMX domains simultaneously:
#!/bin/bash
xm cr config.vmx2 &
xm cr config.vmx3 &
xm cr config.vmx4 &
xm cr config.vmx5 &
Details;
IA32:
+ Build&Boot SMP xen0 without problem
+ Can bootup unmodified IA32 SMP 2.6 linux Guest OS in VMX
+ Can bootup unmodified IA32 UP WindowsXP SP1/SP2 Guest OS in VMX
+ Can bootup unmodified IA32 UP Windows2003 Guest OS in VMX
+ Can bootup IA32 SMP Guest OS in VMX & XenU with different memory size
(VMX:64MB,128MB,196MB,256MB,512MB.XenU:256MB)
+ A selected subset of xm-test runs well
+ A selected subset of LTP runs well in IA32 SMP Guest OS in VMX
+ Can build base kernel 2.6.16 in IA32 SMP Guest OS in VMX(about 30% of
chance build success)
+ Can startX in Dom0
+ Can bootup IA32 SMP 2.6 linux Guest OS in VMX with acpi enable
+ Can startX in IA32 SMP Guest OS in VMX
+ Network is OK in IA32 SMP Guest OS in VMX
PAE:
+ Build&Boot PAE SMP xen0 without problem
+ Can bootup unmodified IA32 nonpae SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified PAE SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified IA32 UP WindowXP SP1/SP2 in VMX
+ Can bootup unmodified PAE UP Windows2003 Guest OS in VMX
+ Can bootup PAE SMP 2.6 linux guest OS in VMX & XenU with different
memory size
(VMX:64MB,128MB,196MB,256MB,512MB,1500MB.XenU:256MB)
+ A selected subset of xm-test runs well
+ A selected subset of LTP runs well in PAE SMP 2.6 linux guest OS in
VMX.
+ Can build base kenerl 2.6.16 in PAE SMP guest OS in VMX.
+ Can startX in Dom0
+ Can bootup PAE SMP 2.6 linux in VMX with acpi enable
+ Can startX in PAE SMP guest OS in VMX
+ Network is OK in PAE SMP guest OS in VMX
IA32E:
+ Build&Boot IA32E SMP xen0 without problem
+ Can bootup unmodified IA32 nonpae SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified PAE SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified IA32E SMP 2.6 linux in VMX
+ Can bootup unmodified IA32 UP WindowXP SP1/SP2 in VMX
+ Can bootup unmodified PAE UP Windows 2003 in VMX
+ Can bootup IA32E SMP Guest OS in VMX & xenU with different memory
size.
(VMX:128MB,256MB,384MB,512MB,1024M,4096MB.XenU:256MB)
+ A selected subset of xm-test runs well
+ A selected subset of LTP runs well in IA32E SMP 2.6 linux Guest OS in
VMX
+ Can build base kenerl 2.6.16 in IA32E SMP guest OS in VMX.
+ Can startX in Dom0
+ Can bootup IA32E 2.6 linux Guest OS in VMX with acpi enable
+ Can startX in Ia32E SMP guest OS in VMX
+ Network is OK in IA32E SMP Guest OS in VMX
For details
------------------------------------------------------------
Platform: IA32
Service OS: FC5, IA32, SMP
Hardware: Grandstale
Default guest OS: IA32,SMP, 2.6 kernel
1, one IA32 nonpae SMP VMX domain with memory 512M PASS
2, one xenU domain with memory 256M
PASS
3, Two IA32 nonpae SMP VMX domains and 2 xenU domains coexist PASS
4, four IA32 nonpae SMP VMX domains coexist(64M,128M,196M,256M) PASS
5, network in IA32 nonpae SMP VMX domain
PASS
6, network in XenU domain
PASS
7, one IA32 UP Windows 2003 in VMX domain
PASS
8, 1 IA32 UP xpsp1 and 1 IA32 UP xpsp2 Windows VMX domains coexist
PASS
10,subset LTP test in IA32 nonpae SMP VMX domain
PASS
11,one VMX boot with IA32 nonpae SMP base kernel(2.6.16)
PASS
12,xm-test
PASS
14,StartX in Dom0
PASS
15,one IA32 nonpae SMP VMX domain with acpi enable
PASS
16,Build base kernel in IA32 nonpae SMP VMX domain
FAIL(about 30% chance of build success )
Xm test on IA32:
========================Xm-test execution summary:
PASS: 44
FAIL: 4
XPASS: 0
XFAIL: 3
Details:
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size
1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096
4192 32767 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767
65507.
FAIL: 01_sedf_multi_pos
[0] xm sedf returned invalid 256 != 0
LTP test on IA32:
========================= Summary Test Report of Last Session
========================================================================
Total Pass Fail NoResult Crash
========================================================================ltp
195 195 0 0 0
========================================================================ltp
195 195 0 0 0
mm 21 21 0 0 0
dio 28 28 0 0 0
nptl 1 1 0 0 0
math 10 10 0 0 0
ipc 8 8 0 0 0
pty 3 3 0 0 0
quickhit 121 121 0 0 0
sched 3 3 0 0 0
========================================================================Total
195 195 0 0 0
Platform: PAE
Service OS: RHEL4U1, PAE, SMP
Hardware: Grandstal
Default guest OS: PAE,SMP, 2.6 kernel
0, one IA32 nonpae SMP 2.6 VMX domain with memory 256M PASS
1, one PAE SMP VMX domain with memory 512M PASS
2, one PAE SMP VMX domain with memory 1500M PASS
3, one xenU domain with memory 256M
PASS
4, 2 PAE SMP VMX domains and 2 xenU domains coexist PASS
5, 2 IA32 nonpae SMP VMX domains and 2 PAE SMP VMX domains
coexist(64m,128m,196m,256m) PASS
6, network in PAE SMP vmx domain
PASS
7, network in xenu domain
PASS
8, one PAE UP Windows 2003 vmx domain PASS
8, 1 IA32 UP xpsp1 and 1 IA32 UP xpsp2 windows vmx domains coexist
PASS
9, xm-test
PASS
11,one vmx boot with PAE SMP base kernel(2.6.16)
PASS
12,startx in dom0
PASS
13,one PAE SMP vmx domain with acpi enable
PASS
14,build linux 2.6.16 base kernel in PAE SMP vmx domain PASS
Xm test on PAE:
======================Xm-test execution summary:
PASS: 44
FAIL: 4
XPASS: 0
XFAIL: 3
Details:
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size
1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096
4192 32767 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767
65507.
FAIL: 01_sedf_multi_pos
[0] xm sedf returned invalid 256 != 0
LTP test On PAE:
======================= Summary Test Report of Last Session
========================================================================
Total Pass Fail NoResult Crash
========================================================================ltp
194 194 0 0 0
========================================================================ltp
194 194 0 0 0
mm 21 21 0 0 0
dio 28 28 0 0 0
nptl 1 1 0 0 0
math 10 10 0 0 0
ipc 8 8 0 0 0
pty 3 3 0 0 0
quickhit 120 120 0 0 0
sched 3 3 0 0 0
========================================================================Total
194 194 0 0 0
platform: IA32E
service os: rhel4u2, IA32E, SMP
hardware: paxville
default guest os: IA32E,SMP, 2.6 kernel
0, one IA32 nonpae SMP 2.6 VMX domain with memory 256M PASS
1, one IA32E SMP VMX domain with memory 512M PASS
2, one xenU domain with memory 256M
PASS
3, 2 IA32E SMP VMX domains and 2 xenU VMX domains coexist
PASS
4, 2 IA32E SMP VMX domains and 2 PAE SMP VMX domains
coexist(64m,128m,196m,256m) PASS
5, network in IA32E SMP VMX domain
PASS
6, network in XenU domain
PASS
8, one PAE SMP VMX domain with 1500M PASS
11, subset LTP in IA32E guest OS in VMX PASS
12, one PAE UP Windows 2003 VMX domain PASS
13, 1 IA32 UP xpsp1 and 1 IA32 UP xpsp2 Windows domains coexist PASS
14, xm-test
PASS
15,one VMX boot with IA32E SMP base kernel(2.6.16)
PASS
16,Build base kernel in IA32E VMX domain
PASS
17,StartX in Dom0
PASS
18,one IA32E SMP VMX domain with acpi enable
PASS
Xm test on IA32E:
========================Xm-test execution summary:
PASS: 44
FAIL: 4
XPASS: 0
XFAIL: 3
Details:
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size
1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096
4192 32767 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767
65507.
FAIL: 01_sedf_multi_pos
[0] xm sedf returned invalid 256 != 0
LTP test on IA32E:
========================= Summary Test Report of Last Session
=============================================================================
Total Pass Fail NoResult Crash
=============================================================================ltp
195 195 0 0 0
=============================================================================ltp
195 195 0 0 0
mm 21 21 0 0 0
dio 28 28 0 0 0
nptl 1 1 0 0 0
math 10 10 0 0 0
ipc 8 8 0 0 0
pty 3 3 0 0 0
quickhit 121 121 0 0 0
sched 3 3 0 0 0
=============================================================================Total
195 195 0 0 0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Roland Paterson-Jones
2006-Sep-20 06:53 UTC
Re: [Xen-devel] VMX status report 11536:041be3f6b38e
Yu, Ping Y wrote:>2).Create eight VMX domains simultaneously, usually, not all four VMX >domains can start successfully. only part of them can start, but two or >one will failed with the following messages " Error: Device 768 (vbd) >could not be connected. Hotplug scripts not working." or "Error: Device >5632 (vbd) could not be connected. Hotplug scripts not working."or " >Error: Device 0 (vif) could not be connected. Hotplug scripts not >working.". > >We have seen this caused by time-outs due to a very busy dom-0. Try increasing the timeout in ./tools/python/xen/xend/server/DevController.py, for example: --- ./tools/python/xen/xend/server/DevController.py 2006-04-13 19:48:39.000000000 +0200 +++ ../xen-3.0.2-2patched/tools/python/xen/xend/server/DevController.py 2006-06-07 13:17:45.000000000 +0200 @@ -25,7 +25,7 @@ from xen.xend.xenstore.xstransact import xstransact, complete from xen.xend.xenstore.xswatch import xswatch -DEVICE_CREATE_TIMEOUT = 10 +DEVICE_CREATE_TIMEOUT = 3600 HOTPLUG_STATUS_NODE = "hotplug-status" HOTPLUG_ERROR_NODE = "hotplug-error" HOTPLUG_STATUS_ERROR = "error" Roland _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks for the fix, and we will verify it in later testing. Ping>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Roland Paterson-Jones >Sent: 2006年9月20日 14:54 >To: Yu, Ping Y >Cc: xen-devel@lists.xensource.com >Subject: Re: [Xen-devel] VMX status report 11536:041be3f6b38e > >Yu, Ping Y wrote: > >>2).Create eight VMX domains simultaneously, usually, not all four VMX >>domains can start successfully. only part of them can start, but two or >>one will failed with the following messages " Error: Device 768 (vbd) >>could not be connected. Hotplug scripts not working." or "Error: Device >>5632 (vbd) could not be connected. Hotplug scripts not working."or " >>Error: Device 0 (vif) could not be connected. Hotplug scripts not >>working.". >> >> >We have seen this caused by time-outs due to a very busy dom-0. > >Try increasing the timeout in >./tools/python/xen/xend/server/DevController.py, for example: > >--- ./tools/python/xen/xend/server/DevController.py 2006-04-13 >19:48:39.000000000 +0200 >+++ ../xen-3.0.2-2patched/tools/python/xen/xend/server/DevController.py >2006-06-07 13:17:45.000000000 +0200 >@@ -25,7 +25,7 @@ > from xen.xend.xenstore.xstransact import xstransact, complete > from xen.xend.xenstore.xswatch import xswatch > >-DEVICE_CREATE_TIMEOUT = 10 >+DEVICE_CREATE_TIMEOUT = 3600 > HOTPLUG_STATUS_NODE = "hotplug-status" > HOTPLUG_ERROR_NODE = "hotplug-error" > HOTPLUG_STATUS_ERROR = "error" > >Roland > > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel