[Xen-ia64-devel] Weekly benchmark results [ww37]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 11456:3e4fa8b5b245
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: 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,
Fujita and Fujitsu members


ltp-domU-20060914.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [ww36]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 11416:685bf9b75eb1
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 1/817 FAIL (see attachment)
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060907.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [ww35]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 11333:586c5fe8cf3e
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

issues: 
 - I found a small bug.
   When I tried the compile with specifying KERNELS=linux-2.6-xenU,
   the process was stopped at old-config. 
   But, it'll be fixed by the Akio's domU_config.patch.

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,
Fujita and Fujitsu members


ltp-domU-20060831.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [ww34]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 11265:3e54734e55f3
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

SUMMARY:
 -
issues: 
 -

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,
Fujita and Fujitsu members


ltp-domU-20060824.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [ww33]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 11045:8c6bb45901e7 with Yongkang's xend-config.sxp
patch
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : Pass
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members



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

RE: [Xen-ia64-devel] Weekly benchmark results [ww32]

[yo.fujita]

Hi

Sorry, please disregard the following!
Because I forgot make uninstall in the
process of building this cset...
Actually this cset has a problem that xend cannot be
started. Is this issue already known in xen-devel?

Thanks,
Fujita
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of yo.fujita
 Sent: Thursday, August 10, 2006 3:31 PM
 To: xen-ia64-devel@lists.xensource.com
 Subject: [Xen-ia64-devel] Weekly benchmark results [ww32]
 
 Hi, all
 
 I will inform this week's benchmark result.
 
 The tools used now is as follows.
  - unixbench4.1.0
  - bonnie++-1.03
  - ltp-full-20060306
  - iozone3_191
  - lmbench-3.0-a5
 
 TEST ENVIRONMENT
 Machine  : Tiger4
 KERN : 2.6.16.13-xen
 changeset: 11031:fc6c3d866477
 Dom0 OS  : RHEL4 U2 (no SMP)
 DomU OS  : RHEL4 U2 (2P)
 No. of DomU's: 1
 Sched: credit
 
 SUMMARY:
  -
 issues:
  - In Tiger4, the following message was outputted periodically
on a display of the domU.
 
kernel unaligned access to 0xe0001a94801e,
ip=0xa001009537b1
kernel unaligned access to 0xe0001a94801e,
ip=0xa00100953860
kernel unaligned access to 0xe0001a94802e,
ip=0xa00100953a70
kernel unaligned access to 0xe0001a94801e,
ip=0xa00100953af0
 
 TEST RESULT
 unixbench4.1.0: Pass
 bonnie++-1.03　   : Pass
 ltp-full-20060306 : Pass
 iozone3_191   : Pass
 lmbench-3.0-a5: Pass
 
 Thanks and best regards,
 Fujita and Fujitsu members
 
 
 
 ___
 Xen-ia64-devel mailing list
 Xen-ia64-devel@lists.xensource.com
 http://lists.xensource.com/xen-ia64-devel



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

RE: [Xen-ia64-devel] Weekly benchmark results [ww32]

[yo.fujita]

Hi Yongkang,

Thanks for your help!
I confirmed that xend was working successfully 
with your patch:-)

Thanks,
Fujita
 -Original Message-
 From: You, Yongkang [mailto:[EMAIL PROTECTED]
 Sent: Thursday, August 10, 2006 4:26 PM
 To: yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww32]
 
 Hi Fujita,
 
 Xen-devel also met issue.
 We can use following patch can resolve it. Have a try.
 
 diff -r 0e32095a7b46 tools/examples/xend-config.sxp
 --- a/tools/examples/xend-config.sxp  Wed Aug  9 21:34:27 2006 +0100
 +++ b/tools/examples/xend-config.sxp  Thu Aug 10 10:52:41 2006 +0800
 @@ -54,7 +54,7 @@
  #  (xend-relocation-hosts-allow '^localhost$ ^.*\.example\.org$')
  #
  #(xend-relocation-hosts-allow '')
 -(xend-relocation-hosts-allow '^localhost$ ^localhost\.localdomain$')
 +(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
 
  # The limit (in kilobytes) on the size of the console buffer
  #(console-limit 1024)
 
 Best Regards,
 Yongkang (Kangkang) 永康
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
yo.fujita
 Sent: 2006年8月10日 15:20
 To: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww32]
 
 Hi
 
 Sorry, please disregard the following!
 Because I forgot make uninstall in the
 process of building this cset...
 Actually this cset has a problem that xend cannot be
 started. Is this issue already known in xen-devel?
 
 Thanks,
 Fujita
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
 yo.fujita
  Sent: Thursday, August 10, 2006 3:31 PM
  To: xen-ia64-devel@lists.xensource.com
  Subject: [Xen-ia64-devel] Weekly benchmark results [ww32]
 
  Hi, all
 
  I will inform this week's benchmark result.
 
  The tools used now is as follows.
   - unixbench4.1.0
   - bonnie++-1.03
   - ltp-full-20060306
   - iozone3_191
   - lmbench-3.0-a5
 
  TEST ENVIRONMENT
  Machine  : Tiger4
  KERN : 2.6.16.13-xen
  changeset: 11031:fc6c3d866477
  Dom0 OS  : RHEL4 U2 (no SMP)
  DomU OS  : RHEL4 U2 (2P)
  No. of DomU's: 1
  Sched: credit
 
  SUMMARY:
   -
  issues:
   - In Tiger4, the following message was outputted periodically
 on a display of the domU.
 
 kernel unaligned access to 0xe0001a94801e,
 ip=0xa001009537b1
 kernel unaligned access to 0xe0001a94801e,
 ip=0xa00100953860
 kernel unaligned access to 0xe0001a94802e,
 ip=0xa00100953a70
 kernel unaligned access to 0xe0001a94801e,
 ip=0xa00100953af0
 
  TEST RESULT
  unixbench4.1.0: Pass
  bonnie++-1.03　   : Pass
  ltp-full-20060306 : Pass
  iozone3_191   : Pass
  lmbench-3.0-a5: Pass
 
  Thanks and best regards,
  Fujita and Fujitsu members
 
 
 
  ___
  Xen-ia64-devel mailing list
  Xen-ia64-devel@lists.xensource.com
  http://lists.xensource.com/xen-ia64-devel
 
 
 
 ___
 Xen-ia64-devel mailing list
 Xen-ia64-devel@lists.xensource.com
 http://lists.xensource.com/xen-ia64-devel



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

[Xen-ia64-devel] Weekly benchmark results [ww31]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10922:561df7d9cecc
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

issues:
 - There occurred hang with domU when running LTP.
   This is same as a last week.
   However, it was passed when applied Isaku's patch (fix vDSO
   Paravirtualization).

 - In Tiger4, the following message was outputted periodically 
   on a display of the domU.
   
   kernel unaligned access to 0xe0001ba6801e, ip=0xa00100701da1
   kernel unaligned access to 0xe0001ba6801e, ip=0xa00100701e71
   kernel unaligned access to 0xe0001ba6801e, ip=0xa00100701f20
   kernel unaligned access to 0xe0001ba6802e, ip=0xa00100702130
   kernel unaligned access to 0xe0001ba6801e, ip=0xa001007021b0

   Is there anyone had the same case? 
  

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20060306 : FAIL
iozone3_191   : PASS
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujitsu members



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

[Xen-ia64-devel] Weekly benchmark results [ww30]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10811:254c090854de
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

issues: 
 - The LTP is all hang in 3times testing.
   It was caused always in same testing fsync02
   And it couldn't reproduce when running fsync02 only.
   I'm not sure why this occurs. 

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : FAIL
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members



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

[Xen-ia64-devel] dom0-smp issue.

[yo.fujita]

Hi

I will report a new issue, which was found by Yongkang at first.

As already reported by Yongkang, we also met the same dom0-smp issue.
Our test environment is as below.

cset  :10700
physical CPUs :3 (2 cores)
HyperThred:enable

We tried 3 patterns of tests.
The first testing was done with the following parameters in elilo.conf.

append=dom0_max_vcpus=4 com2=115200,8n1 console=com2 sched=bvt
tbuf_size=128 -- nomca console=tty0 console=ttyS1,115200,8n1 rhgb
root=/dev/sda2

System can boot up. But I can see only 3 CPUs in /proc/cpuinfo.
And xm vcpu-list result is below.
[EMAIL PROTECTED] ~]# xm vcpu-list
Name  ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0   0 00   r-- 351.5  0
Domain-0   0 11   r-- 351.2  any cpu
Domain-0   0 22   r-- 350.9  any cpu
Domain-0   0 3-   --p   0.0  any cpu

In addition, I tried other test with parameter 8 and 0 of dom0_max_vcpus=.
Each the results are as below.
#case param 8
[EMAIL PROTECTED] ~]# xm vcpu-l
Name  ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0   0 00   r-- 643.4  0
Domain-0   0 11   r-- 643.1  any cpu
Domain-0   0 22   r-- 642.9  any cpu
Domain-0   0 3-   --p   0.0  any cpu
Domain-0   0 4-   --p   0.0  any cpu
Domain-0   0 5-   --p   0.0  any cpu
Domain-0   0 6-   --p   0.0  any cpu
Domain-0   0 7-   --p   0.0  any cpu

#case param 0
[EMAIL PROTECTED] ~]# xm vcpu-l
Name  ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0   0 00   r-- 176.4  0
Domain-0   0 11   r-- 176.1  any cpu
Domain-0   0 22   r-- 175.9  any cpu
Domain-0   0 3-   --p   0.0  any cpu
Domain-0   0 4-   --p   0.0  any cpu
Domain-0   0 5-   --p   0.0  any cpu
Domain-0   0 6-   --p   0.0  any cpu
Domain-0   0 7-   --p   0.0  any cpu
Domain-0   0 8-   --p   0.0  any cpu
Domain-0   0 9-   --p   0.0  any cpu
Domain-0   010-   --p   0.0  any cpu
Domain-0   011-   --p   0.0  any cpu

Through all the tests, active VCPUs are only 3 and others are p. 
I think xen0 can only recognize the 1st CPU of each physical CPU.

Thanks,
Fujita



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

RE: [Xen-ia64-devel] dom0-smp issue.

[yo.fujita]

