[Xen-devel] Problems with the new ioemu

["Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>]

We've encountered a few problems with the new ioemu tree:

ssue1: with vncviewer enabled by 'vnc=1 & vncconsole=1', 
qemu-dm exit(1) for invalid option '-vncviewer'
qemu.log:
domid: 3
qemu: the number of cpus is 1
/usr/lib64/xen/bin/qemu-dm: invalid option -- '-vncviewer'

Even with vncviewer disabled by 'sdl=1' or 'vnc=1 & 
vncconsole=0', still failed to create hvm guest:

Issue2: if no vif option set and vncviewer disabled, qemu 
exits abnormally with following log:
domid: 14
qemu: the number of cpus is 1
Unknown network device: user

Issue3: with vif option set and vncviewer disabled, qemu exits 
abnormally 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

Issue4: cannot compile with GCC v. 4, `make' fails with:
WARNING: "gcc" looks like gcc 4.x
Looking for gcc 3.x
gcc 3.x not found!
QEMU is known to have problems when compiled with gcc 4.x
It is recommended that you use gcc 3.x to build QEMU
To use this compiler anyway, configure with --disable-gcc-check

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Donald.D.Dugger@xxxxxxxxx
Ph: (303)443-3786

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