Re: [zones-discuss] issues with zoneadm attach

2010-05-19 Thread Gael m

Hello

Any thoughts on that one issue ?

Regards

Gael

Sent from my iPhone

On May 17, 2010, at 5:04, "Enda o'Connor - Sun Microsystems Ireland -  
Software Engineer"  wrote:



Hi
Could I see the zonecfg ( ie zonecfg -z apsz8003 export )
also if this zone is on zfs or is using zfs datasets then zfs list  
as well.


Enda

Gael wrote:

Hello,
Before opening yet another never ending case, I wanted to consult  
with you all to see if that is a known issue and some eventual work  
around.
I have been migrating our servers to Solaris 10 U8 with zfs boot.  
The latest version was using 142900-10 for kernel.
Following the release of 142900-11, I decided to experiment a  
patching using live upgrade. I have been using that a lot in the  
last few months.
But it was the first attempt on a machine with zones. As my zones  
are on some hitachi san luns managed by veritas (with ufs...), I  
simply did shutdown the test zones and detached them.
Then I ran the usual commands:  lucreate -n s10u8-20100515, the ABE  
was created without issue. Then I lumounted it, and applied patches  
to it using pca (pca -i -R /.alt.s10u8-20100515), then luumounted  
it, activated it and rebooted on it. As usual, it did come back  
with the newest version of the patches as expected. I have done  
that process quite a bit recently and I do admit it usually works  
fine on GZ only machines.
But here comes troubles... when reattaching the zones (both without  
and with -u option), I'm getting that error vsmd8008:/zones/ 
apsz8003 #zoneadm -z apsz8003 attach -u

zoneadm: getting the detach information failed: Out of memory
zoneadm: zone 'apsz8003': 'detach' failed with exit code 1.
Cannot generate the information needed to attach this zone.
vsmd8008:/zones/apsz8003 #zoneadm -z apsz8003 attach  zoneadm:  
getting the detach information failed: Out of memory

zoneadm: zone 'apsz8003': 'detach' failed with exit code 1.
Cannot generate the information needed to attach this zone.
vsmd8008:/zones/apsz8003 #ls -ltr
total 4870
drwx--   2 root root8192 May 14 10:32 lost+found
drwxr-xr-x   2 root root 512 May 14 23:54 lu
drwxr-xr-x  20 root root 512 May 15 00:26 root
-rw-r--r--   1 root root 2472353 May 15 19:25  
SUNWdetached.xml

drwxr-xr-x  12 root root1024 May 15 20:25 dev
-rw-r--r--   1 root root   0 May 15 20:25 SUNWupdate.xml
The funny thing is that the same zoneadm attach -u process worked  
when i was at 142900-10 (and previous versions). That is how I have  
migrated the machine zones from U4 to U8.
(a very long script and an interesting collection of pkgrm/pkgadd/ 
patchadd to make the old u4 zone look nearly identical to a freshly  
build zone on u8)

Regards
Gael
--
Gael Martinez
--- 
-

___
zones-discuss mailing list
zones-discuss@opensolaris.org



___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] issues with zoneadm attach

2010-05-17 Thread Gael
Hello

vsmd8008:/root #zonecfg -z apsz8003 export
create -b
set zonepath=/zones/apsz8003
set autoboot=true
set pool=fss_default_pool
set ip-type=shared
add net
set address=10.115.96.143
set physical=ce0
end
add rctl
set name=zone.cpu-shares
add value (priv=privileged,limit=10,action=none)
end
add rctl
set name=zone.max-lwps
add value (priv=privileged,limit=1000,action=deny)
end

The zones are sitting on an ufs filesystem.

vsmd8008:/root #df -h
Filesystem size   used  avail capacity  Mounted on
rpool/ROOT/s10u8-20100515
   134G   2.7G   113G 3%/
/devices 0K 0K 0K 0%/devices
ctfs 0K 0K 0K 0%/system/contract
proc 0K 0K 0K 0%/proc
mnttab   0K 0K 0K 0%/etc/mnttab
swap   6.0G   1.6M   5.9G 1%/etc/svc/volatile
objfs0K 0K 0K 0%/system/object
sharefs  0K 0K 0K 0%/etc/dfs/sharetab
/platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
   116G   2.7G   113G 3%
