Re: [Xen-devel] Test report for xen-unstable and qemu-xen

["Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>]

Fabio Fantoni wrote on 2013-08-27:
> Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
> version 3.2.46-1 and all dependency packages for xen, spice and usb
> redirection. Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice
> 0.12.4-0nocelt1 and usbredir 0.6-2 compiled from debian unstable
> sources. ------------------------- git clone
> git://xenbits.xen.org/xen.git (in this build commit is
> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
> controller support for upstream qemu v4 -
> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
> initialization of the ram_memory variable (to fix qemu 1.6 critical
> regression) ------------------------- vi Config.mk # Change upstream
> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c ----
> ./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no
> ------------------------- make debball
> 
> Note: mainly tested with qemu 1.6
> 
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>    works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>    client show only the lines of seabios version and machine UUID; qemu
>    log show nothing more that 2 gb test), while with 2 gb of ram works
>    also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
> -------------
> - Starting xendomain with "xl create" show some debug options:
>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>    ARRANGEMENT: Loader:        0000000000100000->000000000019eb68
>    Modules:       0000000000000000->0000000000000000 TOTAL:        
>    0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>    xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200
>    2MB PAGES: 0x00000000000003f7 1GB PAGES: 0x0000000000000000
> [done].
> -------------
> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
> qemu-xen,
>    on xpmode now works also integration features
> (disks,printers,clipboard sharing) and usb passthrough
> -------------------------
I didn't quite catch your meaning. Can you give more detail of what kind of 
nested cases you test and how many passed and how many fail?

> 
> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen and
> gplpv
>    Workaround: fixed mac address
> -------------
> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem
> to work:
>    xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
>    (22 = Invalid argument): Internal error xen be: qdisk-832:
>    xc_gnttab_set_max_grants failed: Invalid argument
> -------------------------


Best regards,
Yang


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel