On 2/4/11 10:32 PM, Darren Reed wrote:
On a test system that is using only ZFS, I'm trying to create a zone
but it keeps failing with:
netvirt-d1 ~# zoneadm -z exclusivetestzone1 install
ERROR: the zonepath must be a ZFS dataset.
The parent directory of the zonepath must be a ZFS dataset so that
plit up since
> there is no error condition for when it is NULL.
> I'll review be_mount.c next and send comments in a separate mail.
Good point, I'll add a check to make sure it's not NULL.
>
> Thanks
> Tim
>
>> Evan Layton wrote:
>>> Hello Al
of this function - that is, code running in the
> global zone that's processing non-global zones - this if() can be removed,
> along with 1895.
I removed them.
>
> 1944 - A comment stating this is getting the uuid of the newly cloned
> parent BE would be nice.
comment added
&
Evan Layton wrote:
> Hello All,
>
> We're down to the wire on the zone support changes to SNAP upgrade and are
> looking for code review comments. We'll be taking comments up until COB
> Tuesday
> October 7th. Your comments are as always welcome and appreciated.
>
Hello All,
We're down to the wire on the zone support changes to SNAP upgrade and are
looking for code review comments. We'll be taking comments up until COB Tuesday
October 7th. Your comments are as always welcome and appreciated.
Defect 3686 is the blocker bug that was submitted to cover this
Jerry Jelinek wrote:
> Evan Layton wrote:
>> This is the same as what is done with /rpool/ROOT and ZFS boot, with
>> "ROOT" being the confined area where we place BE's. An admin can still
>> create things there but this is the only place that we look for BE
Jerry Jelinek wrote:
> Ethan,
>
> Ethan Quach wrote:
>>
>> Jerry Jelinek wrote:
>>> Ethan Quach wrote:
Hey Jerry,
I just thought about something regarding the zones dataset
namespace. Instead of creating the dataset for zone roots at:
rpool/export/zones/z1/rpool/
