Re: [Xen-users] Slow Disk access on SLES 10 install

[Matthias Lüneberg <Matthias.Lueneberg@xxxxxxxxxxxxxx>]

Hi,

it seems to me that you use a file for the disk,

>disk = [ 'file:/var/lib/xen/images/basesles10/hda,hda,w' ]

if you use a fresh SLES10 installation, you should read SLES10 Release
Notes:
http://www.novell.com/linux/releasenotes/i386/SUSE-SLES/10/RELEASE-NOTES.en.html
Theres a paragraph called: "Sync Mode for Loopback Storage" which could
help.

Hope this helps!

Regards,
Matthias


Am Samstag, den 03.03.2007, 05:20 -0800 schrieb D Sims:
> I have been struggling with a problem for a couple of days and I hope someone
> has some ideas.
> 
> I am using SLES 10 as a base for my Dom0 and I am trying to build a
> paravirtualized guest domain.  
> 
> I have tried lots of combinations of things but the disk during the install
> is increcdibly slow.  I am fairly certain that this is
> something I have set wrong, as I see the same results on two very different
> hardware platforms.  It takes about 2 hours for the first CD install; and
> that time is the same if I use the cd drive as a source of my install or if
> I use an NFS based source.
> 
> 
> Below is my domain config file  --- I have tried lots of combinations of
> things but still the same result.
> 
> 
> --------------------------------------------------------------------------------------------------------------------------
> disk = [ 'file:/var/lib/xen/images/basesles10/hda,hda,w' ]
> memory = 348
> vcpus = 1
> builder = 'linux'
> kernel = '/tmp/YaST2-04473-dmQhaD/vmlinuz-2.6.16.21-0.8-xen'
> ramdisk = '/tmp/YaST2-04473-dmQhaD/inst-initrd'
> name = 'basesles10'
> ip = '192.168.1.253'
> netmask = '255.255.255.0'
> gateway = '192.168.1.1'
> interface = 'eth0'
> vif = [ 'mac=00:16:3e:d1:dc:36,bridge=xenbr0',
> 'mac=00:16:3e:e2:e6:a0,bridge=xenbr1' ]
> localtime = 0
> on_poweroff = 'destroy'
> on_reboot = 'destroy'
> on_crash = 'destroy'
> 
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> 
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> 
> 
> #----------------------------------------------------------------------------
> # enable SDL library for graphics, default = 0
> sdl=0
> 
> #----------------------------------------------------------------------------
> # enable VNC library for graphics, default = 1
> vnc=1
> 
> #----------------------------------------------------------------------------
> # enable spawning vncviewer(only valid when vnc=1), default = 1
> vncviewer=1
> 
> #----------------------------------------------------------------------------
> # no graphics, use serial port
> #nographic=0
> 
> #----------------------------------------------------------------------------
> # enable stdvga, default = 0 (use cirrus logic device model)
> stdvga=0
> 
> #-----------------------------------------------------------------------------
> #   serial port re-direct to pty deivce, /dev/pts/n
> #   then xm console or minicom can connect
> serial='pty'
> 
> #----------------------------------------------------------------------------
> # enable ne2000, default = 0(use pcnet)
> ne2000=0
> 
> 
> #-----------------------------------------------------------------------------
> #   enable audio support
> #audio=1
> 
> 
> #-----------------------------------------------------------------------------
> #    set the real time clock to local time [default=0 i.e. set to utc]
> #localtime=1
> 
> 
> #-----------------------------------------------------------------------------
> #    start in full screen
> #full-screen=1
> 
> extra = 'install=nfs://192.168.1.9//opt/software/SLES10/disk1 TERM=xterm
> textmode=0 vnc=1 hostip=192.168.1.253 netmask=255.255.255.0 ide=nodma
> gateway=192.168.1.1 netdevice=eth0'
> 
> ------------------------------------------------------------------------------------------------------------------
> 
> The ide=nodma is a farily recent addtion;  it did not seem at have any
> effect on things.
> 
> Oddly, I did not see this when I used full virtualization.  That
> installation was very normal.  
> 
> I am positive that I need to set something slightly different - I just do
> not know what it it.
> 
> Thanks for any suggestions.


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