Hi, I report a benchmark result of this week on IPF using xen-unstable and linux-2.6.18-xen. # not ia64 tree - Dom0 crashed. Thus I added the following patches: Xen: http://lists.xensource.com/archives/html/xen-ia64-devel/2009-06/msg00013.html http://lists.xensource.com/archives/html/xen-ia64-devel/2009-06/msg00014.html http://lists.xensource.com/archives/html/xen-ia64-devel/2009-06/msg00015.html Linux: http://lists.xensource.com/archives/html/xen-ia64-devel/2009-06/msg00016.html http://lists.xensource.com/archives/html/xen-ia64-devel/2009-06/msg00017.html - DomVTi cannot use tap:aio. When a guest started, dom0 hit BUG_ON() at mm/rmap.c:522 and the guest hung up. Thus we used vbd. I attached the dom0 call trace. # Notice that DomU can use tap:aio. TEST ENVIRONMENT Machine : Tiger4 Kernel : 2.6.18.8-xen Changeset : 19821:442fb5f1e0a2 (xen-unstable) + three patches 909:865707f40531 (linux-2.6.18-xen) + two patches 137:3ad73b4314e3 (efi-vfirmware) e0bb6b8 (qemu-xen-unstable) Dom0 OS : RHEL4 U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) TEST RESULTS DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: # file: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA Shin'ya and FUJITSU members _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel