Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18501 Status Report --- 1 new issue for guest restore

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

On Mon, Sep 22, 2008 at 10:53:26AM +0800, Zhang, Jingke wrote:
> 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!

I looked into this.
This is because Xen/IA64 foreign p2m exposure doesn't support memory
hot plug. So memory hot plug support by the foreign p2m exposure is
necessary to fix it. I'll take care of it.

thanks,

> 
> >
> >>
> >>     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_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
> >>
> >> Failed case
> >>         Save&Restore                    Save&Restore
> >>         VTI_Live-migration                      Linux VTI
> >>         live-migration One_SMPVTI_4096M                1 VTI
> >> (vcpus=2, mem=4096M)
> >> -----------------------------------------------------------------------
> >>
> >> 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
> 

-- 
yamahata

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