Hi Tristan, Isaku,

Thanks for your reply and sorry for my ignorance...
I tried recompile with CONFIG_NR_CPUS=8.
As it turned out, I can boot up with 4 CPUs when specifying
dom0_max_vcpus=4.
[EMAIL PROTECTED] ~]# xm vcpu-l
Name  ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0   0 00   r-- 193.1  0
Domain-0   0 11   r-- 192.8  any cpu
Domain-0   0 22   r-- 192.6  any cpu
Domain-0   0 33   r-- 192.3  any cpu

But, I could see only 6 CPUs when I specified dom0_max_vcpus=8. (see
attachment)
The #3 CPU's socket of this machine is empty.
I think the empty CPU's socket is not recognized.
Is this correct work?

[EMAIL PROTECTED] ~]# xm vcpu-l
Name  ID  VCPU  CPU  State  Time(s)  CPU
Affinity
Domain-0   0 00   r-- 351.8  0
Domain-0   0 11   r-- 351.4  any cpu
Domain-0   0 22   r-- 351.2  any cpu
Domain-0   0 33   r-- 350.9  any cpu
Domain-0   0 44   r-- 350.7  any cpu
Domain-0   0 55   r-- 350.4  any cpu
Domain-0   0 6-   --p   0.0  any cpu
Domain-0   0 7-   --p   0.0  any cpu

Thanks,
Fujita
 -Original Message-
 From: Tristan Gingold [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 27, 2006 11:22 PM
 To: Masaki Kanno; yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: Re: [Xen-ia64-devel] dom0-smp issue.
 
 Le Jeudi 27 Juillet 2006 15:07, Masaki Kanno a écrit :
  Hi Tristan,
 
  Because Fujita already went home, I post console log instead of Fujita.
 Thanks.
 
 I suppose Isaku was right: your kernel was compiled with CONFIG_NR_CPUS=4,
and
 according to the MADT, the fourth processor is not enabled.
 You should configure your kernel with 16 cpus.
 
 Tristan.


dmesg_dom0_smp.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

RE: [Xen-ia64-devel] why does xenU console stop atFreeingunusedkernel memory:304KB freed?

[yo.fujita]

Hi Alex, Akio,

Thanks for your advice.
 Hopefully the domU console issues are related
 to using older tools.
The domU console issues occurred on RHEL4U2 which had no compile error.

Thanks,
Fujita
 -Original Message-
 From: Alex Williamson [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 07, 2006 1:56 PM
 To: Akio Takebe
 Cc: yo.fujita; 'Zhang, Jingke'; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] why does xenU console stop
 atFreeingunusedkernel memory:304KB freed?
 
 On Fri, 2006-07-07 at 13:41 +0900, Akio Takebe wrote:
  Hi, Fujita
 
  The compile error is a bug of fedora core6.
  fedoracore6 don't have linux/compile.h in glibc-kernheaders.
 
I agree, my build system has compiler.h provided by the
 linux-kernel-headers package (Debian).  You could try copying
 linux-2.6.16.13-xen/include/linux/compiler.h to /usr/include/linux to
 see if tools will build.  Hopefully the domU console issues are related
 to using older tools.  Thanks,
 
   Alex
 
 --
 Alex Williamson HP Open Source  Linux Org.




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

RE: [Xen-ia64-devel] why does xenU console stop atFreeingunusedkernel memory:304KB freed?

[yo.fujita]

Hi Akio,

Thank you for your advice.
It works successfully!
It was fixed by small changes in domU's config and inittab.
I edited lines as below.

#domU's config
Before editing: extra = nomca xencons=tty0 console=tty0 3
After editing : extra = nomca console=tty0 3

#/etc/inittab
Before editing:
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty0
#1:2345:respawn:/sbin/mingetty tty1
#2:2345:respawn:/sbin/mingetty tty2
#3:2345:respawn:/sbin/mingetty tty3
#4:2345:respawn:/sbin/mingetty tty4
#5:2345:respawn:/sbin/mingetty tty5
#6:2345:respawn:/sbin/mingetty tty6

After editing:
# Run gettys in standard runlevels
#1:2345:respawn:/sbin/mingetty tty0
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

Thanks,
Fujita
 -Original Message-
 From: Akio Takebe [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 07, 2006 4:44 PM
 To: yo.fujita; 'Alex Williamson'
 Cc: 'Zhang, Jingke'; xen-ia64-devel@lists.xensource.com; Akio Takebe
 Subject: RE: [Xen-ia64-devel] why does xenU console stop
 atFreeingunusedkernel memory:304KB freed?
 
 Hi, Fujita
 
 I can use domU's console with
 http://free.linux.hp.com/~awilliam/20060706-init/.
 The below is my config file.
 
 [EMAIL PROTECTED] fujita]# cat /etc/xen/takebe
 kernel = /boot/efi/efi/xen/vmlinuz-2.6.16.13-xen-takebe
 ramdisk = /boot/efi/efi/xen/initrd-2.6.16.13-xen.img-takebe
 memory = 512
 name = rhel4-060707
 disk = [ 'file:/root/rhel4_1.img,hda1,w' ]
 vif = [ '' ]
 root = /dev/hda1 ro
 extra = nomca nosmp console=tty0 3
 [EMAIL PROTECTED] fujita]# mount -o loop /root/rhel4_1.img /mnt/
 [EMAIL PROTECTED] fujita]# cat /mnt/etc/inittab
 #
 # inittab   This file describes how the INIT process should set up
 #   the system in a certain run-level.
 #
 # Author:   Miquel van Smoorenburg, [EMAIL PROTECTED]
 #   Modified for RHS Linux by Marc Ewing and Donnie Barnes
 #
 
 # Default runlevel. The runlevels used by RHS are:
 #   0 - halt (Do NOT set initdefault to this)
 #   1 - Single user mode
 #   2 - Multiuser, without NFS (The same as 3, if you do not have
networking)
 #   3 - Full multiuser mode
 #   4 - unused
 #   5 - X11
 #   6 - reboot (Do NOT set initdefault to this)
 #
 id:3:initdefault:
 
 # System initialization.
 si::sysinit:/etc/rc.d/rc.sysinit
 
 l0:0:wait:/etc/rc.d/rc 0
 l1:1:wait:/etc/rc.d/rc 1
 l2:2:wait:/etc/rc.d/rc 2
 l3:3:wait:/etc/rc.d/rc 3
 l4:4:wait:/etc/rc.d/rc 4
 l5:5:wait:/etc/rc.d/rc 5
 l6:6:wait:/etc/rc.d/rc 6
 
 # Trap CTRL-ALT-DELETE
 ca::ctrlaltdel:/sbin/shutdown -t3 -r now
 
 # When our UPS tells us power has failed, assume we have a few minutes
 # of power left.  Schedule a shutdown for 2 minutes from now.
 # This does, of course, assume you have powerd installed and your
 # UPS connected and working correctly.
 pf::powerfail:/sbin/shutdown -f -h +2 Power Failure; System Shutting
Down
 
 # If power was restored before the shutdown kicked in, cancel it.
 pr:12345:powerokwait:/sbin/shutdown -c Power Restored; Shutdown
Cancelled
 
 
 # Run gettys in standard runlevels
 #1:2345:respawn:/sbin/mingetty tty0
 1:2345:respawn:/sbin/mingetty tty1
 2:2345:respawn:/sbin/mingetty tty2
 3:2345:respawn:/sbin/mingetty tty3
 4:2345:respawn:/sbin/mingetty tty4
 5:2345:respawn:/sbin/mingetty tty5
 6:2345:respawn:/sbin/mingetty tty6
 
 # Run xdm in runlevel 5
 x:5:respawn:/etc/X11/prefdm -nodaemon
 
 Best Regards,
 
 Akio Takebe
 
 
 Hi Alex, Akio,
 
 Thanks for your advice.
  Hopefully the domU console issues are related
  to using older tools.
 The domU console issues occurred on RHEL4U2 which had no compile error.
 
 Thanks,
 Fujita
  -Original Message-
  From: Alex Williamson [mailto:[EMAIL PROTECTED]
  Sent: Friday, July 07, 2006 1:56 PM
  To: Akio Takebe
  Cc: yo.fujita; 'Zhang, Jingke'; xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] why does xenU console stop
  atFreeingunusedkernel memory:304KB freed?
 
  On Fri, 2006-07-07 at 13:41 +0900, Akio Takebe wrote:
   Hi, Fujita
  
   The compile error is a bug of fedora core6.
   fedoracore6 don't have linux/compile.h in glibc-kernheaders.
 
 I agree, my build system has compiler.h provided by the
  linux-kernel-headers package (Debian).  You could try copying
  linux-2.6.16.13-xen/include/linux/compiler.h to /usr/include/linux to
  see if tools will build.  Hopefully the domU console issues are related
  to using older tools.  Thanks,
 
 Alex
 
  --
  Alex Williamson HP Open Source  Linux Org.
 
 
 




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

[Xen-ia64-devel] Weekly benchmark results [ww27]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10665:f24993f27cc4
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1
Sched: credit

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 12/817
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060707.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

RE: [Xen-ia64-devel] why does xenU console stop at Freeing unusedkernel memory:304KB freed?

[yo.fujita]

Hi Zhang and all,

We also had same your issue on cset 10665 too.
And as you said, that's okay to ping/ssh domU.
In addition, we found a new issue that is
compile failure(make tools) when using the same
cset on FedoraCore6. please see attachment.

Thanks,
Fujita

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zhang,
Jingke
Sent: Friday, July 07, 2006 11:14 AM
To: xen-ia64-devel@lists.xensource.com
Subject: [Xen-ia64-devel] why does xenU console stop at Freeing
unusedkernel memory:304KB freed?

Hi all,
　　On Cset 10665, when I create a xenU domain I find the console stayed at
“Freeing unused kernel memory:304KB freed”. But I am sure that it has been
created. Because I can ping its dhcp_hostname and I can use ssh to log on
it.
　　What is wrong in the xenU console? Thank you.


compile.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [ww26]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10559:4b51d081378d
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 8/817 FAIL (Please see the attached files)
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060629.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

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

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10443
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1

