Jack wrote:
This doesn't have anything to do with your problem...
But I'm curious, what do you have for CPUs?
Are you limiting dom0 memory on boot? What about
the number of CPUs dom0 can use? e.g.
kernel /boot/amd64/xen.gz com1=9600,8n1 console=com1 dom0_mem=2g
dom0_max_vcpus=2 dom0_vcpus_pin=true
Okay, this is a Intel(r) Xeon(r) CPU E5420 @ 2.50GHz based system, there are 8
cores (twin quadcores).
No, I'm not doing anything to the boot of xVM. I used to do that on my linux versions
> of xen, but got out of the habit when I saw xVM managing it okay on it's own.
Plus,
> I didn't read where they wanted that to happen. Guess I'll give that a shot.
But
> what about ZFS? doesn't it want just a ton of memory? Seems like I should
have a
> bunch around for that. That's why I asked for 48G ram on these machines ;)
>
this is my grub entry:
title Solaris xVM
findroot (pool_rpool,0,a)
kernel$ /boot/$ISADIR/xen.gz
module$ /platform/i86xpv/kernel/$ISADIR/unix
/platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS
module$ /platform/i86pc/$ISADIR/boot_archive
you should limit the dom0 cpus to 2-4 depending on your
load (mpstat) when doing a lot of IO. Even better if you
can isolate dom0 CPUs from the guests. This is easier if
you have a really large system of course :-) You also
should limit the dom0 memory so you don't balloon dom0
memory down. For your setup, I would think 16g should
be plenty... But you won't know for sure until you try :-)
kernel$ /boot/$ISADIR/xen.gz com1=9600,8n1 console=com1 dom0_mem=16g
dom0_max_vcpus=4 dom0_vcpus_pin=true
As a safety net, you could restrict dom0 ballooning
so you don't accidentally take away its memory.
svccfg -s xvm/xend setprop config/dom0-min-mem=16000
svcadm refresh xvm/xend;svcadm restart xvm/xend
Since your using zfs in dom0, you should limit the
size of the arc. I would start with 1/2 the memory
in your dom0 if you have >= 4G. e.g.
echo "set zfs:zfs_arc_max = 0x200000000" >> /etc/system
What version of Opensolaris are you using? Are you using stock Xen bits (that
come with opensolaris)? The bug looks familiar, but I'll have to do some
searching...
Sun Microsystems Inc. SunOS 5.11 snv_101b November 2008
and yes, stock xVM.
Now, I've tried xVM on another 2900 configured identically to this one with the
> Sun Microsystems Inc. SunOS 5.11 snv_111b November 2008 version
-
> have it running right now, and performance is really bad there. It's so slow
> it's unreal, so I just quit on that and went back to the one that worked
pretty
> well. Boot times on the newer 0906 version are around 20 minutes for rhel5.2
> and centos 5.3 won't even boot after being installed. That's why I quit
> there - had something that worked, why complain ;)
The centos5.3 problem is likely
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6836480
But you shouldn't be seeing things go slow like that? Can you try the
above menu.lst changes and arc limits to see if it still runs slow?
You can copy the xdb driver from b118 and it should fix the centos5.3
problem your seeing.
What kind of disk is the boot disk (sata)? If sata, I assume it's
not running in IDE mode?
Thanks,
MRJ
_______________________________________________
xen-discuss mailing list
[email protected]
