Re: Re: [ANNOUNCE] virtbench now has xen support

[Rusty Russell <rusty@rustcorp.com.au>]

On Wed, 2007-06-06 at 10:51 +0200, Jan Michael wrote:
> 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

OK, this looks like look it got upset on the "outb" test.
Unfortunately, redirecting standard input from /dev/null causes xen not
to output any console at all.  I'm not sure how to fix this, but you can
enter names manually on the commandline to avoid running this benchmark.

> 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

It seems that your xen/start_machine script printed out extra stuff,
rahter than just the id to hand back to stop_machine.

Cheers,
Rusty.