On Thu, 2008-06-26 at 17:16 +0100, Lewis Thompson wrote:
Q: Can I configure my zones on a ZFS filesystem?
Thanks for everybody's feedback on this. I would like to update the
Zones FAQ at opensolaris.org with the information. Before I do this I
would like to confirm I have understood
On Tue, 2008-09-09 at 09:04 -0400, Jeff Victor wrote:
The zonecfg man page has an example of the use of fs options:
zonecfg:myzone3 add fs
zonecfg:myzone3:fs set dir=/usr/local
zonecfg:myzone3:fs set special=/opt/local
zonecfg:myzone3:fs set type=lofs
Hi,
I have a simple zone configured to test the VxFS 'convosync=direct'
option. It's an s10u5 machine with no additional patches:
zonecfg:lt203398:fs info
fs:
dir: /foo
special: /dev/lofi/1
raw: /dev/rlofi/1
type:
Hi,
http://opensolaris.org/os/community/zones/faq/#sa_zfs states:
Q: Can I configure my zones on a ZFS filesystem?
A: Solaris 10 Update Release:
It is possible to install a zone on a ZFS file system. However, at this
time, we do not recommend putting the zonepath of a non-global zone on
ZFS
On Wed, 2008-05-21 at 12:56 -0700, Steve Lawrence wrote:
In the global zone, do you have two ip addresses (one on vnet0, one on vnet1)
or is vnet1 configured as standby?
Hi Steve,
We have the following global zone config:
vnet0: flags=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu
On Wed, 2008-05-21 at 15:09 -0700, Erik Nordmark wrote:
Does the initial placement on something different than vnet1 cause a
problem? Or is it just confusing?
Hi Erik,
In this case it is just causing some confusion but functionality is not
impacted.
Thanks,
Lewis
On Tue, 2008-05-20 at 13:56 -0700, Steve Lawrence wrote:
It is documented here:
http://docs.sun.com/app/docs/doc/819-2450/z.admin.task-60?l=koa=viewq=multipathing
The behavior you are seeing is not specifically documented, but it seems
reasonable. What behavior are you expecting?
Hi
Hi,
I have a customer who has a basic IPMP config in his global zone:
vnet0 vnet1 [currently vnet0 has the 'floating' IP]
In addition he has a zone with ip-type=shared where physical=vnet1
When the zone boots the zone interface gets created on vnet0 instead of
vnet1
I have verified this
