Never use a file for your OS image. OMG, can you imagine the overhead! That's for playing around with install options.
LDOM warm migration requires a physical device I.em you give it a raw LUN (a slice if you must). Other than that, at least use a zvol The service domain should be 10u9, use LDOM2.0 / oRacle VM for SpARC and be up to date on patches to at least Decemvber if not January. Also make sure your SP firmware is up to date. You are not going to get above a crawl for disk i/o booting from a file. Don't do lofi devices for zones either. ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Mon Feb 07 23:29:58 2011 Subject: Re: [ldoms-discuss] MySQL store procedure running slow in LDOM environment AFAIK MySQL is in release 5.5.x. Are you using the Community or Enterprise release? > using Community Release 5.5.8 In each case are you using ZFS? How have you setyp the virtual disk for LDOM? What (meta)devices LDOM root on? > Not using ZFS for both cases. > here is how I setup the VD: for old solaris 10, both OS and Database server are on same disk. We have four disks and has raid 1. So first two disk are raided and disk 3 and 4 are raided. So I create two image file with mkfile 15G ldom2 and mkfile 100G for database, then ldm add-vdsdev /ldomdb/ldom2 vol2@primary-vds0, ldm add-vdsdev /ldomdb/ldom2a vol2a@primary-vds0 for the new solaris 10, I use the same virtual disk as old solaris but mysql store procedure takes 40 times slower. However when I use ldm add-vdsdev /dev/dsk/c1t2d0s2 c1t2d0@primary-vds0 exported as physical disk to guest ldom, only took 13 seconds. Thank you! -- This message posted from opensolaris.org _______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss _______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
