Boris Derzhavets
2008-May-23 17:10 UTC
LibMicro test for SNV89 HVM DomU at Ubuntu 8.04 Xen 3.2 Dom0
Both DomU and Dom0 (64-bit):- bash-3.2# uname -a SunOS dhcppc7 5.11 snv_89 i86pc i386 i86pc bash-3.2# cd libMic* bash-3.2# bin/fork -E -C 200 -L -S -W -N fork_100 -B 100 -C 100 > /tmp/fork.output Running: fork_100 for 37.41568 seconds bash-3.2# cd .. bash-3.2# gunzip < libc_hwcap3.tar.gz | ( cd /tmp; tar xfv - ) x libc_hwcap3.so.1, 1646444 bytes, 3216 tape blocks bash-3.2# mount -O -F lofs /tmp/libc_hwcap3.so.1 /lib/libc.so.1 bash-3.2# cd libMic* bash-3.2# bin/fork -E -C 200 -L -S -W -N fork_100 -B 100 -C 100 > /tmp/fork.output1 Running: fork_100 for 35.18513 seconds This message posted from opensolaris.org
Boris Derzhavets
2008-May-23 17:16 UTC
Re: LibMicro test for SNV89 HVM DomU at Ubuntu 8.04 Xen 3.2 Dom0
Runtime snaphot. This message posted from opensolaris.org
Jürgen Keil
2008-May-23 17:46 UTC
Re: LibMicro test for SNV89 HVM DomU at Ubuntu 8.04 Xen 3.2 Dom0
> Both DomU and Dom0 (64-bit):- > bash-3.2# uname -a > SunOS dhcppc7 5.11 snv_89 i86pc i386 i86pc > bash-3.2# cd libMic* > bash-3.2# bin/fork -E -C 200 -L -S -W -N fork_100 -B 100 -C 100 > /tmp/fork.output > Running: fork_100 for 37.41568 secondsBtw: I think that the extremely bad fork_* performance can only observed when running the 32-bit PAE hypervisor, and when the system uses less than 4GB of memory. I filed bug 6702228 for this problem. This message posted from opensolaris.org
Boris Derzhavets
2008-May-24 16:36 UTC
Re: LibMicro test for SNV89 HVM DomU at Ubuntu 8.04 Xen 3.2 Dom0
Second option for profiles:- *********** Installation *********** root@boris-desktop:/etc/xen/vm# cat solaio.hvm name="Solaris89HVM" builder=''hvm'' memory=1024 disk=[''tap:aio:/etc/xen/images/snv.img,hda,w'',''phy:/dev/loop0,hdc:cdrom,r''] vif=[''type=ioemu,bridge=eth0''] device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel=''/usr/lib64/xen/boot/hvmloader'' vcpus=1 serial="pty" sdl=1 boot="d" on_reboot = ''restart'' on_crash = ''restart'' ********* Runtime ********* root@boris-desktop:/etc/xen/vm# cat sol89aio.hvm name="Solaris89HVM" builder=''hvm'' memory=1024 disk=[''tap:aio:/etc/xen/images/snv.img,hda,w''] vif=[''type=ioemu,bridge=eth0''] device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel=''/usr/lib64/xen/boot/hvmloader'' vcpus=1 serial="pty" sdl=1 boot="c" on_reboot = ''restart'' on_crash = ''restart'' Both options:- disk=[''tap:aio:/etc/xen/images/snv.img,hda,w'',''phy:/dev/loop0,hdc:cdrom,r''] disk=[''phy:/dev/sdb13,ioemu:hda,w'',''phy:/dev/loop0,hdc:cdrom,r''] work fine. I didn''t have to losetup writeable device as suggested in blog http://blogs.sun.com/breakdown/ This message posted from opensolaris.org
Apparently Analagous Threads
- 6340766 multiple x86 libmicro regressions in snv_25
- SMC Webconsole 3.1 and ZFS Administration 1.0 - stacktraces in snv_b89
- Cannot get second network interface working in Linux guest
- bundle install rmagick error in unix
- blktap, vmdk, vdi, and disk management support