RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error

["Zhang, Jingke" <jingke.zhang@xxxxxxxxx>]

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.



Thanks,
Zhang Jingke

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