This content has been marked as final. Show 2 replies
I like the concept of Zones inside of LDoms very much. This is the most flexible combination,
because it allows you to even migrate/upgrade the Zone out of the LDom to a sun4u system, if required.
The point here is, what do you exactly mean with "external zpool"?
If you store the Zone on a SAN Disk which is available to your target control domain, everything is fine for
live migration. We always use one or more SAN Disk per Zone for maximum flexibility.
By external pool I am thinking of the way you probably are doing it, separate LUNs mirrored in a zpool for the zones coming from two separate IO/Service domains. So even if this zpool exist inside the LDOM as zone storage this will not prevent LM ? That's good news. The requirement "no zpool if Live Migration" must then only be valid for the LDOM storage itself and not for storage attached to the running LDOM. I am also worried about a possible performance penalty introducing an extra layer of virtualisation. Have you done any tests regarding this ?