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:
+ This bug fixed: Creating 32PAE SMP guest on 32pae/64bit platform
crashes xen0
- Creating 4 VMX simutaneously on 32 platform will hang xen0
- Sometimes build base kernel 2.6.16 in IA32SMP guest fails on 32bit
platform.
Details;
IA-32:
+ Build&Boot SMP xen0 without problem
+ Can bootup unmodified IA-32 SMP 2.6 linux Guest OS in VMX
+ Can bootup unmodified IA-32 WindowsXP SP1/SP2 Guest OS in VMX
+ Can bootup IA-32 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( sometimes
pass, sometimes fail)
+ Can startX in Dom0
+ Can bootup IA-32 SMP 2.6 linux Guest OS in VMX with acpi enable
+ Can startX in Ia-32 SMP Guest OS in VMX
+ Network is OK in IA-32 SMP Guest OS in VMX
IA-32_PAE:
+ Build&Boot pae SMP xen0 without problem
+ Can bootup unmodified IA32 SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified pae SMP 2.6 linux guest OS in VMX
+ Can bootup unmodified ia32 WindowXP SP1/SP2 in VMX
+ Can bootup IA32 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 LTP runs well in IA32 SMP 2.6 linux guest OS in
VMX.
+ A selected subset of xm-test runs well
+ Can build base kenerl 2.6.16 in IA32 SMP guest OS in VMX,(sometimes
faild,unstable).
+ Can startX in Dom0
+ Can bootup IA32 SMP 2.6 linux in VMX with acpi enable
+ Can startX in Ia32 SMP guest OS in VMX
+ Network is OK in Ia32 SMP guest OS in VMX
IA-32e:
+ Build&Boot IA32E SMP xen0 without problem
+ Can bootup unmodified IA32E SMP 2.6 linux in VMX
+ Can bootup ia32e WindowXP SP1/SP2 in VMX
+ Can bootup unmodified IA32PAE 2.6 SMP linux 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 startX in Dom0
+ Can bootup IA32E 2.6 linux Guest OS in VMX with acpi enable
+ Network is OK in IA-32e SMP Guest OS in VMX
For details
------------------------------------------------------------
Platform: IA-32
Service OS: FC5, IA-32, SMP
Hardware: Grandstale
Default guest OS: IA-32-SMP, 2.6 kernel
1, one vmx with memory 512M PASS
2, one xenU with memory 256M PASS
3, Two ia32 smp vmxs and 2 xenUs coexist PASS
4, four ia32 smp vmx coexist(64M,128M,196M,256M) FAIL(on
grandstale hardware platform, it fails, but on Paxville hardware
platform, it works fine)
5, network in ia32 smp VMX domain PASS
6, network in XenU domain PASS
7, one window in VMX domain PASS
8, 1 xpsp1 and 1 xpsp2 windows coexist in VMX domains PASS
10,subset LTP test in VMX domain PASS
11,one vmx boot with ia32 smp base kernel(2.6.16) PASS
12,xm-test PASS
14,StartX in Dom0 PASS
15,one ia32 smp vmx with acpi enable PASS
16,Build base kernel in ia32 SMP guest OS in VMX FAIL(
sometimes pass, sometimes fail)
xm test on ia32:
===========================Xm-test execution summary:
PASS: 44
FAIL: 5
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_reboot_basic_pos
Timed out waiting for console
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
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: IA-32_PAE ( based on UP,attention: guest os is Ia32 )
Service OS: RHEL4U1, IA-32_PAE, SMP
Hardware: Grandstal
Default guest OS: IA-32-UP, 2.6 kernel,
0, one IA32 2.6 VMX domain with memory 256M PASS
1, one ia32 smp vmx with memory 512M PASS
2, one pae smp vmx with memory 1.5GB PASS
3, one xenU with memory 256M PASS
4, 2 ia32 smp vmx and 2 xenU coexist PASS
5, four ia32 smp vmx coexist(64M,128M,196M,256M) PASS
6, network in ia32 smp VMX domain PASS
7, network in XenU domain PASS
8, one xpsp1 ia32 window domain PASS
8, 1 xpsp1 and 1 xpsp2 ia32 windows coexist in VMX domains 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 ia32 smp vmx with acpi enable PASS
14,Build base kernel in ia32 smp guest OS in VMX
FAIL(unstable, sometimes pass, sometimes fail)
xm test on ia32pae:
=============================================Xm-test execution summary:
PASS: 45
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 ia32pae:
===============================================================
Detail Test Report of Last Session
====================================================================The
following testcases do Not pass:
Suite : Scenario TC No. TP No.
ltp:quickhit 0 4 FAIL 22:52:18
Starting LTP quickhit Test Case alarm02
Summary Test Report of Last Session
Summary Test Report of Last Session
=============================================================================
Total Pass Fail NoResult Crash
=============================================================================ltp
194 193 1 0 0
=============================================================================ltp
194 193 1 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 119 1 0 0
sched 3 3 0 0 0
=============================================================================Total
194 193 1 0 0
Platform: IA-32e
Service OS: RHEL4U2, IA-32e, SMP
Hardware: Paxville
Default guest OS: IA-32e-SMP, 2.6 kernel
1, one ia32e smp vmx with memory 512M PASS
2, one xenU with memory 256M PASS
3, 2 ia32e smp vmxs and 2 xenUs coexist PASS
4, 2 ia32e smp vmxs and 2 ia32pae smp vmxs coexist PASS
5, network in ia32e smp VMX domain PASS
6, network in XenU domain PASS
7, one IA32 2.6 VMX domain with memory 256M PASS
8, one IA32PAE 2.6 VMX domain with 1500M PASS
11, subset LTP in ia32e guest OS in VMX PASS
12, one xpsp1 ia32e window domain PASS
13, 1 xpsp1 and 1 xpsp2 ia32e 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 with acpi enable PASS
xm test on ia32e:
=================================Xm-test execution summary:
PASS: 44
FAIL: 5
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_reboot_basic_pos
Timed out waiting for console
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
> 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 thatwe> boot up SMP guest OS in VMX. > > Here is the test summary: > > Issues: > - Creating 4 VMX simutaneously on 32 platform will hang xen0Does it reboot or just hang? Is dom0 pingable? Is the text console alive? If you''re in a text mode console, do you get an oops message printed? Exactly what kind of guests are you starting simultaneously, and on what hypervisor (e.g. PAE?). You say that you''re using an SMP kernel, and since in most distros the SMP kernel also implies guest PAE support, I assume you''re using pae=1 guests?> - Sometimes build base kernel 2.6.16 in IA32SMP guest fails on 32bit > platform.In what way does it fail? Does the guest VM crash? Does the make segfault? Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> 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 thatwe> boot up SMP guest OS in VMX. > > Here is the test summary: > > Issues: > - Creating 4 VMX simutaneously on 32 platform will hang xen0Does it reboot or just hang? Is dom0 pingable? Is the text console alive? Xen0 just hangs, not reboot. And dom0 is unpingable. Although the cursor is blinking in text console, but it is uncontrollable. If you''re in a text mode console, do you get an oops message printed? Exactly what kind of guests are you starting simultaneously, and on what hypervisor (e.g. PAE?). we start ia32 non-pae smp guest OS on ia32 hypervisor. You say that you''re using an SMP kernel, and since in most distros the SMP kernel also implies guest PAE support, I assume you''re using pae=1 guests? We build ia32 non-pae smp kernel by ourselves, so we use pae=0 smp guests.> - Sometimes build base kernel 2.6.16 in IA32SMP guest fails on 32bit > platform.In what way does it fail? Does the guest VM crash? Does the make segfault? Guest didn''t crash. See attachment "kb_ia32_smp_failed_1.JPG, kb_ia32_smp_failed.JGP" for some error messages from building kernel. In fact, we get various error messages. Build kernel in IA32PAE SMP VMX domain and IA32E SMP VMX domain are ok. http://losvmm-bridge.sh.intel.com/bugzilla/show_bug.cgi?id=788 Thanks, Ian _______________________________________________ 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
> > Issues: > > - Creating 4 VMX simutaneously on 32 platform will hang xen0 > > Does it reboot or just hang? Is dom0 pingable? Is the text > console alive? > Xen0 just hangs, not reboot. And dom0 is unpingable. > Although the cursor is blinking in text console, but it > is uncontrollable.Before starting the 4th guest, please change to a text mode console (ctrl-alt-f1) and start the guest from there. See if you get an oops message.> Exactly what kind of guests are you starting simultaneously, > and on what hypervisor (e.g. PAE?). > we start ia32 non-pae smp guest OS on ia32 hypervisor.Just to confirm, that''s a non-pae hypervisor? Do you get the same starting a non-pae guest on a 32b pae hypervisor? [this is by far the most tested combination]> > - Sometimes build base kernel 2.6.16 in IA32SMP guest fails > on 32bit > > platform. > > In what way does it fail? Does the guest VM crash? Does the > make segfault? > Guest didn''t crash. See attachment > "kb_ia32_smp_failed_1.JPG, kb_ia32_smp_failed.JGP" for some > error messages from building kernel. In fact, we get various > error messages. Build kernel in IA32PAE SMP VMX domain and > IA32E SMP VMX domain are ok. > http://losvmm-bridge.sh.intel.com/bugzilla/show_bug.cgi?id=788Which hypervisor does the error occur on? Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ian Pratt >Sent: 2006年9月4日 22:00 >To: Ye, Yuanqing; Zheng, Jeff; xen-devel@lists.xensource.com >Subject: RE: [Xen-devel] VMX status report 11394:96a4379be74a >Just to confirm, that''s a non-pae hypervisor? Do you get the same >starting a non-pae guest on a 32b pae hypervisor? [this is by far the >most tested combination]Hi Ian, This issue happened on both 32bit (none pae) hypervisor and 32bit pae hypervisor. We didn''t catch it in 32e (x86_64) hypervisor. It is to create 4 VMX at the same time. The command is like: "xm create vmx1; xm create vmx2; xm create vmx3; xm create vmx4". Sometimes Xen0 won''t hang. But the 4th VMX can not be created up. Xen0 reported: "Error: Device 768 (vbd) could not be connected. Hotplug"> >> > - Sometimes build base kernel 2.6.16 in IA32SMP guest fails >> on 32bit >> > platform. >Which hypervisor does the error occur on?This issue only happened on IA32 hypervisor (None-PAE). PAE and 32e hypervisor are okay. Best Regards, Yongkang (Kangkang) 永康 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>Hi Ian, > >This issue happened on both 32bit (none pae) hypervisor and 32bit pae >hypervisor. We didn''t catch it in 32e (x86_64) hypervisor. >One mistake. Em. The Xen0 crashed issue should only be caught in 32bit (none pae) hypervisor, when create 4 VMX at the same time. Best Regards, Yongkang (Kangkang) 永康 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
At 22:19 +0800 on 04 Sep (1157408387), You, Yongkang wrote:> It is to create 4 VMX at the same time. The command is like: > "xm create vmx1; xm create vmx2; xm create vmx3; xm create vmx4". > > Sometimes Xen0 won''t hang. But the 4th VMX can not be created up. Xen0 reported: "Error: Device 768 (vbd) could not be connected. Hotplug"I can start four VMX guests like this without any problem (on 32bit non-PAE Xen). Can you give some more details -- what guest OS are you using, how much memory per domain, how many VCPUs per domain? Cheers, Tim. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> This issue happened on both 32bit (none pae) hypervisor and 32bit pae > hypervisor. We didn''t catch it in 32e (x86_64) hypervisor. > > It is to create 4 VMX at the same time. The command is like: > "xm create vmx1; xm create vmx2; xm create vmx3; xm create vmx4". > > Sometimes Xen0 won''t hang. But the 4th VMX can not be created up. Xen0 > reported: "Error: Device 768 (vbd) could not be connected. Hotplug"Please can you follow my suggestion of starting the 4th guest from a text mode console. Even in the case where dom0 doesn''t hang but the domain fails to start please can you send the xen logs from /var/log/. Does starting a 5th simultaneous guest make the problem more or less likely? Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> >Before starting the 4th guest, please change to a text mode console >(ctrl-alt-f1) and start the guest from there. See if you get an oops >message.The text mode console shows nothing when dom0 hangs.> >> Exactly what kind of guests are you starting simultaneously, >> and on what hypervisor (e.g. PAE?). >> we start ia32 non-pae smp guest OS on ia32 hypervisor. > >Just to confirm, that''s a non-pae hypervisor? Do you get the same >starting a non-pae guest on a 32b pae hypervisor? [this is by far the >most tested combination]Yes, this is a non-pae hypervisor. We have tried 4 non-pae guest in 32b pae, and those VMXs could be started successfully.> >> > - Sometimes build base kernel 2.6.16 in IA32SMP guest fails >> on 32bit >> > platform. >> >> In what way does it fail? Does the guest VM crash? Does the >> make segfault? >> Guest didn''t crash. See attachment >> "kb_ia32_smp_failed_1.JPG, kb_ia32_smp_failed.JGP" for some >> error messages from building kernel. In fact, we get various >> error messages. Build kernel in IA32PAE SMP VMX domain and > >Which hypervisor does the error occur on?Kernel build problem exists in non-pae 32b hypervisor and this problem is still there in latest xen-unstable tree.>Thanks, >Ian > >_______________________________________________ >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
Tim, We found that in some hardware, 4 VMXs works well too in 32b non-PAE xen. Maybe this is a hardware specific issue. Ping> >At 22:19 +0800 on 04 Sep (1157408387), You, Yongkang wrote: >> It is to create 4 VMX at the same time. The command is like: >> "xm create vmx1; xm create vmx2; xm create vmx3; xm create vmx4". >> >> Sometimes Xen0 won''t hang. But the 4th VMX can not be created up.Xen0 reported:>"Error: Device 768 (vbd) could not be connected. Hotplug" > >I can start four VMX guests like this without any problem (on 32bit >non-PAE Xen). Can you give some more details -- what guest OS are you >using, how much memory per domain, how many VCPUs per domain? > >Cheers, > >Tim. > > >_______________________________________________ >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