[OmniOS-discuss] LX zone empty error messages

[Michael Talbott]

Ah HA! So, I did not have a zfs dataset at /zones. I created one, retried the process and the same ominous message popped up :( Then I rebooted and tried again, and success! Hurray! Now I can carry on with my testing :)

Thanks!


> On Sep 22, 2016, at 6:42 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> 
>> On Sep 22, 2016, at 9:07 PM, Michael Talbott <mtalbott at lji.org> wrote:
> 
> <SNIP!>
> 
>> And for giggles, I gunzipped the file and tried it with the unzipped version. Same deal. Any ideas?.. I'm running this as a VM for testing before I put it on bare metal. Could that be the issue or did I miss something critical above? I wish the error message said *something* ;) Any other way of getting some extra verbose output to see where it's dying?
> 
> Weird.
> 
> One thing you can try is not only to uninstall the zone, but also delete its configuration (after exporting it) and then re-create it.
> 
> I'm trying to reproduce your bug right now.  I got this:
> 
> zonecfg:lx2> export
> create -b
> set zonepath=/zones/lx2
> set brand=lx
> set autoboot=false
> set ip-type=exclusive
> add net
> set physical=lx2
> add property (name=gateway,value="x.y.z.1")
> add property (name=primary,value="true")
> add property (name=ips,value="x.y.z.246/24")
> end
> add attr
> set name=dns-domain
> set type=string
> set value=x.y.z.net
> end
> add attr
> set name=resolvers
> set type=string
> set value=x.y.z.1
> end
> add attr
> set name=kernel-version
> set type=string
> set value=2.6.32
> end
> zonecfg:lx2> exit
> # zoneadm list -cv
>  ID NAME             STATUS     PATH                           BRAND    IP    
>   0 global           running    /                              ipkg     shared
>   4 lx1              running    /zones/lx1                     lx       excl  
>   - tz2              installed  /zones/tz2                     lipkg    excl  
>   - lx0              installed  /zones/lx0                     lx       excl  
>   - lx2              configured /zones/lx2                     lx       excl  
> # zoneadm -z lx2 install -s /rpool/lx-stuff/joyent-images/centos6.gz 
> WARNING: skipping network interface 'lx2': object not found
> A ZFS file system has been created for this zone.
> # zoneadm list -cv
>  ID NAME             STATUS     PATH                           BRAND    IP    
>   0 global           running    /                              ipkg     shared
>   4 lx1              running    /zones/lx1                     lx       excl  
>   - tz2              installed  /zones/tz2                     lipkg    excl  
>   - lx0              installed  /zones/lx0                     lx       excl  
>   - lx2              installed  /zones/lx2                     lx       excl  
> # 
> 
> 
> Okay... dumb question:  is "/zones" on your box its own ZFS dataset?
> 
> # zfs list | grep /zones
> rpool/zones                        8.57G  34.6G    20K  /zones
> rpool/zones/lx0                    1.33G  34.6G  1.87G  /zones/lx0
> rpool/zones/lx1                    1.86G  34.6G  1.81G  /zones/lx1
> rpool/zones/lx2                     787M  34.6G   787M  /zones/lx2
> rpool/zones/tz2                    4.62G  34.6G  20.5K  /zones/tz2
> rpool/zones/tz2/ROOT               4.62G  34.6G    19K  legacy
> rpool/zones/tz2/ROOT/zbe-14        2.32M  34.6G  1.31G  legacy
> rpool/zones/tz2/ROOT/zbe-15        2.50M  34.6G  1.24G  legacy
> rpool/zones/tz2/ROOT/zbe-16         100K  34.6G  1.11G  legacy
> rpool/zones/tz2/ROOT/zbe-17        1.89M  34.6G  1.25G  legacy
> rpool/zones/tz2/ROOT/zbe-21        1.89M  34.6G  1.26G  legacy
> rpool/zones/tz2/ROOT/zbe-22        2.55M  34.6G  1.26G  legacy
> rpool/zones/tz2/ROOT/zbe-25        10.4M  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-29          73K  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-30        28.8M  34.6G  1.12G  legacy
> rpool/zones/tz2/ROOT/zbe-31        18.5M  34.6G  1.11G  legacy
> rpool/zones/tz2/ROOT/zbe-32        4.55G  34.6G  1.13G  legacy
> rpool/zones/tz2/ROOT/zbe-33        68.5K  34.6G  1.13G  legacy
> # 
> 
> 
> It should be, and MAYBE that's causing your problem?
> 
> Dan
>