11-21-2008
capped-memory in zone
How does capped-memory work in zones?
I have 32G of memory and 10 zones.
I want about physical=4G and swap=4G in each zone.
Is this possible? I am going over the 32G.
10 More Discussions You Might Find Interesting
1. Solaris
Guys,
How to find memory size on solaris zone? We have total 16 GB and have 3 zone, but not sure how to find memory size for each zone? Please help. (1 Reply)
Discussion started by: mokkan
1 Replies
2. Solaris
Hello all,
How can i find the memory usuage per zone in solaris. (5 Replies)
Discussion started by: sophos
5 Replies
3. Solaris
We have several containers on one machine and would like to reserve some memory for the global zone. capped-memory only allows max physical/swap and setting a max on each container isn't an option. The server has 32GB physical and 30GB swap. Currently there are ten containers on it. Normally... (6 Replies)
Discussion started by: kharjahn
6 Replies
4. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
5. Solaris
Hi all,
I have a server running an Oracle database that is part of a Solaris M5000 container. Presumably this is referred to as a zone within a cluster, not sure if I get the terminology right.
Anyway, a third-party manages the zone and unfortunately is not "helpful/friendly" to assist me on... (1 Reply)
Discussion started by: newbie_01
1 Replies
6. Solaris
Calling upon all Solaris zone experts.
I have a Sun T3-1 that is running a few whole-root zones. I've set the 'capped-memory' setting on all the zones.
However, I have a problem on the one zone. Under load it uses more memory that has been allocated to it.
zonecfg -z sunrep02 export
... (4 Replies)
Discussion started by: soliberus
4 Replies
7. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
8. Solaris
We have a zone configured in our X4600 machine with memory capped to 16GB. Most of the time zone is running with high physical memory utilization. It seems from "top" command shows that the command "kernel" is locks 15GB phy. memory and not using swap memory. Whenever we restart the application... (2 Replies)
Discussion started by: rock123
2 Replies
9. Solaris
Is there a way to find the capped memory of a solaris non global zone from the non global zone itself (given rcapd is disabled) (6 Replies)
Discussion started by: CuriousDev
6 Replies
10. Solaris
Hi
I have a problem with Virtual Memory on one local zone (myzone1):
//from local zone (myzone1)
swap -s
total: 22888544k bytes allocated + 0k reserved = 22888544k used, 3325856k available
swap -l
swapfile dev swaplo blocks free
/dev/swap ... (0 Replies)
Discussion started by: primo102
0 Replies
LEARN ABOUT DEBIAN
shorewall6-nesting
SHOREWALL6-NESTING(5) [FIXME: manual] SHOREWALL6-NESTING(5)
NAME
nesting - shorewall6 Nested Zones
SYNOPSIS
child-zone[:parent-zone[,parent-zone]...]
DESCRIPTION
In shorewall6-zones[1](5), a zone may be declared to be a sub-zone of one or more other zones using the above syntax. The child-zone may be
neither the firewall zone nor a vserver zone. The firewall zone may not appear as a parent zone, although all vserver zones are handled as
sub-zones of the firewall zone.
Where zones are nested, the CONTINUE policy in shorewall6-policy[2](5) allows hosts that are within multiple zones to be managed under the
rules of all of these zones.
EXAMPLE
/etc/shorewall6/zones:
#ZONE TYPE OPTION
fw firewall
net ipv6
sam:net ipv6
loc ipv6
/etc/shorewall6/interfaces:
#ZONE INTERFACE BROADCAST OPTIONS
- eth0 detect blacklist
loc eth1 detect
/etc/shorewall6/hosts:
#ZONE HOST(S) OPTIONS
net eth0:[::]
sam eth0:[2001:19f0:feee::dead:beef:cafe]
/etc/shorewall6/policy:
#SOURCE DEST POLICY LOG LEVEL
loc net ACCEPT
sam all CONTINUE
net all DROP info
all all REJECT info
The second entry above says that when Sam is the client, connection requests should first be processed under rules where the source zone is
sam and if there is no match then the connection request should be treated under rules where the source zone is net. It is important that
this policy be listed BEFORE the next policy (net to all). You can have this policy generated for you automatically by using the
IMPLICIT_CONTINUE option in shorewall6.conf[3](5).
Partial /etc/shorewall6/rules:
#ACTION SOURCE DEST PROTO DEST PORT(S)
...
ACCEPT sam loc:2001:19f0:feee::3 tcp ssh
ACCEPT net loc:2001:19f0:feee::5 tcp www
...
Given these two rules, Sam can connect with ssh to 2001:19f0:feee::3. Like all hosts in the net zone, Sam can connect to TCP port 80 on
2001:19f0:feee::5. The order of the rules is not significant.
FILES
/etc/shorewall6/zones
/etc/shorewall6/interfaces
/etc/shorewall6/hosts
/etc/shorewall6/policy
/etc/shorewall6/rules
SEE ALSO
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5),
shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)
NOTES
1. shorewall6-zones
http://www.shorewall.net/manpages6/shorewall-zones.html
2. shorewall6-policy
http://www.shorewall.net/manpages6/shorewall6-policy.html
3. shorewall6.conf
http://www.shorewall.net/manpages6/shorewall6.conf.html
[FIXME: source] 06/28/2012 SHOREWALL6-NESTING(5)