Re: [Xen-ia64-devel] Xen/IPF Unstable CS#17671 Status Report --- one issue fixed, one issue still existed

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

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,


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
>       Save&Restore                    Save&Restore
>       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_4096M                1 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_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
>       
> ------------------------------------------------------------------------
> 
> (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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

-- 
yamahata

17678_e011f938f371.patch
Description: Text Data

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