xen-ia64-devel
Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d638
On Mon, Oct 06, 2008 at 11:16:02AM +0800, Zhang, Jingke wrote:
> Isaku Yamahata wrote:
> > On Mon, Oct 06, 2008 at 09:54:13AM +0800, Zhang, Jingke wrote:
> >> Hi all,
> >> There is no new regression found in Cset#18580. Three old issues
> >> still existed.
> >>
> >> Old issue (3):
> >> 1. Qemu will disappear and VTI hangs when we do 'xm restore' and
> >> 'xm migrate'
> >
> > Hi. Does this still exist?
> > The change set 18578:ba543f51c6f1 should fix this.
> > At least works for me with xm save/restore. I haven't tried xm
> > migrate, though.
> >
> > Does qemu-dm exit with the following message?
> > from xen_vga_vram_map() in hw/vga.c
> > fprintf(stderr, "Failed to map vram nr_pfn=0x%lx
> > vram_addr=%llx: %s\n", nr_pfn, (unsigned long
> > long)vram_addr, strerror(errno)); exit(1);
> >
>
> Yes, my qemu-dm log shows: Failed to map vram nr_pfn=0x200
> vram_addr=c0000000: Invalid argument
> I used GFW#129, image type is QCOW. Since it works for you, what is the
> difference between us? Thanks. :)
Ah, I'm using patched GFW. I sent out two patches as
http://lists.xensource.com/archives/html/xen-ia64-devel/2008-09/msg00067.html
http://lists.xensource.com/archives/html/xen-ia64-devel/2008-09/msg00068.html
But I guess Tristan is too busy to commit those.
The patch in msg00067.html would fix the issue. Could you try that patch?
thanks,
>
> > thanks,
> >
> >> 2. With 4096M, VTI can not boot up emulated rtl8139 network-card
> >> 3. With 4095M, qemu of VTI guest will disappear when booting
> >>
> >> Detail Xen/IA64 Unstable Cset #18580 Status Report
> >> ============================================================
> >> Test Result Summary:
> >> # total case: 17
> >> # passed case: 14
> >> # failed case: 3
> >> ============================================================
> >> Testing Environment:
> >> platform: Tiger4
> >> xen ia64 unstable tree: 18580
> >> dom0 Cset: 687
> >> ioemu commit: 0f3d6384d1b3d96476f78950b14040f9c1c63375
> >> 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#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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke
- Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Isaku Yamahata
- RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke
- Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue,
Isaku Yamahata <=
- RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke
- Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Isaku Yamahata
- RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke
- Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Isaku Yamahata
- Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Tristan Gingold
- RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke
Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, KUWAMURA Shin'ya
|
Previous by Date: |
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke |
Next by Date: |
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke |
Previous by Thread: |
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke |
Next by Thread: |
RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18580, Linux#687, ioemu#0f3d6384... Status Report --- no new issue, Zhang, Jingke |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|