[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [ANNOUNCE] virtbench now has xen support


  • To: Jan Michael <jan.michael@xxxxxxx>
  • From: Jan Michael <Jan.Michael@xxxxxxx>
  • Date: Wed, 6 Jun 2007 10:51:04 +0200
  • Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxx>
  • Delivery-date: Wed, 06 Jun 2007 01:49:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=cern.ch; q=dns; h=received:message-id:date:from:to:subject:mime-version:content-type; b=EHQN9W5p/uqWbH8mhNU0XStcVPRvIgjsoiZ5VXliHrjS+SVDatQrEevxkVzDHqhvZhRhmprCIt/1js/yDSOpW9MpKkbHjL7WpAW6ObPBSJscqvNUcz1shF2BCKfmeLSM;
  • Keywords: CERN SpamKiller Note: -50 Charset: west-latin
  • Keywords: CERN SpamKiller Note: -50 Charset: west-latin
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello Everyone,

I got my hands on a HP blade with 64-bit Intel XEON processors. I could successfully start the benchmark but after a while client 1 closed the connection. Please see the full log below.

Could you please help me to find the error? Is there a some kind of debugging mode I could use to get more details from both, client and server side?

<virtbench execution>
[root@somemachine virtbench-cern]# ./virtbench xen
Bringing up machines11188 blocks
58.7%
11188 blocks
58.7%
11188 blocks
58.7%
11188 blocks
58.7%
....
Time for one context switch via pipe: 7747 (5070 - 8202)
Time for one Copy-on-Write fault: 4266 (4242 - 5865)
Time to exec client once: 331171 (329757 - 332406)
Time for one fork/exit/wait: 196031 (195781 - 196812)
Time to send 4 MB from host: 37688750 (27595500 - 47665250)
Time for one syscall via libc: 428 (417 - 652)
Time to walk linear 64 MB: 2130375 (2123000 - 2168750)
Time to walk random 64 MB: 2135000 (2130250 - 2140625)
virtbench: client 1 closed connection
sh: line 1: Using: command not found
sh: line 2: Started: command not found
virtbench: 'xen/stop_machine virtbench_3
Using config file "/tmp/virtbench-xen_3.cfg".
Started domain virtbench_3
' failed
sh: line 1: Using: command not found
sh: line 2: Started: command not found
virtbench: 'xen/stop_machine virtbench_2
Using config file "/tmp/virtbench-xen_2.cfg".
Started domain virtbench_2
' failed
Error: Domain 'virtbench_1' does not exist.
Error: 'xm destroy' requires 1 arguments.

sh: line 1: Using: command not found
sh: line 2: Started: command not found
virtbench: 'xen/stop_machine virtbench_1
Using config file "/tmp/virtbench-xen_1.cfg".
Started domain virtbench_1
' failed
sh: line 1: Using: command not found
sh: line 2: Started: command not found
virtbench: 'xen/stop_machine virtbench_0
Using config file "/tmp/virtbench-xen_0.cfg".
Started domain virtbench_0
' failed
</virtbench execution>

Thank you very much,

        Jan Michael


On 23.05.2007, at 20:05, Jan Michael wrote:
Hello,

as I found out it is a little bit tricky to use one's initrd. Because Virtbench is overriding the init command in the domU configuration file with rdinit and therefore it is not possible to load modules:

<virtbench-xen.cfg.in>
extra = "rdinit=/virtclient @VIRTBENCH_ID@ @SERVERIP@ @SERVERPORT@ /dev/xvda1 202 1 eth0 %s" % string.replace('@IP@', '.', '/')
</virtbench-xen.cfg.in>

The template file virtbench-xen.cfg.in is used to create an individual xen configuration file for each user domain. Despite this I tried to get the virtclient working with my own initrd. I was able to successfully load the xen network and block device driver. At the end of the init script I could start virtclient from the ramdisk.

So I modified the start_machine script in that way that it will manipulate the init start script of the ramdisk and after that it creates one initrd for each domU. The domU configuration uses now a prepared ramdisk rather than this one from virtbench.

The benchmark passed with the following outcome:

Time for one context switch via pipe: 8734 (8640 - 9575)
Time for one Copy-on-Write fault: 5898 (5814 - 8963)
Time to exec client once: 573046 (565921 - 615390)
Time for one fork/exit/wait: 347687 (345750 - 362250)
Time to send 4 MB from host: 55785000 (27069625 - 315191500)
Time for one int-0x80 syscall: 370 (370 - 403)
Time for one syscall via libc: 376 (376 - 377)
Time to walk linear 64 MB: 1790875 (1711750 - 3332875)
Time to walk random 64 MB: 2254500 (2246000 - 2266250)
Time for one outb PIO operation: 721 (717 - 733)
DISABLED pte-update: glibc version is too old
Time to read from disk (256 kB): 18810406 (14266718 - 24088906)
Time for one disk read: 56343 (38593 - 201718)
DISABLED vmcall: not a VT guest
DISABLED vmmcall: not an SVM guest
Time to send 4 MB between guests: 94326750 (79872250 - 729306500)
Time for inter-guest pingpong: 130316 (119722 - 186511)
Time to sendfile 4 MB between guests: 134768000 (86528000 - 417646000)
Time to receive 1000 1k UDPs between guests: 26010000 (23384000 - 66784000)

Last question for today: What is the unit of these time values?

Thanks,

        Jan

        
On 22.05.2007, at 11:33, Jeremy Fitzhardinge wrote:
Jan Michael wrote:
I can say that we are using a kernel builf from the attached kernel
config and a special initrd image for our domUs.
The initrd image contains the modules xenblk.ko and xennet.ko. So
netfront and blkfront are not compiled into the kernel.

Modular is OK if they're in the initrd you're using.

Our linux gurus made the kernel and the initrd image. I think I have
to integrate those modules into the initrd image you are using and
have to load them. But at this point I have no knowledge how to do
this...

It's distro-dependent, but mkinitrd works for RH-type systems.
Something like "mkinitrd --with=xenblk --with=xennet -v my-initrd.img
<kernel version>".

    J


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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.