domains is
successful on IPF.
Thanks,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
I report a benchmark result of this week.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.16.29-xen
Changeset: 11745:5176c3ea3293 (xen-ia64-unstable)
Dom0 OS : RHEL4 U2 (2P)
DomU OS : RHEL4 U2 (2P)
# of DomU: 1
,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
I report a benchmark result of this week.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.16.29-xen
Changeset: 11810:fcd746cf4647 (xen-ia64-unstable)
Dom0 OS : RHEL4 U2 (2P)
DomU OS : RHEL4 U2 (2P)
# of DomU: 1
Scheduler: credit
TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03 : Pass
ltp-full-20060306 : 2/817 FAIL (see attachment)
iozone3_191 : Pass
lmbench-3.0-a5: Pass
Thanks and best regards,
KUWAMURA and Fujitsu members
--
KUWAMURA Shin'ya
Test Start Time
Hi Anthoy,
I confirmed that this patch fixed the issue of dom0 hang-up by
creating and destroying a domain VTi 650 times at intervals of 90
seconds.
Thank you.
Best Regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel
Hi,
I report a benchmark result of this week.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.16.29-xen
Changeset: 12018:11b718eb22c9 (xen-ia64-unstable)
Dom0 OS : RHEL4 U2 (2P)
DomU OS : RHEL4 U2 (2P)
# of DomU: 1
Hi,
I report a benchmark result of this week.
The latest changeset could not be compiled, so xen-ia64-unstable:12525
was used.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.16.29-xen
Changeset: 12525:7e7846ea4ab3 (xen-ia64-unstable)
Dom0 OS :
Hi,
I report a benchmark result of this week.
shmt09 failed. This detailed output:
shmat1: Invalid argument
shmt09 1 PASS : sbrk, sbrk, shmget, shmat
shmt09 2 PASS : sbrk, shmat
shmt09 3 FAIL : Error: shmat Failed, shmid = 134971393, errno = 22
TEST ENVIRONMENT
Hi Yamahata-san,
On [EMAIL PROTECTED],
Isaku Yamahata wrote:
On Fri, Dec 08, 2006 at 10:39:33PM +0900, KUWAMURA Shin'ya wrote:
shmt09 failed. This detailed output:
shmat1: Invalid argument
shmt09 1 PASS : sbrk, sbrk, shmget, shmat
shmt09 2 PASS : sbrk, shmat
Hi,
I report a benchmark result of this week.
semget05 seems LTP's bug (Thanks to Yamahata), so I treat it as LTP's
bug.
But semop05 failed now. It passed manually.
Details:
automatically:
semop05 1 BROK : couldn't create semaphore in setup
semop05 2 BROK : Remaining cases broken
Hi,
I report a benchmark result of this week.
In LTP, clone06 and sockioctl01 failed. Both cases passed when
testing manually.
sockioctl01's fail caused by a bad configuration (/dev/tty0 is
missing). I will fix it.
clone06 fails because the environment variable TERM is unset.
In such cases,
Hi,
I report a benchmark result of this week.
In LTP, pselect01 and syslog05 failed. Both cases passed when
testing manually.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.16.33-xen
Changeset: 13475:b4df7de0cbf7 (xen-ia64-unstable)
Dom0 OS
Hi,
I report a benchmark result of this week.
In LTP, dio02, dio03, dio06, dio08, dio09, dio12, dio14, dio15, dio17,
dio18, dio19, dio21, dio22, dio23, dio25, dio26, dio27 and dio28
failed.
All of them output write failed: Input/output error when the test
Write with Direct IO, Read without
Hi Yamahata,
On [EMAIL PROTECTED], Isaku Yamahata wrote:
On Fri, Feb 02, 2007 at 06:37:15PM +0900, KUWAMURA Shin'ya wrote:
In LTP, dio02, dio03, dio06, dio08, dio09, dio12, dio14, dio15, dio17,
dio18, dio19, dio21, dio22, dio23, dio25, dio26, dio27 and dio28
failed.
All of them output
=ttyS1,115200,8n1 \
rhgb root=/dev/sda2
The serial output:
ELILO boot: Uncompressing Linux... done
Loading file ..\xen\initrd-2.6.18-xen.img...done
Loading file ..\xen\vmlinuz-2.6.18-xen...done
Uncompressing... done
(No output from this line...)
Best regards,
--
KUWAMURA Shin'ya
Hi,
I report a benchmark result of this week.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
semop05 failed but passed when I manually ran it.
The case gf18 passed since the
On Thu, 8 Feb 2007 17:39:22 +0900
[EMAIL PROTECTED](Horms) said:
On Thu, Feb 08, 2007 at 05:29:34PM +0900, KUWAMURA Shin'ya wrote:
Hi all,
At xen-ia64-unstable:13867, the serial console connected to my Tiger4
machine outputs no messages. Do anyone have any ideas?
Cset:13773
tbuf_size=8 dom0_max_vcpus=2 -- console=tty0
console=ttyS1 rhgb root=/dev/sda2
Best Regards,
--
KUWAMURA Shin'ya
--- xen/arch/ia64/linux-xen/setup.c.orig2007-02-13 14:29:02.0
+0900
+++ xen/arch/ia64/linux-xen/setup.c 2007-02-13 16:55:32.0 +0900
@@ -354,7 +354,7
?
I tried it on only Tiger4.
Best Regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
I report a benchmark result of this week.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
These cases also fail on the native kernel, so this problem is
unrelated to Xen.
Hi,
I report a benchmark result of this week.
I did not test a VTi domain, since a warning appeared when linking
PV-on-HVM drivers:
*** Warning: HYPERVISOR_grant_table_op [/home/kuwa/proj/
xen-ia64-unstable.hg/unmodified_drivers/linux-2.6/platform-pci/
xen-platform-pci.ko] undefined!
In
Hi,
I report a benchmark result of this week on IPF using
xen-ia64-unstable.
I did not test a VT-i domain because linking PV-on-HVM drivers still
failed.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22
Hi,
I report a benchmark result of this week on IPF using
xen-ia64-unstable.
I did not test a VT-i domain because linking PV-on-HVM drivers still
failed.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22
Hi,
I report a benchmark result of this week on IPF using
xen-ia64-unstable.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
TEST ENVIRONMENT
Machine : Tiger4
Hi,
On [EMAIL PROTECTED],
KUWAMURA Shin'ya wrote:
ltp-full-20061121 : 18/831 FAIL (see attachment)
Sorry, I forgot an attachment file.
Thanks,
--
KUWAMURA Shin'ya
Thu Apr 5 16:48:09 JST 2007
Test Start Time: Thu Apr 5 16:48:09 2007
-
Testcase
Hi Keir,
On [EMAIL PROTECTED]
KUWAMURA Shin'ya wrote:
- pygrub cannot access a domain more than 2^32 * SECTOR_SIZE because
get_fs_offset() treats the offset as a 32-bit integer. In GPT, the
offset must be treated as 64-bit integer.
- This patch returns a part of a GUID unique
Hi,
I report a benchmark result of this week on IPF using
xen-ia64-unstable.
I did not test a VT-i domain because compiling PV-on-HVM drivers failed.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23
Hi,
I report a benchmark result of this week on IPF using
xen-ia64-unstable.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
TEST ENVIRONMENT
Machine : Tiger4
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
semop05 failed on domU,
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 [0x2000, 0x300]
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
As for this changeset, booting domU using tap:aio succeeded, but
failed after the second. DomU's output:
Xen p2m: to [0x2000, 0x2400) (65536 KBytes)
XENBUS: Timeout
Hi,
On [EMAIL PROTECTED]
KUWAMURA Shin'ya wrote:
ltp-full-20061121 : 19/831 FAIL (see attachment)
Sorry, I forgot the attachment file.
Thanks,
--
KUWAMURA Shin'ya
Test Start Time: Thu Jun 28 16:37:00 2007
-
Testcase Result
Hi Isaku,
On [EMAIL PROTECTED]
Isaku Yamahata wrote:
On Fri, Jun 29, 2007 at 03:26:18PM +0900, KUWAMURA Shin'ya wrote:
As for this changeset, booting domU using tap:aio succeeded, but
failed after the second. DomU's output:
Xen p2m: to [0x2000, 0x2400) (65536
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
TEST ENVIRONMENT
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Building the xen-vnif PV-on-HVM driver failed. This issue has already
fixed on staging trees by the following patches:
http://xenbits.xensource.com/staging/xen-unstable.hg?rev/48c8244c47c7
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Building xen-vnif PV-on-HVM driver still fails. This issue has already
fixed on staging trees by the following patches:
http://xenbits.xensource.com/staging/xen-unstable.hg?rev/48c8244c47c7
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
The testcase semop04 and
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
- PV-on-HVM drivers cannot be compiled for RHEL4U2
RHEL4U2's kernel (2.6.9-22.EL) does not have the macro DEFINE_RWLOCK,
so compiling machine_reboot.c failed.
Message:
Hi Alex,
On Fri, 24 Aug 2007 06:12:40 -0600
[EMAIL PROTECTED](Alex Williamson) said:
On Fri, 2007-08-24 at 17:07 +0900, KUWAMURA Shin'ya wrote:
- Console problem
I cannot login dom0 by tty and serial consoles. I avoid this issue by
adding xencons=ttyS to options of dom0 kernel
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
- PV-on-HVM drivers cannot be compiled for RHEL4U2
RHEL4U2's kernel (2.6.9-22.EL) does not have the macro DEFINE_RWLOCK,
so compiling machine_reboot.c failed.
- LTP FAIL
In LTP, test cases
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
- PV-on-HVM drivers cannot be compiled for RHEL4U2
- Call trace when shutdown domU
This issue has already been fixed by ia64/linux-2.6.18-xen:192.
- LTP FAIL
In LTP, test cases related with
patches.
/ia64/xen-unstable.hg/unmodified_drivers/linux-2.6/platform-pci/
xencomm.c:71: error: syntax error before gfp_mask
This compilation issue was fixed by an attached patch.
But insmod fails with the same error as RHEL4U4.
Best Regards,
--
KUWAMURA Shin'ya
# HG changeset patch
# User
Hi Isaku,
On [EMAIL PROTECTED]
Isaku Yamahata wrote:
On Mon, Sep 10, 2007 at 04:31:15PM +0900, KUWAMURA Shin'ya wrote:
In RHEL4U4, insmod xen-platform-pci.ko failed with these patches.
kernel's message:
xen_platform_pci: Unknown symbol xencomm_arch_hypercall_suspend
Could you try
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Creating DomU using tap:aio failed:
Error: Device 769 (tap) could not be connected. Hotplug scripts not working.
But if using 'file:' instead of 'tap:aio', booting domU succeeded.
Now,
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Creating DomU using blktap still failed, but the following patch fixes
it.
http://xenbits.xensource.com/staging/xen-unstable.hg?rev/be5f27ff147b
In LTP, test cases related with direct IO still
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Creating DomU using blktap still failed on ia64, but the following
patch fixes it.
xen-unstable 15920
http://xenbits.xensource.com/xen-unstable.hg?rev/be5f27ff147b
In LTP, test cases
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
In LTP, test cases related with direct IO still failed.
# dio02 dio03 dio06 dio08 dio09 dio12 dio14 dio15 dio17 dio18 dio19
# dio21 dio22 dio23 dio25 dio26 dio27 dio28
TEST ENVIRONMENT
Hi Isaku,
On [EMAIL PROTECTED]
Isaku Yamahata wrote:
On Fri, Oct 19, 2007 at 06:30:54PM +0900, KUWAMURA Shin'ya wrote:
The failures related with direct IO were fixed.
Since the dio issues begun when xenLinux base version was
changed from 2.6.16 to 2.6.18, I supposed that it was
not Xen
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
LTP was updated to 20070930. The bug of semget05 is fixed, so all
cases of LTP passed.
The guest firmware was changed to open guest firmware.
TEST ENVIRONMENT
Machine : Tiger4
Hi,
This fixes build errors of PV-on-HVM drivers for RHEL4U2 on ia64:
/ia64/xen-unstable.hg/unmodified_drivers/linux-2.6/platform-pci/xencomm.c:71:
error: syntax error before gfp_mask
Signed-off-by: KUWAMURA Shin'ya [EMAIL PROTECTED]
--
KUWAMURA Shin'ya
# HG changeset patch
# User
-vfirmware)
Dom0 OS : RHEL4U2
HOW TO TEST
1. run xm create DOMAIN
2. wait until login prompt appears
3. run xm save DOMAIN savefile
4. run xm restore savefile
5. check the status of the DOMAIN
--
KUWAMURA Shin'ya
___
Xen
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Building PV-on-HVM drivers failed for RHEL4U2. The following patches
fixes this problem.
- PV-on-HVM: xencomm - compilation fix for old Linux kernels.
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16340:ef6415fdaf8a (ia64/xen-unstable)
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16362:568816a7cb0a (ia64/xen-unstable)
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16417:53dc1cf50506 (ia64/xen-unstable)
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16540:8ba08f2244b2 (ia64/xen-unstable)
4. run xm restore savefile
5. check the status of the DOMAIN
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16604:d90dbf72049c (ia64/xen-unstable)
,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16682:7515dc56c124 (ia64/xen-unstable)
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 16714:235bef53d5bd (ia64/xen-unstable)
Hi Isaku,
On [EMAIL PROTECTED],
Isaku Yamahata wrote:
Could you try the attached patch?
Thank you. These patches worked well with the attached patch.
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1202085889 -32400
# Node ID
Hi Alex,
On Mon, 04 Feb 2008 08:42:20 -0700
[EMAIL PROTECTED](Alex Williamson) said:
Can you please send a sign-off for this?
I added Signed-off-by: line.
Best Regards,
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1202194119 -32400
# Node
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Creating domVTi still failed, but the following patch fixed this issue.
ia64/xen-unstable 17061
ioemu: Stub out direct-Linux-boot support for anything other than x86.
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 17089:f853c0497095 (ia64/xen-unstable)
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 17133:daf39fc8038a (ia64/xen-unstable)
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
On DomVTi, a kernel panic occurred when xen-vnif.ko was loaded. The
issue was fixed by reverting the following patch:
Hi Neil,
On Mon, 17 Mar 2008 14:54:30 +
[EMAIL PROTECTED](Neil Turton) said:
- accel_watch_workqueue = create_workqueue(accel_watch);
+ accel_watch_workqueue = create_workqueue(net_accel);
This patch work fine. Thank you.
Best Regards,
--
KUWAMURA Shin'ya
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
Now, loading xen-vnif.ko succeeded.
On domU syslog08 failed, but passed when I reran it.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 17313:edfb58ca4d96 (ia64/xen-unstable)
On Wed, 09 Apr 2008 13:03:50 -0500
[EMAIL PROTECTED](Alex Williamson) said:
On Wed, 2008-04-09 at 17:10 +0100, Keir Fraser wrote:
Fourth release candidates are available from the public xen-3.1-testing.hg
and xen-3.2-testing.hg.
BSD/IA64/Sun people: Please at least build test
par_mem on ia64
cd LMbench directory/bin/i686-pc-linux-gnu
./par_mem -L 128 -M 16M
Best Regards,
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1207901130 -32400
# Node ID 6713ab838e777d4a408880ebc4373eb586ef5036
# Parent
On Wed, 09 Apr 2008 13:03:50 -0500
[EMAIL PROTECTED](Alex Williamson) said:
On Wed, 2008-04-09 at 17:10 +0100, Keir Fraser wrote:
Fourth release candidates are available from the public xen-3.1-testing.hg
and xen-3.2-testing.hg.
BSD/IA64/Sun people: Please at least build test
Hi,
I report a benchmark result of last week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 17465:1fbc9073a566 (ia64/xen-unstable)
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
All test cases passed.
TEST ENVIRONMENT
Machine : Tiger4
Kernel : 2.6.18.8-xen
Changeset: 17602:f23e7e07bf1d (ia64/xen-unstable)
Hi,
I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.
The PV domain did not start, since qemu-dm abnormally terminated.
So I added 'videoram=16m' to the vfb parameter.
This issue has already been fixed by xen-unstable 17656:13dda75739f2.
TEST
iozone3_191 : Pass
lmbench-3.0-a5: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
Test Start Time: Thu May 29 15:57:22 2008
-
Testcase Result Exit Value
-- --
abort01
: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
On ia64, the changeset 17961:9cf72db44ee9 cause a compilation error,
`PAGE_SIZE' undeclared. XC_PAGE_SIZE is correct.
Best regards,
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1215569158 -32400
# Node ID
: Pass
lmbench-3.0-a5: Pass
Best regards,
KUWAMURA Shin'ya and Fujitsu members
Thu Jul 10 11:21:04 JST 2008
Test Start Time: Thu Jul 10 11:21:04 2008
-
Testcase Result Exit Value
(2P, with PV-on-HVM drivers)
CONFIG_QEMU : ioemu
Best regards,
--
KUWAMURA Shin'ya
(XEN) ia64_fault, vector=0x18, ifa=0xf040fb8a0010, iip=0xf400040638e0,
ipsr=0x101008226038, isr=0x00800030
(XEN) General Exception: IA-64 Reserved Register/Field fault (data access
(ia64/linux-2.6.18-xen)
126:d255b2cfdd5a (efi-vfirmware)
Dom0 OS : RHEL4 U2 (2P)
DomU OS : RHEL4 U2 (8P, using tap:aio)
CONFIG_QEMU : ioemu
Best regards,
--
KUWAMURA Shin'ya
(XEN) *** xen_handle_domain_access: exception table lookup
-3.0-a5: Pass
DomVTi: CRASH
Best regards,
KUWAMURA Shin'ya and Fujitsu members
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Hi,
On [EMAIL PROTECTED]
Isaku Yamahata wrote:
Could you try the following patch?
Yes, I will test it.
Best regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64
PV-on-HVM drivers,
and domid 6 was created with PV-on-HVM drivers.
Thus, this issue was caused by PV-on-HVM drivers.
Best regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen
that dom0 hung up.
Without it, dom0 booted and LTP completed on domU.
Best regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
] ld2 r15=[r14]
f4000405fb06: e0 f8 03 fe 49 c0 mov r14=32767;;
f4000405fb0c: f0 70 1c e2 cmp4.eq
p6,p7=r15,r14
Best regards,
--
KUWAMURA Shin'ya
(XEN) ia64_fault, vector=0x18, ifa=0xf411c080, iip=0xf4000405fb00
: 0a 30 38 20 87 38 [MMI] cmp4.eq
p6,p7=r14,r16;;
Best regards,
--
KUWAMURA Shin'ya
(XEN) ia64_fault, vector=0x18, ifa=0xf433c080, iip=0xf4000405f0e0,
ipsr=0x121008226018, isr=0x00800030
(XEN) General Exception: IA-64 Reserved Register/Field fault (data
Hi,
On [EMAIL PROTECTED],
Isaku Yamahata wrote:
On Fri, Jul 25, 2008 at 04:37:25PM +0900, KUWAMURA Shin'ya wrote:
On cset:18134, creating DomVTi with PV-on-HVM drivers causes the
hypervisor panic on both hp rx2620 and Tiger4.
I attached the panic message on hp rx2620.
I tried PV
iozone3_191 : Pass
lmbench-3.0-a5: Pass
DomVTi: CRASH
Best regards,
KUWAMURA Shin'ya and Fujitsu members
Test Start Time: Thu Jul 31 10:33:34 2008
-
Testcase Result Exit Value
,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
:
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
Test Start Time: Thu Aug 7 11:49:30 2008
-
Testcase
drivers.
Best regards,
--
KUWAMURA Shin'ya
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
This adds XEN_DOMCTL_subscribe to xencomm.
Signed-off-by: KUWAMURA Shin'ya [EMAIL PROTECTED]
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1218606077 -32400
# Node ID ba8dd5a100a93d0770d8be000faf7667031f069c
# Parent
Sync domctl.h for XEN_DOMCTL_subscribe
Signed-off-by: KUWAMURA Shin'ya [EMAIL PROTECTED]
--
KUWAMURA Shin'ya
# HG changeset patch
# User KUWAMURA Shin'ya [EMAIL PROTECTED]
# Date 1218605915 -32400
# Node ID 6fdc45f4931e37db85de89a4f45018e25fd52d57
# Parent
Hi,
On [EMAIL PROTECTED],
Isaku Yamahata wrote:
This seems worthwhile for the next release because it's quite trivial.
For 1/2 patch, please sent it to xen-devel?
OK, I resend it to xen-devel.
Best regards,
--
KUWAMURA Shin'ya
___
Xen-ia64
1 - 100 of 196 matches
Mail list logo
