Yu, Ping Y
2006-Dec-28 02:29 UTC
[Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
We have tested the latest xen on VT platform with Intel 965/5000P chipset. Here is the test summary: Today''s new issues: ============================1).[Block issue] IA32/PAE/IA32E: Linux VMX domain can''t boot up normally with acpi=0 in configuration file. For IA32 guest in IA32 Xen, it stop somewhere like attachment "screenshot for ia32_guest.jpg" shows: For PAE guest in PAE Xen, it gives a call trace like "pae_guest_calltrace.txt" shows. Issues: ============================1). IA32/PAE/IA32E: Reboot Linux VMX domain causes Xen0 reboot. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=847 Reboot cases in xm-test causes Xen0 reboot, so we don''t get xm-test detail report. 2). IA32E: IA32E ACPI Linux VMX domain crashes. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=845 3). IA32: WinXP/2K3 fail to boot up, it gives a black window. And got following messages in xm dmesg: (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! (XEN) vioapic.c:267:d142 error delivery mode 7 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=844 4).IA32E: Can not install ia32e FC4/RHEL4u1/RHEL4u2/RHEL4u3 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=842 5). IA32/IA32E: VBD still doesn''t work well. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=831 6). 32 bit guest OS Vista RTM network doesn''t work. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840 Details: =========================IA32: + Build&Boot SMP Xen0 without problem + Can bootup SMP XenU with 256 M memory + Can''t bootup unmodified IA32 SMP 2.6 Linux VMX domain + Can''t bootup IA32 SMP Linux VMX domain & XenU with different memory size (VMX:64MB,128MB,196MB,256MB,512MB.XenU:256MB) + Can''t boot up IA32 SMP Linux VMX domain with base kernel + Can''t build base kernel 2.6.16 in IA32 SMP Linux VMX domain + Can startX in Dom0 + Can bootup IA32 SMP 2.6 Linux VMX domain with acpi enable + Can bootup unmodified IA32 UP ACPI Win2K VMX domain + Can''t bootup unmodified IA32 UP noACPI Windows2K3 VMX domain + Can''t bootup unmodified IA32 UP ACPI WindowsXP SP2 VMX domain + Can''t bootup unmodified IA32 UP ACPI Windows2K3 VMX domain + Can''t bootup unmodified IA32 SMP ACPI Win2K3 VMX domain + Can''t bootup unmodified IA32 SMP ACPI WinXP VMX domain PAE: + Build&Boot PAE SMP xen0 without problem + Can bootup SMP XenU with 256 M Memory + Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain + Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain + Can''t bootup PAE SMP 2.6 Linux VMX domain & XenU with different memory size (VMX:64MB,128MB,196MB,256MB,512MB,1500MB.XenU:256MB) + Can''t bootup PAE SMP Linux VMX domain with base kernel + Can startX in Dom0 + Can bootup PAE SMP 2.6 Linux in VMX with acpi enable + Can bootup unmodified IA32 UP nonACPI Windows2K VMX domain + Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain + Can bootup unmodified PAE UP ACPI Windows2K3 VMX domain + Can bootup unmodified PAE UP ACPI Windows Beta 2 Vista VMX domain + Can bootup unmodified IA32 SMP Win2K3 VMX domain + Can bootup unmodified IA32 SMP WinXP VMX domain + Can bootup unmodified IA32 SMP Windows Beta 2 Vista VMX domain + Can''t bootup unmodified IA32 SMP Windows RTM Vista VMX domain IA32E: + Build&Boot IA32E SMP xen0 without problem + Can bootup SMP XenU with 256 M Memory + Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain + Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain + Can''t bootup unmodified IA32E SMP 2.6 Linux in VMX + Can''t bootup IA32E SMP VMX domain & xenU with different memory size. (VMX:128MB,256MB,384MB,512MB,1024M,4096MB.XenU:256MB) + Can''t bootup four IA32E SMP Linux VMX domain in sequence + Can''t boot up Linux VMX domain with base kernel + Can startX in Dom0 + Can''t bootup IA32E 2.6 Linux VMX domain with acpi enable + Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain + Can bootup unmodified IA32 UP ACPI Windows 2K3 VMX domain + Can bootup unmodified IA32 SMP Win2K3 VMX domain + Can bootup unmodified IA32 SMP WinXP VMX domain + Can bootup unmodified PAE SMP ACPI Windows Beta 2 Vista VMX domain + Can''t bootup unmodified PAE SMP ACPI Windows RTM Vista VMX domain + Can bootup unmodified IA32E UP WinXP VMX domain + Can bootup unmodified IA32E UP Win2K3 VMX domain + Can bootup unmodified IA32E SMP Win2K3 VMX domain + Can bootup unmodified IA32E SMP WinXP VMX domain + Can bootup unmodified IA32E SMP Windows Beta 2 Vista VMX domain + Can bootup unmodified IA32E SMP Windows RTM Vista VMX domain + Can bootup >4G IA32E SMP Window RTM Vista VMX domain + Can''t bootup >4G IA32E SMP Linux VMX domain For details ------------------------------------------------------------ Platform: IA32 Service OS: FC5, IA32, SMP Hardware: Conroe Default guest OS: IA32,SMP, 2.6 kernel 1, one xenU domain with memory 256M PASS 2, one IA32 nonPAE SMP VMX domain with memory 256M FAIL 3, one IA32 nonPAE SMP VMX domain with memory 512M FAIL 4, one VMX boot with IA32 nonPAE SMP base kernel(2.6.16) FAIL 5, one IA32 nonPAE SMP VMX domain with acpi enable PASS 6, Two IA32 nonPAE SMP VMX domains and 2 xenU domains coexist FAIL 8, network in XenU domain PASS 9, network in IA32 nonPAE SMP VMX domain FAIL 10, StartX in Linux VMX domain FAIL 11, StartX in Dom0 PASS 12, xm-test FAIL 13, subset LTP test in IA32 nonPAE SMP VMX domain FAIL 14, Build base kernel in IA32 nonPAE SMP VMX domain FAIL 15, one IA32 UP nonACPI Win2K3 VMX domain FAIL 16, one IA32 UP nonACPI 2K3 and XPsp2 Windows VMX domains coexist FAIL 17, one IA32 UP ACPI Windows 2K VMX domain PASS 18, one IA32 UP ACPI Windows XP sp2 VMX domain FAIL 19, one IA32 UP ACPI Windows 2003 VMX domain FAIL 20, one IA32 SMP Windows XP VMX domain FAIL 21, one IA32 SMP Windows 2K3 VMX domain FAIL Platform: PAE Service OS: FC5, PAE, SMP Hardware: Conroe Default guest OS: PAE,SMP, 2.6 kernel 1, one xenU domain with memory 256M PASS 2, one IA32 nonPAE SMP 2.6 VMX domain with memory 256M FAIL 3, one PAE SMP Linux VMX domain with memory 512M FAIL 4, one PAE SMP Linux VMX domain with memory 1500M FAIL 5, one Linux VMX domain boot with PAE SMP base kernel(2.6.16) FAIL 6, one PAE SMP Linux VMX domain with acpi enable PASS 7, 2 PAE SMP VMX domains and 2 xenU domains coexist FAIL 8, Four PAE SMP Linux VMX domains coexist FAIL 9, network in xenu domain PASS 10, network in PAE SMP Linux VMX domain FAIL 11, Startx in PAE SMP Linux VMX domain FAIL 12, startx in dom0 PASS 13, xm-test FAIL 14, subset LTP test in PAE SMP VMX domain FAIL 15, build Linux 2.6.16 base kernel in PAE SMP Linux VMX domain FAIL 16, one IA32 nonACPI Window VMX domain PASS 17, IA32 UP nonACPI 2K and XPsp2 Windows VMX domains coexist PASS 18, one IA32 UP ACPI Windows 2K VMX domain PASS 19, one IA32 UP ACPI Windows XP sp2 VMX domain PASS 20, one IA32 UP ACPI Windows 2K3 VMX domain PASS 21, one IA32 UP ACPI Windows Beta2 Vista VMX domain PASS 22, one IA32 SMP Windows 2K3 VMX domain PASS 23, one IA32 SMP Windows XP VMX domain PASS 24, one IA32 SMP Windows Beta 2 Vista VMX domain PASS 25, one IA32 SMP Windows RTM Vista VMX domain FAIL platform: IA32E service os: rhel4u3, IA32E, SMP hardware: Clovertown default guest os: IA32E,SMP, 2.6 kernel 1, one xenU domain with memory 256M PASS 2, one IA32 nonPAE SMP 2.6 Linux VMX domain with memory 256M FAIL 3, one PAE SMP Linux VMX domain with 1500M FAIL 4, one PAE SMP Linux VMX domain with 5120M memory FAIL 5, one IA32E SMP Linux VMX domain with 512M memory FAIL 6, one IA32E SMP Linux VMX domain with 5120M memory FAIL 7, Two 5120 M IA32E Linux VMX domain coexist FAIL 8, one Linux VMX boot with IA32E SMP base kernel(2.6.16) FAIL 9, one IA32E SMP Linux VMX domain with acpi enable FAIL 10, 2 IA32E SMP Linux VMX domains and 2 xenU VMX domains coexist FAIL 11, Four IA32E SMP Linux VMX domains coexist FAIL 12, network in IA32E SMP Linux VMX domain FAIL 13, network in XenU domain PASS 14, Startx in IA32E SMP Linux VMX domain FAIL 15, StartX in Dom0 PASS 16, xm-test FAIL 17, subset LTP in IA32E Linux VMX domain FAIL 18, Build base kernel in IA32E Linux VMX domain FAIL 19, one IA32 UP nonACPI Windows VMX domain PASS 20, one IA32 UP noACPI 2K3 and XPsp2 Windows VMX domains coexist PASS 21, one IA32 UP ACPI Windows 2K VMX domain PASS 22, one IA32 UP ACPI Windows XP VMX domain PASS 23, one IA32 UP ACPI Windows 2K3 VMX domain PASS 25, one IA32 SMP Windows XP VMX domain PASS 26, one IA32 SMP Windows 2K3 VMX domain PASS 27, one IA32 SMP Windows Beta 2 Vista VMX domain PASS 28, one IA32 SMP Windows RTM Vista VMX domain FAIL 29, one IA32E UP Windows XP VMX domain PASS 30, one IA32E UP Windows 2K3 VMX domain PASS 31, one IA32E UP Windows Vista VMX domain PASS 32, one IA32E SMP Windows XP VMX domain PASS 33, one IA32E SMP Windows 2K3 VMX domain PASS 34, one IA32E SMP Windows Beta 2 Vista VMX domain PASS 35, one IA32E SMP Windows RTM Vista VMX domain PASS 36, one IA32E SMP Window Vista with 5120 M memory PASS 37, Two 5120M IA32 SMP Win2K3 VMX domain and IA32E Linux VMX domain coexist FAIL Best Regards Ping _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yu, Ping Y
2006-Dec-28 02:50 UTC
RE: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
The block issue is opened for bug 848, and could anybody take a look at this issue? http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=848 Thanks Ping>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Yu, Ping Y >Sent: 2006年12月28日 10:30 >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b > > >We have tested the latest xen on VT platform with Intel 965/5000P >chipset. >Here is the test summary: > >Today''s new issues: >============================>1).[Block issue] IA32/PAE/IA32E: Linux VMX domain can''t boot up normally >with acpi=0 in configuration file. > For IA32 guest in IA32 Xen, it stop somewhere like attachment >"screenshot for ia32_guest.jpg" shows: > For PAE guest in PAE Xen, it gives a call trace like >"pae_guest_calltrace.txt" shows. > >Issues: >============================>1). IA32/PAE/IA32E: Reboot Linux VMX domain causes Xen0 reboot. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=847 >Reboot cases in xm-test causes Xen0 reboot, so we don''t get xm-test >detail report. > >2). IA32E: IA32E ACPI Linux VMX domain crashes. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=845 > >3). IA32: WinXP/2K3 fail to boot up, it gives a black window. And >got following messages in xm dmesg: > (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 > (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for >in-use IRQ! > (XEN) vioapic.c:267:d142 error delivery mode 7 > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=844 > >4).IA32E: Can not install ia32e FC4/RHEL4u1/RHEL4u2/RHEL4u3 > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=842 > >5). IA32/IA32E: VBD still doesn''t work well. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=831 > >6). 32 bit guest OS Vista RTM network doesn''t work. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840 > >Details: >=========================>IA32: > >+ Build&Boot SMP Xen0 without problem >+ Can bootup SMP XenU with 256 M memory >+ Can''t bootup unmodified IA32 SMP 2.6 Linux VMX domain >+ Can''t bootup IA32 SMP Linux VMX domain & XenU with different memory >size > (VMX:64MB,128MB,196MB,256MB,512MB.XenU:256MB) >+ Can''t boot up IA32 SMP Linux VMX domain with base kernel >+ Can''t build base kernel 2.6.16 in IA32 SMP Linux VMX domain >+ Can startX in Dom0 >+ Can bootup IA32 SMP 2.6 Linux VMX domain with acpi enable >+ Can bootup unmodified IA32 UP ACPI Win2K VMX domain >+ Can''t bootup unmodified IA32 UP noACPI Windows2K3 VMX domain >+ Can''t bootup unmodified IA32 UP ACPI WindowsXP SP2 VMX domain >+ Can''t bootup unmodified IA32 UP ACPI Windows2K3 VMX domain >+ Can''t bootup unmodified IA32 SMP ACPI Win2K3 VMX domain >+ Can''t bootup unmodified IA32 SMP ACPI WinXP VMX domain > >PAE: > >+ Build&Boot PAE SMP xen0 without problem >+ Can bootup SMP XenU with 256 M Memory >+ Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain >+ Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain >+ Can''t bootup PAE SMP 2.6 Linux VMX domain & XenU with different memory >size > (VMX:64MB,128MB,196MB,256MB,512MB,1500MB.XenU:256MB) >+ Can''t bootup PAE SMP Linux VMX domain with base kernel >+ Can startX in Dom0 >+ Can bootup PAE SMP 2.6 Linux in VMX with acpi enable >+ Can bootup unmodified IA32 UP nonACPI Windows2K VMX domain >+ Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain >+ Can bootup unmodified PAE UP ACPI Windows2K3 VMX domain >+ Can bootup unmodified PAE UP ACPI Windows Beta 2 Vista VMX domain >+ Can bootup unmodified IA32 SMP Win2K3 VMX domain >+ Can bootup unmodified IA32 SMP WinXP VMX domain >+ Can bootup unmodified IA32 SMP Windows Beta 2 Vista VMX domain >+ Can''t bootup unmodified IA32 SMP Windows RTM Vista VMX domain > >IA32E: >+ Build&Boot IA32E SMP xen0 without problem >+ Can bootup SMP XenU with 256 M Memory >+ Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain >+ Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain >+ Can''t bootup unmodified IA32E SMP 2.6 Linux in VMX >+ Can''t bootup IA32E SMP VMX domain & xenU with different memory size. > (VMX:128MB,256MB,384MB,512MB,1024M,4096MB.XenU:256MB) >+ Can''t bootup four IA32E SMP Linux VMX domain in sequence >+ Can''t boot up Linux VMX domain with base kernel >+ Can startX in Dom0 >+ Can''t bootup IA32E 2.6 Linux VMX domain with acpi enable >+ Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain >+ Can bootup unmodified IA32 UP ACPI Windows 2K3 VMX domain >+ Can bootup unmodified IA32 SMP Win2K3 VMX domain >+ Can bootup unmodified IA32 SMP WinXP VMX domain >+ Can bootup unmodified PAE SMP ACPI Windows Beta 2 Vista VMX domain >+ Can''t bootup unmodified PAE SMP ACPI Windows RTM Vista VMX domain >+ Can bootup unmodified IA32E UP WinXP VMX domain >+ Can bootup unmodified IA32E UP Win2K3 VMX domain >+ Can bootup unmodified IA32E SMP Win2K3 VMX domain >+ Can bootup unmodified IA32E SMP WinXP VMX domain >+ Can bootup unmodified IA32E SMP Windows Beta 2 Vista VMX domain >+ Can bootup unmodified IA32E SMP Windows RTM Vista VMX domain >+ Can bootup >4G IA32E SMP Window RTM Vista VMX domain >+ Can''t bootup >4G IA32E SMP Linux VMX domain > > >For details >------------------------------------------------------------ > >Platform: IA32 >Service OS: FC5, IA32, SMP >Hardware: Conroe >Default guest OS: IA32,SMP, 2.6 kernel > >1, one xenU domain with memory 256M >PASS >2, one IA32 nonPAE SMP VMX domain with memory 256M FAIL >3, one IA32 nonPAE SMP VMX domain with memory 512M FAIL >4, one VMX boot with IA32 nonPAE SMP base kernel(2.6.16) >FAIL >5, one IA32 nonPAE SMP VMX domain with acpi enable >PASS >6, Two IA32 nonPAE SMP VMX domains and 2 xenU domains coexist FAIL >8, network in XenU domain >PASS >9, network in IA32 nonPAE SMP VMX domain >FAIL >10, StartX in Linux VMX domain >FAIL >11, StartX in Dom0 >PASS >12, xm-test >FAIL >13, subset LTP test in IA32 nonPAE SMP VMX domain >FAIL >14, Build base kernel in IA32 nonPAE SMP VMX domain >FAIL >15, one IA32 UP nonACPI Win2K3 VMX domain >FAIL >16, one IA32 UP nonACPI 2K3 and XPsp2 Windows VMX domains coexist >FAIL >17, one IA32 UP ACPI Windows 2K VMX domain >PASS >18, one IA32 UP ACPI Windows XP sp2 VMX domain FAIL >19, one IA32 UP ACPI Windows 2003 VMX domain FAIL >20, one IA32 SMP Windows XP VMX domain FAIL >21, one IA32 SMP Windows 2K3 VMX domain FAIL > > >Platform: PAE >Service OS: FC5, PAE, SMP >Hardware: Conroe >Default guest OS: PAE,SMP, 2.6 kernel > >1, one xenU domain with memory 256M >PASS >2, one IA32 nonPAE SMP 2.6 VMX domain with memory 256M FAIL >3, one PAE SMP Linux VMX domain with memory 512M >FAIL >4, one PAE SMP Linux VMX domain with memory 1500M >FAIL >5, one Linux VMX domain boot with PAE SMP base kernel(2.6.16) >FAIL >6, one PAE SMP Linux VMX domain with acpi enable >PASS >7, 2 PAE SMP VMX domains and 2 xenU domains coexist FAIL >8, Four PAE SMP Linux VMX domains coexist >FAIL >9, network in xenu domain >PASS >10, network in PAE SMP Linux VMX domain FAIL >11, Startx in PAE SMP Linux VMX domain FAIL >12, startx in dom0 >PASS >13, xm-test >FAIL >14, subset LTP test in PAE SMP VMX domain >FAIL >15, build Linux 2.6.16 base kernel in PAE SMP Linux VMX domain FAIL >16, one IA32 nonACPI Window VMX domain PASS >17, IA32 UP nonACPI 2K and XPsp2 Windows VMX domains coexist PASS >18, one IA32 UP ACPI Windows 2K VMX domain >PASS >19, one IA32 UP ACPI Windows XP sp2 VMX domain PASS >20, one IA32 UP ACPI Windows 2K3 VMX domain PASS >21, one IA32 UP ACPI Windows Beta2 Vista VMX domain >PASS >22, one IA32 SMP Windows 2K3 VMX domain PASS >23, one IA32 SMP Windows XP VMX domain PASS >24, one IA32 SMP Windows Beta 2 Vista VMX domain >PASS >25, one IA32 SMP Windows RTM Vista VMX domain >FAIL > > > >platform: IA32E >service os: rhel4u3, IA32E, SMP >hardware: Clovertown >default guest os: IA32E,SMP, 2.6 kernel > >1, one xenU domain with memory 256M >PASS >2, one IA32 nonPAE SMP 2.6 Linux VMX domain with memory 256M FAIL >3, one PAE SMP Linux VMX domain with 1500M >FAIL >4, one PAE SMP Linux VMX domain with 5120M memory >FAIL >5, one IA32E SMP Linux VMX domain with 512M memory FAIL >6, one IA32E SMP Linux VMX domain with 5120M memory FAIL >7, Two 5120 M IA32E Linux VMX domain coexist >FAIL >8, one Linux VMX boot with IA32E SMP base kernel(2.6.16) >FAIL >9, one IA32E SMP Linux VMX domain with acpi enable >FAIL >10, 2 IA32E SMP Linux VMX domains and 2 xenU VMX domains coexist >FAIL >11, Four IA32E SMP Linux VMX domains coexist >FAIL >12, network in IA32E SMP Linux VMX domain >FAIL >13, network in XenU domain >PASS >14, Startx in IA32E SMP Linux VMX domain >FAIL >15, StartX in Dom0 >PASS >16, xm-test >FAIL >17, subset LTP in IA32E Linux VMX domain >FAIL >18, Build base kernel in IA32E Linux VMX domain >FAIL >19, one IA32 UP nonACPI Windows VMX domain >PASS >20, one IA32 UP noACPI 2K3 and XPsp2 Windows VMX domains coexist PASS >21, one IA32 UP ACPI Windows 2K VMX domain >PASS >22, one IA32 UP ACPI Windows XP VMX domain >PASS >23, one IA32 UP ACPI Windows 2K3 VMX domain PASS >25, one IA32 SMP Windows XP VMX domain PASS >26, one IA32 SMP Windows 2K3 VMX domain PASS >27, one IA32 SMP Windows Beta 2 Vista VMX domain >PASS >28, one IA32 SMP Windows RTM Vista VMX domain >FAIL >29, one IA32E UP Windows XP VMX domain PASS >30, one IA32E UP Windows 2K3 VMX domain PASS >31, one IA32E UP Windows Vista VMX domain >PASS >32, one IA32E SMP Windows XP VMX domain PASS >33, one IA32E SMP Windows 2K3 VMX domain >PASS >34, one IA32E SMP Windows Beta 2 Vista VMX domain >PASS >35, one IA32E SMP Windows RTM Vista VMX domain >PASS >36, one IA32E SMP Window Vista with 5120 M memory >PASS >37, Two 5120M IA32 SMP Win2K3 VMX domain and > IA32E Linux VMX domain coexist FAIL > > >Best Regards >Ping >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2006-Dec-28 09:29 UTC
Re: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
I''ve seen all manner of problems booting Linux guests since changesets 13115 (add HPET support), 13097 and 13096 (various changes to HVM platform timer support). With luck there have been just one or two issues introduced that are causing all these problems, but we''ll have to throw out those patches if the situation doesn''t improve in the next week. Xiaowei: I''m pretty sure I can eyeball bugs in the new vpt.c code. For example, how can it be right that last_plt_gtime is incremented by period in some places and period_cycles in others? The two quantities have different units! -- Keir On 28/12/06 2:50 am, "Yu, Ping Y" <ping.y.yu@intel.com> wrote:> The block issue is opened for bug 848, and could anybody take a look at this > issue? > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=848 > > Thanks > > Ping > >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Yu, Ping Y >> Sent: 2006年12月28日 10:30 >> To: xen-devel@lists.xensource.com >> Subject: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b >> >> >> We have tested the latest xen on VT platform with Intel 965/5000P >> chipset. >> Here is the test summary: >> >> Today''s new issues: >> ============================>> 1).[Block issue] IA32/PAE/IA32E: Linux VMX domain can''t boot up normally >> with acpi=0 in configuration file. >> For IA32 guest in IA32 Xen, it stop somewhere like attachment >> "screenshot for ia32_guest.jpg" shows: >> For PAE guest in PAE Xen, it gives a call trace like >> "pae_guest_calltrace.txt" shows. >> >> Issues: >> ============================>> 1). IA32/PAE/IA32E: Reboot Linux VMX domain causes Xen0 reboot. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=847 >> Reboot cases in xm-test causes Xen0 reboot, so we don''t get xm-test >> detail report. >> >> 2). IA32E: IA32E ACPI Linux VMX domain crashes. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=845 >> >> 3). IA32: WinXP/2K3 fail to boot up, it gives a black window. And >> got following messages in xm dmesg: >> (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 >> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for >> in-use IRQ! >> (XEN) vioapic.c:267:d142 error delivery mode 7 >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=844 >> >> 4).IA32E: Can not install ia32e FC4/RHEL4u1/RHEL4u2/RHEL4u3 >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=842 >> >> 5). IA32/IA32E: VBD still doesn''t work well. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=831 >> >> 6). 32 bit guest OS Vista RTM network doesn''t work. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840 >> >> Details: >> =========================>> IA32: >> >> + Build&Boot SMP Xen0 without problem >> + Can bootup SMP XenU with 256 M memory >> + Can''t bootup unmodified IA32 SMP 2.6 Linux VMX domain >> + Can''t bootup IA32 SMP Linux VMX domain & XenU with different memory >> size >> (VMX:64MB,128MB,196MB,256MB,512MB.XenU:256MB) >> + Can''t boot up IA32 SMP Linux VMX domain with base kernel >> + Can''t build base kernel 2.6.16 in IA32 SMP Linux VMX domain >> + Can startX in Dom0 >> + Can bootup IA32 SMP 2.6 Linux VMX domain with acpi enable >> + Can bootup unmodified IA32 UP ACPI Win2K VMX domain >> + Can''t bootup unmodified IA32 UP noACPI Windows2K3 VMX domain >> + Can''t bootup unmodified IA32 UP ACPI WindowsXP SP2 VMX domain >> + Can''t bootup unmodified IA32 UP ACPI Windows2K3 VMX domain >> + Can''t bootup unmodified IA32 SMP ACPI Win2K3 VMX domain >> + Can''t bootup unmodified IA32 SMP ACPI WinXP VMX domain >> >> PAE: >> >> + Build&Boot PAE SMP xen0 without problem >> + Can bootup SMP XenU with 256 M Memory >> + Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain >> + Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain >> + Can''t bootup PAE SMP 2.6 Linux VMX domain & XenU with different memory >> size >> (VMX:64MB,128MB,196MB,256MB,512MB,1500MB.XenU:256MB) >> + Can''t bootup PAE SMP Linux VMX domain with base kernel >> + Can startX in Dom0 >> + Can bootup PAE SMP 2.6 Linux in VMX with acpi enable >> + Can bootup unmodified IA32 UP nonACPI Windows2K VMX domain >> + Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain >> + Can bootup unmodified PAE UP ACPI Windows2K3 VMX domain >> + Can bootup unmodified PAE UP ACPI Windows Beta 2 Vista VMX domain >> + Can bootup unmodified IA32 SMP Win2K3 VMX domain >> + Can bootup unmodified IA32 SMP WinXP VMX domain >> + Can bootup unmodified IA32 SMP Windows Beta 2 Vista VMX domain >> + Can''t bootup unmodified IA32 SMP Windows RTM Vista VMX domain >> >> IA32E: >> + Build&Boot IA32E SMP xen0 without problem >> + Can bootup SMP XenU with 256 M Memory >> + Can''t bootup unmodified IA32 nonPAE SMP 2.6 Linux VMX domain >> + Can''t bootup unmodified PAE SMP 2.6 Linux VMX domain >> + Can''t bootup unmodified IA32E SMP 2.6 Linux in VMX >> + Can''t bootup IA32E SMP VMX domain & xenU with different memory size. >> (VMX:128MB,256MB,384MB,512MB,1024M,4096MB.XenU:256MB) >> + Can''t bootup four IA32E SMP Linux VMX domain in sequence >> + Can''t boot up Linux VMX domain with base kernel >> + Can startX in Dom0 >> + Can''t bootup IA32E 2.6 Linux VMX domain with acpi enable >> + Can bootup unmodified IA32 UP ACPI WindowXP SP2 VMX domain >> + Can bootup unmodified IA32 UP ACPI Windows 2K3 VMX domain >> + Can bootup unmodified IA32 SMP Win2K3 VMX domain >> + Can bootup unmodified IA32 SMP WinXP VMX domain >> + Can bootup unmodified PAE SMP ACPI Windows Beta 2 Vista VMX domain >> + Can''t bootup unmodified PAE SMP ACPI Windows RTM Vista VMX domain >> + Can bootup unmodified IA32E UP WinXP VMX domain >> + Can bootup unmodified IA32E UP Win2K3 VMX domain >> + Can bootup unmodified IA32E SMP Win2K3 VMX domain >> + Can bootup unmodified IA32E SMP WinXP VMX domain >> + Can bootup unmodified IA32E SMP Windows Beta 2 Vista VMX domain >> + Can bootup unmodified IA32E SMP Windows RTM Vista VMX domain >> + Can bootup >4G IA32E SMP Window RTM Vista VMX domain >> + Can''t bootup >4G IA32E SMP Linux VMX domain >> >> >> For details >> ------------------------------------------------------------ >> >> Platform: IA32 >> Service OS: FC5, IA32, SMP >> Hardware: Conroe >> Default guest OS: IA32,SMP, 2.6 kernel >> >> 1, one xenU domain with memory 256M >> PASS >> 2, one IA32 nonPAE SMP VMX domain with memory 256M FAIL >> 3, one IA32 nonPAE SMP VMX domain with memory 512M FAIL >> 4, one VMX boot with IA32 nonPAE SMP base kernel(2.6.16) >> FAIL >> 5, one IA32 nonPAE SMP VMX domain with acpi enable >> PASS >> 6, Two IA32 nonPAE SMP VMX domains and 2 xenU domains coexist FAIL >> 8, network in XenU domain >> PASS >> 9, network in IA32 nonPAE SMP VMX domain >> FAIL >> 10, StartX in Linux VMX domain >> FAIL >> 11, StartX in Dom0 >> PASS >> 12, xm-test >> FAIL >> 13, subset LTP test in IA32 nonPAE SMP VMX domain >> FAIL >> 14, Build base kernel in IA32 nonPAE SMP VMX domain >> FAIL >> 15, one IA32 UP nonACPI Win2K3 VMX domain >> FAIL >> 16, one IA32 UP nonACPI 2K3 and XPsp2 Windows VMX domains coexist >> FAIL >> 17, one IA32 UP ACPI Windows 2K VMX domain >> PASS >> 18, one IA32 UP ACPI Windows XP sp2 VMX domain FAIL >> 19, one IA32 UP ACPI Windows 2003 VMX domain FAIL >> 20, one IA32 SMP Windows XP VMX domain FAIL >> 21, one IA32 SMP Windows 2K3 VMX domain FAIL >> >> >> Platform: PAE >> Service OS: FC5, PAE, SMP >> Hardware: Conroe >> Default guest OS: PAE,SMP, 2.6 kernel >> >> 1, one xenU domain with memory 256M >> PASS >> 2, one IA32 nonPAE SMP 2.6 VMX domain with memory 256M FAIL >> 3, one PAE SMP Linux VMX domain with memory 512M >> FAIL >> 4, one PAE SMP Linux VMX domain with memory 1500M >> FAIL >> 5, one Linux VMX domain boot with PAE SMP base kernel(2.6.16) >> FAIL >> 6, one PAE SMP Linux VMX domain with acpi enable >> PASS >> 7, 2 PAE SMP VMX domains and 2 xenU domains coexist FAIL >> 8, Four PAE SMP Linux VMX domains coexist >> FAIL >> 9, network in xenu domain >> PASS >> 10, network in PAE SMP Linux VMX domain FAIL >> 11, Startx in PAE SMP Linux VMX domain FAIL >> 12, startx in dom0 >> PASS >> 13, xm-test >> FAIL >> 14, subset LTP test in PAE SMP VMX domain >> FAIL >> 15, build Linux 2.6.16 base kernel in PAE SMP Linux VMX domain FAIL >> 16, one IA32 nonACPI Window VMX domain PASS >> 17, IA32 UP nonACPI 2K and XPsp2 Windows VMX domains coexist PASS >> 18, one IA32 UP ACPI Windows 2K VMX domain >> PASS >> 19, one IA32 UP ACPI Windows XP sp2 VMX domain PASS >> 20, one IA32 UP ACPI Windows 2K3 VMX domain PASS >> 21, one IA32 UP ACPI Windows Beta2 Vista VMX domain >> PASS >> 22, one IA32 SMP Windows 2K3 VMX domain PASS >> 23, one IA32 SMP Windows XP VMX domain PASS >> 24, one IA32 SMP Windows Beta 2 Vista VMX domain >> PASS >> 25, one IA32 SMP Windows RTM Vista VMX domain >> FAIL >> >> >> >> platform: IA32E >> service os: rhel4u3, IA32E, SMP >> hardware: Clovertown >> default guest os: IA32E,SMP, 2.6 kernel >> >> 1, one xenU domain with memory 256M >> PASS >> 2, one IA32 nonPAE SMP 2.6 Linux VMX domain with memory 256M FAIL >> 3, one PAE SMP Linux VMX domain with 1500M >> FAIL >> 4, one PAE SMP Linux VMX domain with 5120M memory >> FAIL >> 5, one IA32E SMP Linux VMX domain with 512M memory FAIL >> 6, one IA32E SMP Linux VMX domain with 5120M memory FAIL >> 7, Two 5120 M IA32E Linux VMX domain coexist >> FAIL >> 8, one Linux VMX boot with IA32E SMP base kernel(2.6.16) >> FAIL >> 9, one IA32E SMP Linux VMX domain with acpi enable >> FAIL >> 10, 2 IA32E SMP Linux VMX domains and 2 xenU VMX domains coexist >> FAIL >> 11, Four IA32E SMP Linux VMX domains coexist >> FAIL >> 12, network in IA32E SMP Linux VMX domain >> FAIL >> 13, network in XenU domain >> PASS >> 14, Startx in IA32E SMP Linux VMX domain >> FAIL >> 15, StartX in Dom0 >> PASS >> 16, xm-test >> FAIL >> 17, subset LTP in IA32E Linux VMX domain >> FAIL >> 18, Build base kernel in IA32E Linux VMX domain >> FAIL >> 19, one IA32 UP nonACPI Windows VMX domain >> PASS >> 20, one IA32 UP noACPI 2K3 and XPsp2 Windows VMX domains coexist PASS >> 21, one IA32 UP ACPI Windows 2K VMX domain >> PASS >> 22, one IA32 UP ACPI Windows XP VMX domain >> PASS >> 23, one IA32 UP ACPI Windows 2K3 VMX domain PASS >> 25, one IA32 SMP Windows XP VMX domain PASS >> 26, one IA32 SMP Windows 2K3 VMX domain PASS >> 27, one IA32 SMP Windows Beta 2 Vista VMX domain >> PASS >> 28, one IA32 SMP Windows RTM Vista VMX domain >> FAIL >> 29, one IA32E UP Windows XP VMX domain PASS >> 30, one IA32E UP Windows 2K3 VMX domain PASS >> 31, one IA32E UP Windows Vista VMX domain >> PASS >> 32, one IA32E SMP Windows XP VMX domain PASS >> 33, one IA32E SMP Windows 2K3 VMX domain >> PASS >> 34, one IA32E SMP Windows Beta 2 Vista VMX domain >> PASS >> 35, one IA32E SMP Windows RTM Vista VMX domain >> PASS >> 36, one IA32E SMP Window Vista with 5120 M memory >> PASS >> 37, Two 5120M IA32 SMP Win2K3 VMX domain and >> IA32E Linux VMX domain coexist FAIL >> >> >> Best Regards >> Ping >> > > _______________________________________________ > 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
Zhai, Edwin
2006-Dec-28 09:40 UTC
Re: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
keir, r13159 caused hvm smp linux guest hang after "ENABLING IO-APIC IRQs", while UP is okay. seems guest are waiting timer intr. any suggestions? On Thu, Dec 28, 2006 at 09:29:10AM +0000, Keir Fraser wrote:> I''ve seen all manner of problems booting Linux guests since changesets 13115 > (add HPET support), 13097 and 13096 (various changes to HVM platform timer > support). With luck there have been just one or two issues introduced that > are causing all these problems, but we''ll have to throw out those patches if > the situation doesn''t improve in the next week. > > Xiaowei: I''m pretty sure I can eyeball bugs in the new vpt.c code. For > example, how can it be right that last_plt_gtime is incremented by period in > some places and period_cycles in others? The two quantities have different > units! > > -- Keir > > On 28/12/06 2:50 am, "Yu, Ping Y" <ping.y.yu@intel.com> wrote: > > > The block issue is opened for bug 848, and could anybody take a look at this > > issue? > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=848 > > > > Thanks > > > > Ping > >-- best rgds, edwin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Yang, Xiaowei
2006-Dec-28 09:46 UTC
RE: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
>Xiaowei: I''m pretty sure I can eyeball bugs in the new vpt.c code. For >example, how can it be right that last_plt_gtime is incremented byperiod in>some places and period_cycles in others? The two quantities havedifferent>units! >Keir, Sorry for the neglect! The quick fix is as below. diff -r a9a43705f26b xen/arch/x86/hvm/vpt.c --- a/xen/arch/x86/hvm/vpt.c Wed Dec 27 00:38:01 2006 +0000 +++ b/xen/arch/x86/hvm/vpt.c Thu Dec 28 17:37:17 2006 +0800 @@ -109,9 +109,9 @@ void pt_update_irq(struct vcpu *v) { pt = list_entry(list, struct periodic_time, list); if ( !is_irq_masked(v, pt->irq) && pt->pending_intr_nr - && pt->last_plt_gtime + pt->period < max_lag ) - { - max_lag = pt->last_plt_gtime + pt->period; + && pt->last_plt_gtime + pt->period_cycles < max_lag ) + { + max_lag = pt->last_plt_gtime + pt->period_cycles; irq = pt->irq; } } We are double checking the patches! Thanks, Xiaowei _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2006-Dec-28 09:58 UTC
Re: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
That''s different from the failures that I''m seeing right now, I think (although all are variations on ''hanging'' during early boot). I checked in r13159 because without it I was failing io_apic.c:check_timer(). My guess was that Linux had decided to use HPET to replace the PIT, and HPET0 always interrupts on GSI 2 in legacy routing mode. But we were routing PIT IRQ (ISA IRQ 0) to GSI 0 and so it looked to Linux as though no timer interrupts were happening (it was ''listening'' on GSI 0 rather than GSI 2). This was the root cause of the ''bad delivery mode 7'' messages that have been reported -- Linux was eventually programming an ExtINT delivery mode into the IOAPIC as part of unlock_ExtINT_logic(). It may be that r13159 has introduced some new bug as well as fixing an old bug. Perhaps I missed an interrupt override (ISA0 -> GSI2) somewhere. Ah.... Actually various code thinks it ''knows'' about IRQ0 and that code won''t know about the reroute to GSI2. For example, we won''t be pinning PIT to CPU0 and various hooks in vpt.c won''t be triggering. That certainly needs fixing... Hopefully that is the last bug. ;-) -- Keir On 28/12/06 9:40 am, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:> keir, > r13159 caused hvm smp linux guest hang after "ENABLING IO-APIC IRQs", while UP > is okay. > > seems guest are waiting timer intr. > any suggestions? > > > On Thu, Dec 28, 2006 at 09:29:10AM +0000, Keir Fraser wrote: >> I''ve seen all manner of problems booting Linux guests since changesets 13115 >> (add HPET support), 13097 and 13096 (various changes to HVM platform timer >> support). With luck there have been just one or two issues introduced that >> are causing all these problems, but we''ll have to throw out those patches if >> the situation doesn''t improve in the next week. >> >> Xiaowei: I''m pretty sure I can eyeball bugs in the new vpt.c code. For >> example, how can it be right that last_plt_gtime is incremented by period in >> some places and period_cycles in others? The two quantities have different >> units! >> >> -- Keir >> >> On 28/12/06 2:50 am, "Yu, Ping Y" <ping.y.yu@intel.com> wrote: >> >>> The block issue is opened for bug 848, and could anybody take a look at this >>> issue? >>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=848 >>> >>> Thanks >>> >>> Ping >>>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2006-Dec-28 15:35 UTC
Re: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
On 28/12/06 9:58 am, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:> Ah.... Actually various code thinks it ''knows'' about IRQ0 and that code > won''t know about the reroute to GSI2. For example, we won''t be pinning PIT > to CPU0 and various hooks in vpt.c won''t be triggering. That certainly needs > fixing... Hopefully that is the last bug. ;-)Everything seems to work rather better with this fixed! Changeset 13175:ce83c1896acc, currently in our staging tree. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhai, Edwin
2006-Dec-29 01:38 UTC
Re: [Xen-devel] [Block issue] VMX status report 13161:a9a43705f26b
On Thu, Dec 28, 2006 at 03:35:02PM +0000, Keir Fraser wrote:> On 28/12/06 9:58 am, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote: > > > Ah.... Actually various code thinks it ''knows'' about IRQ0 and that code > > won''t know about the reroute to GSI2. For example, we won''t be pinning PIT > > to CPU0 and various hooks in vpt.c won''t be triggering. That certainly needs > > fixing... Hopefully that is the last bug. ;-) > > Everything seems to work rather better with this fixed! Changeset > 13175:ce83c1896acc, currently in our staging tree.it works now! many thanks for your fix.> > -- Keir >-- best rgds, edwin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel