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-devel

Re: [Xen-devel] Regressions introduced by ioemu-remote -- Xen #18039.

To: Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>, <haicheng.li@xxxxxxxxx>
Subject: Re: [Xen-devel] Regressions introduced by ioemu-remote -- Xen #18039.
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 14 Jul 2008 09:56:31 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Mon, 14 Jul 2008 01:56:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <487B1072.3030600@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acjlj4JYwL8uqFGCEd2vKwAX8io7RQ==
Thread-topic: [Xen-devel] Regressions introduced by ioemu-remote -- Xen #18039.
User-agent: Microsoft-Entourage/11.4.0.080122
Actually this is already applied to out private tree but hasn't been
automatically pushed publicly for some reason. I'm sure Ian will sort it out
today.

 -- Keir

On 14/7/08 09:38, "Yosuke Iwamatsu" <y-iwamatsu@xxxxxxxxxxxxx> wrote:

> Perhaps the attached patch will fix the Issue2?
> cs 18025 changed the size of vga ram, so we should reduce VGA_RAM_SIZE
> to 4MB for ioemu-remote tree likewise.
> 
> Thanks,
> -- Yosuke
> 
> Li, Haicheng wrote:
>> With ioemu-remote, still failed to create hvm guest with vncviewer
>> disabled by 'sdl=1' or 'vnc=1 & vncconsole=0'. Two issues were found
>> with Xen #18039 as log pasted below.
>> 
>> BTW, will xen-3.3 release use ioemu-remote as default qemu? Looks there
>> would be some compatibility issues between xm/xend and ioemu-remote.
>> 
>> Issue1: if no vif option set. qemu exits with following log:
>> domid: 14
>> qemu: the number of cpus is 1
>> Unknown network device: user
>> 
>> Issue2: with vif option set, qemu exits with following log:
>> domid: 18
>> qemu: the number of cpus is 1
>> config qemu network with xen bridge for  tap18.0 eth4
>> Strip off blktap sub-type prefix to
>> /share/imgs/hli22/xen-test/manual-test/ia32e_xp_smp.qcow (drv 'qcow')
>> qemu: could not open vbd '/local/domain/18/device/vbd/768/phantom_vbd'
>> or hard disk image
>> '/share/imgs/hli22/xen-test/manual-test/ia32e_xp_smp.qcow' (drv 'qcow'
>> format '0')
>> Watching /local/domain/0/device-model/18/logdirty/next-active
>> Watching /local/domain/0/device-model/18/command
>> char device redirected to /dev/pts/3
>> qemu_map_cache_init nr_buckets = 10000 size 3145728
>> shared page at pfn 7ffe
>> buffered io page at pfn 7ffc
>> Time offset set 0
>> Register xen platform.
>> Done register platform.
>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>> (qemu) Failed allocation for dom 18: 2048 extents of order 0
>> Failed to populate physmap
>> Failed set_mm_mapping
>> NULL vram_pointer
>> 
>> 
>> -- haicheng
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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