From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ANNOUNCE] virtbench w/ kvm support
Date: Mon, 23 Apr 2007 15:49:34 +0300 [thread overview]
Message-ID: <462CAB5E.9080301@qumranet.com> (raw)
In-Reply-To: <1177305795.17026.56.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Rusty Russell wrote:
> Hi all,
>
> I've been toying around with a benchmark suite for virtualization, and
> I've just added kvm support. You can download the source tarball
> straight from the mercurial repo:
>
> http://ozlabs.org/~rusty/virtbench/
> http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2
>
> README excerpt below.
>
> Feedback and patches welcome!
>
Virtbench does not have puppy-nature on x86_64:
[avi@cleopatra virtbench]$ make
cc -g -Wall -Wmissing-prototypes -DNUM_MACHINES=4 -o virtbench server.c
results.c stdrusty.c talloc.c micro/context-switch.c micro/cow.c
micro/exec.c micro/fork.c micro/int-syscall.c micro/libc-syscall.c
micro/memburn.c micro/pio.c micro/pte-update.c micro/read-bandwidth.c
micro/read-latency.c micro/vmcall.c inter/bandwidth.c inter/pingpong.c
inter/sendfile.c inter/udp-bandwidth.c
results.c: In function ‘results_to_dist_summary’:
results.c:247: warning: format ‘%llu’ expects type ‘long long unsigned
int’, but argument 4 has type ‘u64’
results.c: In function ‘results_to_quick_summary’:
results.c:274: warning: format ‘%llu’ expects type ‘long long unsigned
int’, but argument 3 has type ‘u64’
results.c:274: warning: format ‘%llu’ expects type ‘long long unsigned
int’, but argument 4 has type ‘u64’
results.c:274: warning: format ‘%llu’ expects type ‘long long unsigned
int’, but argument 5 has type ‘u64’
results.c: In function ‘results_to_csv’:
results.c:287: warning: format ‘%llu’ expects type ‘long long unsigned
int’, but argument 4 has type ‘u64’
cc -g -Wall -Wmissing-prototypes -DNUM_MACHINES=4 -o virtclient client.c
stdrusty.c talloc.c micro/context-switch.c micro/cow.c micro/exec.c
micro/fork.c micro/int-syscall.c micro/libc-syscall.c micro/memburn.c
micro/pio.c micro/pte-update.c micro/read-bandwidth.c
micro/read-latency.c micro/vmcall.c inter/bandwidth.c inter/pingpong.c
inter/sendfile.c inter/udp-bandwidth.c
# 50M
dd if=/dev/zero of=rootfs/virtbench-root.tmp count=50 bs=1048576
50+0 records in
50+0 records out
52428800 bytes (52 MB) copied, 0.384909 seconds, 136 MB/s
mke2fs -q -F rootfs/virtbench-root.tmp
# /dev/xvda needed for xen
set -e; sudo mount -text2 -o,loop,rw rootfs/virtbench-root.tmp /mnt; \
trap 'sudo umount /mnt' 0; \
sudo mkdir /mnt/lib /mnt/tmp /mnt/dev /mnt/proc; \
sudo mknod /mnt/dev/null c 1 3; \
sudo mknod /mnt/dev/zero c 1 5; \
sudo mknod /mnt/dev/console c 5 1; \
sudo mknod /mnt/dev/xvda b 202 0; \
sudo mknod /mnt/dev/xvda1 b 202 1
sync
[ rootfs/virtbench-root -ot rootfs/virtbench-root-0 ] || cp
rootfs/virtbench-root rootfs/virtbench-root-0
set -e; trap 'sudo umount /mnt' 0; \
sudo mount -text2 -o,loop,rw rootfs/virtbench-root-0 /mnt; \
sudo cp virtclient /mnt; \
sudo cp /lib/ld-linux* /mnt/lib; \
sudo cp /lib/libc* /mnt/lib; \
sudo cp -a /lib/tls /mnt/lib/tls
cp: cannot stat `/lib/ld-linux*': No such file or directory
make: *** [rootfs/virtbench-root-0] Error 1
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-23 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 5:23 [ANNOUNCE] virtbench w/ kvm support Rusty Russell
[not found] ` <1177305795.17026.56.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-04-23 12:49 ` Avi Kivity [this message]
[not found] ` <462CAB5E.9080301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-24 0:12 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462CAB5E.9080301@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox