[ANNOUNCE] virtbench now has xen support

[ANNOUNCE] virtbench now has xen support

[Rusty Russell]

Hi all,

	I've been working on a set of easy-to-run benchmarks for hypervisor
optimization called virtbench, and the latest commit adds Xen support.

	http://ozlabs.org/~rusty/virtbench
	http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2

>From the README:

	# Build the code
	make
	# Set the guest kernel location and maybe more
	vi ./SETTINGS
	# Run the benchmark (local mode)
	./virtbench local
	# Run the benchmark (kvm mode)
	sudo ./virtbench kvm
	# Run the benchmark (Xen mode)
	sudo ./virtbench xen
	# Run the benchmark (lguest mode)
	sudo ./virtbench lguest

Feedback welcome!
Rusty.

Re: [ANNOUNCE] virtbench now has xen support

[Jan Michael]

Hi Rusty,

thanks for your work. I tried your benchmark on my XEN installation.

<xm info>
release                : 2.6.18-1.2835.slc4xen
version                : #1 SMP Wed Nov 29 21:05:58 CET 2006
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2800
hw_caps                : bfebfbff:20000000:00000000:00000180:0000641d
total_memory           : 2047
free_memory            : 1024
xen_major              : 3
xen_minor              : 0
xen_extra              : .3-rc5-1.2835.s
xen_caps               : xen-3.0-x86_32p
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
cc_compile_by          : root
cc_compile_date        : Wed Nov 29 20:56:00 CET 2006
xend_config_format     : 2
</xm info>

and ended up in the following error.	

<make error>
[root@lxdev19 virtbench-bd8e67e50775]# 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/host-net-bandwidth.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
micro/pte-update.c: In function `do_pte_update':
micro/pte-update.c:45: error: too many arguments to function `mremap'
make: *** [virtbench] Error 1
</make error>

So first thing I would like to know if my XEN installation is  
compatible with your benchmark suite and if not which are the  
requirements?

Thank you for your help and support,

	Jan Michael


On 15.05.2007, at 04:38, Rusty Russell wrote:
> Hi all,
>
> 	I've been working on a set of easy-to-run benchmarks for hypervisor
> optimization called virtbench, and the latest commit adds Xen support.
>
> 	http://ozlabs.org/~rusty/virtbench
> 	http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2
>
>> From the README:
>
> 	# Build the code
> 	make
> 	# Set the guest kernel location and maybe more
> 	vi ./SETTINGS
> 	# Run the benchmark (local mode)
> 	./virtbench local
> 	# Run the benchmark (kvm mode)
> 	sudo ./virtbench kvm
> 	# Run the benchmark (Xen mode)
> 	sudo ./virtbench xen
> 	# Run the benchmark (lguest mode)
> 	sudo ./virtbench lguest
>
> Feedback welcome!
> Rusty.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [ANNOUNCE] virtbench now has xen support

[Anthony Liguori]

Jan Michael wrote:
> Hi Rusty,
> 
> thanks for your work. I tried your benchmark on my XEN installation.
> 
> <xm info>
> release                : 2.6.18-1.2835.slc4xen
> version                : #1 SMP Wed Nov 29 21:05:58 CET 2006
> machine                : i686
> nr_cpus                : 2
> nr_nodes               : 1
> sockets_per_node       : 2
> cores_per_socket       : 1
> threads_per_core       : 1
> cpu_mhz                : 2800
> hw_caps                : bfebfbff:20000000:00000000:00000180:0000641d
> total_memory           : 2047
> free_memory            : 1024
> xen_major              : 3
> xen_minor              : 0
> xen_extra              : .3-rc5-1.2835.s
> xen_caps               : xen-3.0-x86_32p
> xen_pagesize           : 4096
> platform_params        : virt_start=0xf5800000
> xen_changeset          : unavailable
> cc_compiler            : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
> cc_compile_by          : root
> cc_compile_date        : Wed Nov 29 20:56:00 CET 2006
> xend_config_format     : 2
> </xm info>
> 
> and ended up in the following error.   
> 
> <make error>
> [root@lxdev19 virtbench-bd8e67e50775]# 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/host-net-bandwidth.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
> micro/pte-update.c: In function `do_pte_update':
> micro/pte-update.c:45: error: too many arguments to function `mremap'
> make: *** [virtbench] Error 1
> </make error>

I've just pushed an update that should disable this test for older 
versions of glibc.  Would appreciate if you let me know whether this 
fixed your build.

Regards,

Anthony Liguori

> 
> So first thing I would like to know if my XEN installation is compatible 
> with your benchmark suite and if not which are the requirements?
> 
> Thank you for your help and support,
> 
>     Jan Michael
> 
> 
> On 15.05.2007, at 04:38, Rusty Russell wrote:
>> Hi all,
>>
>>     I've been working on a set of easy-to-run benchmarks for hypervisor
>> optimization called virtbench, and the latest commit adds Xen support.
>>
>>     http://ozlabs.org/~rusty/virtbench
>>     http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2
>>
>>> From the README:
>>
>>     # Build the code
>>     make
>>     # Set the guest kernel location and maybe more
>>     vi ./SETTINGS
>>     # Run the benchmark (local mode)
>>     ./virtbench local
>>     # Run the benchmark (kvm mode)
>>     sudo ./virtbench kvm
>>     # Run the benchmark (Xen mode)
>>     sudo ./virtbench xen
>>     # Run the benchmark (lguest mode)
>>     sudo ./virtbench lguest
>>
>> Feedback welcome!
>> Rusty.
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel

Re: [ANNOUNCE] virtbench now has xen support

[Jan Michael]

Hi Anthony,

On 15.05.2007, at 21:50, Anthony Liguori wrote:
> I've just pushed an update that should disable this test for older  
> versions of glibc.  Would appreciate if you let me know whether  
> this fixed your build.

That did the trick. Virtbench was sucessfully build on my system. I  
was also able to run virtbench in local mode but when I tried to run  
virtbench for xen I got the following error:

<error>
[root@lxdev19 virtbench-44dc217a9422]# KERNEL="/etc/xen/vmlinuz" ./ 
virtbench xen --progress
virtbench: Start command failed for xen
</error>

