Sam Nicholson wrote: > Well, with zfs on-board, vmstat's going to show it all used up. > > If I'm running out of memory, I'm really running out of places to hold > references to memory. I've got 8GB and that much more swap. And the system > is performing nothing harder than a series of pkgadds. (luupgrade, as it > were, but other loads, pax -rw /net/server/dir . will do it also.) > > (Pause while I go look for something...Seem to recall some forum msgs > regarding zfs) > > Sigh, I now know far more than I ever wanted to about Xen. > > OK, I'm suspicious that it's a ZFS/Xen interaction. I'm off to test (best as > I can) the following hypothesis: > > Solaris/x86xpv reports the same memory values to ZFS/arc as does Solaris > x86pc. But ZFZ/arc is designed to let Solaris have enough memory for > Solaris. But perhaps not enough for Solaris+Xen. My tool will be mdb -k > ::memstat > > I'm adding the zfs->discuss list to the distro. > > But it will be a few days before I can pull this system down to do that. > Hopefully someone already knows the answer...
If your using zfs on dom0, you need to do some tuning. Here are some zfs tuning suggestions.. MRJ -- On dom0, you should limit the amount of memory uses by adding dom0_mem to grubs menu.lst. Normally, if you have zfs, you should set dom0_mem to ~ 2G. kernel$ /boot/$ISADIR/xen.gz com1=9600,8n1 console=com1 dom0_mem=2g You should also limit the amount of memory can give away. svccfg -s xvm/xend setprop config/dom0-min-mem=2000 svcadm refresh xvm/xend;svcadm restart xvm/xend If your using zfs in dom0, you should limit the size of the arc. I would also stay away from debug bits on dom0 when your using zfs. echo "set zfs:zfs_arc_max = 0x10000000" >> /etc/system If your using a disk file (vs a zvol) on a zfs filesystem, you should set the recordsize for that fs to 8k. zvols already default to 8k. zfs set recordsize=8k rpool/guests _______________________________________________ xen-discuss mailing list [email protected]
