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

[Xen-ia64-devel] [IA64] Weekly benchmark results [ww25]

To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] [IA64] Weekly benchmark results [ww25]
From: "KUWAMURA Shin'ya" <kuwa@xxxxxxxxxxxxxx>
Date: Fri, 22 Jun 2007 16:57:11 +0900 (JST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 22 Jun 2007 00:56:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.

Booting domU using tap:aio failed. Timeout occurred when connecting to
a disk.  DomU's booting message:
  (..snip)
  xen privcmd uses pseudo physical addr range [0x20000000, 0x3ffff000000] 
(4193776MB)
  Xen p2m: assign p2m table of [0x0000000000000000, 0x0000000020004000)
  Xen p2m: to [0x0000000020000000, 0x0000000024000000) (65536 KBytes)
  XENBUS: Timeout connecting to device: device/vbd/769 (state 3)
  XENBUS: Device with no driver: device/console/0
  VFS: Cannot open root device "hda1" or unknown-block(0,0)
  Please append a correct "root=" boot option
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
But if using 'file:' instead of 'tap:aio', booting domU succeeded.

semop01 failed on DomVTi, but passed manually.

TEST ENVIRONMENT
    Machine          : Tiger4
    Kernel           : 2.6.18-xen
    Changeset        : 15406:810885428743 (ia64/xen-unstable)
                       65:3df04f34c4aa    (ia64/linux-2.6.18-xen)
    Dom0 OS          : RHEL4 U2 (2P)
    DomU OS          : RHEL4 U2 (8P, using tap:aio)
    DomVTi OS        : RHEL4 U2 (8P, with PV-on-HVM drivers)
    Scheduler        : credit

TEST RESULT
  DomU: boot FAILED
  DomVTi:
    unixbench4.1.0    : Pass
    bonnie++-1.03     : Pass
    ltp-full-20061121 : 1/831 FAIL
    iozone3_191       : Pass
    lmbench-3.0-a5    : Pass

Best regards,
KUWAMURA and Fujitsu members

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] [IA64] Weekly benchmark results [ww25], KUWAMURA Shin'ya <=