Scott L. Burson wrote: > Quoting Mark Johnson <[EMAIL PROTECTED]>: > >> First, your disks need to be running in sata mode >> vs ata mode. i.e. format should report c0t0d0 vs >> c0d0. > > You're talking about the BIOS setting? > >> You should limit dom0's memory to 2G. e.g. >> kernel /boot/amd64/xen.gz com1=9600,8n1 console=com1 dom0_mem=2G > > Ouch, that's unfortunate. I run some large computational processes on > this machine from time to time. I guess I will have to run them in a > domU... we'll see how they perform. (I guess I can give the domU direct > access to the swap partitions (removing them from dom0, of course); that > should help.)
In general, dom0's really not meant to be used as a general purpose computer. You can, but if your using it in a desktop scenario, your better off going with VirtualBox (unless you need support for 64-bit guests, MP, migration, etc.). You don't have to limit dom0_mem, but zfs doesn't like when memory is taken away. Limiting the arc cache helps, but isn't a complete solution. You can try without it and see. >> The zfs arc has to be limited. e.g. >> echo "set zfs:zfs_arc_max = 0x10000000" >> /etc/system >> >> If you are using files vs zvols for disks, you >> should setup the recordsize to 8k. e.g. >> zfs set recordsize=8k tank/guests > > Is there any reason I would want to use a file rather than a zvol? zvols are much better.. Can't be migrated though. In your case, you would want to use zvols. MRJ >> You should make sure dom0 doesn't balloon down >> significantly. >> svccfg -s xvm/xend setprop config/dom0-min-mem 2000 >> svcadm refresh xvm/xend;svcadm restart xvm/xend > > Thanks for all the tips. I will give it another try. > > -- Scott > _______________________________________________ xen-discuss mailing list [email protected]
