Zhang, Jingke wrote:
> Hi all,
> The old VTI Save-Restore issue was fixed now. Then VTI
> save&restore, 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 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@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