I already tried to investigate this error viewing the virtbench  
logfile which I specified in SETTINGS file. But the logfile was not  
created :-(.

What can I do to get your benchmark work for my XEN installation?

Thanks,

	Jan

Re: [ANNOUNCE] virtbench now has xen support

[Rusty Russell]

On Fri, 2007-05-18 at 12:14 +0200, Jan Michael wrote:
> Hi Anthony,
> 
> On 15.05.2007, at 21:50, Anthony Liguori wrote:
> > I've just pushed an update that should disable this test for older  
> > versions of glibc.  Would appreciate if you let me know whether  
> > this fixed your build.
> 
> That did the trick. Virtbench was sucessfully build on my system. I  
> was also able to run virtbench in local mode but when I tried to run  
> virtbench for xen I got the following error:
> 
> <error>
> [root@lxdev19 virtbench-44dc217a9422]# KERNEL="/etc/xen/vmlinuz" ./ 
> virtbench xen --progress
> virtbench: Start command failed for xen
> </error>
> 
> I already tried to investigate this error viewing the virtbench  
> logfile which I specified in SETTINGS file. But the logfile was not  
> created :-(.

This is a failure of the "xen/start" command.  I had this happen when 
"/etc/init.d/xend restart" failed.  You can probably comment that line
out if you're already running Xen (perhaps xen's init scripts are
flaky).

Thanks for the report!
Rusty.

Re: [ANNOUNCE] virtbench now has xen support

[Jan Michael]

Hi Rusty,

On 18.05.2007, at 13:51, Rusty Russell wrote:
> On Fri, 2007-05-18 at 12:14 +0200, Jan Michael wrote:
>> Hi Anthony,
>>
>> On 15.05.2007, at 21:50, Anthony Liguori wrote:
>>> I've just pushed an update that should disable this test for older
>>> versions of glibc.  Would appreciate if you let me know whether
>>> this fixed your build.
>>
>> That did the trick. Virtbench was sucessfully build on my system. I
>> was also able to run virtbench in local mode but when I tried to run
>> virtbench for xen I got the following error:
>>
>> <error>
>> [root@lxdev19 virtbench-44dc217a9422]# KERNEL="/etc/xen/vmlinuz" ./
>> virtbench xen --progress
>> virtbench: Start command failed for xen
>> </error>
>>
>> I already tried to investigate this error viewing the virtbench
>> logfile which I specified in SETTINGS file. But the logfile was not
>> created :-(.
>
> This is a failure of the "xen/start" command.  I had this happen when
> "/etc/init.d/xend restart" failed.  You can probably comment that line
> out if you're already running Xen (perhaps xen's init scripts are
> flaky).

Now I'm one step further. The domUs will be created, but they are  
destroyed after seconds. I started one of them manually with console  
so that I could see the error message:

<boot error>
md: autorun ...
md: ... autorun DONE.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- 
block(1,0)
</boot error>

That must have been something to do with the kernel I'm using. I have  
to investigate (google) this. But if you can also help me in this  
case - you're welcome!

Cheers,

	Jan

Re: [ANNOUNCE] virtbench now has xen support

[Rusty Russell]

On Fri, 2007-05-18 at 19:56 +0200, Jan Michael wrote:
> Hi Rusty,

Hi JaN!

> Now I'm one step further. The domUs will be created, but they are  
> destroyed after seconds. I started one of them manually with console  
> so that I could see the error message:
> 
> <boot error>
> md: autorun ...
> md: ... autorun DONE.
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- 
> block(1,0)
> </boot error>
> 
> That must have been something to do with the kernel I'm using. I have  
> to investigate (google) this. But if you can also help me in this  
> case - you're welcome!

Hmm, perhaps your kernel doesn't have INITRD support?  The default Xen
kernel works (at least, for me on i386 it does)...

Thanks,
Rusty.

Re: [ANNOUNCE] virtbench now has xen support

[Jan Michael]

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

Salut Rusty,

On 21.05.2007, at 08:16, Rusty Russell wrote:
> On Fri, 2007-05-18 at 19:56 +0200, Jan Michael wrote:
>> Hi Rusty,
>
> Hi JaN!
>
>> Now I'm one step further. The domUs will be created, but they are
>> destroyed after seconds. I started one of them manually with console
>> so that I could see the error message:
>>
>> <boot error>
>> md: autorun ...
>> md: ... autorun DONE.
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
>> block(1,0)
>> </boot error>
>>
>> That must have been something to do with the kernel I'm using. I have
>> to investigate (google) this. But if you can also help me in this
>> case - you're welcome!
>
> Hmm, perhaps your kernel doesn't have INITRD support?  The default Xen
> kernel works (at least, for me on i386 it does)...

Hm. No. Unfortunately the kernel I'm using has INITRD support,  
because we need it also for self-installation of our domUs in  
productive environment. I attached the whole startup log. The RAM  
disk driver is loaded in line 50.
Do you have any other suggestions?

Thanks,

	Jan



[-- Attachment #2: virtbench-xen_0.log --]
[-- Type: application/octet-stream, Size: 3779 bytes --]

     1	Linux version 2.6.9-42.0.3.EL.cernxenU (root@lxcert-i386) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Thu Nov 16 20:40:17 CET 2006
     2	BIOS-provided physical RAM map:
     3	Xen: 0000000000000000 - 0000000008800000 (usable)
     4	0MB HIGHMEM available.
     5	136MB LOWMEM available.
     6	Using x86 segment limits to approximate NX protection
     7	Built 1 zonelists
     8	Kernel command line:  root=/dev/ram0 rw rdinit=/virtclient 0 128/142/202/89 45375 /dev/xvda1 202 1 eth0 192/168/19/1
     9	Initializing CPU#0
    10	CPU 0 irqstacks, hard=c032f000 soft=c030f000
    11	PID hash table entries: 1024 (order: 10, 16384 bytes)
    12	Xen reported: 2800.092 MHz processor.
    13	Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    14	Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    15	vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000
    16	Memory: 123788k/139264k available (1443k kernel code, 7160k reserved, 539k data, 104k init, 0k highmem)
    17	Checking if this processor honours the WP bit even in supervisor mode... Ok.
    18	Calibrating delay using timer specific routine.. 5603.53 BogoMIPS (lpj=28017694)
    19	Security Scaffold v1.0.0 initialized
    20	SELinux:  Initializing.
    21	SELinux:  Starting in permissive mode
    22	There is already a security framework initialized, register_security failed.
    23	selinux_register_security:  Registering secondary module capability
    24	Capability LSM initialized as secondary
    25	Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    26	CPU: Trace cache: 12K uops, L1 D cache: 16K
    27	CPU: L2 cache: 1024K
    28	Enabling fast FPU save and restore... done.
    29	Enabling unmasked SIMD FPU exception support... done.
    30	Checking 'hlt' instruction... OK.
    31	Brought up 1 CPUs
    32	checking if image is initramfs... it is
    33	Freeing initrd memory: 1707k freed
    34	Grant table initialized
    35	NET: Registered protocol family 16
    36	Brought up 1 CPUs
    37	xen_mem: Initialising balloon driver.
    38	audit: initializing netlink socket (disabled)
    39	audit(1179734418.650:1): initialized
    40	Total HugeTLB memory allocated, 0
    41	VFS: Disk quotas dquot_6.5.1
    42	Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    43	SELinux:  Registering netfilter hooks
    44	Initializing Cryptographic API
    45	ksign: Installing public key data
    46	Loading keyring
    47	- Added public key 54FCFCA8F64BD776
    48	- User ID: Red Hat, Inc. (Kernel Module GPG key)
    49	i8042.c: No controller found.
    50	RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
    51	Xen virtual console successfully installed as tty1
    52	Event-channel device installed.
    53	Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    54	ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    55	ide-floppy driver 0.99.newide
    56	mice: PS/2 mouse device common for all mice
    57	md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
    58	NET: Registered protocol family 2
    59	IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    60	TCP established hash table entries: 8192 (order: 5, 131072 bytes)
    61	TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
    62	TCP: Hash tables configured (established 8192 bind 8192)
    63	Initializing IPsec netlink socket
    64	NET: Registered protocol family 1
    65	NET: Registered protocol family 17
    66	XENBUS: Device with no driver: device/vbd/51713
    67	XENBUS: Device with no driver: device/vif/0
    68	md: Autodetecting RAID arrays.
    69	md: autorun ...
    70	md: ... autorun DONE.
    71	Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
    72	

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

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

[Jeremy Fitzhardinge]

Jan Michael wrote:
> Salut Rusty,
>
> On 21.05.2007, at 08:16, Rusty Russell wrote:
>> On Fri, 2007-05-18 at 19:56 +0200, Jan Michael wrote:
>>> Hi Rusty,
>>
>> Hi JaN!
>>
>>> Now I'm one step further. The domUs will be created, but they are
>>> destroyed after seconds. I started one of them manually with console
>>> so that I could see the error message:
>>>
>>> <boot error>
>>> md: autorun ...
>>> md: ... autorun DONE.
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
>>> block(1,0)
>>> </boot error>
>>>
>>> That must have been something to do with the kernel I'm using. I have
>>> to investigate (google) this. But if you can also help me in this
>>> case - you're welcome!
>>
>> Hmm, perhaps your kernel doesn't have INITRD support?  The default Xen
>> kernel works (at least, for me on i386 it does)...
>
> Hm. No. Unfortunately the kernel I'm using has INITRD support, because
> we need it also for self-installation of our domUs in productive
> environment. I attached the whole startup log. The RAM disk driver is
> loaded in line 50.
> Do you have any other suggestions?
    66    XENBUS: Device with no driver: device/vbd/51713
    67    XENBUS: Device with no driver: device/vif/0

looks worrysome.  Do you have netfront and blkfront compiled into (your
kernel, either built-in or as modules in your initrd)?

Though it seems you have a more basic problem with mounting the initrd.

    J

Re: [ANNOUNCE] virtbench now has xen support

[Rusty Russell]

On Mon, 2007-05-21 at 10:13 +0200, Jan Michael wrote:
> Salut Rusty,
> 
> On 21.05.2007, at 08:16, Rusty Russell wrote:
> > Hmm, perhaps your kernel doesn't have INITRD support?  The default Xen
> > kernel works (at least, for me on i386 it does)...
> 
> Hm. No. Unfortunately the kernel I'm using has INITRD support,  

Hi Jan!

	Hmm, it has found the initrd, and ramdisk seems to be there.  Any
chance you can send your kernel config?  Obviously we want it to "just
work" with whatever configs it can...

Thanks for chasing this!
Rusty.

Re: [ANNOUNCE] virtbench now has xen support

[Jan Michael]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

Hi Rusty,

On 22.05.2007, at 01:45, Rusty Russell wrote:
> On Mon, 2007-05-21 at 10:13 +0200, Jan Michael wrote:
>> Salut Rusty,
>>
>> On 21.05.2007, at 08:16, Rusty Russell wrote:
>>> Hmm, perhaps your kernel doesn't have INITRD support?  The  
>>> default Xen
>>> kernel works (at least, for me on i386 it does)...
>>
>> Hm. No. Unfortunately the kernel I'm using has INITRD support,
>
> Hi Jan!
>
> 	Hmm, it has found the initrd, and ramdisk seems to be there.  Any
> chance you can send your kernel config?  Obviously we want it to "just
> work" with whatever configs it can...

Sure. No problem. Please find attached our kernel config for domUs.
Did you see the mail from Jeremy?

On 21.05.2007, at 15:13, Jeremy Fitzhardinge wrote:
>     66    XENBUS: Device with no driver: device/vbd/51713
>     67    XENBUS: Device with no driver: device/vif/0
>
> looks worrysome.  Do you have netfront and blkfront compiled into  
> (your
> kernel, either built-in or as modules in your initrd)?
>
> Though it seems you have a more basic problem with mounting the  
> initrd.

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.
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...

Cheers,

	Jan


[-- Attachment #2: config-2.6.9-42.0.3.EL.cernxenU --]
[-- Type: application/octet-stream, Size: 21679 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9-42.0.3.EL.cernxenU
# Tue Nov 21 10:50:57 2006
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDITFILESYSTEM=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HOTPLUG=y
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Processor type and features
#
CONFIG_MEM_MIRROR=y
# CONFIG_X86_PC is not set
CONFIG_X86_XEN=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
CONFIG_SMP=y
CONFIG_SMP_ALTERNATIVES=y
CONFIG_NR_CPUS=32
# CONFIG_SCHED_MC is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
# CONFIG_PCI is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG_CPU=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
CONFIG_CCISS_DUMP=y
CONFIG_CCISS_DUMP_GLUE=m
CONFIG_DISKDUMP=m

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDEDUMP=m
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_IDE_ARM is not set
# CONFIG_BLK_DEV_IDEDMA is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID5=m
CONFIG_MD_RAID6=m
CONFIG_MD_MULTIPATH=m
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m

#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_MAX_SGE=40

#
# IEEE 1394 (FireWire) support
#

#
# I2O device support
#

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_TUNNEL=m

#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_CT_ACCT=y
CONFIG_IP_NF_CT_PROTO_SCTP=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_PHYSDEV=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
CONFIG_IP_NF_MATCH_SCTP=m
CONFIG_IP_NF_MATCH_COMMENT=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set

#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_LIMIT=m
CONFIG_IP6_NF_MATCH_MAC=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_MULTIPORT=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_MARK=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AHESP=m
CONFIG_IP6_NF_MATCH_LENGTH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_PHYSDEV=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_MARK=m
CONFIG_IP6_NF_RAW=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=y

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
CONFIG_NET_DIVERT=y
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_NET_CLS_IND=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_TUX=m

#
# TUX options
#
CONFIG_TUX_EXTCGI=y
# CONFIG_TUX_EXTENDED_LOG is not set
# CONFIG_TUX_DEBUG is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
CONFIG_ETHERTAP=m

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m

#
# Ethernet (1000 Mbit)
#

#
# Ethernet (10000 Mbit)
#

#
# Token Ring devices
#

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# ATM drivers
#
CONFIG_ATM_TCP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
CONFIG_NETDUMP=m

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_CRASH=m

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_ISA=m
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m

#
# Other I2C Chip support
#
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_RTC8564=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_LM87=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# InfiniBand support
#
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_IPOIB=m
CONFIG_INFINIBAND_IPOIB_DEBUG=y
# CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set
CONFIG_INFINIBAND_SDP=m
# CONFIG_INFINIBAND_SDP_DEBUG is not set
CONFIG_INFINIBAND_RDS=m
# CONFIG_INFINIBAND_RDS_DEBUG is not set

#
# EDAC - error detection and reporting (RAS)
#
# CONFIG_EDAC is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS_XATTR=y
CONFIG_DEVPTS_FS_SECURITY=y
CONFIG_TMPFS=y
CONFIG_TMPFS_XATTR=y
CONFIG_TMPFS_SECURITY=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
CONFIG_RELAYFS_FS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=m
CONFIG_VXFS_FS=m
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
# CONFIG_NFSD_V2_ACL is not set
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_EFI_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_INFO=y
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_KPROBES=y
CONFIG_DEBUG_STACK_USAGE=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_4KSTACKS=y
# CONFIG_SCHEDSTATS is not set

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
# CONFIG_SECURITY_SELINUX_MLS is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_SIGNATURE=y
CONFIG_CRYPTO_SIGNATURE_DSA=y
CONFIG_CRYPTO_MPILIB=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030203

#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
CONFIG_XEN_UNPRIVILEGED_GUEST=y
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DISABLE_SERIAL=y
CONFIG_XEN_COMPAT_030002_AND_LATER=y
# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
CONFIG_XEN_COMPAT_030002=y
CONFIG_HAVE_ARCH_ALLOC_SKB=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
CONFIG_NO_IDLE_HZ=y
CONFIG_XEN_UTIL=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_DEVMEM=y
CONFIG_XEN_SKBUFF=y
CONFIG_XEN_REBOOT=y
CONFIG_XEN_SMPBOOT=y

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_SMP=y
CONFIG_X86_NO_TSS=y
CONFIG_X86_NO_IDT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

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

[Jeremy Fitzhardinge]

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

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

[Jan Michael]

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

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

[Petersson, Mats]

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Jan Michael
> Sent: 24 May 2007 16:37
> To: Jeremy Fitzhardinge; Anthony Liguori; Rusty Russell; Xen 
> Mailing List
> Cc: Alex Iribarren
> Subject: Re: [Xen-devel] Re: [ANNOUNCE] virtbench now has xen support
> 
> Hi Everybody,
> 
> On 23.05.2007, at 20:05, Jan Michael wrote:
> > 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)
> 
> I didn't had anything to do with benchmarking in the past, and  
> especially not with virtualization benchmarks, so there are again  
> some questions related to the results of the benchmarking test:
> 
> 	1. What can I read out of every single value which is 
> listed above?  

The time it takes to perform the particular microbenchmark. 

> Can you please give a short explenation?
> 	2. What are the unit(s) of the measured values?

Good question, and I don't know the actual answer. I suspect they are
clock-cycles or perhaps nanoseconds. It's clearly not milliseconds or
microseconds, so it's a "very short time-unit". 

> 	3. What is a good value and what is a bad value? On 
> what does these  
> measures depend on - hardware or software or both?

They aren't good or bad values as such - they are comparative numbers.
There are no "absolute" good or bad values. If I say "ten seconds", that
may be a good value if you're running 100m. But it's certainly a bad
value for a computer running 10000 instructions, for example. 

Using these values, one could either compare one implementation of Xen
with another, or compare two machines with different specs (e.g.
different processors, different memory types, different network cards or
disks, or whatever). The on with the higher numbers is the slower one. 

> 	4. If I get a certain value like this one: Time for one 
> context  
> switch via pipe: 8734 (8640 - 9575). What can I do to improve/tune  
> the performance or the values?

Like any other performance improvement, you'd have to figure out where
the majority of time[1] is spent for this microbenchmark, and then try
to improve that somehow. Repeatedly (unless it runs for a long time in
itself) running this particular benchmark and running "oprofile" on the
machine would be able to give a fair idea of where in the system the
time is spent. 

The numbers in the bracket is the upper/lower numbers, the first number
being the average of several runs. 

> 	5. I googled through the web to find any results to 
> compare with  
> mine, but I couldn't find anything. Do you have some?

I don't.
> 	6. In the README file is said that virtbench contains 
> "low level"  
> benchmarks. What do you consider as a "high level" benchmark?

Low-level benchmark is similar to "microbenchmark". It tests ONE
particular feature of the system in isolation. For example, the "context
switch via pipe" is sending a message via a pipe from one process to
another process, and measuring the time it takes from sending the
message until it's been received at the other end. This is a good way to
measure very precise parts of a system, but improving this by 10%, 20%
or 50% may serve no purpose if it isn't a large portion of a higher
level functionality. E.g. if you run the Blurg[2] web-server, it may not
use pipes at all, so the performance of Blurg is completely unrelated of
the performance of this particular benchmark. Some other functions in
the microbenchmark are likely to have some effect on Blurg, but it may
also be that a major portion of Blurg's execution time isn't in the
OS/Hypervisor at all, so it doesn't really make much difference at all. 

To give another type of example: 

We can measure the horse-power of a car-enging. There are several ways
to do this. The most realistic is one that actually uses the car itself
(such as a rolling-road), but we can also dismount the engine from the
car and measure it without the gearbox, cooling fans, water pumps, and
whatever else that can be "removed". This method will of course generate
(somewhat) more power, but also less useful numbers. On the other hand,
all of this is pointless if you can't actually USE the power (e.g. the
suspension isn't good enough to go round corners, the brakes don't work
well, so if you don't have half a kilometer to stop, you can't use the
maximum speed of the car, etc, etc) on the road/racetrack, right? So the
BEST way to compare two cars would be to use the same (skilled) driver
around a track or a road, to see which performs best. 

Microbenchmarks measure the engine-power, braking power, suspension
springs, etc, etc. High level/application benchmarks measures the
systems ability to perform a higher level task, such as web-serving,
file-serving, complex calculation tasks, or some such. 

[1] Figuring out where the majority of time is spent is USUALLY the best
place to start. However, there are cases where small distributed bits of
code are the major part. In the past, I've seen cases where a function
called many times got inlined, and eaach individual "call" of the
function didn't amount to much, but since it was called many times
during the overall benchmark, it amounted to a noticable overhead. In
another case, there was a "trace-function" that got called thousands of
times a second, but since tracing was turned off, it didn't actually do
anything but return. This "nothing but return" was about 2% of the
overall time of the "benchmark". However, the effect of actually CALLING
the function (passing a bunch of parameters and often extracting those
parameters from pointers/data structures) was taking about 15% of the
overall time. Moving the check to see if there was any output to be done
to outside the function call improved the overall performance by about
16%. Worth having, eh?

[2] Blurg is a fictional web-server, not a product in real life, but for
this example, it doesn't really matter. 

--
Mats
> 
> Ok. Enough of my questions so far. If you answere these ones 
> I'll may  
> be have more afterwards.
> Thanks for your help,
> 
> 	Jan 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 

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

[Rusty Russell]

On Thu, 2007-05-24 at 17:37 +0200, Jan Michael wrote:
> I didn't had anything to do with benchmarking in the past, and  
> especially not with virtualization benchmarks, so there are again  
> some questions related to the results of the benchmarking test:
> 
> 	1. What can I read out of every single value which is listed above?  
> Can you please give a short explenation?
> 	2. What are the unit(s) of the measured values?

Hi Jan!

Each one is in nanoseconds, shorter is better.  All of them are run on
processes within one randomly-chosen domU of the four (some are
inter-guest test which run on two domUs)

> > Time for one context switch via pipe: 8734 (8640 - 9575)

Two processes within the domU, one is doing a read() waiting for the
other to do a write(), then vice versa

> > Time for one Copy-on-Write fault: 5898 (5814 - 8963)

This measures the time for a page marked readonly to become writable
when the guest writes to it.

> > Time to exec client once: 573046 (565921 - 615390)

This measures the client process execing itself.

> > Time for one fork/exit/wait: 347687 (345750 - 362250)

This measure the client process fork()ing, the child exiting, and the
parent waiting for it.

> > Time to send 4 MB from host: 55785000 (27069625 - 315191500)

This measures network speed: 4MB TCP transfer from the virtbench process
(dom0) to the client (domU).

> > Time for one int-0x80 syscall: 370 (370 - 403)
> > Time for one syscall via libc: 376 (376 - 377)

These are the time taken to do a getppid() system call.

> > Time to walk linear 64 MB: 1790875 (1711750 - 3332875)
> > Time to walk random 64 MB: 2254500 (2246000 - 2266250)

Memory walking.

> > Time for one outb PIO operation: 721 (717 - 733)

One io operation, roughly the time taken for a hypervisor entry & exit.

> > DISABLED pte-update: glibc version is too old

This test measures the time to update two page table entries, but
required mremap() which is only in modern glibcs.

> > Time to read from disk (256 kB): 18810406 (14266718 - 24088906)

Read 256k from the block device.

> > Time for one disk read: 56343 (38593 - 201718)

Read a single block from the block device (ie. latency).

> > DISABLED vmcall: not a VT guest
> > DISABLED vmmcall: not an SVM guest

These only apply to fully-virtualized guests.

> > Time to send 4 MB between guests: 94326750 (79872250 - 729306500)

domU <-> domU 4MB TCP write.

> > Time for inter-guest pingpong: 130316 (119722 - 186511)

domU <-> domU TCP latency.

> > Time to sendfile 4 MB between guests: 134768000 (86528000 - 417646000)

domU <-> domU 4MB TCP write using sendfile().

> > Time to receive 1000 1k UDPs between guests: 26010000 (23384000 -  
> > 66784000)

Sending 1000 UDP packets from domU <-> domU.  This benchmark is horribly
unreliable and should probably be removed.

> 	3. What is a good value and what is a bad value? On what does these  
> measures depend on - hardware or software or both?

Both... run "virtbench local" on the same hardware on a normal Linux
kernel to see what native results are.  This is really the target to aim
for.

> 	4. If I get a certain value like this one: Time for one context  
> switch via pipe: 8734 (8640 - 9575). What can I do to improve/tune  
> the performance or the values?

That would be Xen-specific, I'm not entirely sure how much that can be
improved.

> 	5. I googled through the web to find any results to compare with  
> mine, but I couldn't find anything. Do you have some?

I do not release benchmark numbers myself; they're quite dependent on
particular hardware, and also virtualization technology is moving
rapidly enough to make them quite obsolete.  virtbench is mainly useful
for spotting regressions, measuring code optimizations and explaining
the results of higher-level benchmarks.

> 	6. In the README file is said that virtbench contains "low level"  
> benchmarks. What do you consider as a "high level" benchmark?

Things like: kernbench, SDET, Spec, etc.

I hope that helps,
Rusty.

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

[Rusty Russell]

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.