SUMMARY:
 - We used 2cpus on the domU testing.
 - We used sched=credit.
 - We applied the following patch, which have been already
   applied in xen-unstable.hg tree, for keeping work the credit 
   scheduler on the SMP.
--- a/xen/common/sched_credit.c2006-06-22 07:20:52.0 +0900
+++ b/xen/common/sched_credit.c2006-06-22 08:21:05.0 +0900
@@ -967,9 +967,6 @@
 if ( peer_cpu == cpu )
 break;

-BUG_ON( peer_cpu = csched_priv.ncpus );
-BUG_ON( peer_cpu == cpu );
-
 /*
  * Get ahold of the scheduler lock for this peer CPU.
  *
@@ -1072,7 +1069,6 @@
 ret.task = snext-vcpu;

 CSCHED_VCPU_CHECK(ret.task);
-BUG_ON( !vcpu_runnable(ret.task) );

 return ret;
 }

issues: 
 - The problem occurred in the last week's test was not
   reproduced.

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 8/817 FAIL (Please see the attached files)
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060622.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

Hi Yongkang,

Thanks for your information!
We also must try the latest changeset.
If it happens again, the cause is in our environment.
I'll inform you a result. Please wait for a while.

Thanks,
Fujita
 -Original Message-
 From: You, Yongkang [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 19, 2006 3:37 PM
 To: yo.fujita; Alex Williamson
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Hi Fujita,
 
 I tried the latest Changeset 10419. But I couldn't reproduce this problem
in
 my box. Is it fixed? I create and destroy SMP XenU for more than 100
times.
 And try to make kernels in xenU 2 times. I didn't meet the xen0 hang.
 
 My box has 3072M memory. Xen0 has 512M, xenU has 512M. XenU has been
assigned
 with 2 CPUs.
 
 Best Regards,
 Yongkang (Kangkang) 永康
 
 -Original Message-
 From: yo.fujita [mailto:[EMAIL PROTECTED]
 Sent: 2006年6月19日 10:27
 To: You, Yongkang; 'Alex Williamson'
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
  Hi Fujita,
 
  Maybe it is not guest image issue. In our nightly testing for XenU, we
 still
  focus on the UP stability and basic booting/destroying testing.
Automatic
 SMP
  XenU isn't fully added into nightly testing (will add it this week). I
 noticed
  your report mentioned that the stress testing and keeping
 creating/destroying
  SMP XenU will catch this issue. I can do some trying to see if I can
 reproduce.
 Hi Yongkang,
 
 Thanks for your comments.
 As you said, I meant the problem is not in the image itself but the
stress
 of booting domU. In other words, I thought larger size image takes more
 stress on Xen.
 So I guess a customized image for testing (necessity minimum size)
doesn't
 cause
 the problem.
 We appreciate it if you can try to reproduce these issues.
 
 Thanks,
 Fujita
 
 
 
  Best Regards,
  Yongkang (Kangkang) 永康
 
  -Original Message-
  From: yo.fujita [mailto:[EMAIL PROTECTED]
  Sent: 2006年6月19日 8:53
  To: 'Alex Williamson'; You, Yongkang
  Cc: xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
  
  Thanks Fujita.  Is anyone else seeing these hangs booting domU?
   The Intel status report on the same changeset has no indication of
   dom0 hangs on their tests.
  Hi Alex, Yongkang,
  
   In Fujitsu, it's only me who saw this problem because few developers
 have
  started any tests relating to SMP.
  I think the reason why Intel's results was not match to ours is the
  difference of stress on booting SMP domU because the our guest image
is
 just
  only a copy of root file system of native Linux, which any functions
was
 not
  edited.
  
  My domU environment.
  Disk size :5G
  OS:RHEL4U2
  Memory:512M
  CPUs  :2
  Yongkang, do you have any comments?
  
   Has anything else changed in the test environment?  Thanks,
  No. We switched this test to SMP from UP two weeks ago.
  
  Thanks,
  Fujita



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

RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

Yongkang,

I have a request.
I'm using a scheduler credit for test.
If you're using other scheduler, can you try the credit?

Thanks,
Fujita
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of yo.fujita
 Sent: Monday, June 19, 2006 4:03 PM
 To: 'You, Yongkang'; 'Alex Williamson'
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Hi Yongkang,
 
 Thanks for your information!
 We also must try the latest changeset.
 If it happens again, the cause is in our environment.
 I'll inform you a result. Please wait for a while.
 
 Thanks,
 Fujita
  -Original Message-
  From: You, Yongkang [mailto:[EMAIL PROTECTED]
  Sent: Monday, June 19, 2006 3:37 PM
  To: yo.fujita; Alex Williamson
  Cc: xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
  Hi Fujita,
 
  I tried the latest Changeset 10419. But I couldn't reproduce this
problem
 in
  my box. Is it fixed? I create and destroy SMP XenU for more than 100
 times.
  And try to make kernels in xenU 2 times. I didn't meet the xen0 hang.
 
  My box has 3072M memory. Xen0 has 512M, xenU has 512M. XenU has been
 assigned
  with 2 CPUs.
 
  Best Regards,
  Yongkang (Kangkang) 永康
 
  -Original Message-
  From: yo.fujita [mailto:[EMAIL PROTECTED]
  Sent: 2006年6月19日 10:27
  To: You, Yongkang; 'Alex Williamson'
  Cc: xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
  
   Hi Fujita,
  
   Maybe it is not guest image issue. In our nightly testing for XenU,
we
  still
   focus on the UP stability and basic booting/destroying testing.
 Automatic
  SMP
   XenU isn't fully added into nightly testing (will add it this week).
I
  noticed
   your report mentioned that the stress testing and keeping
  creating/destroying
   SMP XenU will catch this issue. I can do some trying to see if I can
  reproduce.
  Hi Yongkang,
  
  Thanks for your comments.
  As you said, I meant the problem is not in the image itself but the
 stress
  of booting domU. In other words, I thought larger size image takes more
  stress on Xen.
  So I guess a customized image for testing (necessity minimum size)
 doesn't
  cause
  the problem.
  We appreciate it if you can try to reproduce these issues.
  
  Thanks,
  Fujita
  
  
  
   Best Regards,
   Yongkang (Kangkang) 永康
  
   -Original Message-
   From: yo.fujita [mailto:[EMAIL PROTECTED]
   Sent: 2006年6月19日 8:53
   To: 'Alex Williamson'; You, Yongkang
   Cc: xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
   
   Thanks Fujita.  Is anyone else seeing these hangs booting domU?
The Intel status report on the same changeset has no indication of
dom0 hangs on their tests.
   Hi Alex, Yongkang,
   
In Fujitsu, it's only me who saw this problem because few
developers
  have
   started any tests relating to SMP.
   I think the reason why Intel's results was not match to ours is the
   difference of stress on booting SMP domU because the our guest image
 is
  just
   only a copy of root file system of native Linux, which any functions
 was
  not
   edited.
   
   My domU environment.
   Disk size :5G
   OS:RHEL4U2
   Memory:512M
   CPUs  :2
   Yongkang, do you have any comments?
   
Has anything else changed in the test environment?  Thanks,
   No. We switched this test to SMP from UP two weeks ago.
   
   Thanks,
   Fujita
 
 
 
 ___
 Xen-ia64-devel mailing list
 Xen-ia64-devel@lists.xensource.com
 http://lists.xensource.com/xen-ia64-devel



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

RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

Hi Yongkang, Alex,

I tried the latest cset 10419 too.
And the same problem was reproduced.
I think this may be caused by the credit scheduler.
Now our developers are researching this problem.

Setting
server  :tiger4
dom0mem :512M
domUmem :512M
domU cpus   :2
sched   :credit

Test details
create 3/10 hung with dom0.
destroy 4/7 hung with dom0.

Thanks,
Fujita
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of yo.fujita
 Sent: Monday, June 19, 2006 4:21 PM
 To: 'You, Yongkang'; 'Alex Williamson'
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Yongkang,
 
 I have a request.
 I'm using a scheduler credit for test.
 If you're using other scheduler, can you try the credit?
 
 Thanks,
 Fujita
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
yo.fujita
  Sent: Monday, June 19, 2006 4:03 PM
  To: 'You, Yongkang'; 'Alex Williamson'
  Cc: xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
  Hi Yongkang,
 
  Thanks for your information!
  We also must try the latest changeset.
  If it happens again, the cause is in our environment.
  I'll inform you a result. Please wait for a while.
 
  Thanks,
  Fujita
   -Original Message-
   From: You, Yongkang [mailto:[EMAIL PROTECTED]
   Sent: Monday, June 19, 2006 3:37 PM
   To: yo.fujita; Alex Williamson
   Cc: xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
  
   Hi Fujita,
  
   I tried the latest Changeset 10419. But I couldn't reproduce this
 problem
  in
   my box. Is it fixed? I create and destroy SMP XenU for more than 100
  times.
   And try to make kernels in xenU 2 times. I didn't meet the xen0 hang.
  
   My box has 3072M memory. Xen0 has 512M, xenU has 512M. XenU has been
  assigned
   with 2 CPUs.
  
   Best Regards,
   Yongkang (Kangkang) 永康
  
   -Original Message-
   From: yo.fujita [mailto:[EMAIL PROTECTED]
   Sent: 2006年6月19日 10:27
   To: You, Yongkang; 'Alex Williamson'
   Cc: xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
   
Hi Fujita,
   
Maybe it is not guest image issue. In our nightly testing for XenU,
 we
   still
focus on the UP stability and basic booting/destroying testing.
  Automatic
   SMP
XenU isn't fully added into nightly testing (will add it this
week).
 I
   noticed
your report mentioned that the stress testing and keeping
   creating/destroying
SMP XenU will catch this issue. I can do some trying to see if I
can
   reproduce.
   Hi Yongkang,
   
   Thanks for your comments.
   As you said, I meant the problem is not in the image itself but the
  stress
   of booting domU. In other words, I thought larger size image takes
more
   stress on Xen.
   So I guess a customized image for testing (necessity minimum size)
  doesn't
   cause
   the problem.
   We appreciate it if you can try to reproduce these issues.
   
   Thanks,
   Fujita
   
   
   
Best Regards,
Yongkang (Kangkang) 永康
   
-Original Message-
From: yo.fujita [mailto:[EMAIL PROTECTED]
Sent: 2006年6月19日 8:53
To: 'Alex Williamson'; You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

Thanks Fujita.  Is anyone else seeing these hangs booting
domU?
 The Intel status report on the same changeset has no indication
of
 dom0 hangs on their tests.
Hi Alex, Yongkang,

 In Fujitsu, it's only me who saw this problem because few
 developers
   have
started any tests relating to SMP.
I think the reason why Intel's results was not match to ours is
the
difference of stress on booting SMP domU because the our guest
image
  is
   just
only a copy of root file system of native Linux, which any
functions
  was
   not
edited.

My domU environment.
Disk size :5G
OS:RHEL4U2
Memory:512M
CPUs  :2
Yongkang, do you have any comments?

 Has anything else changed in the test environment?  Thanks,
No. We switched this test to SMP from UP two weeks ago.

Thanks,
Fujita
 
 
 
  ___
  Xen-ia64-devel mailing list
  Xen-ia64-devel@lists.xensource.com
  http://lists.xensource.com/xen-ia64-devel
 
 
 
 ___
 Xen-ia64-devel mailing list
 Xen-ia64-devel@lists.xensource.com
 http://lists.xensource.com/xen-ia64-devel



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

RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of yo.fujita
 Sent: Tuesday, June 20, 2006 9:03 AM
 To: 'You, Yongkang'; 'Alex Williamson'
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Hi Yongkang, Alex,
 
 I tried the latest cset 10419 too.
 And the same problem was reproduced.
 I think this may be caused by the credit scheduler.
 Now our developers are researching this problem.
 
 Setting
 server  :tiger4
 dom0mem :512M
 domUmem :512M
 domU cpus   :2
 sched   :credit
 
 Test details
 create 3/10 hung with dom0.
 destroy 4/7 hung with dom0.
 
 Thanks,
 Fujita
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
yo.fujita
  Sent: Monday, June 19, 2006 4:21 PM
  To: 'You, Yongkang'; 'Alex Williamson'
  Cc: xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
  Yongkang,
 
  I have a request.
  I'm using a scheduler credit for test.
  If you're using other scheduler, can you try the credit?
 
  Thanks,
  Fujita
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf Of
 yo.fujita
   Sent: Monday, June 19, 2006 4:03 PM
   To: 'You, Yongkang'; 'Alex Williamson'
   Cc: xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
  
   Hi Yongkang,
  
   Thanks for your information!
   We also must try the latest changeset.
   If it happens again, the cause is in our environment.
   I'll inform you a result. Please wait for a while.
  
   Thanks,
   Fujita
-Original Message-
From: You, Yongkang [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 3:37 PM
To: yo.fujita; Alex Williamson
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
   
Hi Fujita,
   
I tried the latest Changeset 10419. But I couldn't reproduce this
  problem
   in
my box. Is it fixed? I create and destroy SMP XenU for more than 100
   times.
And try to make kernels in xenU 2 times. I didn't meet the xen0
hang.
   
My box has 3072M memory. Xen0 has 512M, xenU has 512M. XenU has been
   assigned
with 2 CPUs.
   
Best Regards,
Yongkang (Kangkang) 永康
   
-Original Message-
From: yo.fujita [mailto:[EMAIL PROTECTED]
Sent: 2006年6月19日 10:27
To: You, Yongkang; 'Alex Williamson'
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

 Hi Fujita,

 Maybe it is not guest image issue. In our nightly testing for
XenU,
  we
still
 focus on the UP stability and basic booting/destroying testing.
   Automatic
SMP
 XenU isn't fully added into nightly testing (will add it this
 week).
  I
noticed
 your report mentioned that the stress testing and keeping
creating/destroying
 SMP XenU will catch this issue. I can do some trying to see if I
 can
reproduce.
Hi Yongkang,

Thanks for your comments.
As you said, I meant the problem is not in the image itself but the
   stress
of booting domU. In other words, I thought larger size image takes
 more
stress on Xen.
So I guess a customized image for testing (necessity minimum size)
   doesn't
cause
the problem.
We appreciate it if you can try to reproduce these issues.

Thanks,
Fujita



 Best Regards,
 Yongkang (Kangkang) 永康

 -Original Message-
 From: yo.fujita [mailto:[EMAIL PROTECTED]
 Sent: 2006年6月19日 8:53
 To: 'Alex Williamson'; You, Yongkang
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Thanks Fujita.  Is anyone else seeing these hangs booting
 domU?
  The Intel status report on the same changeset has no
indication
 of
  dom0 hangs on their tests.
 Hi Alex, Yongkang,
 
  In Fujitsu, it's only me who saw this problem because few
  developers
have
 started any tests relating to SMP.
 I think the reason why Intel's results was not match to ours is
 the
 difference of stress on booting SMP domU because the our guest
 image
   is
just
 only a copy of root file system of native Linux, which any
 functions
   was
not
 edited.
 
 My domU environment.
 Disk size :5G
 OS:RHEL4U2
 Memory:512M
 CPUs  :2
 Yongkang, do you have any comments?
 
  Has anything else changed in the test environment?  Thanks,
 No. We switched this test to SMP from UP two weeks ago.
 
 Thanks,
 Fujita
  
  
  
   ___
   Xen-ia64-devel mailing list
   Xen-ia64-devel@lists.xensource.com
   http://lists.xensource.com/xen-ia64-devel
 
 
 
  ___
  Xen-ia64-devel mailing list
  Xen-ia64

RE: [Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

 Hi Fujita,
 
 Maybe it is not guest image issue. In our nightly testing for XenU, we
still
 focus on the UP stability and basic booting/destroying testing. Automatic
SMP
 XenU isn't fully added into nightly testing (will add it this week). I
noticed
 your report mentioned that the stress testing and keeping
creating/destroying
 SMP XenU will catch this issue. I can do some trying to see if I can
reproduce.
Hi Yongkang,

Thanks for your comments.
As you said, I meant the problem is not in the image itself but the stress
of booting domU. In other words, I thought larger size image takes more
stress on Xen.
So I guess a customized image for testing (necessity minimum size) doesn't
cause
the problem.
We appreciate it if you can try to reproduce these issues.

Thanks,
Fujita


 
 Best Regards,
 Yongkang (Kangkang) 永康
 
 -Original Message-
 From: yo.fujita [mailto:[EMAIL PROTECTED]
 Sent: 2006年6月19日 8:53
 To: 'Alex Williamson'; You, Yongkang
 Cc: xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [ww24]
 
 Thanks Fujita.  Is anyone else seeing these hangs booting domU?
  The Intel status report on the same changeset has no indication of
  dom0 hangs on their tests.
 Hi Alex, Yongkang,
 
  In Fujitsu, it's only me who saw this problem because few developers
have
 started any tests relating to SMP.
 I think the reason why Intel's results was not match to ours is the
 difference of stress on booting SMP domU because the our guest image is
just
 only a copy of root file system of native Linux, which any functions was
not
 edited.
 
 My domU environment.
 Disk size :5G
 OS:RHEL4U2
 Memory:512M
 CPUs  :2
 Yongkang, do you have any comments?
 
  Has anything else changed in the test environment?  Thanks,
 No. We switched this test to SMP from UP two weeks ago.
 
 Thanks,
 Fujita



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

[Xen-ia64-devel] Weekly benchmark results [ww24]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10414:fbc0e953732e
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1

SUMMARY:
 - In this week, we used 2cpu on the domU test as last week.
issues: 
 - We came across many hangs in this week's test and all of
   them was happened with dom0.
- The number of hangs in the process of booting domU : 7/10
- The number of hangs in unixbench testing : 2/2
   So we gave up the test on this cset.
   
   And I tested whether Isaku's patch as below can fix the hang of 
   LMbench bandwidth kept occurring in these days.
   Great! This was Pass.
- 10385: 511ced948390 (work around for skbuff_ctor() on 
   non-privileged domain)
- 10411: 4f0bc5744557 (Network buffers do not need to be 
   multi-page contiguous)


TEST RESULT
unixbench4.1.0: 3/3 FAIL
bonnie++-1.03　   : Pass
ltp-full-20060306 : N/A
iozone3_191   : N/A (bandwidth test was pass.)
lmbench-3.0-a5: N/A

Thanks and best regards,
Fujita and Fujitsu members



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

[Xen-ia64-devel] Weekly benchmark results (ww23)

[yo.fujita]

Hi, all

I will inform this week's benchmark results.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10255:4e78528e3480
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (2P)
No. of DomU's: 1

SUMMARY:
 - In this week, we tried guest-smp, which is two CPUs.
issues: 
 - LTP was hung in fsync02 on domU.
 - lmbench was hung in  Bandwidth measurements on domU.

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 2/2 FAIL
iozone3_191   : Pass
lmbench-3.0-a5: 1 FAIL

Thanks and best regards,
Fujita and Fujitsu members



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

[Xen-ia64-devel] Weekly benchmark results [4/4 week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16.13-xen
changeset: 10154:c7e8d1673140
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 - This is the first attempt in VP_ enable.
issues: 
 - lmbench was hung every time in  Bandwidth measurements on domU.
   Now, I'm searching for the source to specify the cause.

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20060306 : 2/817 FAIL (Please see the attached files)
iozone3_191   : PASS
lmbench-3.0-a5: 3 FAIL

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060525.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [4/3 week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tools used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16-xen
changeset: 10015:99f880fea7e1
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : FAIL 2/817
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060518.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [4/5 week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16-xen
changeset: 9858:b3cc9b6e470e
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20060306 : 2/817 FAIL (Please see the attached files)
iozone3_191   : PASS
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060427.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [4/4 week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16-xen
changeset: 9744:7ed6c203efe9
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20060306 : 2/817 FAIL (Please see the attached files)
iozone3_191   : PASS
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060420.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [3/5th 4/1st week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16-xen
changeset: 9478:986538da9be0
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY: 
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20060306 : 51/817 FAIL (Please see the attached files)
iozone3_191   : PASS
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060330.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] Weekly benchmark results [3/3rd week]

[yo.fujita]

Hi, all

I will inform this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20060306
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.16-rc5-xenU
changeset: 9268:ab05373d6edd
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 - The version of LTP did the up-grade from 20051205 to 20060306.
issues: 
 - Yongkang's dom0 timer issue occurred in my environment.

TEST RESULT
unixbench4.1.0: Pass
bonnie++-1.03　   : Pass
ltp-full-20060306 : 52/817 FAIL
iozone3_191   : Pass
lmbench-3.0-a5: Pass

Thanks and best regards,
Fujita and Fujitsu members


ltp-domU-20060316.log
Description: Binary data
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel

RE: [Xen-ia64-devel] Weekly benchmark results [3/2nd week]

[yo.fujita]

Hi YongKang,

No, I doesn't try LTP on dom0 yet.
I will execute it now.
I will inform the result later.

Thanks,
Fujita
 -Original Message-
 From: You, Yongkang [mailto:[EMAIL PROTECTED]
 Sent: Friday, March 10, 2006 5:06 PM
 To: yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [3/2nd week]
 
 Hi Fujita,
 
 Did you try to run LTP and get the results in xen0 environment?
 
 Best Regards,
 Yongkang (Kangkang) 永康
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
yo.fujita
 Sent: 2006年3月10日 14:32
 To: xen-ia64-devel@lists.xensource.com
 Subject: [Xen-ia64-devel] Weekly benchmark results [3/2nd week]
 
 Hi, all
 
 I will inform this week's benchmark result.
 
 The tool used now is as follows.
  - unixbench4.1.0
  - bonnie++-1.03
  - ltp-full-20051205
  - iozone3_191
  - lmbench-3.0-a5
 
 TEST ENVIRONMENT
 Machine  : Tiger4
 KERN : 2.6.16-rc5-xenU
 changeset: 9157:a693ccb4d581
 Dom0 OS  : RHEL4 U2 (no SMP)
 DomU OS  : RHEL4 U2 (no SMP)
 No. of DomU's: 1
 
 SUMMARY:
  - DomU came to do boot successfully!
 issues:
  -
 
 TEST RESULT
 unixbench4.1.0: PASS
 bonnie++-1.03　   : PASS
 ltp-full-20051205 : 51/816 FAIL (Please see the attached files)
 iozone3_191   : PASS
 lmbench-3.0-a5: PASS
 
 Thanks and best regards,
 Fujita and Fujitsu members



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

[Xen-ia64-devel] Weekly benchmark results [2/3rd week]

[yo.fujita]

Hi,

I tried Xen build by the last changeset of 2/15(Cs: 8828:982b9678af2c).
Then, when Xend start was done by the host machine, the keyboard did hang.

In addition, domU not Boot.
Please look at the attached file. Its xm create log.

TEST ENVIRONMENT
Machine  : Tiger4
changeset: 8828:982b9678af2c
Dom0 OS  : RHEL4 U2 (no SMP)

Thanks
Fujita
[EMAIL PROTECTED] ~]# xm create -f /etc/xen/rhel4-060215 Using config file 
/etc/xen/rhel4-060215.
[xend.XendDomainInfo] DEBUG (XendDomainInfo:177) XendDomainInfo.create(['vm', 
['name', 'rhel4-060215'], ['memory', '512'], ['vcpus', '1'], ['image', 
['linux', ['kernel', '/boot/vmlinux-2.6.16-rc2-xenU-060215'], ['ramdisk', 
'/boot/initrd-2.6.16-rc2-xenU.img-060215'], ['root', '/dev/hda1 ro'], ['args', 
'nomca nosmp xencons=tty0 console=tty0 root=/dev/hda1 3']]], ['device', ['vbd', 
['uname', 'file:/home/takebe/rhel4.img'], ['dev', 'hda1'], ['mode', 'w') 
[xend.XendDomainInfo] DEBUG (XendDomainInfo:283) parseConfig: config is ['vm', 
['name', 'rhel4-060215'], ['memory', '512'], ['vcpus', '1'], ['image', 
['linux', ['kernel', '/boot/vmlinux-2.6.16-rc2-xenU-060215'], ['ramdisk', 
'/boot/initrd-2.6.16-rc2-xenU.img-060215'], ['root', '/dev/hda1 ro'], ['args', 
'nomca nosmp xencons=tty0 console=tty0 root=/dev/hda1 3']]], ['device', ['vbd', 
['uname', 'file:/home/takebe/rhel4.img'], ['dev', 'hda1'], ['mode', 'w' 
[xend.XendDomainInfo] DEBUG (XendDomainInfo:379) parseConfig: result is 
{'ssidref': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'image': 
['linux', ['kernel', '/boot/vmlinux-2.6.16-rc2-xenU-060215'], ['ramdisk', 
'/boot/initrd-2.6.16-rc2-xenU.img-060215'], ['root', '/dev/hda1 ro'], ['args', 
'nomca nosmp xencons=tty0 console=tty0 root=/dev/hda1 3']], 'on_poweroff': 
None, 'cpus': None, 'name': 'rhel4-060215', 'backend': [], 'vcpus': 1, 
'cpu_weight': None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', 
['vbd', ['uname', 'file:/home/takebe/rhel4.img'], ['dev', 'hda1'], ['mode', 
'w']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [xend.XendDomainInfo] 
DEBUG (XendDomainInfo:1142) XendDomainInfo.construct: None 0 
[xend.XendDomainInfo] DEBUG (XendDomainInfo:1174) XendDomainInfo.initDomain: 1 
1.0 [xend] DEBUG (balloon:84) Balloon: free 1420; need 513; done.
[xend] INFO (image:133) buildDomain os=linux dom=1 vcpus=1
[xend] DEBUG (image:171) dom= 1
[xend] DEBUG (image:172) image  = /boot/vmlinux-2.6.16-rc2-xenU-060215
[xend] DEBUG (image:173) store_evtchn   = 1
[xend] DEBUG (image:174) console_evtchn = 2
[xend] DEBUG (image:175) cmdline=  root=/dev/hda1 ro nomca nosmp 
xencons=tty0 console=tty0 root=/dev/hda1 3
[xend] DEBUG (image:176) ramdisk= 
/boot/initrd-2.6.16-rc2-xenU.img-060215
[xend] DEBUG (image:177) vcpus  = 1
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: 0x400-0x4b26f48
 Init. ramdisk: 0x4b28000-0x4e31200
 TOTAL: 0x400-0x4e34000
 ENTRY ADDRESS: 0x400ff20
store_mfn: 0x2683d080, console_mfn: 0x2683d078 [xend] DEBUG 
(blkif:24) exception looking up device number for hda1: [Errno 2] No such file 
or directory: '/dev/hda1'
[xend] DEBUG (DevController:103) DevController: writing {'virtual-device': 
'769', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/1/769'} to /local/domain/1/device/vbd/769.
[xend] DEBUG (DevController:105) DevController: writing {'domain': 
'rhel4-060215', 'frontend': '/local/domain/1/device/vbd/769', 'dev': 'hda1', 
'state': '1', 'params': '/home/takebe/rhel4.img', 'mode': 'w', 'frontend-id': 
'1', 'type': 'file'} to /local/domain/0/backend/vbd/1/769.
[xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details: 
{'ssidref': '0', 'uuid': '41ee8ab8-98f8-1119-329e-64542a95d17d', 'on_reboot': 
'restart', 'start_time': '1140145107.41', 'on_poweroff': 'destroy', 'name': 
'rhel4-060215', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 
'restart', 'image': (linux (kernel /boot/vmlinux-2.6.16-rc2-xenU-060215) 
(ramdisk /boot/initrd-2.6.16-rc2-xenU.img-060215) (root '/dev/hda1 ro') (args 
'nomca nosmp xencons=tty0 console=tty0 root=/dev/hda1 3')), 'maxmem': '512'} 
[xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: 
{'console/ring-ref': '3893', 'console/port': '2', 'name': 'rhel4-060215', 
'console/limit': '1048576', 'vm': '/vm/41ee8ab8-98f8-1119-329e-64542a95d17d', 
'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 
'store/ring-ref': '3894', 'store/port': '1'} [xend] DEBUG (DevController:132) 
Waiting for devices vif.
[xend] DEBUG (DevController:132) Waiting for devices usb.
[xend] DEBUG (DevController:132) Waiting for devices vbd.
[xend] DEBUG (DevController:138) Waiting for 769.
[xend] DEBUG (DevController:403) hotplugStatusCallback 
/local/domain/0/backend/vbd/1/769/hotplug-status.
[xend] ERROR (SrvBase:87) Request wait_for_devices failed.
Traceback (most recent call last):
  File /usr/lib/python/xen/web/SrvBase.py, 

RE: [Xen-ia64-devel] I found 4 exact LTP cases failed in IA64/Xen0 with1700+ cases until now.

[yo.fujita]

Hi Dan, Yongkang,

 Could you share information with each other about what
 LTP tests are passing and failing?
Yes, I think that it is very important.
I match it with a version of his LTP to share information 
with Yongkang.
However, because my information is on domU, the result might be
different from Yongkang.

 I think it is important to have the weekly testing
 but I think that if a test fails on native Linux/ia64,
 we should not consider it as a failure on Xen/ia64.
In my case, LTP on native linux is all success.

Thanks,
Fujita

 -Original Message-
 From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:[EMAIL PROTECTED]
 Sent: Monday, January 30, 2006 9:37 AM
 To: You, Yongkang; xen-ia64-devel@lists.xensource.com; yo.fujita
 Subject: RE: [Xen-ia64-devel] I found 4 exact LTP cases failed in
IA64/Xen0
 with1700+ cases until now.
 
 Yongkang and Fujita --
 
 Could you share information with each other about what
 LTP tests are passing and failing?  I think it is important
 to have the weekly testing but I think that if a test
 fails on native Linux/ia64, we should not consider it
 as a failure on Xen/ia64.
 
 Thanks,
 Dan
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf
  Of You, Yongkang
  Sent: Wednesday, January 25, 2006 4:45 PM
  To: xen-ia64-devel@lists.xensource.com
  Subject: [Xen-ia64-devel] I found 4 exact LTP cases failed in
  IA64/Xen0 with1700+ cases until now.
 
  Hi all,
 
  This is a resend email, because the last email is too large
  to reach the Mailing list. :)
 
  I have reported 4 cases failed or crashed in the past several
  days. Now I have finished a fuller LTP testing, which
  executed 1700+ cases (there are some duplicated cases).
  Excluding the cases that are failed on Native Linux too, I
  only caught 4 special failed cases, which I have reported yet.
 
  Now I have a brief summary:
  ==Test environment=
  Xen0: RHEL4u2
  Xen Source: xen-ia64-unstable 8481
  LTP Source: 2005-12-5
  
 
  The following testcases do Not pass:
  FAIL ltp:syscalls Case alarm04
  FAIL ltp:math float_exp_log
  FAIL ltp:math float_power
  CRASH ltp:crashme crash01
 
  The following is only the summary of testing result. It is
  automatically counted by LTP script. So the total failed case
  number can't show the real IA64 Xen0 status. The exact failed
  cases have been listed above.
 
 Summary Test Report of Last Session
  =
  =Total Pass  Fail NoResult Crash
  =
  =ltp 1739  1692   46 0  1
  stress_part2  22202  0  0
  mm21210  0  0
  nptl  1 1 0  0  0
  multicast 4 1 3  0  0
  commands  118 3  0  0
  pty   3 3 0  0  0
  pipes 6 6 0  0  0
  network_comman7 6 1  0  0
  quickhit 121   1210  0  0
  sched 3 3 0  0  0
  fs54540  0  0
  syscalls 685   6841  0  0
  admin_tools   8 7 1  0  0
  dio   28280  0  0
  fsx   1 0 1  0  0
  ipc   8 8 0  0  0
  math  108 2  0  0
  ltplite  320   3155  0  0
  stress_part1 127   10225 0  0
  crashme   1 0 0  0  1
  stress_part3 298   2962  0  0
  =
  =Total   1739  1692   46 0  1
 
  Best Regards,
  Yongkang (Kangkang) 永康
 
 
  ___
  Xen-ia64-devel mailing list
  Xen-ia64-devel@lists.xensource.com
  http://lists.xensource.com/xen-ia64-devel
 



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

[Xen-ia64-devel] Weekly benchmark results [1/3rd week]

[yo.fujita]

Hi, all

I will inform of this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20051103
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.12-xenU
changeset: 8602:cfa3b96b056d
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 -
issues: 
 -

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20051103 : 49/816 FAIL (Please see the attached files)
iozone3_191   : PASS
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujisu members
Test Start Time: Mon Jan 16 19:47:33 2006
-
Testcase   Result Exit Value
   -- --
abort01PASS   0
accept01   PASS   0
access01   PASS   0
access02   FAIL   6
access03   PASS   0
access04   FAIL   6
access05   FAIL   6
acct01 PASS   0
acct02 PASS   0
adjtimex01 PASS   0
adjtimex02 PASS   0
alarm01PASS   0
alarm02PASS   0
alarm03PASS   0
alarm04FAIL   1
alarm05PASS   0
alarm06PASS   0
alarm07PASS   0
asyncio02  PASS   0
bind01 PASS   0
bind02 PASS   0
brk01  PASS   0
capget01   PASS   0
capget02   PASS   0
capset01   PASS   0
capset02   PASS   0
chdir01PASS   0
chdir01A   PASS   0
chdir02PASS   0
chdir03PASS   0
chdir04PASS   0
chmod01PASS   0
chmod01A   PASS   0
chmod02PASS   0
chmod03FAIL   6
chmod04FAIL   6
chmod05PASS   0
chmod06PASS   0
chmod07PASS   0
chown01PASS   0
chown02PASS   0
chown03PASS   0
chown04FAIL   6
chown05PASS   0
chroot01   FAIL   6
chroot02   PASS   0
chroot03   PASS   0
chroot04   PASS   0
clone01PASS   0
clone02PASS   0
clone03PASS   0
clone04PASS   0
clone05PASS   0
clone06PASS   0
clone07PASS   0
close01PASS   0
close02PASS   0
close08PASS   0
confstr01  PASS   0
connect01  PASS   0
creat01FAIL   6
creat03PASS   0
creat04PASS   0
creat05PASS   0
creat06FAIL   6
creat07PASS   0
creat08PASS   0
creat09PASS   0
dup01  PASS   0
dup02  PASS   0
dup03  PASS   0
dup04  PASS   0
dup05  PASS   0
dup06  PASS   0
dup07  PASS   0
dup201 PASS   0
dup202 PASS   0
dup203 PASS   0
dup204 PASS   0
dup205 PASS   0
execl01PASS   0
execle01   PASS   0
execlp01   PASS   0
execv01PASS   0
execve01   PASS   0
execve02   PASS   

[Xen-ia64-devel] Weekly benchmark results [1/2nd week]

[yo.fujita]

Hi, all

I will inform of this week's benchmark result.

The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20051103
 - iozone3_191
 - lmbench-3.0-a5

TEST ENVIRONMENT
Machine  : Tiger4
KERN : 2.6.12-xenU
changeset: 8474:f31cb5961db3 (1/5 latest)
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1

SUMMARY:
 - DomU did hang while executing iozone3. In the file
   writing test execution.
   The benchmark succeeded when having tested again.
issues: 
 -

TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : PASS
ltp-full-20051103 : 49/816 FAIL (Please see the attached files)
iozone3_191   : FAIL
lmbench-3.0-a5: PASS

Thanks and best regards,
Fujita and Fujisu members
Test Start Time: Fri Jan 13 18:47:16 2006
-
Testcase   Result Exit Value
   -- --
abort01PASS   0
accept01   PASS   0
access01   PASS   0
access02   FAIL   6
access03   PASS   0
access04   FAIL   6
access05   FAIL   6
acct01 PASS   0
acct02 PASS   0
adjtimex01 PASS   0
adjtimex02 PASS   0
alarm01PASS   0
alarm02PASS   0
alarm03PASS   0
alarm04FAIL   1
alarm05PASS   0
alarm06PASS   0
alarm07PASS   0
asyncio02  PASS   0
bind01 PASS   0
bind02 PASS   0
brk01  PASS   0
capget01   PASS   0
capget02   PASS   0
capset01   PASS   0
capset02   PASS   0
chdir01PASS   0
chdir01A   PASS   0
chdir02PASS   0
chdir03PASS   0
chdir04PASS   0
chmod01PASS   0
chmod01A   PASS   0
chmod02PASS   0
chmod03FAIL   6
chmod04FAIL   6
chmod05PASS   0
chmod06PASS   0
chmod07PASS   0
chown01PASS   0
chown02PASS   0
chown03PASS   0
chown04FAIL   6
chown05PASS   0
chroot01   FAIL   6
chroot02   PASS   0
chroot03   PASS   0
chroot04   PASS   0
clone01PASS   0
clone02PASS   0
clone03PASS   0
clone04PASS   0
clone05PASS   0
clone06PASS   0
clone07PASS   0
close01PASS   0
close02PASS   0
close08PASS   0
confstr01  PASS   0
connect01  PASS   0
creat01FAIL   6
creat03PASS   0
creat04PASS   0
creat05PASS   0
creat06FAIL   6
creat07PASS   0
creat08PASS   0
creat09PASS   0
dup01  PASS   0
dup02  PASS   0
dup03  PASS   0
dup04  PASS   0
dup05  PASS   0
dup06  PASS   0
dup07  PASS   0
dup201 PASS   0
dup202 PASS   0
dup203 PASS   0
dup204 PASS   0
dup205 PASS   0
execl01PASS   0
execle01   PASS   0
execlp01  

RE: [Xen-ia64-devel] Weekly benchmark results [1/1st week]

[yo.fujita]

Hi, Dan-san

Sorry for a late mail.
I retried LTP.
As a result, it became an almost similar result.
Total Failures: 52 (Please look at the attached file details.)

The difference is only the following compared with the last result.
762,763c762,763
 gf16   FAIL   1
 gf17   PASS   0
---
 gf16   PASS   0
 gf17   FAIL   1

 - I saw much fewer failures when I tried LTP a couple of
   weeks ago.  Many tests failed for me at first because
   there was not enough disk space.  Do you have enough
   disk space on the domU filesystem?

Yes, Some of the error were the one due to disk space shortage.
After increasing the disk space, I will try again.

Thanks
Fujita

 -Original Message-
 From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:[EMAIL PROTECTED]
 Sent: Monday, January 09, 2006 9:00 AM
 To: yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [1/1st week]
 
 Hi Fujita-san --
 
 Thanks very much for running these tests weekly!
 
 On LTP, a few questions:
 - Are the failures reproducible?  Or are some failures
   random?  (may be the same problem as the gcc failures)
 - Of the 52 failures, I think some of the tests also fail
   on Linux/ia64.  We should probably exclude those (or
   not count them as Xen failures).
 - I saw much fewer failures when I tried LTP a couple of
   weeks ago.  Many tests failed for me at first because
   there was not enough disk space.  Do you have enough
   disk space on the domU filesystem?
 
 Thanks,
 Dan
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf
  Of yo.fujita
  Sent: Saturday, January 07, 2006 1:31 AM
  To: xen-ia64-devel@lists.xensource.com
  Subject: [Xen-ia64-devel] Weekly benchmark results [1/1st week]
 
  Hi, all
 
  I will inform of this week's benchmark result.
 
  The tool used now is as follows.
   - unixbench4.1.0
   - bonnie++-1.03
   - ltp-full-20051103
   - iozone3_191
   - lmbench-3.0-a5
 
  TEST ENVIRONMENT
  Machine  : Tiger4
  KERN : 2.6.12-xenU
  changeset: 8474:22f28fffa0a8 (1/5 latest)
  Dom0 OS  : RHEL4 U2 (no SMP)
  DomU OS  : RHEL4 U2 (no SMP)
  No. of DomU's: 1
 
  SUMMARY:
   - changeset8474, All benchmarks normally ended
  issues:
   -
 
  TEST RESULT
  unixbench4.1.0: PASS
  bonnie++-1.03　   : PASS
  ltp-full-20051103 : 52/816 FAIL (Please see the attached files)
  iozone3_191   : PASS
  lmbench-3.0-a5: PASS
 
  Thanks and best regards,
  Fujita and Fujisu members
 
Test Start Time: Wed Jan 11 18:43:36 2006
-
Testcase   Result Exit Value
   -- --
abort01PASS   0
accept01   PASS   0
access01   PASS   0
access02   FAIL   6
access03   PASS   0
access04   FAIL   6
access05   FAIL   6
acct01 PASS   0
acct02 PASS   0
adjtimex01 PASS   0
adjtimex02 PASS   0
alarm01PASS   0
alarm02PASS   0
alarm03PASS   0
alarm04FAIL   1
alarm05PASS   0
alarm06PASS   0
alarm07PASS   0
asyncio02  PASS   0
bind01 PASS   0
bind02 PASS   0
brk01  PASS   0
capget01   PASS   0
capget02   PASS   0
capset01   PASS   0
capset02   PASS   0
chdir01PASS   0
chdir01A   PASS   0
chdir02PASS   0
chdir03PASS   0
chdir04PASS   0
chmod01PASS   0
chmod01A   PASS   0
chmod02PASS   0
chmod03FAIL   6
chmod04FAIL   6
chmod05PASS   0
chmod06PASS   0
chmod07PASS   0
chown01PASS   0
chown02PASS   0
chown03PASS   0
chown04

RE: [Xen-ia64-devel] Weekly benchmark results [12/4rd week]

[yo.fujita]

Sorry.
I forgot attachment logfile.

Thanks
Fujita

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of yo.fujita
 Sent: Saturday, January 07, 2006 3:01 PM
 To: 'Magenheimer, Dan (HP Labs Fort Collins)';
 xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] Weekly benchmark results [12/4rd week]
 
 Dan,
 
 I retested gcc loop on the changeset 8474.
 To our regret the same phenomenon occurred, this seems to be the same bug
as
 you cited in the previous mail.
 
 I ran the test for about 2 hours and saw segmentation fault 3 times.
 
 In addition, I got the following kernel oops.
  Unable to handle kernel paging request at virtual address
32000f000200
 collect2[22056]: Oops 11012296146944 [1] 
 I attach the result log to this mail.
 
 I'll try to see if I can narrow down the condition that causes this bug.
 
 Thanks
 Fujita
 
  -Original Message-
  From: Magenheimer, Dan (HP Labs Fort Collins)
 [mailto:[EMAIL PROTECTED]
  Sent: Saturday, January 07, 2006 6:13 AM
  To: yo.fujita; xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] Weekly benchmark results [12/4rd week]
 
  I suspect that this is the same problem as reported here:
 
 
 http://lists.xensource.com/archives/html/xen-ia64-devel/2005-12/msg00185.h
  tml
 
  This is the first report on domU. I've only observed it on dom0.
  Because it seems random, it may be very difficult to track
  down.
 
  Dan
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf
   Of yo.fujita
   Sent: Friday, January 06, 2006 3:32 AM
   To: 'yo.fujita'; xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] Weekly benchmark results [12/4rd week]
  
   Hi, all
  
   I had put out the following mail before.
   And, it was pointed out that there was an unexpected value in the
   bench result of DomU.
   Thanks, Eddie.
  
   Please look at the following value.
   dom0:
 C Compiler Throughput   702.0 lpm
   (60 secs, 3 samples)
   domU:
 C Compiler Throughput 64655.7 lpm
   (62 secs, 2 samples)
  
   dom0:
 Shell Scripts (1 concurrent)   2276.3 lpm
   (60 secs, 3 samples)
   domU:
 Shell Scripts (1 concurrent) 473647.0 lpm
   (61 secs, 2 samples)
  
   The value of dom0 and domU is greatly different.
   I investigated this phenomenon.
   As for the understood thing, domU uncommonly abort in gcc.
   Please look at cc_loop.txt of the attached file.
   This is a result of loop only C compile of unixbench.
   When the result is Bad wait status:0xb or 0x100, the value will become
   abnormal.
   As for Shell Scripts, it might be similar.
   the next benchmark will be executed with changeset8474.
  
   Thanks,
   Fujita
  
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
   Behalf Of yo.fujita
Sent: Thursday, December 29, 2005 3:59 PM
To: xen-ia64-devel@lists.xensource.com
Subject: [Xen-ia64-devel] Weekly benchmark results [12/4rd week]
   
Hi,
   
I am investigating stability of Dom0 and DomU by using
   various benchmark
tools.
We Fujitsu contribute with the results of benchmarks to
   this community
periodically from now on.
   
Although it is only the detail result of unixbench this
   time, we will post
the detail result of all benchmarks someday.
   
The tool used now is as follows.
 - unixbench4.1.0
 - bonnie++-1.03
 - ltp-full-20051103
 - iozone3_191
 - lmbench-3.0-a5
   
TEST ENVIRONMENT
Machine  : Tiger4
CPU  : Itanium2 1.5GHz *2 (Madison)
MEM  : 8GB
HDD  : Ultra 320 SCSI 36.7GB(MAS3367NC)
KERN : 2.6.12-xen0
changeset: 8372:7ef565a7cc86 (12/15 latest)
Dom0 OS  : RHEL4 U2 (no SMP)
DomU OS  : RHEL4 U2 (no SMP)
No. of DomU's: 1
   
SUMMARY
 - ltp-full-20051103 :hang in bench testing.
 - Iozone3_191   :hang in bench testing.
 - bonnie++-1.03 :bench is pass. but hang immediately after.
   
issues:
 - If changeset is after 8732, DomU will not start.
   
TEST RESULT
unixbench4.1.0: PASS
bonnie++-1.03　   : FAIL
ltp-full-20051103 : FAIL
iozone3_191   : PASS
lmbench-3.0-a5: PASS
Thanks and best regards,
Fujita and Fujisu members
  
 
 
 
 ___
 Xen-ia64-devel mailing list
 Xen-ia64-devel@lists.xensource.com
 http://lists.xensource.com/xen-ia64-devel
[EMAIL PROTECTED] unixbench-4.1.0]# ./testloop 
Sat Jan  7 11:32:31 JST 2006
current iter=50
current iter=100
current iter=150
current iter=200
current iter=250
current iter=300
current iter=350
current iter=400
current iter=450
current iter=500
current iter=550
current iter=600
current iter=650

RE: [Xen-ia64-devel] DomU does not start.

[yo.fujita]

Hi Dan, Kevin,

Sorry for a late mail. And, thanks for thinking about my problem.
8734 seems to be a future changeset. ;-)
Oops! Sorry it's a typing miss...

I tried the start of domU with changeset:8473 this time.
problem of RAMDISK was able to be cleared this time.
But, the problem occurred newly.
It stops with the mount of root. ( Please look at an attached log.)
I investigated a little.
stop is done with ext3_fill_super of sb_bread.
( /linux-2.6.12-xenU/fs/ext3/super.c )

this is my Configfile. Is there a wrong place?

kernel = /boot/vmlinux-2.6.12-xenU
ramdisk = /boot/initrd-2.6.12-xenU.img
memory = 512
name = rhel4-2
disk = [ 'file:/root/rhel4.img,hda1,w' ]
root = /dev/hda1 ro
extra = nomca nosmp xencons=tty0 console=tty0 3

thanks,
Fujita

 -Original Message-
 From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:[EMAIL PROTECTED]
 Sent: Friday, December 30, 2005 7:37 AM
 To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] DomU does not start.
 
 Committed as cset 8436.  Fujita, please test to see
 if this solves the problem with booting domU with and
 without initrd.
 
 Thanks,
 Dan
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf
  Of Tian, Kevin
  Sent: Thursday, December 29, 2005 2:23 AM
  To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] DomU does not start.
 
  BTW, we may need this patch:
 
  diff -r f218e6ba2653 tools/libxc/xc_linux_build.c
  --- a/tools/libxc/xc_linux_build.c  Fri Dec 23 21:14:21 2005
  +++ b/tools/libxc/xc_linux_build.c  Thu Dec 29 16:43:19 2005
  @@ -397,6 +397,9 @@
   {
   ctxt-initrd.start= vinitrd_start;
   ctxt-initrd.size = initrd_len;
  +} else {
  +ctxt-initrd.start= 0;
  +ctxt-initrd.size = 0;
   }
   strncpy((char *)ctxt-cmdline, cmdline, IA64_COMMAND_LINE_SIZE);
   ctxt-cmdline[IA64_COMMAND_LINE_SIZE-1] = '\0';
 
  Thanks,
  Kevin
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On
  Behalf Of Tian, Kevin
  Sent: 2005年12月29日 17:04
  To: yo.fujita; xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] DomU does not start.
  
  From: yo.fujita
  Sent: 2005年12月29日 16:20
  Hi
  
  I can't start domU after changeset8372.
  applied two patches of changeset 8734 after that.
  However, the following message displays and DomU does not start.
  
  RAMDISK: Couldn't find valid RAM disk image starting at 0 .
  
  Don't someone have information?
  
  Thanks
  Fujita
  
  8734 seems to be a future changeset. ;-)
  
  Do you need initrd to boot your domU image? If yes, you may
  add an option in
  example file:
  
  ramdisk = initrd_name
  
  If no, can you try appending a noinitrd to extra field in
  your example file like:
  
  Extra = 4 noinitrd
  
  I guess there's some issue when domU image file doesn't
  require an initrd.
  
  Thanks,
  Kevin
  
  ___
  Xen-ia64-devel mailing list
  Xen-ia64-devel@lists.xensource.com
  http://lists.xensource.com/xen-ia64-devel
 
  ___
  Xen-ia64-devel mailing list
  Xen-ia64-devel@lists.xensource.com
  http://lists.xensource.com/xen-ia64-devel
 
[EMAIL PROTECTED] xen]# xm create -c rhel4-2
Using config file rhel4-2.
Started domain rhel4-2
Dentry cache hash table entries: 32768 (order: 4, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 3, 131072 bytes) 
Placing software IO TLB between 0x434000 - 0xc34000   
Memory: 217648k/244736k available (7998k code, 26432k reserved, 3484k data, 
256k init)
McKinley Errata 9 workaround not needed; disabling it   
  
Mount-cache hash table entries: 1024 
Boot processor id 0x0/0xc718
SMP mode deactivated.   
Brought up 1 CPUs
Total of 1 processors activated (263.92 BogoMIPS).
checking if image is initramfs... it is   
Freeing initrd memory: 3104kB freed
grant table at e100
Grant table initialized
NET: Registered protocol family 16
ACPI: Subsystem revision 20050309 
ACPI: SCI (ACPI GSI 0) not registered
ACPI: Interpreter enabled
ACPI: Using IOSAPIC for interrupt routing
SCSI subsystem initialized   
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing   
PCI: If a device doesn't work, try pci=routeirq.  If it helps, post a report
perfmon: version 2.0 IRQ 238  
perfmon: Generic PMU detected, 8 PMCs, 4 PMDs, 4 counters (32 bits)
PAL Information Facility v0.5  
perfmon: added sampling format default_format
perfmon_default_smpl: default_format v2.0 registered
Total HugeTLB memory allocated, 0   
Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]).
Initializing Cryptographic API  
pci_hotplug

RE: [Xen-ia64-devel] DomU does not start.

[yo.fujita]

Hi Dan, Kevin,

I try kevin's patch.
Result is reported later.

Thanks,
Fujita

 -Original Message-
 From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:[EMAIL PROTECTED]
 Sent: Friday, January 06, 2006 2:06 AM
 To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] DomU does not start.
 
 Yes, Kevin's fix is now checked in as 8474.
 Please see if this resolves the problem.
 
 Thanks,
 Dan
 
  -Original Message-
  From: Tian, Kevin [mailto:[EMAIL PROTECTED]
  Sent: Thursday, January 05, 2006 4:58 AM
  To: yo.fujita; Magenheimer, Dan (HP Labs Fort Collins);
  xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] DomU does not start.
 
  Hi, Fujita,
  I'm not sure about your target memory layout. But
  generally if you plug a =2G memory bank in your box, you may
  need the patch I sent out yesterday to disable virtual memmap
  in guest. Or else vbd driver doesn't work. If you only have
  1G-like system, then that's possibly a different issue.
 
  Thanks,
  Kevin
 
  -Original Message-
  From: yo.fujita [mailto:[EMAIL PROTECTED]
  Sent: 2006年1月5日 19:07
  To: 'Magenheimer, Dan (HP Labs Fort Collins)'; Tian, Kevin;
  xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] DomU does not start.
  
  Hi Dan, Kevin,
  
  Sorry for a late mail. And, thanks for thinking about my problem.
  8734 seems to be a future changeset. ;-)
  Oops! Sorry it's a typing miss...
  
  I tried the start of domU with changeset:8473 this time.
  problem of RAMDISK was able to be cleared this time.
  But, the problem occurred newly.
  It stops with the mount of root. ( Please look at an attached log.)
  I investigated a little.
  stop is done with ext3_fill_super of sb_bread.
  ( /linux-2.6.12-xenU/fs/ext3/super.c )
  
  this is my Configfile. Is there a wrong place?
  
  kernel = /boot/vmlinux-2.6.12-xenU
  ramdisk = /boot/initrd-2.6.12-xenU.img
  memory = 512
  name = rhel4-2
  disk = [ 'file:/root/rhel4.img,hda1,w' ]
  root = /dev/hda1 ro
  extra = nomca nosmp xencons=tty0 console=tty0 3
  
  thanks,
  Fujita
  
   -Original Message-
   From: Magenheimer, Dan (HP Labs Fort Collins)
  [mailto:[EMAIL PROTECTED]
   Sent: Friday, December 30, 2005 7:37 AM
   To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] DomU does not start.
  
   Committed as cset 8436.  Fujita, please test to see
   if this solves the problem with booting domU with and
   without initrd.
  
   Thanks,
   Dan
  
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Tian, Kevin
Sent: Thursday, December 29, 2005 2:23 AM
To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] DomU does not start.
   
BTW, we may need this patch:
   
diff -r f218e6ba2653 tools/libxc/xc_linux_build.c
--- a/tools/libxc/xc_linux_build.c Fri Dec 23 21:14:21 2005
+++ b/tools/libxc/xc_linux_build.c Thu Dec 29 16:43:19 2005
@@ -397,6 +397,9 @@
 {
 ctxt-initrd.start= vinitrd_start;
 ctxt-initrd.size = initrd_len;
+} else {
+ctxt-initrd.start= 0;
+ctxt-initrd.size = 0;
 }
 strncpy((char *)ctxt-cmdline, cmdline,
  IA64_COMMAND_LINE_SIZE);
 ctxt-cmdline[IA64_COMMAND_LINE_SIZE-1] = '\0';
   
Thanks,
Kevin
   
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tian, Kevin
Sent: 2005年12月29日 17:04
To: yo.fujita; xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] DomU does not start.

From: yo.fujita
Sent: 2005年12月29日 16:20
Hi

I can't start domU after changeset8372.
applied two patches of changeset 8734 after that.
However, the following message displays and DomU does
  not start.

RAMDISK: Couldn't find valid RAM disk image starting at 0 .

Don't someone have information?

Thanks
Fujita

8734 seems to be a future changeset. ;-)

Do you need initrd to boot your domU image? If yes, you may
add an option in
example file:

ramdisk = initrd_name

If no, can you try appending a noinitrd to extra field in
your example file like:

Extra = 4 noinitrd

I guess there's some issue when domU image file doesn't
require an initrd.

Thanks,
Kevin

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



___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http

RE: [Xen-ia64-devel] DomU does not start.

[yo.fujita]

Hi Dan, Kevin,

Thank you. I succeeded in Boot of DomU by the patch of kevin. (8474)
I will start the benchmark on DomU.

However, VTI did not stand up.
Is this because virtual memmap was disable?
Please look at an attached VTI bootlog.

Thanks,
Fujita

 -Original Message-
 From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:[EMAIL PROTECTED]
 Sent: Friday, January 06, 2006 9:55 AM
 To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] DomU does not start.
 
 Oops, one more possible problem.  Since you are requesting
 512MB for domU, there may not be enough machine memory
 available on some machines.  (Because of a problem/bug,
 Xen can't some memory over 1GB.)
 
 If you get a strange message about not able to balloon,
 try reducing the amount of domU memory.
 
 Dan
 
  -Original Message-
  From: Magenheimer, Dan (HP Labs Fort Collins)
  Sent: Thursday, January 05, 2006 10:06 AM
  To: 'Tian, Kevin'; yo.fujita; xen-ia64-devel@lists.xensource.com
  Subject: RE: [Xen-ia64-devel] DomU does not start.
 
  Yes, Kevin's fix is now checked in as 8474.
  Please see if this resolves the problem.
 
  Thanks,
  Dan
 
   -Original Message-
   From: Tian, Kevin [mailto:[EMAIL PROTECTED]
   Sent: Thursday, January 05, 2006 4:58 AM
   To: yo.fujita; Magenheimer, Dan (HP Labs Fort Collins);
   xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] DomU does not start.
  
   Hi, Fujita,
 I'm not sure about your target memory layout. But
   generally if you plug a =2G memory bank in your box, you may
   need the patch I sent out yesterday to disable virtual memmap
   in guest. Or else vbd driver doesn't work. If you only have
   1G-like system, then that's possibly a different issue.
  
   Thanks,
   Kevin
  
   -Original Message-
   From: yo.fujita [mailto:[EMAIL PROTECTED]
   Sent: 2006年1月5日 19:07
   To: 'Magenheimer, Dan (HP Labs Fort Collins)'; Tian, Kevin;
   xen-ia64-devel@lists.xensource.com
   Subject: RE: [Xen-ia64-devel] DomU does not start.
   
   Hi Dan, Kevin,
   
   Sorry for a late mail. And, thanks for thinking about my problem.
   8734 seems to be a future changeset. ;-)
   Oops! Sorry it's a typing miss...
   
   I tried the start of domU with changeset:8473 this time.
   problem of RAMDISK was able to be cleared this time.
   But, the problem occurred newly.
   It stops with the mount of root. ( Please look at an attached log.)
   I investigated a little.
   stop is done with ext3_fill_super of sb_bread.
   ( /linux-2.6.12-xenU/fs/ext3/super.c )
   
   this is my Configfile. Is there a wrong place?
   
   kernel = /boot/vmlinux-2.6.12-xenU
   ramdisk = /boot/initrd-2.6.12-xenU.img
   memory = 512
   name = rhel4-2
   disk = [ 'file:/root/rhel4.img,hda1,w' ]
   root = /dev/hda1 ro
   extra = nomca nosmp xencons=tty0 console=tty0 3
   
   thanks,
   Fujita
   
-Original Message-
From: Magenheimer, Dan (HP Labs Fort Collins)
   [mailto:[EMAIL PROTECTED]
Sent: Friday, December 30, 2005 7:37 AM
To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] DomU does not start.
   
Committed as cset 8436.  Fujita, please test to see
if this solves the problem with booting domU with and
without initrd.
   
Thanks,
Dan
   
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf
 Of Tian, Kevin
 Sent: Thursday, December 29, 2005 2:23 AM
 To: Tian, Kevin; yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] DomU does not start.

 BTW, we may need this patch:

 diff -r f218e6ba2653 tools/libxc/xc_linux_build.c
 --- a/tools/libxc/xc_linux_build.c   Fri Dec 23 21:14:21 2005
 +++ b/tools/libxc/xc_linux_build.c   Thu Dec 29 16:43:19 2005
 @@ -397,6 +397,9 @@
  {
  ctxt-initrd.start= vinitrd_start;
  ctxt-initrd.size = initrd_len;
 +} else {
 +ctxt-initrd.start= 0;
 +ctxt-initrd.size = 0;
  }
  strncpy((char *)ctxt-cmdline, cmdline,
   IA64_COMMAND_LINE_SIZE);
  ctxt-cmdline[IA64_COMMAND_LINE_SIZE-1] = '\0';

 Thanks,
 Kevin

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On
 Behalf Of Tian, Kevin
 Sent: 2005年12月29日 17:04
 To: yo.fujita; xen-ia64-devel@lists.xensource.com
 Subject: RE: [Xen-ia64-devel] DomU does not start.
 
 From: yo.fujita
 Sent: 2005年12月29日 16:20
 Hi
 
 I can't start domU after changeset8372.
 applied two patches of changeset 8734 after that.
 However, the following message displays and DomU does
   not start.
 
 RAMDISK: Couldn't find valid RAM disk image starting at 0 .
 
 Don't someone have information?
 
 Thanks
 Fujita
 
 8734 seems to be a future changeset