It isn't a deficiency in the zones virtualisation model. In fact it is a
deliberate design goal
that zones NOT have such a high level of privielge available to them. The
reason you can't
create pools in a zone is because they don't have access to the privielges to
do so.
If you really need t
Easy is a relative term. I'd rather not have to refactor the code to work
around a deficiency in the virtualisaton method. I've decided to switch to a
full hypervisor and leave zones for less problematic configurations.
--
This message posted from opensolaris.org
__
+--
| On 2009-07-15 12:24:43, Alastair Neil wrote:
|
| How then do you create two zpools with the same name one for the test zone
and one for the devel zone?
You don't. But you can easily hack around it.
e.g.,
rpool/zo
How then do you create two zpools with the same name one for the test zone and
one for the devel zone?
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
On Wed, Jul 15, 2009 at 11:28:21AM -0700, Alastair Neil wrote:
> I am trying to set up two zones to exactly duplicate a production server one
> for test and one for development. The production server has a number of
> zpools which are specifically named and the scripts we are testing expect
> t
I am trying to set up two zones to exactly duplicate a production server one
for test and one for development. The production server has a number of zpools
which are specifically named and the scripts we are testing expect this naming.
I have run in to a brick wall, as it seems that it is impos