RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18633, Linux#701, ioemu#629adb3f... Status --- no new issue

["Zhang, Jingke" <jingke.zhang@xxxxxxxxx>]

Isaku Yamahata wrote:
> On Mon, Oct 20, 2008 at 03:28:37PM +0800, Zhang, Jingke wrote:
>> 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?
>
> I believe that 131:9210bd27a551 of efi-vfirmware.hg fixed it.
> I had tested only 3037MB, 3098MB cases, though.

Ok, I see. Thanks Isaku.

>
> thanks,
>
>>     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_4096M                1 VTI (vcpus=2, mem=4096M)
>>         SMPVTI_LTP                      VTI (vcpus=4, mem=512) run
>>         LTP Save&Restore                    Save&Restore
>>         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_XenU                    1 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@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel



Thanks,
Zhang Jingke

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel