If zonecfg determines that the target fs type is nfs it will error and not
allow the zone to be configured. You can jump through hoops and do things to
hide that fact from zonecfg so it doesn't believe that the zone root is
running over nfs but I've got to think that it's not going to be well
teste
I 'm unable to modify pset size configuration.
# poolcfg -c 'modify pset pset-app (uint pset.size = 16 )'
poolcfg: put property pset.size failed: Bad parameter supplied
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-di
Ketan a écrit :
I 'm unable to modify pset size configuration.
# poolcfg -c 'modify pset pset-app (uint pset.size = 16 )'
poolcfg: put property pset.size failed: Bad parameter supplied
I believe you cannot directly changed the size of the pset through the
pset.size property.
pset.size is ju
Indeed, but keep in mind that blog was using straight lofi. What is
described below is leveraging zpool/zfs interfaces. straight lofi was
slow and not too useful outside proof of concept. zpool/zfs seems to be
running just fine.
Derek McEachern wrote:
If zonecfg determines that the target f
Hi Kevin,
It seams that I have the same issue when creating a zone on opensolaris, in
august 2009 this time.
r...@opensolaris:~# zoneadm list -cp
0:global:running:/::native:shared
-:bastoszone:configured:/export/bastoszone::ipkg:shared
r...@opensolaris:~# zoneadm -z bastoszone install
A ZFS f
On Tue 25 Aug 2009 at 01:22PM, bastien sprenger wrote:
> Hi Kevin,
> It seams that I have the same issue when creating a zone on opensolaris, in
> august 2009 this time.
>
> r...@opensolaris:~# zoneadm list -cp
> 0:global:running:/::native:shared
> -:bastoszone:configured:/export/bastoszone::ip
