zone reboot
you never have to reboot the platform to do stuff to zones, and the reboot time 
for  a zone is 10 seconds on an Ultrasparc II single-cpu system. On a T-series 
machine it's about 5 seconds.


________________________________
From: veritas-vx-boun...@mailman.eng.auburn.edu 
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of William Havey
Sent: Friday, March 05, 2010 11:28 AM
To: Hudes, Dana
Cc: veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] Simulator 5.1 and Solaris 10 zones

Is this a reboot of the server or a reboot of the zone?

On Fri, Mar 5, 2010 at 11:07 AM, Hudes, Dana 
<hud...@hra.nyc.gov<mailto:hud...@hra.nyc.gov>> wrote:
If you add an inherit-pkg-dir to a configuration and then install the zone, the 
only way to get rid of it is uninstall (another reason to keep zone root on it 
own filesystem and user data within the zone on another filesystem), OTOH, if 
you just did add-fs then you can remove it from the configurtion reboot and 
it's gone.


________________________________
From: William Havey [mailto:bbha...@gmail.com<mailto:bbha...@gmail.com>]
Sent: Friday, March 05, 2010 10:22 AM
To: Hudes, Dana
Cc: veritas-vx@mailman.eng.auburn.edu<mailto:veritas-vx@mailman.eng.auburn.edu>
Subject: Re: [Veritas-vx] Simulator 5.1 and Solaris 10 zones

Dana,

If /opt, or any directory, is inadvertently added to zone root, can it be 
removed from the zone configuration without having to re-install the zone?

Bill

On Fri, Mar 5, 2010 at 9:39 AM, Hudes, Dana 
<hud...@hra.nyc.gov<mailto:hud...@hra.nyc.gov>> wrote:
Note that while you can have a local disk or shared (SAN, presumably) disk for 
zone root, it is not recommended practice to use the boot disk for zone roots, 
not even if its a separate filesystem. If you have only 2 drives and you 
understandably want to have those mirrored, slice them and make a separate dg 
or zpool for the zone roots. You can throw other stuff in that zpool/dg such as 
home directories but not the Solaris OS. I wouldn't play games with sticking 
/opt (and certainly not /var) in there since that's inherited/copied by local 
zones.

While you can get away with using the root pool/dg for zone roots and it will 
indeed let you and you can boot the zone, come time to use Live Upgrade you 
will find it doesn't work.
Even adding patches in the regular manner has trouble with zone root on 
platform root.


________________________________
From: 
veritas-vx-boun...@mailman.eng.auburn.edu<mailto:veritas-vx-boun...@mailman.eng.auburn.edu>
 
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu<mailto:veritas-vx-boun...@mailman.eng.auburn.edu>]
 On Behalf Of William Havey
Sent: Friday, March 05, 2010 8:56 AM
To: veritas-vx@mailman.eng.auburn.edu<mailto:veritas-vx@mailman.eng.auburn.edu>
Subject: [Veritas-vx] Simulator 5.1 and Solaris 10 zones

http://support.veritas.com/docs/345258

This technote is on the need to set a service group attribute "ContainerInfo". 
It doesn't say how, only what. Neither does the Admin Guide say how-to. The 
Simulator.fails to accept any values for Name, Type, and Enabled.

Any help on using the Simulator 5.1 to configure Solaris 10 local zones 
supporting Oracle  11 would be greatly appreciated.

Bill


_______________________________________________
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to