OpenSolaris

Printable Version Enter a New Search
Bug ID 5085664
Synopsis zones don't work on nosuid filesystems
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:zones
Keywords zones
Responsible Engineer Gerald Jelinek
Reported Against s10_55
Duplicate Of
Introduced In solaris_10
Commit to Fix snv_28
Fixed In snv_28
Release Fixed solaris_nevada(snv_28) , solaris_10u3(s10u3_01) (Bug ID:2137754)
Related Bugs 4963321 , 5000972
Submit Date 11-August-2004
Last Update Date 3-December-2005
Description
From a platinum beta customer:

I just tried again on a local disk, with not much success either:
initially, I used /var/crash/zone/local-test (on a local ufs file system)
as zone root for another test zone.  As before, installation went fine, but
booting the zone failed:

# zoneadm -z local-test boot
zoneadm: zone 'local-test': failed to open /var/crash/zone/local-test/dev/zconsole: No such device or address
zoneadm: zone 'local-test': could not prep console slave
zoneadm: zone 'local-test': call to zoneadmd failed

This was due to /var/crash having been mounted nosuid.  After mount -o
remount,suid, I get beyond that error, but not much (and am again at the
same point where booting the zone on an NFS file system failed, at least
the symptoms are identical):

# zoneadm -z local-test boot
zoneadm: zone 'local-test': child process terminated abnormally on signal 10
zoneadm: zone 'local-test': call to zoneadmd failed

Might this be due to the fact that of course the loopback-mounted /lib,
/platform, /sbin, and /usr file systems still come from an NFS server?
Work Around
N/A
Comments
N/A