Veritas InfoScale™ 7.3.1 Virtualization Guide - Solaris
- Section I. Overview of Veritas InfoScale Solutions used in Solaris virtualization
- Section II. Zones and Projects
- Storage Foundation and High Availability Solutions support for Solaris Zones
- About VCS support for zones
- About the Mount agent
- Configuring VCS in zones
- Prerequisites for configuring VCS in zones
- Deciding on the zone root location
- Configuring the service group for the application
- Exporting VxVM volumes to a non-global zone
- About SF Oracle RAC support for Oracle RAC in a zone environment
- Known issues with supporting SF Oracle RAC in a zone environment
- Software limitations of Storage Foundation support of non-global zones
- Storage Foundation and High Availability Solutions support for Solaris Projects
- Storage Foundation and High Availability Solutions support for Solaris Zones
- Section III. Oracle VM Server for SPARC
- Storage Foundation and High Availability Solutions support for Oracle VM Server for SPARC
- Oracle VM Server for SPARC deployment models
- Benefits of deploying Storage Foundation High Availability solutions in Oracle VM server for SPARC
- Features
- Split Storage Foundation stack model
- Guest-based Storage Foundation stack model
- Layered Storage Foundation stack model
- System requirements
- Installing Storage Foundation in a Oracle VM Server for SPARC environment
- Provisioning storage for a guest domain
- Software limitations
- Known issues
- Cluster Server support for using CVM with multiple nodes in a Oracle VM Server for SPARC environment
- VCS: Configuring Oracle VM Server for SPARC for high availability
- About VCS in a Oracle VM Server for SPARC environment
- About Cluster Server configuration models in an Oracle VM Server for SPARC environment
- Cluster Server setup to fail over a logical domain on a failure of logical domain
- Cluster Server setup to fail over an Application running inside logical domain on a failure of Application
- Oracle VM Server for SPARC guest domain migration in VCS environment
- Overview of a live migration
- About configuring VCS for Oracle VM Server for SPARC with multiple I/O domains
- Configuring VCS to manage a Logical Domain using services from multiple I/O domains
- Configuring storage services
- Configure a service group to monitor services from multiple I/O domains
- Configure the AlternateIO resource
- Configure the service group for a Logical Domain
- SF Oracle RAC support for Oracle VM Server for SPARC environments
- Support for live migration in FSS environments
- Storage Foundation and High Availability Solutions support for Oracle VM Server for SPARC
- Section IV. Reference
Provisioning boot disks for a guest domain
This section describes how to provision boot disks for a guest domain.
A VxVM volume appears as a full disk by default and can be used as a boot disk for a guest domain.
The following process gives the outline of how a VxVM volume can be used as a boot disk.
The example control domain is named primary
and the guest domain is named ldom1
. The prompts in each step show in which domain to run the command.
To provision boot disks for guest domains
- On the control domain, create a VxVM volume of required size for hosting the guest boot image. In this example, a 7GB volume is created:
primary# vxassist -g boot_dg make bootdisk1-vol 7g
Veritas recommends that you have a mirrored volume to store the boot image:
primary# vxassist -g boot_dg make bootdisk1-vol 7g \ layout=mirror
See the vxassist(1M) manual page for more options.
- Configure a service by exporting the
/dev/vx/dsk/boot_dg/bootdisk1-vol
volume as a virtual disk:primary# ldm add-vdiskserverdevice \ /dev/vx/dsk/boot_dg/bootdisk1-vol bootdisk1-vol@primary-vds0
- Add the exported disk to
ldom1
:primary# ldm add-vdisk vdisk1 bootdisk1-vol@primary-vds0 ldom1
- Follow Oracle's recommended steps to install and boot a guest domain, and use the virtual disk
vdisk1
as the boot disk during the network, CD, or ISO image install.
Note:
It is not supported to encapsulate such a boot disk inside the guest using VxVM or any other 3rd party Volume Management software. Full SCSI disks can be encapsulated, while vdisks that come from volumes cannot.