[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#19277 Status (Linux#804, ioemu#82787c..) --- Two new issues
Hi Isaku, Latest Cset#19277 has two new issues. I verified the old problem Qcow VTI boots slowly is fixed in latest IOEMU. Two new issues: === 1. Default xmexample.vti file is wrong due to Cset19257 By Cset#19257, xmexample.vti has been changed. Using that config file, IPF will try to find /usr/lib64/qemu-dm to boot VTI. But ia64 does not have /usr/lib64 (different with x86_64). 2. Qcow VTI can not boot up with hdc With hdc in the config file disk item, the qcow VTI can not be booted. It can be seen in qemu log. Fixed issue: === [FIXED] 1. With Qcow image, VTI boots up very slowly. Detail Xen/IA64 Unstable Cset #19277 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 19277 dom0 Cset:804 ioemu commit: 82787c6f689d869ad349df83ec3f58702afe00fe processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Cset#19245 compile fail, please merge with xen-unstable
Hi Isaku, Latest ia64-unstable can not be compiled with latest remote-ioemu. There is an error for function xc_domain_update_msi_irq between current ia64-hypervisor and ioemu-remote. (Please check tools/ioemu-remote/hw/pt-msi.c:130 and tools/libxc/xc_domain.c:918). We did some checking: === According to ioemu commit (f00f286226e425c355a73fecc492b6e11bac419a), there is one patch to xen-unstable:19246 at the same time (see http://xenbits.xensource.com/xen-unstable.hg?rev/9bc5799566be). But unfortunately, your latest merging with xen-unstable (Cset:19243) was just before the 19246. Please merge the xen-unstable again for fix. :-) BTW, the qcow-VTI boots slowly issue can be fixed by latest ioemu code. After your merging, we will verify that fix. Thank you very much! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Cset#19203: Destroy VTI made dom0 crash --- blocking issue for ABAT
Isaku Yamahata wrote: Could you try the attached patch? Hi Isaku, Sorry for replying late, I just retruned to work after weekend. On our machine, I verified this issue was gone with Cset#19206. Thank you for your fix! On Fri, Feb 13, 2009 at 05:03:07PM +0800, Zhang, Jingke wrote: Hi all, With latest Cset#19203, dom0 will crash when destroying VTI, either by xm des ... or run poweroff in VTI. It blocks this round of ABAT testing. Serial log info is in below: = (XEN) Assertion 'entry-prev-next == entry' failed, line 170, file /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h (XEN) Xen BUG at /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h:170 (XEN) FIXME: implement ia64 dump_execution_state() (XEN) (XEN) Call Trace: (XEN) [f400040fbbf0] show_stack+0x90/0xb0 (XEN) sp=f002fcd8fbf0 bsp=f002fcd89708 (XEN) [f400040fc700] dump_stack+0x30/0x50 (XEN) sp=f002fcd8fdc0 bsp=f002fcd896e8 (XEN) [f40004060d10] __bug+0x70/0xa0 (XEN) sp=f002fcd8fdc0 bsp=f002fcd896b8 (XEN) [f40004031050] free_domheap_pages+0x380/0x700 (XEN) sp=f002fcd8fdc0 bsp=f002fcd89658 (XEN) [f400040a7e30] domain_page_flush_and_put+0x1c0/0x500 (XEN) sp=f002fcd8fdc0 bsp=f002fcd89610 (XEN) [f400040a8300] domain_put_page+0x190/0x530 (XEN) sp=f002fcd8fdd0 bsp=f002fcd895a0 (XEN) [f400040a8980] zap_domain_page_one+0x2e0/0x4e0 (XEN) sp=f002fcd8fde0 bsp=f002fcd89500 (XEN) [f400040a8e40] dom0vp_zap_physmap+0x70/0x90 (XEN) sp=f002fcd8fdf0 bsp=f002fcd894c8 (XEN) [f4000407f990] do_dom0vp_op+0x2a0/0x730 (XEN) sp=f002fcd8fdf0 bsp=f002fcd89480 (XEN) [f40004002e30] fast_hypercall+0x170/0x340 (XEN) sp=f002fcd8fe00 bsp=f002fcd89480 (XEN) (XEN) (XEN) Panic on CPU 2: (XEN) Xen BUG at /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h:170 (XEN) (XEN) (XEN) Reboot in five seconds... Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Cset#19203: Destroy VTI made dom0 crash --- blocking issue for ABAT
Hi all, With latest Cset#19203, dom0 will crash when destroying VTI, either by xm des ... or run poweroff in VTI. It blocks this round of ABAT testing. Serial log info is in below: = (XEN) Assertion 'entry-prev-next == entry' failed, line 170, file /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h (XEN) Xen BUG at /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h:170 (XEN) FIXME: implement ia64 dump_execution_state() (XEN) (XEN) Call Trace: (XEN) [f400040fbbf0] show_stack+0x90/0xb0 (XEN) sp=f002fcd8fbf0 bsp=f002fcd89708 (XEN) [f400040fc700] dump_stack+0x30/0x50 (XEN) sp=f002fcd8fdc0 bsp=f002fcd896e8 (XEN) [f40004060d10] __bug+0x70/0xa0 (XEN) sp=f002fcd8fdc0 bsp=f002fcd896b8 (XEN) [f40004031050] free_domheap_pages+0x380/0x700 (XEN) sp=f002fcd8fdc0 bsp=f002fcd89658 (XEN) [f400040a7e30] domain_page_flush_and_put+0x1c0/0x500 (XEN) sp=f002fcd8fdc0 bsp=f002fcd89610 (XEN) [f400040a8300] domain_put_page+0x190/0x530 (XEN) sp=f002fcd8fdd0 bsp=f002fcd895a0 (XEN) [f400040a8980] zap_domain_page_one+0x2e0/0x4e0 (XEN) sp=f002fcd8fde0 bsp=f002fcd89500 (XEN) [f400040a8e40] dom0vp_zap_physmap+0x70/0x90 (XEN) sp=f002fcd8fdf0 bsp=f002fcd894c8 (XEN) [f4000407f990] do_dom0vp_op+0x2a0/0x730 (XEN) sp=f002fcd8fdf0 bsp=f002fcd89480 (XEN) [f40004002e30] fast_hypercall+0x170/0x340 (XEN) sp=f002fcd8fe00 bsp=f002fcd89480 (XEN) (XEN) (XEN) Panic on CPU 2: (XEN) Xen BUG at /home/build/nightly/builds_xen_ia64_unstable/xen-3.3-hg-xen_ia64_unstable-19203-20090213/xen/include/xen/list.h:170 (XEN) (XEN) (XEN) Reboot in five seconds... Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#19130 Status (Linux#786, ioemu#466706..) --- PASS
Hi all, There is no new issue with Cset#19130. All the cases (without qcow image) can pass! Detail Xen/IA64 Unstable Cset #19130 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 19130 dom0 Cset:786 ioemu commit: 46670677957c3d8a17e6e4a8d3e9919e5b21c4bc processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18957 Status (Linux#767, ioemu#b36996b3..) --- one new issue
Zhang, Jingke wrote: Hi all, The dom0 crash with 2048M memory issue has been fixed. One issue was found in Cset#18952 for Qcow image. One issue was fixed: = [FIXED] With dom0_max_mem=2048M, dom0 will crash while booting. (no such issue before dom0#742) New issue: = [NEW] linux guest boot very slow with qcow image by Cset#18952 For this new issue, we found it relates to the remote-ioemu. We used the default one qemu-xen-unstable.git in Config.mk. It is very old (git log shows the latest is Dec16). If using the staging/qemu-xen-unstable.git (Jan,07), the VTI booting speed is normal. Hope the staging qemu will be merged to unstable qemu. Thanks! Old issues: = 1. [IRQ] with IRQBALANCE service start, dom0 will crash on RHEL5u2 2. [Windows Network] Dom0 and Win2k3_VTI with e1000 can not ping each other 3. [CPU Sceduler] When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Detail Xen/IA64 Unstable Cset #18957 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18957 dom0 Cset:767 ioemu commit: b36996b39a4128ad9396bc0cf5ec3a57a7d31aa8 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18957 Status (Linux#767, ioemu#b36996b3..) --- one new issue
Hi all, The dom0 crash with 2048M memory issue has been fixed. One issue was found in Cset#18952 for Qcow image. One issue was fixed: = [FIXED] With dom0_max_mem=2048M, dom0 will crash while booting. (no such issue before dom0#742) New issue: = [NEW] linux guest boot very slow with qcow image by Cset#18952 Old issues: = 1. [IRQ] with IRQBALANCE service start, dom0 will crash on RHEL5u2 2. [Windows Network] Dom0 and Win2k3_VTI with e1000 can not ping each other 3. [CPU Sceduler] When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Detail Xen/IA64 Unstable Cset #18957 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18957 dom0 Cset:767 ioemu commit: b36996b39a4128ad9396bc0cf5ec3a57a7d31aa8 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18877 Status (Linux#753, ioemu#b4d410a1..) --- no regression
Hi all, There is no new issue in latest Cset#18877. With dom0 memory assigned 1024M (please see old issue1), all the cases can pass! Old known issues: = 1. [Dom0] With dom0_max_mem=2048M, dom0 will crash while booting. (no such issue before dom0#742) 2. [IRQ] with IRQBALANCE service start, dom0 will crash on RHEL5u2 3. [Windows Network] Dom0 and Win2k3_VTI with e1000 can not ping each other 4. [CPU Sceduler] When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Detail Xen/IA64 Unstable Cset #18877 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18877 dom0 Cset:753 ioemu commit: b4d410a1c28fcd1ea528d94eb8b94b79286c25ed processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18860 Status --- Dom0 Crash
wrote: Only call stack? Panic messages and/or register dump aren't available? Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18860 Status --- Dom0 Crash
Isaku Yamahata wrote: On Mon, Dec 08, 2008 at 11:31:15AM +0800, Zhang, Jingke wrote: Hi Isaku, We re-get the detail information from serial port, please see below. Two comments add: Thank you. 1. We can be sure the Cset#18832 works well on the same tiger4 machine. But we did not do regression test between 18832 and this 18860. 2. It is strange that on another Tiger4 box, dom0 will NOT crash. Do you have any idea from the serial log? Thanks! I haven't hit this crash. And Kuwamura-san's test seems that he haven't hit it either. Kuwamura-san, is it correct? Hmm... it seems to depend on hw configuration? I'm inclined to suspect masking/unmasking interruption race. event channel issues? But that's just only my very vague guess. The difference between 18832 and 18860 means the merging xen-unstable into xen-ia64-unstable. Looking the log, I suspect linux-2.6.18-xen instead of xen. Could you provide the linux c/s which corresponds to 18832 and 18860? Hi Isaku, Yes, some of our machines do not crash. I am afraid there may be some potential issue. By testing 18832, we use linux#742. While 18860 uses linux#753. Thanks! thanks, ACPI: bus type pci registered (XEN) mm.c:769:d0 vcpu 0 iip 0xa0010054b360: bad mpa d 0 0x807ff14f08 (= 0x 100ab4000) Unable to handle kernel NULL pointer dereference (address 0008) swapper[1]: Oops 8804682956800 [1] Modules linked in: Pid: 1, CPU 0, comm: swapper psr : 1010085a2010 ifs : 850d ip : [a00100136340]Not tainted ip is at cache_alloc_refill+0x300/0x540 unat: pfs : 450d rsc : 0007 rnat: 1010085a6010 bsps: a0010054b360 pr : a581 ldrs: ccv : fpsr: 0009804c8a70433f csd : ssd : b0 : a00100136280 b6 : a001005659d0 b7 : a0010054f2a0 f6 : 1003e f7 : 1003e f8 : 1003e0040 f9 : 0 f10 : 0 f11 : 0 r1 : a001011448b0 r2 : r3 : e0807ff14f30 r8 : 00f0 r9 : 001b r10 : e0807ff14f20 r11 : 2094 r12 : e0007f5cfd90 r13 : e0007f5c8000 r14 : r15 : e0007ff1a114 r16 : 00100100 r17 : e0807ff14f24 r18 : e0807ff14f20 r19 : e0807ff14f08 r20 : 0040 r21 : e0007ff14f00 r22 : r23 : 00200200 r24 : e0007ff14f48 r25 : e19e6480 r26 : e0007ff18080 r27 : r28 : e19e6670 r29 : e19e6660 r30 : 003b r31 : e19e6488 Call Trace: [a0010001db20] show_stack+0x40/0xa0 sp=e0007f5cf940 bsp=e0007f5c9500 [a0010001e780] show_regs+0x840/0x880 sp=e0007f5cfb10 bsp=e0007f5c94a8 [a00100043460] die+0x1c0/0x380 sp=e0007f5cfb10 bsp=e0007f5c9460 [a0010006dae0] ia64_do_page_fault+0x880/0x9a0 sp=e0007f5cfb30 bsp=e0007f5c9410 [a001000702c0] xen_leave_kernel+0x0/0x3e0 sp=e0007f5cfbc0 bsp=e0007f5c9410 [a00100136340] cache_alloc_refill+0x300/0x540 sp=e0007f5cfd90 bsp=e0007f5c93a0 [a001001367c0] __kmalloc+0x240/0x360 sp=e0007f5cfd90 bsp=e0007f5c9368 [a00100106af0] __kzalloc+0x30/0x80 sp=e0007f5cfd90 bsp=e0007f5c9340 [a00100551f90] acpi_ds_build_internal_package_obj+0x190/0x340 sp=e0007f5cfd90 bsp=e0007f5c92f0 [a0010054e290] acpi_ds_eval_data_object_operands+0x1b0/0x260 sp=e0007f5cfd90 bsp=e0007f5c92b8 [a00100550070] acpi_ds_exec_end_op+0x730/0xac0 sp=e0007f5cfda0 bsp=e0007f5c9270 [a00100578700] acpi_ps_parse_loop+0x1040/0x1940 sp=e0007f5cfda0 bsp=e0007f5c9210 [a00100576b40] acpi_ps_parse_aml+0x100/0x560 sp=e0007f5cfdb0 bsp=e0007f5c91b8 [a0010054ee10] acpi_ds_execute_arguments+0x1f0/0x260 sp=e0007f5cfdb0 bsp=e0007f5c9160 [a0010054f0c0] acpi_ds_get_package_arguments+0xc0/0xe0 sp=e0007f5cfdb0 bsp=e0007f5c9140 [a00100574710] acpi_ns_init_one_object+0x2b0/0x380 sp=e0007f5cfdb0 bsp=e0007f5c90f0 [a001005753c0] acpi_ns_walk_namespace+0x280/0x2e0 sp=e0007f5cfdb0 bsp=e0007f5c9080
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18860 Status --- Dom0 Crash
Hi all, We found the latest Cset#18860 will make dom0 crash. Last stable Cset we have tested is 18832. Thanks! Build info: xen: 18860 linux: 753 remote-ioemu: b4d410a1c28fcd1ea528d94eb8b94b79286c25ed Call trace: = [a0010001db20] show_stack+0x40/0xa0 sp=e0007f5cf940 bsp=e0007f5c9500 [a0010001e780] show_regs+0x840/0x880 sp=e0007f5cfb10 bsp=e0007f5c94a8 [a00100043460] die+0x1c0/0x380 sp=e0007f5cfb10 bsp=e0007f5c9460 [a0010006dae0] ia64_do_page_fault+0x880/0x9a0 sp=e0007f5cfb30 bsp=e0007f5c9410 [a001000702c0] xen_leave_kernel+0x0/0x3e0 sp=e0007f5cfbc0 bsp=e0007f5c9410 [a00100136340] cache_alloc_refill+0x300/0x540 sp=e0007f5cfd90 bsp=e0007f5c93a0 [a001001367c0] __kmalloc+0x240/0x360 sp=e0007f5cfd90 bsp=e0007f5c9368 [a00100106af0] __kzalloc+0x30/0x80 sp=e0007f5cfd90 bsp=e0007f5c9340 [a00100551f90] acpi_ds_build_internal_package_obj+0x190/0x340 sp=e0007f5cfd90 bsp=e0007f5c92f0 [a0010054e290] acpi_ds_eval_data_object_operands+0x1b0/0x260 sp=e0007f5cfd90 bsp=e0007f5c92b8 [a00100550070] acpi_ds_exec_end_op+0x730/0xac0 sp=e0007f5cfda0 bsp=e0007f5c9270 [a00100578700] acpi_ps_parse_loop+0x1040/0x1940 sp=e0007f5cfda0 bsp=e0007f5c9210 [a00100576b40] acpi_ps_parse_aml+0x100/0x560 sp=e0007f5cfdb0 bsp=e0007f5c91b8 [a0010054ee10] acpi_ds_execute_arguments+0x1f0/0x260 sp=e0007f5cfdb0 bsp=e0007f5c9160 [a0010054f0c0] acpi_ds_get_package_arguments+0xc0/0xe0 sp=e0007f5cfdb0 bsp=e0007f5c9140 [a00100574710] acpi_ns_init_one_object+0x2b0/0x380 sp=e0007f5cfdb0 bsp=e0007f5c90f0 [a001005753c0] acpi_ns_walk_namespace+0x280/0x2e0 sp=e0007f5cfdb0 bsp=e0007f5c9080 [a00100570b50] acpi_walk_namespace+0x90/0xc0 sp=e0007f5cfdb0 bsp=e0007f5c9030 [a00100574400] acpi_ns_initialize_objects+0x60/0xc0 sp=e0007f5cfdb0 bsp=e0007f5c9018 [a001005884e0] acpi_initialize_objects+0x60/0x100 sp=e0007f5cfdd0 bsp=e0007f5c8ff0 [a00100c802f0] acpi_init+0xb0/0x460 sp=e0007f5cfdd0 bsp=e0007f5c8fd0 [a00100011900] init+0x320/0x840 sp=e0007f5cfe00 bsp=e0007f5c8f98 [a0010001bfd0] kernel_thread_helper+0x30/0x60 sp=e0007f5cfe30 bsp=e0007f5c8f70 [a001000110e0] start_kernel_thread+0x20/0x40 sp=e0007f5cfe30 bsp=e0007f5c8f70 0Kernel panic - not syncing: Attempted to kill init! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18831 Status (Linux#742, ioemu#b4d410a1..) --- no regression
Hi all, There is no new regression in latest Cset#18831. All the cases can pass! Old known issues: = 1. [IRQ] with IRQBALANCE service start, dom0 will crash on RHEL5u2 2. [Windows Network] Dom0 and Win2k3_VTI with e1000 can not ping each other 3. [CPU Sceduler] When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Detail Xen/IA64 Unstable Cset #18831 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18831 dom0 Cset:742 ioemu commit: b4d410a1c28fcd1ea528d94eb8b94b79286c25ed processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Xen/IPF Unstable CS#18767 Status (Linux#720, ioemu#b4d410a1..) --- no regression
Hi all, There is no new regression in Cset#18767. All the cases can pass! Old issues: = 1. [IRQ] with IRQBALANCE service start, dom0 will crash on RHEL5u2 2. [Windows Network] Dom0 and Win2k3_VTI with e1000 can not ping each other 3. [CPU Sceduler] When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Detail Xen/IA64 Unstable Cset #18767 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18767 dom0 Cset:720 ioemu commit: b4d410a1c28fcd1ea528d94eb8b94b79286c25ed processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Test Report] Weekly Xen-IPF Test Report ------ 2008-11-14
Hi all, No new Csets for IPF last week. Latest Cset#18763 is stable. We also did some stress test for VTI with Cset#18633. Result is good! Next stress, we will choose the last three cases running for 24 hours each. = Platform: Tiger4 VTI Configuration: UP, 512M [PASS] Xen crashme stress, 8 hours [PASS] Xen helltest stress, 8 hours [PASS] Xen cvworkloads stress, 8 hours [PASS] Xen ltp stress, 8 hours [PASS] Xen kernelbuild stress, 8 hours [PASS] Run crashme,helltest,cvworkload ltp kernelbuild serially for 20 hours [PASS] Run crashme helltest cvworkload ltp kernelbuild parallely for 20 hours [PASS] Xen stress for win2k8, 8 hours Current unfixed issues (total 3): = 1. with IRQBALANCE service start, dom0 will crash on RHEL5u2 2. Dom0 and Win2k3_VTI with e1000 can not ping each other 3. When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow during NVRAM loading period. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18761 --- test blocked by dom0 crashing
Hi all, We found dom0 will crash when booting VTI guest with latest Cset#18761. (xenU guest is ok) Last stable cset is 18759. Call trace is: = (XEN) General Exception: IA-64 Reserved Register/Field fault (data access). (XEN) d 0xf413c080 domid 1 (XEN) vcpu 0xf002f9ff8000 vcpu 0 (XEN) (XEN) CPU 3 (XEN) psr : 101008226000 ifs : 8001 ip : [f400040012a0] (XEN) ip is at ia64_frametable_probe+0x0/0x160 (XEN) unat: pfs : 0286 rsc : 0003 (XEN) rnat: bsps: pr : 8169 (XEN) ldrs: ccv : fpsr: 0009804c0270033f (XEN) csd : ssd : (XEN) b0 : f400040b2670 b6 : f40004010ef0 b7 : (XEN) f6 : 0 f7 : 0 (XEN) f8 : 0 f9 : 0 (XEN) f10 : 0 f11 : 0 (XEN) r1 : f400043cfe80 r2 : f002f9d0 r3 : f002f9d8 (XEN) r8 : r9 : r10 : (XEN) r11 : 0009804c0270033f r12 : f002f9fffdf0 r13 : f002f9ff8000 (XEN) r14 : f40004168d08 r15 : 0013fffb r16 : 07ff (XEN) r17 : 0003f000 r18 : 000f r19 : f002f9f0 (XEN) r20 : r21 : r22 : (XEN) r23 : r24 : f002f9fffe20 r25 : f002f9fffe28 (XEN) r26 : r27 : r28 : (XEN) r29 : r30 : r31 : (XEN) (XEN) Call Trace: (XEN) [f400040e80d0] show_stack+0x80/0xa0 (XEN) sp=f002f9fffa20 bsp=f002f9ff95a0 (XEN) [f400040a32e0] ia64_fault+0x790/0xad0 (XEN) sp=f002f9fffbf0 bsp=f002f9ff9568 (XEN) [f400040df980] ia64_leave_kernel+0x0/0x300 (XEN) sp=f002f9fffbf0 bsp=f002f9ff9568 (XEN) [f400040012a0] ia64_frametable_probe+0x0/0x160 (XEN) sp=f002f9fffdf0 bsp=f002f9ff9560 (XEN) [f400040b2670] ia64_mfn_valid+0x80/0xb0 (XEN) sp=f002f9fffdf0 bsp=f002f9ff9538 (XEN) [f400040cf9c0] translate_phy_pte+0x210/0x2b0 (XEN) sp=f002f9fffdf0 bsp=f002f9ff94f8 (XEN) [f400040cfd10] thash_vhpt_insert+0x30/0x280 (XEN) sp=f002f9fffdf0 bsp=f002f9ff94a8 (XEN) [f400040c5880] physical_tlb_miss+0x50/0x70 (XEN) sp=f002f9fffdf0 bsp=f002f9ff9478 (XEN) [f400040c7db0] vmx_hpw_miss+0x650/0x1460 (XEN) sp=f002f9fffdf0 bsp=f002f9ff93b0 (XEN) [f400040c0d80] ia64_leave_hypervisor+0x0/0x250 (XEN) sp=f002f9fffe00 bsp=f002f9ff93b0 (XEN) (XEN) (XEN) Panic on CPU 3: (XEN) Fault in Xen. (XEN) (XEN) (XEN) Reboot in five seconds... Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18694, Linux#706, ioemu#b4d410a1.. Status --- 1 new
Hi all, There is one new regression in Cset#18691. With latest Cset#18694, all the case can pass! One regression between Cset#18688 and Cset#18691: == 1. Qemu graphic mode display abnormally while booting VTI_Windows and Linux-Xwin. This issue existed in either sdl=1 or vnc=1 mode. And this issue does not exist with Cset#18688. Detail Xen/IA64 Unstable Cset #18694 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18694 dom0 Cset:706 ioemu commit: b4d410a1c28fcd1ea528d94eb8b94b79286c25ed processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18688, Linux#705, ioemu#629adb3f... Status --- no new issue, report 3 old bugs
Isaku Yamahata wrote: On Tue, Oct 28, 2008 at 12:12:45PM +0900, Isaku Yamahata wrote: I thought Jingke isn't saying this topic. What he found maybe he failed to create the domain when the domain is created and destoryed continuously for more 62 times. Seems the issue is from the the algorithm for deallocating rid blocks doesn't work, when destroying the guest. Oh I see. Thank you for the explanation. Could you try the following patch? IA64: fix XENMEM_add_to_physmap with XENMAPSPACE_mfn. page reference count was leaked so that hvm domain wasn't freed. This patch fixes it. Signed-off-by: Isaku Yamahata [EMAIL PROTECTED] diff --git a/xen/arch/ia64/xen/mm.c b/xen/arch/ia64/xen/mm.c --- a/xen/arch/ia64/xen/mm.c +++ b/xen/arch/ia64/xen/mm.c @@ -3365,7 +3365,6 @@ arch_memory_op(int op, XEN_GUEST_HANDLE( /* Map at new location. */ /* Here page-count_info = PGC_allocated | N where N = 1*/ __guest_physmap_add_page(d, xatp.gpfn, mfn); -page = NULL; /* prevent put_page() */ out: domain_unlock(d); Yes, I retest it with your patch. VTI guest can be booted when domain_id is 62. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18688, Linux#705, ioemu#629adb3f... Status --- no new issue, report 3 old bugs
Hi all, There is no regression in Cset#18688. All the case can pass! But, we tried many manual testing on IPF and found some old bugs. See detail below: === 1. SMP Windows2008 boots much slower with other VTI guest togather (Win2k8 needs 7 minutes) If booting win2k8 singlely, it can be booted within 200 seconds. (win2k8's Memory=1024, vcpus=2) 2. On RHEL5u2 with IRQBALANCE service start, dom0 will crash 3. IPF-Xen can not boot up domain with dom_id 62 (not regression, should be there for a long time) Detail Xen/IA64 Unstable Cset #18688 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18688 dom0 Cset:705 ioemu commit: 629adb3f5244169731ff18b16ae919641d81ad76 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] How about stub-domain in IPF-Xen now?
Hi Isaku, We checked the stub-domain in x86 side, basically it works well for booting, smp, and memory (only some issues on save-restore). I remember we did not support stub-domain for resource limit. Do you have new plan to let IA64-Xen support it? Or is ia64 stub-domain available now? Thanks! :) Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18633, Linux#701, ioemu#629adb3f... Status --- no new issue
Hi all, There is no new regression found in Cset#18633. Two old issue were fixed in remote-ioemu by KUWAMURA: [FIXED] 1. With 4096M, VTI can not boot up emulated rtl8139 network-card [FIXED] 2. With 4095M, qemu of VTI guest will disappear when booting I also found one old issue (low priority) was also fixed now. The VTI with special memory 3073M can be booted. KUWAMURA, Is this fixing related to your patch? Issue information is: [IPF] VTI will crash while booting with 3073M memory It is told by Akio Takebe that Kuwamura had checked the memory area that we cannot boot hvm a guest from 3073MB to 3299MB. Results are below: FAIL: 3073-3077, 3079-3094, 3098MB PASS: 3078, 3095-3097, 3099-3299MB http://lists.xensource.com/archives/html/xen-ia64-devel/2008-07/msg00200.html Detail Xen/IA64 Unstable Cset #18633 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18633 dom0 Cset:701 ioemu commit: 629adb3f5244169731ff18b16ae919641d81ad76 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#131 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue
KUWAMURA Shin'ya wrote: Hi, On [EMAIL PROTECTED], Isaku Yamahata wrote: So not only MMIO hole (1GB), but also VGA io hole (VGA_IO_SIZE) should be taken into consideration. I added VGA_IO_SIZE. I confirmed that a VTi domain with 4095MB booted up and the rtl8139 NIC worked. Best regards, Hi KUWAMURA and Isaku, With the patch on CS#18580, Linux#687, ioemu#0f3d6384..., the two issues can be fixed! I also rerun the whole test, no regression. Thanks! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue
Hi all, There is no new regression found in Cset#18580. Three old issues still existed. Old issue (3): 1. Qemu will disappear and VTI hangs when we do 'xm restore' and 'xm migrate' 2. With 4096M, VTI can not boot up emulated rtl8139 network-card 3. With 4095M, qemu of VTI guest will disappear when booting Detail Xen/IA64 Unstable Cset #18580 Status Report Test Result Summary: # total case: 17 # passed case: 14 # failed case: 3 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18580 dom0 Cset: 687 ioemu commit: 0f3d6384d1b3d96476f78950b14040f9c1c63375 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Failed case SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue
Isaku Yamahata wrote: On Mon, Oct 06, 2008 at 09:54:13AM +0800, Zhang, Jingke wrote: Hi all, There is no new regression found in Cset#18580. Three old issues still existed. Old issue (3): 1. Qemu will disappear and VTI hangs when we do 'xm restore' and 'xm migrate' Hi. Does this still exist? The change set 18578:ba543f51c6f1 should fix this. At least works for me with xm save/restore. I haven't tried xm migrate, though. Does qemu-dm exit with the following message? from xen_vga_vram_map() in hw/vga.c fprintf(stderr, Failed to map vram nr_pfn=0x%lx vram_addr=%llx: %s\n, nr_pfn, (unsigned long long)vram_addr, strerror(errno)); exit(1); Yes, my qemu-dm log shows: Failed to map vram nr_pfn=0x200 vram_addr=c000: Invalid argument I used GFW#129, image type is QCOW. Since it works for you, what is the difference between us? Thanks. :) thanks, 2. With 4096M, VTI can not boot up emulated rtl8139 network-card 3. With 4095M, qemu of VTI guest will disappear when booting Detail Xen/IA64 Unstable Cset #18580 Status Report Test Result Summary: # total case: 17 # passed case: 14 # failed case: 3 Testing Environment: platform: Tiger4 xen ia64 unstable tree: 18580 dom0 Cset: 687 ioemu commit: 0f3d6384d1b3d96476f78950b14040f9c1c63375 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Failed case SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue
Isaku Yamahata wrote: On Mon, Oct 06, 2008 at 11:16:02AM +0800, Zhang, Jingke wrote: Isaku Yamahata wrote: On Mon, Oct 06, 2008 at 09:54:13AM +0800, Zhang, Jingke wrote: Hi all, There is no new regression found in Cset#18580. Three old issues still existed. Old issue (3): 1. Qemu will disappear and VTI hangs when we do 'xm restore' and 'xm migrate' Hi. Does this still exist? The change set 18578:ba543f51c6f1 should fix this. At least works for me with xm save/restore. I haven't tried xm migrate, though. Does qemu-dm exit with the following message? from xen_vga_vram_map() in hw/vga.c fprintf(stderr, Failed to map vram nr_pfn=0x%lx vram_addr=%llx: %s\n, nr_pfn, (unsigned long long)vram_addr, strerror(errno)); exit(1); Yes, my qemu-dm log shows: Failed to map vram nr_pfn=0x200 vram_addr=c000: Invalid argument I used GFW#129, image type is QCOW. Since it works for you, what is the difference between us? Thanks. :) Ah, I'm using patched GFW. I sent out two patches as http://lists.xensource.com/archives/html/xen-ia64-devel/2008-09/msg00067.html http://lists.xensource.com/archives/html/xen-ia64-devel/2008-09/msg00068.html But I guess Tristan is too busy to commit those. The patch in msg00067.html would fix the issue. Could you try that patch? Thanks, I see. GFW building needs too much to set up the compile environment. So, I am afraid it may need some time for me to check it. Anyway, I will mark the old issue1 as a GFW issue first. Hope Tristan can check it in soon. :) thanks, thanks, 2. With 4096M, VTI can not boot up emulated rtl8139 network-card 3. With 4095M, qemu of VTI guest will disappear when booting Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18501 Status Report --- 1 new issue for guest restore
Isaku Yamahata wrote: On Sat, Sep 20, 2008 at 01:27:03PM +0800, Zhang, Jingke wrote: Hi all, Cset#18501 has one new issue. 1. Qemu will disappear and VTI hangs when we do 'xm restore' and 'xm migrate' Given that the last report is based on the change set of 18483, I is likely that the change set of 18501:3d96f88fb220 caused the issue. To be honest I'm not sure at this moment, though. Yes, we did nightly test based on our building Cset (last building is 18483). So, this issue should happen from 18484 to 18501. Totally 18 csets, do you have any hint for us to narrow down the issue? Thank you very much! Old issue (2): 1. With 4096M, VTI can not boot up emulated rtl8139 network-card 2. With 4095M, qemu of VTI guest will disappear when booting Detail Xen/IA64 Unstable Cset #18501 Status Report Test Result Summary: # total case: 17 # passed case: 14 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18501 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Failed case SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18501 Status Report --- 1 new issue for guest restore
Hi all, Cset#18501 has one new issue. 1. Qemu will disappear and VTI hangs when we do 'xm restore' and 'xm migrate' Old issue (2): 1. With 4096M, VTI can not boot up emulated rtl8139 network-card 2. With 4095M, qemu of VTI guest will disappear when booting Detail Xen/IA64 Unstable Cset #18501 Status Report Test Result Summary: # total case: 17 # passed case: 14 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18501 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Failed case SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18483 Status Report --- 2 new issues for remote-ioemu
Isaku Yamahata wrote: On Mon, Sep 15, 2008 at 12:47:31PM +0800, Zhang, Jingke wrote: Hi all, With remote-ioemu, Cset#18483 has two new issues (both can pass with local ioemu): 1. Qemu windows will disappear soon after booting, with 4095M memory. (Did you mean 4096M?) No, just 4095M. If you use that memory, qemu will disappear. I wasn't able to reproduce it. Could you elaborate on it? - Do you mean vncvewer's window by qemu windows? - Is the X server you were using running on the IA64 target machine? Or did you tried to boot vncviewer remotely? (probably with ssh portforwarding) - Even after window disappearing, is it possible for new vncviewer to connect to qemu-dm by xm vncviewer command? 2. The Linux 4096M VTI can not boot up network with remote-ioemu. Which network device are you using? e100, e1000 or rtl8193? I found e100 instability with 256MB memory, but with e1000 network works well. I haven't tried rtl8193. We use the default one --- rtl8139. thanks, Detail Xen/IA64 Unstable Cset #18483 Status Report Test Result Summary: # total case: 17 # passed case: 16 # failed case: 1 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18483 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Failed case One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] RE: [Xen-devel] ANNOUNCE: Removing in-tree ioemu from xen-unstable.hg
Isaku Yamahata wrote: On Fri, Sep 12, 2008 at 11:18:12AM +0800, Zhang, Jingke wrote: Isaku Yamahata wrote: Hi. It would be very nice to arrange to send mails to the xen-changelog mailing list when commiting to qemu-xen-unstable.git. thanks, On Thu, Sep 11, 2008 at 04:54:51PM +0100, Keir Fraser wrote: With patches just submitted to allow stubdom to work with the new out-of-tree qemu-xen-unstable.git, I think the final obstacle to removing the in-tree ioemu has disappeared. I therefore plan to delete the internal ioemu tree early next week unless anyone has a strong reason to delay this action. Hi Isaku, Will it affect IPF once Keir deleted the internal ioemu tree early next week? Do you have any plan to drop IPF's internal ioemu soon? If so, I will modify our building scripts. Thank you very much! My plan is - Fix present remaining issues and merge xen-unstable to xen-ia64-unstable keeping the internal ioemu Soon. Around 12 Sep. or 16 Sep. - Merge the c/s which delete the ioemu to xen-ia64-unstable. Probably the late next week or the early next next week. thanks, Thanks Isaku! And I will modify corresponding scripts then. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
Isaku Yamahata wrote:
Could you try the following patch to ioemu?
NOTE:This is only a band aid patch. GFW needs modifcation.
ioemu: prevent qemu-dm segv.
With dade7f0bdc8d and old bios, qemu-dm results in segv.
Signed-off-by: Isaku Yamahata [EMAIL PROTECTED]
diff -r 9b5e1e05e886 tools/ioemu/hw/cirrus_vga.c
--- a/tools/ioemu/hw/cirrus_vga.c Mon Sep 01 17:50:13 2008 +0900
+++ b/tools/ioemu/hw/cirrus_vga.c Fri Sep 05 12:42:37 2008 +0900
@@ -2553,7 +2553,11 @@
end = begin + VGA_RAM_SIZE;
fprintf(logfile,mapping vram to %lx - %lx\n, begin, end);
-
+if (!s-vram_mfns) {
+fprintf(logfile, Found old firmware skiping mapping
vram\n); +return;
+}
+
xatp.domid = domid;
xatp.space = XENMAPSPACE_mfn;
Hi Isaku,
I checked my building environment. My source were built twice by make -j3
and CONFIG_QEMU=ioemu make -j3. But they both use local ioemu (ia64 is
different with x86?). What command did you use to enable ioemu-remote?
So, remote-ioemu may not affect VTI booting, I will double check that with
your patch. Thanks.
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
Zhang, Jingke wrote: Isaku Yamahata wrote: On Tue, Sep 02, 2008 at 11:22:27AM +0800, Zhang, Jingke wrote: Hi all, We found all the VTI guests can not be booted up with this Cset#18421 (XenU can boot). Last test on Cset#18369 is good to work. The failure is: when we boot up VTI, qemu will show a white box and disappeared after 1 second. I have checked both local ioemu and remote-ioemu, they both can not work. Did anyone find this by using latest Xen-ia64? Hmm, I'm afraid that c/s 18394:dade7f0bdc8d causes it. Could you confirm that? I suppose that even if the window of virtual frame buffer dissapears, VTi guest OS is still working and serial console can be accessed. If so, GFW should be patched to tell qemu-dm where the virtual frame buffer memory is. Hi Isaku, I checked the console of VTI, it does not work. CPU time always stays 0.2 (guest should hang). Anyway, I will try 18394 to narrow down this issue. Hi Isaku, It should be as you said. 18394 caused the issue. I tested 18394, issue exists. With 18393, VTI can be booted well. Thanks! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] heads up: ioemu-remote will be default soon.
Isaku Yamahata wrote: Hi. ioemu-remote is used as default device model on x86 and Keir is planning to delete ioemu from the tree soon so that xen/ia64 should switch from ioemu to ioemu-remote. Now that few patches were commited [1], ioemu-remote compiles for ia64 with the ia64 source tree and I sent out the patch to switch to ioemu-remote as default qemu-dm. Please make sure that your system to use ioemu-remote. Especially for those who are responsible for build/test system. Hi Isaku, As you said, currently we will still support local ioemu (by 'make CONFIG_QEMU=ioemu') and remote-ioemu on IA64. When ioemu is deleted from Xen. We will only support remote-ioemu. Am I right? Just confirm with your information, thanks! thanks, [1] related c/s xen-unstable: 18409:05c7efee10a1, 18408:48b33c4275f1, 18403:1721689cc834 ioemu-remote: 58cbd0ecff9e12e75b32fe21c51083ac9550e40d Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
Hi all, We found all the VTI guests can not be booted up with this Cset#18421 (XenU can boot). Last test on Cset#18369 is good to work. The failure is: when we boot up VTI, qemu will show a white box and disappeared after 1 second. I have checked both local ioemu and remote-ioemu, they both can not work. Did anyone find this by using latest Xen-ia64? Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] VTI will crash with memory=3073M
Hi Tristan, We found VTI guest with 3073M (memory is a little more than 3G) can not be booted up. After some investigation, our engineer found some pages are ruined by unknow reason. A EFI driver was loaded to 4G+, and its initilization code used the ruined pages, so bug out. I used latest openGFW binary (xenia64-gfw-126.bin). This issue is very easy to reproduce. Could you please help to look at it? Thank you very much! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] RE: VTI will crash with memory=3073M
Tristan Gingold wrote: On Tue, Sep 02, 2008 at 11:43:58AM +0800, Zhang, Jingke wrote: Hi Tristan, We found VTI guest with 3073M (memory is a little more than 3G) can not be booted up. After some investigation, our engineer found some pages are ruined by unknow reason. A EFI driver was loaded to 4G+, and its initilization code used the ruined pages, so bug out. I used latest openGFW binary (xenia64-gfw-126.bin). This issue is very easy to reproduce. Could you please help to look at it? Thank you very much! Hi, Can you explain what do you mean by 'ruined' ? Tristan. Hi Tristan, We found some code pages are polluted by an EFI driver (currently, we did not locate which driver), and leads to the issue. Thanks! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
Isaku Yamahata wrote: On Tue, Sep 02, 2008 at 11:22:27AM +0800, Zhang, Jingke wrote: Hi all, We found all the VTI guests can not be booted up with this Cset#18421 (XenU can boot). Last test on Cset#18369 is good to work. The failure is: when we boot up VTI, qemu will show a white box and disappeared after 1 second. I have checked both local ioemu and remote-ioemu, they both can not work. Did anyone find this by using latest Xen-ia64? Hmm, I'm afraid that c/s 18394:dade7f0bdc8d causes it. Could you confirm that? I suppose that even if the window of virtual frame buffer dissapears, VTi guest OS is still working and serial console can be accessed. If so, GFW should be patched to tell qemu-dm where the virtual frame buffer memory is. Hi Isaku, I checked the console of VTI, it does not work. CPU time always stays 0.2 (guest should hang). Anyway, I will try 18394 to narrow down this issue. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] RE: VTI will crash with memory=3073M
Akio Takebe wrote: Zhang, Jingke wrote: Tristan Gingold wrote: On Tue, Sep 02, 2008 at 11:43:58AM +0800, Zhang, Jingke wrote: Hi Tristan, We found VTI guest with 3073M (memory is a little more than 3G) can not be booted up. After some investigation, our engineer found some pages are ruined by unknow reason. A EFI driver was loaded to 4G+, and its initilization code used the ruined pages, so bug out. I used latest openGFW binary (xenia64-gfw-126.bin). This issue is very easy to reproduce. Could you please help to look at it? Thank you very much! Hi, Can you explain what do you mean by 'ruined' ? Tristan. Hi Tristan, We found some code pages are polluted by an EFI driver (currently, we did not locate which driver), and leads to the issue. Thanks! I guess the same problem. http://lists.xensource.com/archives/html/xen-ia64-devel/2008-07/msg00200.html Yes, it should be the issue. Have any idea to the root cause? Thank you very much! Best Regards, Akio Takebe Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] IPF/Xen-3.3.0-rc4 StatusReport --- no issue found
Hi all, We have done the ABAT test to Xen3.3.0-rc4 (staging#18314) on IA64. No issue was found for IPF. Thanks! Detail Xen/IA64 Unstable Cset #18314 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18314 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18286, dom0 CS#633 StatusReport --- some call trace in dom0
Hi all, All the test cases can pass with Cset#18286. When I check the 'dmesg', I found the unknown hypercalls was gone. But I met many call trace (39 times) printed out. My dom0 source is Cset#633. = ACPI: Device [CSFF] status [0008]: functional but not present; setting present ACPI: PCI Root Bridge [CSFF] (:ff) xen_mem: Initialising balloon driver. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub BUG: warning at /home/build/nightly/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:28/pci_bus_probe_wrapper() Call Trace: [a0010001db20] show_stack+0x40/0xa0 sp=e0007f5cfbe0 bsp=e0007f5c91b0 [a0010001dbb0] dump_stack+0x30/0x60 sp=e0007f5cfdb0 bsp=e0007f5c9198 [a001006b8a90] pci_bus_probe_wrapper+0x150/0x180 sp=e0007f5cfdb0 bsp=e0007f5c9170 [a001005ffea0] driver_probe_device+0x100/0x1e0 sp=e0007f5cfdc0 bsp=e0007f5c9138 [a001006001a0] __driver_attach+0xc0/0x160 sp=e0007f5cfdc0 bsp=e0007f5c9108 [a001005ff140] bus_for_each_dev+0x80/0x100 sp=e0007f5cfdc0 bsp=e0007f5c90d0 [a001005ffcc0] driver_attach+0x40/0x60 sp=e0007f5cfde0 bsp=e0007f5c90b0 [a001005fe8c0] bus_add_driver+0xe0/0x2c0 sp=e0007f5cfde0 bsp=e0007f5c9070 [a001006006f0] driver_register+0x170/0x1a0 sp=e0007f5cfde0 bsp=e0007f5c9050 [a0010050fda0] __pci_register_driver+0xa0/0x100 sp=e0007f5cfde0 bsp=e0007f5c9028 [a00100c81e20] pcistub_init+0x200/0x380 sp=e0007f5cfde0 bsp=e0007f5c8fd0 [a00100011900] init+0x320/0x840 sp=e0007f5cfe00 bsp=e0007f5c8f98 [a0010001bfd0] kernel_thread_helper+0x30/0x60 sp=e0007f5cfe30 bsp=e0007f5c8f70 [a001000110e0] start_kernel_thread+0x20/0x40 sp=e0007f5cfe30 bsp=e0007f5c8f70 BUG: warning at /home/build/nightly/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:28/pci_bus_probe_wrapper() .. Another 38 times of the call trace were omitted in the letter Detail Xen/IA64 Unstable Cset #18286 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18286 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18158 (dma heap logic) Status Report --- no issue
That is good, thanks! By the way, as Keir has suggested IPF-Xen does not need to support remote-qemu (or stubdom) in Xen3.3, will IPF plan to support them in Xen3.3 release? Thanks, Zhang Jingke -Original Message- From: Isaku Yamahata [mailto:[EMAIL PROTECTED] Sent: 2008年8月1日 19:14 To: Zhang, Jingke Cc: xen-ia64-devel@lists.xensource.com Subject: Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18158 (dma heap logic) Status Report --- no issue On Fri, Aug 01, 2008 at 06:31:14PM +0800, Zhang, Jingke wrote: For IPF has not enabled remote-qemu and stubdom yet, I built the source with old-qemu and disable stubdom. Xen-ia32 has checked in dma heap logic patch (18157:445681d122c0 and 18158:b25fa9df7375), so I did a regression test on the Cset#18158 (staging tree). No regression was found for IPF. Great. BTW, we found in some old Cset, Dom0 will print out some unknown hypercalls on my tiger4 platform (by 'dmesg' command). Also met this before? This issue was resolved by c/s 616:0deba952a6d3 in the ia64 linux tree which haven't been pulled up to the x86 tree yet. thanks, == .. xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 There are a lot of unknown hypercalls. == Detail Xen/IA64 Unstable Cset #18158 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18158 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel -- yamahata ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18158 (dma heap logic) Status Report --- no issue
Hi all, For IPF has not enabled remote-qemu and stubdom yet, I built the source with old-qemu and disable stubdom. Xen-ia32 has checked in dma heap logic patch (18157:445681d122c0 and 18158:b25fa9df7375), so I did a regression test on the Cset#18158 (staging tree). No regression was found for IPF. BTW, we found in some old Cset, Dom0 will print out some unknown hypercalls on my tiger4 platform (by 'dmesg' command). Also met this before? == .. xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 xencomm_hypercall_physdev_op: unknown physdev op 16 xencomm_hypercall_physdev_op: unknown physdev op 15 There are a lot of unknown hypercalls. == Detail Xen/IA64 Unstable Cset #18158 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18158 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] IPF-Xen3.3-RC1 testing is blocked by a compiling issue of remote-qemu
Isaku Yamahata wrote: On Thu, Jul 31, 2008 at 10:33:25AM +0800, Zhang, Jingke wrote: This error should be related to the remote-qemu building (we have disabled stub-domain compiling). If I use CONFIG_QEMU=ioemu make -j3 command to make, it can work. Does anyone also meet this issue? If so, we need to fix this for IPF in Xen3.3 release. Thanks! Hi, thank you for reporting. As long as I know, ioemu-remote and stub domain on ia64 haven't been addressed yet. And yes, I agree with you that those should be fixed. Are there any other issues on ia64 to be addressed for Xen 3.3 release? It would be desirable to exercise well dma heap logic (18157:445681d122c0 and 18158:b25fa9df7375), I'm not sure it's possible before the release. Hi Isaku, Thank you for your information on IPF stub-domain and remote-qemu. For the Xen3.3 release test on IPF, we plan to test remote-ioemu since it can work on x86 side (we do not have plan to enable stub-domain for testing currently). Besides those two, we did not find any old issue left specially for IPF in this 3.3 release, for IPF is stable by our nightly testing. :-) To the new dma heap logic changes, I will do a regression testing to see if IPF has new issues. Thanks! My top priority at this moment is the panic which Inakoshi-san reported recently that is the reason why I haven't requested Keir to pull the ia64 changes even after 3.3-rc1 had been released. thanks, Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] IPF-Xen3.3-RC1 testing is blocked by a compiling issue of remote-qemu
Hi all, I am trying to build Xen3.3.0-RC1 on IPF with remote-qemu, but met an error: make[4]: Entering directory `/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu-r emote/i386-dm' gcc -I. -I.. -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu- dir/target-i386 -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu- dir -MMD -MP -DNEED_CPU_H -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu- dir/tcg -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu- dir/tcg/ia64 -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu- dir/fpu -DHAS_AUDIO -DHAS_AUDIO -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/..//to ols/libxc -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/..//to ols/xenstore -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/..//to ols/include -I/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/..//to ols/blktap/lib -Wall -O2 -g -fno-strict-aliasing -O2 -fomit-frame-pointer -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wno-unused -Wno-declaration-after-statement -Wno-pointer-sign -DCONFIG_PASSTHROUGH -I../hw -mno-sdata -DUSE_SSE2=1 -msse2 -Wno-unused -Wno-declaration-after-statement -Wno-pointer-sign -DCONFIG_PASSTHROUGH -c -o vl.o /home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu-di r/vl.c cc1: error: unrecognized command line option -msse2 make[4]: *** [vl.o] Error 1 make[4]: Leaving directory `/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu-r emote/i386-dm' make[3]: *** [subdir-i386-dm] Error 2 make[3]: Leaving directory `/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools/ioemu-r emote' make[2]: *** [subdir-install-ioemu-dir] Error 2 make[2]: Leaving directory `/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools' make[1]: *** [subdirs-install] Error 2 make[1]: Leaving directory `/home/build/nightly/builds_xen_ia64_unstable/xen3.3.0-rc1/tools' make: *** [install-tools] Error 2 This error should be related to the remote-qemu building (we have disabled stub-domain compiling). If I use CONFIG_QEMU=ioemu make -j3 command to make, it can work. Does anyone also meet this issue? If so, we need to fix this for IPF in Xen3.3 release. Thanks! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18134 Status Report --- no issue
Samuel Thibault wrote: Zhang, Jingke, le Thu 24 Jul 2008 09:07:03 +0800, a écrit : As we know, Xen has some changes in the building process now. For x86 side can not play with stub-domain well, we did not compile the stub-domain in IPF. Oh? I'm interested in the build log then, because it's working with patchman... Samuel Hi Samuel, For currently we did not have enough resource to check if a bug related to stub-domain or VTI, so I just dropped stub-domain during my compiling (it does not mean stub-domain can not be compiled well). So we may check the stub-domain in IPF in the future. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#18134 Status Report --- no issue
Hi all, As we know, Xen has some changes in the building process now. For x86 side can not play with stub-domain well, we did not compile the stub-domain in IPF. We also used the old qemu (not .git) in our test. All the test case can pass with Cset#18134, no new issue. Detail Xen/IA64 Unstable Cset #18134 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 18134 xen schedule: credit gfw: open guest firmware Cset#126 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#17943 Status Report --- no newissue
Hi Tristan, There should be some mistake of my setting. With latest open-GFW#126, this bug can be fixed! Sorry for the misleading. Thanks, Zhang Jingke -Original Message- From: Tristan Gingold [mailto:[EMAIL PROTECTED] Sent: 2008年7月21日 9:36 To: Zhang, Jingke Cc: [EMAIL PROTECTED]; xen-ia64-devel@lists.xensource.com Subject: Re: [Xen-ia64-devel] Xen/IPF Unstable CS#17943 Status Report --- no newissue On Wed, Jul 09, 2008 at 08:39:38AM +0800, Zhang, Jingke wrote: Zhang, Jingke wrote: Hi all, All the cases passed in this Cset#17943. One old issue still exists, and it should be related to the open guest firmware (we reproduce it in latest Cset#126): [open-GFW] Linux VTI will crash when inputing a new description for the newly-added boot option. Hi Tristan, We met the Linux VTI crash when Input the description to newly added boot option with the latest open GFW xenia64-gfw-126.bin. We noticed that your patch for open-GFW Cset#114 (http://xenbits.xensource.com/ext/efi-vfirmware.hg?rev/42899f0d94c3) may fix the similar error, did you meet the same thing with us? Thanks! Hi, thank you for finding this error. Can you describe how to reproduce it ? That's would be useful to me! Tristan. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] [Question] Which feature of Xen-IPF will reserve much memory of a VTI guest?
Isaku Yamahata wrote: Hi Jingke. Although I haven't digged into it and I'm not sure, I suppose that Linux/ia64 may round up/down usable memory when parsing efi memory map. Presumably looking into /proc/iomem may help to track down the issue. thanks, I will see into that file. Greatly appreciate your help! :) On Wed, Jul 09, 2008 at 01:36:19PM +0800, Zhang, Jingke wrote: Hi all, When we check the /proc/meminfo in the VTI, we found the total memory is about 100MB less than what we config. For x86_64 and KVM side, they are different. So, I want to ask a question: Is there any feature reserving much memory of VTI? Thank you very much! BTW, by command dmesg | grep reserve: For RHEL4u4 VTI -- Memory: 942976k/1018784k available (5714k code, 87712k reserved, 2279k data, 384k init) For RHEL4u4 x86_64 VMX -- Memory: 1024844k/1048544k available (2105k kernel code, 0k reserved, 1297k data, 196k init) For RHEL4u4 x86_64 KVM -- Memory: 1024772k/1048512k available (2105k kernel code, 0k reserved, 1297k data, 196k init) Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [Question] Which feature of Xen-IPF will reserve much memory of a VTI guest?
Hi all, When we check the /proc/meminfo in the VTI, we found the total memory is about 100MB less than what we config. For x86_64 and KVM side, they are different. So, I want to ask a question: Is there any feature reserving much memory of VTI? Thank you very much! BTW, by command dmesg | grep reserve: For RHEL4u4 VTI -- Memory: 942976k/1018784k available (5714k code, 87712k reserved, 2279k data, 384k init) For RHEL4u4 x86_64 VMX -- Memory: 1024844k/1048544k available (2105k kernel code, 0k reserved, 1297k data, 196k init) For RHEL4u4 x86_64 KVM -- Memory: 1024772k/1048512k available (2105k kernel code, 0k reserved, 1297k data, 196k init) Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17940 Status Report --- no new issue
Hi all, All the cases passed in this Cset#17940. One old issue still exists: [NVRAM] RHEL5_VTI guest crashed when being inputed a new description for the new-added boot option. Detail Xen/IA64 Unstable Cset #17940 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 17940 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17892 Status Report --- no new issue (irqbalance service stopped)
Hi all, In the past, we used GCC3.x biulding system and native is RHEL4u3. From now on, we updated the building and nightly test system to GCC4.1.2. The native Linux of nightly testing machine is RHEL5u2 (with default installed RPMs, skipping virtualization component). We met a little issue, which is irqbalance service can not start in dom0, many call trace will output. Then I returned Native and closed that by 'setup' command. Dom0 works. In this Cset#17892, all the cases passed! No new issue. One old issue still exists: [NVRAM] RHEL5_VTI guest crashed when being inputed a new description for the new-added boot option. Detail Xen/IA64 Unstable Cset #17892 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.68 service os: RHEL5u2 IA64 SMP with 2 VCPUs vti guest os: RHEL5u2 RHEL4u3 xenU guest os: RHEL4u4 xen ia64 unstable tree: 17892 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_Live-migration Linux VTI live-migration Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] RE: Dom0 (built by GCC4.1.2) can not be booted up
Isaku Yamahata wrote: Hi Zhang. Just as unreliable suggestions. Do you enablied CONFIG_PCI_MSI=y for the kernel? My config disables it. I guess that the Makefiles that generates .config for Liux was changed so that xen/ia64 has to catch it up. Probably xen-unstable.hg/buildconfigs/enable-xen-config has to be updated, but I haven't digged into it. thanks, Thank you for your suggestion! I checked with the config. The CONFIG_PCI_MSI in my config file is not set. We have tried out a work-around method, disable irqbalance service when system boots. Then dom0 can boot. But the same issue did not happen on ia32 part. So, I am afraid there may be some issue here. Thanks! On Sun, Jun 22, 2008 at 11:50:11AM +0800, Zhang, Jingke wrote: Hi Isaku, Recently, we tried to make and make install Xen-17892 on RHEL5u2 native (not installed the virtualization rhel5u2-ia64). Its GCC is 4.1.2version. Although the building can finish successfully, dom0 can not be booted up. The booting course is smooth to kuduz, network..., but failed at HAL deamon. At that place, system reported some info: linux-2.6.18-xen.hg/kernel/irq/migration.c:27/move_native_irp() call trace.. (output many call trace info continously) This issue broke our nightly test now. I tried to use some old version of Xen, such as 17772. It still had the same error. So did you ever meet the same thing by using GCC 4.1.2 as your building env? Thanks very much! Thanks, Zhang Jingke Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Dom0 (built by GCC4.1.2) can not be booted up
Hi Isaku, Recently, we tried to make and make install Xen-17892 on RHEL5u2 native (not installed the virtualization rhel5u2-ia64). Its GCC is 4.1.2version. Although the building can finish successfully, dom0 can not be booted up. The booting course is smooth to kuduz, network..., but failed at HAL deamon. At that place, system reported some info: linux-2.6.18-xen.hg/kernel/irq/migration.c:27/move_native_irp() call trace.. (output many call trace info continously) This issue broke our nightly test now. I tried to use some old version of Xen, such as 17772. It still had the same error. So did you ever meet the same thing by using GCC 4.1.2 as your building env? Thanks very much! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17772 Status Report --- no new issue
Hi all, All the case can pass, no new issue is in this Cset. Thanks! Detail Xen/IA64 Unstable Cset #17772 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17772 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17769 Status Report --- one manual test issue
Hi all, All the cases passed in this Cset. But, one issue was found by manual test (should be already there). Thanks! Summary: [NVRAM] RHEL5_VTI guest crashed when being inputed a new description for the new-added boot option. My reproducing steps: 1. Use latest open-gfw binary (Cset#126) to boot up a RHEL5_VTI on Cset#17769. 2. At the beginning of booting, choose Boot Maintenance Manager and add one boot option from efi/redhat/elilo.conf. 3. then try to input the decription. After 2 seconds, VTI guest crashed. Detail Xen/IA64 Unstable Cset #17769 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17769 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17766 Status Report --- no new issue
Hi all, All the cases passed in this Cset. Detail Xen/IA64 Unstable Cset #17766 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17766 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17700 Status Report --- no new issue
Hi all, All the cases passed in this Cset. Detail Xen/IA64 Unstable Cset #17700 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17700 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case Summary Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen bug#1253 has been fixed on IA32
Hi Isaku, Latest IPF Cset has the xen bug#1253, which has been fixed by xen-unstable Cset#17682 (http://xenbits.xensource.com/xen-unstable.hg?rev/4b4b829e34a2). Could you please merge it in the next Cset? Thank you! Bug#1253: summary is The saved domain with qcow image cannot be restored. Link is http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1253. Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17699 Status Report --- no new issue
Hi all, All the cases passed in this Cset. Detail Xen/IA64 Unstable Cset #17699 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17699 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#17671 Status Report --- one issue fixed, one issue still existed
Isaku Yamahata wrote: Hi Zhang. Could you try the attached patch? This patch is for temporal work around. Is it important to implement SAL_MC_SET_PARAMS and SAL_SET_VECTORS? If so, they have to be implemented in both gfw and xen vmm. thanks, Hi Isaku, I use your patch on latest 17677. Both sp1 and sp2 of VTI_Win2003server can be booted up successfully. Thanks! BTW, there is a little typo in your patch: (should drop the /* and */, or it will not success to compile) +* status = -1; not implemented On Mon, May 19, 2008 at 09:36:40AM +0800, Zhang, Jingke wrote: Hi all, With Cset#17671, qcow creating issue was fixed! It can use qcow file to create a VTI with disk = [ 'tap:qcow:/***,hda,w' ] config file. One old issue still existed: == Windows guest still can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003, both SP1 and SP2 guest will crash at starting windows... Detail Xen/IA64 Unstable Cset #17671 Status Report Test Result Summary: # total case: 18 # passed case: 15 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17671 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build (all the cases containing windows VTI) Failed case id Description SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17677 Status Report
Hi all, No new issue was found in this nightly test. Old issue (1): == Windows guest can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003, both SP1 and SP2 guest will crash at starting windows... Detail Xen/IA64 Unstable Cset #17677 Status Report Test Result Summary: # total case: 17 # passed case: 15 # failed case: 2 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17677 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build (all the cases containing windows VTI) Failed case id Description SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17678 Status Report --- Fixed win2k3 crashing issue!
Hi all, All the cases passed in this Cset. Both Win2k3 and Win2k8 (2008 used old nvram file) can be booted successfully! Care should be given to latest guest firmware, that I failed to use it to make nvram for window2008. Except this, no special issue for IA64. Thanks! Detail Xen/IA64 Unstable Cset #17678 Status Report Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17678 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU --- Failed case id Description Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17671 Status Report --- one issue fixed, one issue still existed
Hi all, With Cset#17671, qcow creating issue was fixed! It can use qcow file to create a VTI with disk = [ 'tap:qcow:/***,hda,w' ] config file. One old issue still existed: == Windows guest still can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003, both SP1 and SP2 guest will crash at starting windows... Detail Xen/IA64 Unstable Cset #17671 Status Report Test Result Summary: # total case: 18 # passed case: 15 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17671 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build (all the cases containing windows VTI) Failed case id Description SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#17661 Status Report --- Twonew issues found
Xu, Anthony wrote: it would also report failure in the qemu screen. --- VTI_Windows2003 guest will crash at starting windows.. Windows2003 Server SP1 has a bug , which cause guest crash. We need to move to Windows 2003 Server SP2. - Anthony Isaku Yamahata wrote: On Fri, May 16, 2008 at 10:53:09AM +0800, Zhang, Jingke wrote: Issue2. Windows guest can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003 guest will crash at starting windows.. C/s 17606:b03e24f9c1d8 is the culprit. SAL_SET_VECTORS 0, SAL_SET_VECTORS 1 and SAL_MC_SET_PARAMS are called. Hmm, not only VMM, but also gfw needs fix? thanks, I retest Windows2k3 VTI against Cset17607. My win2k3 is SP1 version and I am trying to update it. Thank you Anthony! The results of three Csets is: With win2k3-SP1 Crash? 17602 No 17607 Yes 17661 Yes So, the issue exists between 17603~17607 as Isaku told (17606). Thanks! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#17661 Status Report --- Twonew issues found
Zhang, Jingke wrote: Hi all, The old VTI Save-Restore issue was fixed now. Then VTI saverestore, live-migration can pass! Two new block isses were found: Issue1. Qcow image made by qcow-create of this Cset failed to be recognazied. --- On IA32 part, we still met an issue about qcow, which can be worked around by using disk = [ 'tap:qcow:/***,hda,w' ] in configuration file. But, I failed to boot up VTI qcow file in this way. Hi Isaku, To the issue1, IA32 part's fix was on Cset#17646, which has not been merged to IA64 side. This issue may block our nightly testing work. Could you please have a look at this patch (link is http://xenbits.xensource.com/xen-unstable.hg?rev/e3b13e1ecf6c)? Issue2. Windows guest can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003 guest will crash at starting windows.. Detail Xen/IA64 Unstable Cset #17661 Status Report Test Result Summary: # total case: 18 # passed case: 15 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17661 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case idDescription SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build (all the cases containing windows VTI) Failed case idDescription SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17661 Status Report --- Two new issues found
Hi all, The old VTI Save-Restore issue was fixed now. Then VTI saverestore, live-migration can pass! Two new block isses were found: Issue1. Qcow image made by qcow-create of this Cset failed to be recognazied. --- On IA32 part, we still met an issue about qcow, which can be worked around by using disk = [ 'tap:qcow:/***,hda,w' ] in configuration file. But, I failed to boot up VTI qcow file in this way. Issue2. Windows guest can not be booted up. --- VTI_Windows2008 can not be booted. When we ran bootmgfw.efi, it would also report failure in the qemu screen. --- VTI_Windows2003 guest will crash at starting windows.. Detail Xen/IA64 Unstable Cset #17661 Status Report Test Result Summary: # total case: 18 # passed case: 15 # failed case: 3 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17661 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build (all the cases containing windows VTI) Failed case id Description SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17602 Status Report --- 1 new issue: VTI restore failed
Hi all, This is today's Xen/IPF nightly test report against Cset#17602. One new issue was found in VTI restore. That is to say VTI guest can be saved successfully, but it will fail to be restored. By /var/log/xen/xend-debug.log, we can see: == Enabling Linux guest OS optimizations Nvram save successful! ERROR Internal error: Nvram not initialized. Nvram save failed! (2 = No such file or directory) == Is this related to Cset#17600: [IA64] fix restoring HVM domain with PV driver? Thank you very much! Xen/IA64 Unstable Cset #17602 Status Report Test Result Summary: # total case: 18 # passed case: 17 # failed case: 1 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17602 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Failed case id Description SaveRestoreSaveRestore Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#17602 Status Report --- 1 newissue: VTI restore failed
Kouya Shimura wrote: Is this related to Cset#17600: [IA64] fix restoring HVM domain with PV driver? Thank you very much! No, probably due to the cset 17531:18727843db60. changeset: 17531:18727843db60 user:Keir Fraser [EMAIL PROTECTED] date:Fri Apr 25 13:44:45 2008 +0100 summary: x86, hvm: Guest CPUID configuration. There is no xc_cpuid_apply_policy() function for ia64 yet. From xend.log: [2008-05-14 17:27:04 4600] ERROR (XendDomain:1144) Restore failed Traceback (most recent call last): File //usr/lib/python/xen/xend/XendDomain.py, line 1136, in domain_restore_\ fd return XendCheckpoint.restore(self, fd, paused=paused, relocating=relocatin\ g) File //usr/lib/python/xen/xend/XendCheckpoint.py, line 312, in restore restore_image.setCpuid() File //usr/lib/python/xen/xend/image.py, line 557, in setCpuid xc.domain_set_policy_cpuid(self.vm.getDomid()) AttributeError: domain_set_policy_cpuid Thanks, Kouya Yes, my xend.log reported the same with you. Thank you very much! Zhang, Jingke writes: Hi all, This is today's Xen/IPF nightly test report against Cset#17602. One new issue was found in VTI restore. That is to say VTI guest can be saved successfully, but it will fail to be restored. By /var/log/xen/xend-debug.log, we can see: == Enabling Linux guest OS optimizations Nvram save successful! ERROR Internal error: Nvram not initialized. Nvram save failed! (2 = No such file or directory) == Is this related to Cset#17600: [IA64] fix restoring HVM domain with PV driver? Thank you very much! Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IPF Unstable CS#17525 Status Report
Xen/IA64 Unstable Cset #17525 Status Report Test Result Summary: # total case: 18 # passed case: 18 # failed case: 0 Testing Environment: platform: Tiger4 processor: Itanium 2 Processor logic Processors number: 8 (2 processors with Dual Core) pal version: 9.08 service os: RHEL4u3 IA64 SMP with 2 VCPUs vti guest os: RHEL4u2 RHEL4u3 xenU guest os: RHEL4u2 xen ia64 unstable tree: 17525 xen schedule: credit gfw: open guest firmware Cset#122 Detailed Test Results: Passed case id Description SaveRestoreSaveRestore VTI_PV Linux VTI PV Two_UP_VTI_Co2 UP_VTI (mem=256) One_UP_VTI 1 UP_VTI (mem=256) One_UP_XenU 1 UP_xenU(mem=256) SMPVTI_LTP VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M) SMPVTI_Network 1 VTI (mem=256,vcpu=2) and'ping' SMPXenU_Network 1 XenU (vcpus=2) and 'ping' One_SMP_XenU1 SMP xenU (vcpus=2) One_SMP_VTI 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild UPVTI_Kernel_Build 1 UP VTI and do kernel build SMPVTI_Windows SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU VTI_Windows_PV Windows VTI PV Failed case id Description N/A Thanks, Zhang Jingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#16212
Xen/IA64 Healthiness Report All the cases passed in this changeset. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 16212 Xen Schedule: credit VTI Guest Firmware Open guest firmware --- version 19 Summary Test Report: - Total cases: 18 Passed: 18 Failed: 0 Case Name Status Case Description Pv pass Win_PV pass Four_SMPVTI_Coexist pass 4 VTI (mem=256, vcpus=2) Xen/IA64 Healthiness Report -Cset#15165 Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTI pass 1 UP_VTI (mem=256) One_UP_XenU pass 1 UP_xenU(mem=256) SMPVTI_LTP pass VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist pass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Network pass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTI pass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 16201 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#16177
Xen/IA64 Healthiness Report Only Win pv failed in this changeset, network still does not work in the Windows vti with pv driver. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 16177 Xen Schedule: credit VTI Guest Firmware Open guest firmware --- version 19 Summary Test Report: - Total cases: 18 Passed: 17 Failed: 1 Case Name Status Case Description Pv pass Win_PV fail Four_SMPVTI_Coexist pass 4 VTI (mem=256, vcpus=2) Xen/IA64 Healthiness Report -Cset#15165 Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTI pass 1 UP_VTI (mem=256) One_UP_XenU pass 1 UP_xenU(mem=256) SMPVTI_LTP pass VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist pass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Network pass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTI pass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 16120 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#16120
Xen/IA64 Healthiness Report Only Win pv failed in this changeset, network still does not work in the Windows vti with pv driver. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 16120 Xen Schedule: credit VTI Guest Firmware Open guest firmware --- version 19 Summary Test Report: - Total cases: 18 Passed: 17 Failed: 1 Case Name Status Case Description Pv pass Win_PV fail Four_SMPVTI_Coexist pass 4 VTI (mem=256, vcpus=2) Xen/IA64 Healthiness Report -Cset#15165 Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTI pass 1 UP_VTI (mem=256) One_UP_XenU pass 1 UP_xenU(mem=256) SMPVTI_LTP pass VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist pass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Network pass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTI pass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 16116 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#16116
Xen/IA64 Healthiness Report Only Win pv failed in this changeset, network still does not work in the Windows vti with pv driver. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 16116 Xen Schedule: credit VTI Guest Firmware Open guest firmware --- version 19 Summary Test Report: - Total cases: 18 Passed: 17 Failed: 1 Case Name Status Case Description Pv pass Win_PV fail Four_SMPVTI_Coexist pass 4 VTI (mem=256, vcpus=2) Xen/IA64 Healthiness Report -Cset#15165 Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTI pass 1 UP_VTI (mem=256) One_UP_XenU pass 1 UP_xenU(mem=256) SMPVTI_LTP pass VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist pass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Network pass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTI pass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 16113 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#16113
Xen/IA64 Healthiness Report Only Win pv failed in this changeset, network still does not work in the Windows vti with pv driver. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 16113 Xen Schedule: credit VTI Guest Firmware Open guest firmware --- version 19 Summary Test Report: - Total cases: 18 Passed: 17 Failed: 1 Case Name Status Case Description Pv pass Win_PV fail Four_SMPVTI_Coexist pass 4 VTI (mem=256, vcpus=2) Xen/IA64 Healthiness Report -Cset#15165 Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTI pass 1 UP_VTI (mem=256) One_UP_XenU pass 1 UP_xenU(mem=256) SMPVTI_LTP pass VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist pass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Network pass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTI pass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 16099 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#15892
Xen/IA64 Healthiness Report Only Win pv failed in this changeset, network still does not work in the Windows vti with pv driver. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Dual Core) PAL version: 9.08 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 15892 Xen Schedule: credit VTI Guest Firmware Open guest firmware - Cset #19 Summary Test Report: - Total cases: 18 Passed:17 Failed: 1 Case Name Status Case Description Pv pass Win_PV fail Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: 15724 - Thank you, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#14419
Xen/IA64 Healthiness Report All the cases in the test passed. No new issues in this Cset. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 14419:1584263f9fc5 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 14366:a862200c572a Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#14074
Xen/IA64 Healthiness Report Only one issue: 1. SMP_VTI domain will meet kernel panic after rebooting itself for some times. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 14074:b3e19f3092b6 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 14068:707a696e840d Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13957
Xen/IA64 Healthiness Report All the cases passed in the test. There are no issues in the recent Csets. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13957:9529d667d042 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13907:ac18d251df63 Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13904
Xen/IA64 Healthiness Report All the cases could pass in the test. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13904:6c63ff54 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13867:fbc233a1dc53 Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13837
Xen/IA64 Healthiness Report All testing cases pass. The qume's problem in Cset#13773 has been solved. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 vcpus 1G memory VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13837:fbc128aafdeb Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13837:fbc128aafdeb Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13773
Xen/IA64 Healthiness Report One issues: 1. Qemu can not be opened when creating a VTI domain. But the VTI can be created successfully without qemu. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13773:ef646312685f Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13441:7e9077dd4010 Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13438
Xen/IA64 Healthiness Report All the cases passed in the test. So, only one issue: 1. With serial='pty', UP_VTI booting speed is a little slower. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13438:43115ffc6635 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13372:c6b683ba68f5 Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] With Cset#13360, dom0-booting crashed.
Hi all, Cset#13360 met a dom0 crash. So tests can not be made. The serial port log is in the attachment. Thanks, Zhangjingke (XEN) Your elilo is not Xen-aware. Bootparams fixed (XEN) Xen command line: BOOT_IMAGE=scsi0:\EFI\redhat\xen.gz com2=57600,8n1 cons ole=com2 sched=credit dom0_mem=1024M dom0_max_vcpus=2 (XEN) xen image pstart: 0x400, xenheap pend: 0x800 (XEN) Xen patching physical address access by offset: 0x0 (XEN) find_memory: efi_memmap_walk returns max_page=bffed (XEN) Before xen_heap_start: f419fe00 (XEN) After xen_heap_start: f41bc000 (XEN) Init boot pages: 0x1d8 - 0x400. (XEN) Init boot pages: 0x800 - 0x7f708000. (XEN) Init boot pages: 0x7fe58000 - 0x7fefc000. (XEN) Init boot pages: 0x1 - 0x17fffc000. (XEN) Init boot pages: 0x28000 - 0x2fee00010. (XEN) Init boot pages: 0x2fee00070 - 0x2fee03f56. (XEN) Init boot pages: 0x2fee03fc5 - 0x2fee07000. (XEN) Init boot pages: 0x2fef4584d - 0x2fef4e010. (XEN) Init boot pages: 0x2fef4e9a0 - 0x2ffe14000. (XEN) Init boot pages: 0x2ffe8 - 0x2fffb4000. (XEN) System RAM: 6118MB (6265792kB) (XEN) size of virtual frame_table: 15360kB (XEN) virtual machine to physical table: f3a00098 size: 3120kB (XEN) max_page: 0xbffed (XEN) allocating frame table/mpt table at mfn 0. (XEN) Domain heap initialised: DMA width 30 bits (XEN) Xen heap: 62MB (63760kB) (XEN) ACPI: RSDP (v002 INTEL ) @ 0x7ff50 000 (XEN) ACPI: XSDT (v001 INTEL SR870BN4 0x01072002 MSFT 0x00010013) @ 0x7 ff50090 (XEN) ACPI: FADT (v003 INTEL SR870BN4 0x01072002 MSFT 0x00010013) @ 0x7 ff50138 (XEN) ACPI: MADT (v001 INTEL SR870BN4 0x01072002 MSFT 0x00010013) @ 0x7 ff50230 (XEN) ACPI: DSDT (v001 Intel SR870BN4 0x INTL 0x20030918) @ 0x0 000 (XEN) SAL 3.20: Intel Corp SR870BN4 version 3.0 (XEN) SAL Platform features: BusLock (XEN) SAL: AP wakeup using external interrupt vector 0xf0 (XEN) cpu package is Multi-Core capable: number of cores=2 (XEN) cpu package is Multi-Threading capable: number of siblings=2 (XEN) avail:0x31700740, status:0x740,control:0x3170, vm?0x100 (XEN) WARNING: no opcode provided from hardware(0)!!! (XEN) vm buffer size: 1048576, order: 6 (XEN) cpu_init: current=f4108000 (XEN) vm_buffer: 0xf7e0 (XEN) vhpt_init: vhpt paddr=0x7fee, end=0x7fee (XEN) iosapic_system_init: Disabling PC-AT compatible 8259 interrupts (XEN) ACPI: Local APIC address e800fee0 (XEN) ACPI: LSAPIC (acpi_id[0x00] lsapic_id[0xc0] lsapic_eid[0x18] enabled) (XEN) CPU 0 (0xc018) enabled (BSP) (XEN) ACPI: LSAPIC (acpi_id[0x01] lsapic_id[0xc2] lsapic_eid[0x18] disabled) (XEN) CPU 1 (0xc218) disabled (XEN) ACPI: LSAPIC (acpi_id[0x02] lsapic_id[0xc4] lsapic_eid[0x18] enabled) (XEN) CPU 2 (0xc418) enabled (XEN) ACPI: LSAPIC (acpi_id[0x03] lsapic_id[0xc6] lsapic_eid[0x18] disabled) (XEN) CPU 3 (0xc618) disabled (XEN) ACPI: LSAPIC (acpi_id[0x04] lsapic_id[0xc1] lsapic_eid[0x18] enabled) (XEN) CPU 4 (0xc118) enabled (XEN) ACPI: LSAPIC (acpi_id[0x05] lsapic_id[0xc3] lsapic_eid[0x18] disabled) (XEN) CPU 5 (0xc318) disabled (XEN) ACPI: LSAPIC (acpi_id[0x06] lsapic_id[0xc5] lsapic_eid[0x18] enabled) (XEN) CPU 6 (0xc518) enabled (XEN) ACPI: LSAPIC (acpi_id[0x07] lsapic_id[0xc7] lsapic_eid[0x18] disabled) (XEN) CPU 7 (0xc718) disabled (XEN) ACPI: LSAPIC (acpi_id[0x08] lsapic_id[0xc0] lsapic_eid[0x98] enabled) (XEN) CPU 8 (0xc098) enabled (XEN) ACPI: LSAPIC (acpi_id[0x09] lsapic_id[0xc2] lsapic_eid[0x98] disabled) (XEN) CPU 9 (0xc298) disabled (XEN) ACPI: LSAPIC (acpi_id[0x0a] lsapic_id[0xc4] lsapic_eid[0x98] enabled) (XEN) CPU 10 (0xc498) enabled (XEN) ACPI: LSAPIC (acpi_id[0x0b] lsapic_id[0xc6] lsapic_eid[0x98] disabled) (XEN) CPU 11 (0xc698) disabled (XEN) ACPI: LSAPIC (acpi_id[0x0c] lsapic_id[0xc1] lsapic_eid[0x98] enabled) (XEN) CPU 12 (0xc198) enabled (XEN) ACPI: LSAPIC (acpi_id[0x0d] lsapic_id[0xc3] lsapic_eid[0x98] disabled) (XEN) CPU 13 (0xc398) disabled (XEN) ACPI: LSAPIC (acpi_id[0x0e] lsapic_id[0xc5] lsapic_eid[0x98] enabled) (XEN) CPU 14 (0xc598) enabled (XEN) ACPI: LSAPIC (acpi_id[0x0f] lsapic_id[0xc7] lsapic_eid[0x98] disabled) (XEN) CPU 15 (0xc798) disabled (XEN) ACPI: IOSAPIC (id[0x0] address[fec0] gsi_base[0]) (XEN) ACPI: IOSAPIC (id[0x1] address[fec1] gsi_base[24]) (XEN) ACPI: IOSAPIC (id[0x2] address[fec2] gsi_base[48]) (XEN) ACPI: IOSAPIC (id[0x3] address[fec3] gsi_base[72]) (XEN) ACPI: IOSAPIC (id[0x4] address[fec4] gsi_base[96]) (XEN) ACPI: IOSAPIC (id[0x5] address[fec5] gsi_base[120]) (XEN) ACPI: IOSAPIC (id[0x6] address[fec6] gsi_base[144]) (XEN) ACPI: PLAT_INT_SRC (low level type[0x3] id[0x00c0] eid[0x18] iosapic_vecto r[0x1e] global_irq[0x16] (XEN) PLATFORM int CPEI (0x3): GSI 22 (level, low) - CPU 0 (0xc018) vector 30 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
RE: [Xen-ia64-devel] With Cset#13360, dom0-booting crashed.
Hi all, We found some dir settings changed in the building folder. The image file vmlinuz.gz was in a new dir named build-linux-2.6.16.33-xen_ia64. (Not in the linux-2.6.16.33-xen). So, system could not find the image of dom0 while it booted. Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zhang, Jingke Sent: Thursday, January 11, 2007 9:17 AM To: xen-ia64-devel@lists.xensource.com Subject: [Xen-ia64-devel] With Cset#13360, dom0-booting crashed. Hi all, Cset#13360 met a dom0 crash. So tests can not be made. The serial port log is in the attachment. Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13360
Xen/IA64 Healthiness Report Totally one old issue: 1. With serial='pty', UP_VTI booting speed is a little slower. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13360:91be8436952d Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 13124:42babba5 Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] crash while initializing balloon driver
Hi Alex, With the new Cset#13122, I met the xen0's crash even dom0_mem=512M. My elilo.conf and the serial port information are in the attachments. Thank you. Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Williamson Sent: Friday, January 05, 2007 8:41 AM To: xen-ia64-devel Subject: [Xen-ia64-devel] crash while initializing balloon driver FYI, if you experience a crash like the one shown below, this is due to changes in the domain builder now allowing dom0 memory to be sparsely populated. Isaku has already sent a patch for this to xen-devel and we'll pull it into the xen-ia64-devel branch once its accepted. In the meantime, set your dom0_mem= boot option to a smaller value (1G will probably work on most systems). Thanks, Alex xen_mem: Initialising balloon driver. Bad page state in process 'swapper' page:e0010ecee848 flags:0x8080 mapping: mapcount:0 count:1 Trying to fix it up, but a reboot is needed Backtrace: Call Trace: [a0010001cf40] show_stack+0x40/0xa0 spà011af27c40 bspà011af212a0 [a0010001cfd0] dump_stack+0x30/0x60 spà011af27e10 bspà011af21288 [a001000e5400] bad_page+0xa0/0x120 spà011af27e10 bspà011af21268 Unable to handle kernel paging request at virtual address 00200200 swapper[1]: Oops 11003706212352 [1] Modules linked in: Pid: 1, CPU 0, comm: swapper psr : 0210085a2010 ifs : 8815 ip : [a001000e7b61] Not tainted ip is at get_page_from_freelist+0x3c1/0xae0 unat: pfs : 8815 rsc : 000b rnat: bsps: pr : 6681 ldrs: ccv : fpsr: 0009804c8a70433f csd : ssd : b0 : a001000e78b0 b6 : a0010004b680 b7 : a00100014750 f6 : 1003e8348d37270c2ca06 f7 : 1003e9e3779b97f4a7c16 f8 : 1003e0a001000e7e9 f9 : 100038000 f10 : 0fffaf000 f11 : 1003e r1 : a0010103eb60 r2 : r3 : r8 : 0001 r9 : a00100df7210 r10 : 0002 r11 : e0010ecee878 r12 : e0011af274b0 r13 : e0011af2 r14 : 0001 r15 : fff1 r16 : 0001 r17 : 00200200 r18 : 00100108 r19 : 00200200 r20 : e0010ecee870 r21 : 00100100 r22 : 00100100 r23 : a00100df7290 r24 : e0011af20f14 r25 : a00100e654a8 r26 : a00100e654a8 r27 : 0080 r28 : r29 : r30 : r31 : Call Trace: [a0010001cf40] show_stack+0x40/0xa0 spà011af27040 bspà011af216e8 -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel elilo.conf Description: elilo.conf 00400) (63MB) (XEN) dom mem: type= 7, attr=0x0008, range=[0x0400-0x000 0081a) (65MB) (XEN) dom mem: type= 7, attr=0x0008, range=[0x081a-0x000 00ff8) (125MB) (XEN) dom mem: type= 7, attr=0x0008, range=[0x0ff8-0x000 01000) (512KB) (XEN) dom mem: type= 7, attr=0x0008, range=[0x1000-0x000 01edb1000) (237MB) (XEN) dom mem: type= 5, attr=0x8009, range=[0x7f70a000-0x000 07fb0) (3MB) (XEN) dom mem: type= 5, attr=0x8009, range=[0x7fe0-0x000 07fe58000) (352KB) (XEN) dom mem: type= 6, attr=0x8009, range=[0x7fefe000-0x000 08000) (1MB) (XEN) dom mem: type=11, attr=0x0001, range=[0xfe00-0x000 0ff00) (16MB) (XEN) dom mem: type= 6, attr=0x8001, range=[0xff00-0x000 1) (16MB) (XEN) dom mem: type= 6, attr=0x8009, range=[0x00017fffe000-0x000 18000) (8KB) (XEN) dom mem: type= 5, attr=0x8009, range=[0x0002ffe14000-0x000 2ffe8) (432KB) (XEN) dom mem: type= 6, attr=0x8009, range=[0x0002fffb6000-0x000 3) (296KB) (XEN) dom mem: type=11, attr=0x8001, range=[0x0800-0x000 00c00) (64MB) (XEN) dom mem: type=12, attr=0x8001, range=[0x0c00-0x000 01000) (64MB) (XEN) Scrubbing Free RAM: .. ..done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *** Serial input - DOM0 (type 'CTRL-a' three times to switch input to Xen ). (XEN) vcpu_get_lrr0:
RE: [Xen-ia64-devel] crash while initializing balloon driver
Okay Alex, I will try 13117 as you said. Thanks! Thanks, Zhangjingke -Original Message- From: Alex Williamson [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 12:22 PM To: Zhang, Jingke Cc: xen-ia64-devel Subject: RE: [Xen-ia64-devel] crash while initializing balloon driver On Thu, 2007-01-04 at 21:02 -0700, Alex Williamson wrote: On Fri, 2007-01-05 at 11:31 +0800, Zhang, Jingke wrote: Hi Alex, With the new Cset#13122, I met the xen0's crash even dom0_memQ2M. My elilo.conf and the serial port information are in the attachments. Thank you. Can you verify that it works with Isaku's patch here: http://lists.xensource.com/archives/html/xen-devel/2007-01/msg00102.html It works on HP systems as long as I don't specify a dom0_mem= that leaves gaps in the memory map, I was hoping it would be true in the interim for other systems as well. Thanks, Actually, looking more closely at your attached log, this cset may be the culprit: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs-4807ed1056 Does reverting this cset allow you to boot (hg export 13117 | patch -p1 -R)? The balloon driver crash occurs much later in dom0 bootup. Looks like we should probably only set the noncache flag if the WB attribute is not present since a range can have both WB and UC set. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] crash while initializing balloon driver
Hi Alex, As you said, I use hg export 13117 | patch -p1 -R in the Cset#13122. Without 13117's patch, dom0 can boot up (Mem=1024M). Thanks, Zhangjingke -Original Message- From: Alex Williamson [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 12:22 PM To: Zhang, Jingke Cc: xen-ia64-devel Subject: RE: [Xen-ia64-devel] crash while initializing balloon driver On Thu, 2007-01-04 at 21:02 -0700, Alex Williamson wrote: On Fri, 2007-01-05 at 11:31 +0800, Zhang, Jingke wrote: Hi Alex, With the new Cset#13122, I met the xen0's crash even dom0_memQ2M. My elilo.conf and the serial port information are in the attachments. Thank you. Can you verify that it works with Isaku's patch here: http://lists.xensource.com/archives/html/xen-devel/2007-01/msg00102.html It works on HP systems as long as I don't specify a dom0_mem= that leaves gaps in the memory map, I was hoping it would be true in the interim for other systems as well. Thanks, Actually, looking more closely at your attached log, this cset may be the culprit: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs-4807ed1056 Does reverting this cset allow you to boot (hg export 13117 | patch -p1 -R)? The balloon driver crash occurs much later in dom0 bootup. Looks like we should probably only set the noncache flag if the WB attribute is not present since a range can have both WB and UC set. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13111
Xen/IA64 Healthiness Report Two issues: 1. UP_VTI booting speed is very slow. (Without serial='pty') 2. SMP_VTI LTP test could not finish within 80 minutes. If we made UP_xen0 and MT_disabled, that case could pass. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13111:912f8af36878 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 0 Noresult: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPNoresultVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13091
Xen/IA64 Healthiness Report Several issues: 1. If we enable MT and make xen0 to be UP, all the cases can pass. 2. If we disable MT and make xen0 to be SMP, VTI booting speed is very slow and SMPVTI_LTP performed slowly. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13091:c3b455c4676c Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13083
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boots slowly. UP_VTI's booting needs 170s or so. 2. SMPVTI_LTP performed slowly. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13083:6e68e8a8cc99 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTP__fail__VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#13022
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boots slowly, given 'serial=pty' is enabled. 2. SMPVTI_LTP performed slowly. Except SMPVTI_LTP case, all the other nightly cases can pass in manually testing. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 13022:2fc3392d0889 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTP__fail__VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12900
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boot slowly, if enabled 'serial=pty'. 2. Even without serial='pty', the VTI domain boots very slowly. (UPVTI needs 150s and VTI_Win2k3svr needs 8 minutes or so) 3. SMPVTI_LTP performed slowly. Except SMPVTI_LTP case, all the other nightly cases can pass in manually testing. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12900:c0d41ac21486 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTP__fail__VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-devel] Re: [Xen-ia64-devel] VTI Windows installation andbooting HowTo
Hi Alex, Using Flash.fd.2006.12.01 and Cset#12796 (with the accel_ide_pio patch from FJ), I have done the VTI_Win2k3server installation within an hour. ( Please make sure that serial='pty' has been commented in your VTI config file.) I did not meet the problem you said. Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Williamson Sent: Thursday, December 07, 2006 3:54 AM To: You, Yongkang Cc: [EMAIL PROTECTED]; xen-ia64-devel Subject: [Xen-devel] Re: [Xen-ia64-devel] VTI Windows installation andbooting HowTo On Thu, 2006-11-16 at 23:32 +0800, You, Yongkang wrote: 3. In EFI shell, go to fs0: ; run cp efi\microsoft\winnt50\boot . 4. Go to msutil\ ; run nvrboot; input I - boot - ENTER - Q; exit EFI shell; continue. 5. Windows will the perform installation. It takes 5 hours to complete installation. VTI domain still met slow CD-ROM issue, which will cause VTI domain installation slowly. In recent Changeset VTI performance depredates a lot, the installation might be slower. I've tried this many times, and I always seem to get stuck here. I do step #4 above, exit from EFI shell, and get a quick text flash that looks like it's selecting and booting Windows 2003, then my VNC session goes blank. It runs for a little over an hour consuming 100% of a vcpu, then according to the xend.log the domain reboots. I've using the 12.01 GFW with xen-ia64-unstable.hg tip (12796). It repeats the same thing again if I re-attempt from step 4. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-devel mailing list [EMAIL PROTECTED] http://lists.xensource.com/xen-devel ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-devel] Re: [Xen-ia64-devel] VTI Windows installationandbooting HowTo
Hi Alex, The whole environments I used are: - MT: disabled Xen0: UP Comment *** serial='pty' *** in the config file (very important!) GFW: Flash.fd.2006.12.01 VTI Network: close (this may not be necessary, but I guess it may make installation faster) - Maybe you can do a compare with your settings. Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zhang, Jingke Sent: Friday, December 08, 2006 4:03 PM To: Alex Williamson; You, Yongkang Cc: [EMAIL PROTECTED]; xen-ia64-devel Subject: RE: [Xen-devel] Re: [Xen-ia64-devel] VTI Windows installationandbooting HowTo Hi Alex, Using Flash.fd.2006.12.01 and Cset#12796 (with the accel_ide_pio patch from FJ), I have done the VTI_Win2k3server installation within an hour. ( Please make sure that serial='pty' has been commented in your VTI config file.) I did not meet the problem you said. Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Williamson Sent: Thursday, December 07, 2006 3:54 AM To: You, Yongkang Cc: [EMAIL PROTECTED]; xen-ia64-devel Subject: [Xen-devel] Re: [Xen-ia64-devel] VTI Windows installation andbooting HowTo On Thu, 2006-11-16 at 23:32 +0800, You, Yongkang wrote: 3. In EFI shell, go to fs0: ; run cp efi\microsoft\winnt50\boot . 4. Go to msutil\ ; run nvrboot; input I - boot - ENTER - Q; exit EFI shell; continue. 5. Windows will the perform installation. It takes 5 hours to complete installation. VTI domain still met slow CD-ROM issue, which will cause VTI domain installation slowly. In recent Changeset VTI performance depredates a lot, the installation might be slower. I've tried this many times, and I always seem to get stuck here. I do step #4 above, exit from EFI shell, and get a quick text flash that looks like it's selecting and booting Windows 2003, then my VNC session goes blank. It runs for a little over an hour consuming 100% of a vcpu, then according to the xend.log the domain reboots. I've using the 12.01 GFW with xen-ia64-unstable.hg tip (12796). It repeats the same thing again if I re-attempt from step 4. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-devel mailing list [EMAIL PROTECTED] http://lists.xensource.com/xen-devel ___ Xen-devel mailing list [EMAIL PROTECTED] http://lists.xensource.com/xen-devel ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12801
Xen/IA64 Healthiness Report This Cset is the same with the last Cset#12796 Several issues: 1. VTI Linux domain boot slowly, if enabled 'serial=pty'. 2. SMPVTI_LTP performed slowly. Except SMPVTI_LTP case, all the other nightly cases can pass in manually testing. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12801:968caf47b548 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTP__fail__VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12796
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boot slowly, if enabled 'serial=pty'. 2. SMPVTI_LTP performed slowly. Except SMPVTI_LTP case, all the other nightly cases can pass in manually testing. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.47 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12796:d901f2fe8c25 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.12.01 MD5: 09a224270416036a8b4e6f8496e97854 Summary Test Report: - Total cases: 16 Passed:15 Failed: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTP__fail__VTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU pass SMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
RE: [Xen-ia64-devel] [PATCH][RFC][IA64] Accelerate IDE PIO on HVM/IA64
Hi Kouya, With your patch, win2k3 installation can be done within 40 minutes! I have integrated #Cset12525 with the accelerating patch. It took 20 minutes to load file (you will see it in a blue screen). And then the guest quickly installed the win2k3 from the CD-ROM, totally within 40 minutes! What a wonderful patch! :) Thanks, Zhangjingke -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kouya SHIMURA Sent: Monday, December 04, 2006 10:28 AM To: [EMAIL PROTECTED]; xen-ia64-devel@lists.xensource.com Subject: [Xen-ia64-devel] [PATCH][RFC][IA64] Accelerate IDE PIO on HVM/IA64 This patch significantly accelerates IDE PIO on HVM/IA64: * reduces the installation time of Windows 2003 Server from 10 hours(!) to 50min. * accelerates Windows CrashDumping speed from 40KB/sec (It takes over three hours for 512MB guest) to 850KB/sec. All reason for above slowness is the overhead of IDE PIO. Of course Windows should use DMA mode but we can't handle it. (FYI. Once installed, Windows usually uses DMA mode) On the other hand, x86 arch is rescued from this issue since it has a CISC instruction and multiple PIO requests can be processed in qemu-dm at one transaction. So this patch gives no benefit for x86. There are some dirty hacks in this patch: * To begin with, is it permissive to delegate the part of process of qemu-dm to hypervisor? * Currently it uses remnant of buffered_iopage (for VGA). Maybe I should prepare another page for IDE PIO. * May I use #ifdef __ia64__ ? * and so on. Please show me the right way. Thanks, Kouya Signed-off-by: Kouya Shimura [EMAIL PROTECTED] ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12525
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boot slowly, if enabled 'serial=pty'. (performance issues): 2. SMPVTI LTP test has a 100% performance downgrade. 3. UPVTI Kernel build has a performance downgrade. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.15 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12525:7e7846ea4ab3 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.11.07 MD5: 797c2d6c391a6fc6f16d267e01b382f8 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU passSMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] RE: The vcpus can change from one LP to another LP very frequently
Ok, let me try. Thanks! Thanks, Zhangjingke -Original Message- From: Keir Fraser [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 4:01 PM To: Zhang, Jingke Cc: xen-ia64-devel Subject: Re: The vcpus can change from one LP to another LP very frequently Can you narrow it down to a specific changeset? If it turns out to be a credit-scheduler change (which is most likely) then you should email Emmanuel Ackaouy [EMAIL PROTECTED]. -- Keir On 22/11/06 7:57 am, Zhang, Jingke [EMAIL PROTECTED] wrote: Hi Keir, With #Cset12018, the vcpus of xen0 and the SMP guest can stay at one LP for a long time. But from the #Cset 12425 on (maybe an earlier Cset), the vcpus would jumped from here and there very fast. This fast changing will cause a lot of performance downgrade in SMP_VTI. Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12523
Xen/IA64 Healthiness Report Several issues: 1. Destroying XenU domains makes Xen0 Crash. 2. VTI Linux domain boot slowly, if enabled 'serial=pty'. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.15 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12523:0114b372dfae Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.11.07 MD5: 797c2d6c391a6fc6f16d267e01b382f8 Summary Test Report: - Total cases: 16 Passed:15 Failed: 0 Crash: 1 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexist__crash__ 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU passSMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] [IPF-XenU] On Cset 12444, create/destroy Two SMP_xenU may make xen0 crashed!
Hi all, On Cset 12444, when creating and destroying two SMP_XenU guests, I met xen0 crashed. I can reproduce it for many times. This problem also existed on Cset 12425. The steps are: 1. Create 2 SMP_XenU guests at the same time; 2. When they booted up, type xm destroy id, xen0 will crash. Log is: ~~~ (XEN) vcpu_get_lrr0: Unmasked interrupts unsupported (XEN) vcpu_get_lrr1: Unmasked interrupts unsupported (XEN) lookup_domain_mpa: d 0xf7c54080 id 1 current 0xf7c28000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xc019064 (= 0x2000) (XEN) Warning: UC to WB for mpaddr=c019064 (XEN) lookup_domain_mpa: d 0xf7bd0080 id 2 current 0xf7ba8000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xc019064 (= 0x2000) (XEN) Warning: UC to WB for mpaddr=c019064 (XEN) BUG at mm.c:407 (XEN) FIXME: implement ia64 dump_execution_state() (XEN) (XEN) (XEN) Panic on CPU 2: (XEN) BUG at mm.c:407 (XEN) (XEN) (XEN) Reboot in five seconds... ~~~ BTW, Env is: Service OS: RHEL4u3 IA64 with 2 CPUs xen0's sched: credit Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
