WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu er

To: "Zhang, Jingke" <jingke.zhang@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Fri, 5 Sep 2008 12:58:05 +0900
Cc: "xen-ia64-devel@xxxxxxxxxxxxxxxxxxx" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 04 Sep 2008 20:58:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BB1F052FCDB1EA468BD99786C8B1ED2C018BDA78E7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE486@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080902041743.GB4485%yamahata@xxxxxxxxxxxxx> <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE546@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE696@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080905023228.GA20288%yamahata@xxxxxxxxxxxxx> <20080905034016.GD20288%yamahata@xxxxxxxxxxxxx> <BB1F052FCDB1EA468BD99786C8B1ED2C018BDA78E7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Fri, Sep 05, 2008 at 11:43:55AM +0800, Zhang, Jingke wrote:
> Isaku Yamahata wrote:
> > Could you try the following patch to ioemu?
> > NOTE:This is only a band aid patch. GFW needs modifcation.
> >
> > ioemu: prevent qemu-dm segv.
> >
> > With dade7f0bdc8d and old bios, qemu-dm results in segv.
> >
> > Signed-off-by: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
> >
> > diff -r 9b5e1e05e886 tools/ioemu/hw/cirrus_vga.c
> > --- a/tools/ioemu/hw/cirrus_vga.c       Mon Sep 01 17:50:13 2008 +0900
> > +++ b/tools/ioemu/hw/cirrus_vga.c       Fri Sep 05 12:42:37 2008 +0900
> > @@ -2553,7 +2553,11 @@
> >          end = begin + VGA_RAM_SIZE;
> >
> >      fprintf(logfile,"mapping vram to %lx - %lx\n", begin, end);
> > -
> > +    if (!s->vram_mfns) {
> > +        fprintf(logfile, "Found old firmware skiping mapping
> > vram\n"); +        return;
> > +    }
> > +
> >      xatp.domid = domid;
> >      xatp.space = XENMAPSPACE_mfn;
> >
> 
> Hi Isaku,
>     I checked my building environment. My source were built twice by "make 
> -j3" and "CONFIG_QEMU=ioemu make -j3". But they both use local ioemu (ia64 is 
> different with x86?). What command did you use to enable ioemu-remote?
>     So, remote-ioemu may not affect VTI booting, I will double check that 
> with your patch. Thanks.

Hi Zhang.
Don't specify "CONFIG_QEMU=ioemu" or
specify 
"CONFIG_QEMU=http://xenbits.xensource.com/git-http/qemu-xen-unstable.git";
git command is necessary to build with ioemu-remote while building
it pulls the ioemu-remote tree from the above URL.

-- 
yamahata

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