Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18483 Status Report --- 2 new issues for remote-ioemu

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

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?)
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.

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
>         Save&Restore                    Save&Restore
>         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_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
>         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
> 

-- 
yamahata

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