/platform/sun4u-us3/lib/libc_psr.so.1
/platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
   116G   2.7G   113G 3%
/platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
fd   0K 0K 0K 0%/dev/fd
rpool/ROOT/s10u8-20100515/var
   134G   1.6G   113G 2%/var
swap   512M64K   512M 1%/tmp
swap   5.9G32K   5.9G 1%/var/run
swap   5.9G 0K   5.9G 0%/dev/vx/dmp
swap   5.9G 0K   5.9G 0%/dev/vx/rdmp
/dev/vx/dsk/apsz8003/apsz8003-root
   7.9G   1.9G   5.9G24%/zones/apsz8003
/dev/vx/dsk/apsz8004/apsz8004-root
   7.9G   1.9G   5.9G25%/zones/apsz8004
rpool/export   134G21K   113G 1%/export
rpool/home 256M21K   256M 1%/home
rpool  134G98K   113G 1%/rpool
rpool/var-core 1.0G   2.1M  1022M 1%/var/core
vsmd8008:/root #
Regards
On Mon, May 17, 2010 at 5:04 AM, Enda o'Connor - Sun Microsystems Ireland -
Software Engineer  wrote:

> Hi
> Could I see the zonecfg ( ie zonecfg -z apsz8003 export )
> also if this zone is on zfs or is using zfs datasets then zfs list as well.
>
> Enda
>
> Gael wrote:
>
>>  Hello,
>>
>> Before opening yet another never ending case, I wanted to consult with you
>> all to see if that is a known issue and some eventual work around.
>>
>> I have been migrating our servers to Solaris 10 U8 with zfs boot. The
>> latest version was using 142900-10 for kernel.
>> Following the release of 142900-11, I decided to experiment a patching
>> using live upgrade. I have been using that a lot in the last few months.
>> But it was the first attempt on a machine with zones. As my zones are on
>> some hitachi san luns managed by veritas (with ufs...), I simply did
>> shutdown the test zones and detached them.
>> Then I ran the usual commands:  lucreate -n s10u8-20100515, the ABE was
>> created without issue. Then I lumounted it, and applied patches to it using
>> pca (pca -i -R /.alt.s10u8-20100515), then luumounted it, activated it and
>> rebooted on it. As usual, it did come back with the newest version of the
>> patches as expected. I have done that process quite a bit recently and I do
>> admit it usually works fine on GZ only machines.
>>
>> But here comes troubles... when reattaching the zones (both without and
>> with -u option), I'm getting that error
>> vsmd8008:/zones/apsz8003 #zoneadm -z apsz8003 attach -u
>> zoneadm: getting the detach information failed: Out of memory
>> zoneadm: zone 'apsz8003': 'detach' failed with exit code 1.
>> Cannot generate the information needed to attach this zone.
>> vsmd8008:/zones/apsz8003 #zoneadm -z apsz8003 attach  zoneadm: getting the
>> detach information failed: Out of memory
>> zoneadm: zone 'apsz8003': 'detach' failed with exit code 1.
>> Cannot generate the information needed to attach this zone.
>>
>> vsmd8008:/zones/apsz8003 #ls -ltr
>> total 4870
>> drwx--   2 root root8192 May 14 10:32 lost+found
>> drwxr-xr-x   2 root root 512 May 14 23:54 lu
>> drwxr-xr-x  20 root root 512 May 15 00:26 root
>> -rw-r--r--   1 root root 2472353 May 15 19:25 SUNWdetached.xml
>> drwxr-xr-x  12 root root1024 May 15 20:25 dev
>> -rw-r--r--   1 root root   0 May 15 20:25 SUNWupdate.xml
>>
>> The funny thing is that the same zoneadm attach -u process worked when i
>> was at 142900-10 (and previous versions). That is how I have migrated the
>> machine zones from U4 to U8.
>> (a very long script and an interesting collection of pkgrm/pkgadd/patchadd
>> to make the old u4 zone look nearly identical to a freshly build zone on u8)
>>
>> Regards
>> Gael
>>