Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0 Virtualization Guide - Linux
Last Published:
2021-12-21
Product(s):
InfoScale & Storage Foundation (8.0)
Platform: Linux
- Section I. Overview of Veritas InfoScale Solutions used in Linux virtualization
- Overview of supported products and technologies
- About Veritas InfoScale Solutions support for Linux virtualization environments
- About Kernel-based Virtual Machine (KVM) technology
- About the RHEV environment
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Veritas InfoScale Solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring Cluster Server in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing Linux virtualization use cases
- Application visibility and device discovery
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- Virtual machine availability
- Virtual machine availability for live migration
- Virtual to virtual clustering in a Red Hat Enterprise Virtualization environment
- Virtual to virtual clustering in a Microsoft Hyper-V environment
- Virtual to virtual clustering in a Oracle Virtual Machine (OVM) environment
- Disaster recovery for virtual machines in the Red Hat Enterprise Virtualization environment
- Disaster recovery of volumes and file systems using Volume Replicator (VVR) and Veritas File Replicator (VFR)
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About the Cluster Server agents for Docker, Docker Daemon, and Docker Container
- Managing storage capacity for Docker containers
- Offline migration of Docker containers
- Disaster recovery of volumes and file systems in Docker environments
- Application visibility and device discovery
- Section IV. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Mapping devices using paths
Mapping can be achieved using device ID: /dev/disk/by-path/
These links use the persistent properties of a path. For fibre channel devices, the sym-link name is composed of the bus identifier, the Worldwide Name (WWN) of the target, followed by the LUN identifier. A device will have an entry for each path to the device. In environments where multi-pathing is to be performed in the guest, make a mapping for each path for the device.
In the following example both paths to device sdd are mapped to guest_3.
To map a path to a guest
- Identify the devices to map to the guest. Obtain the device IDs.
# udevadm info -q symlink --name sdd | cut -d\ -f 3 disk/by-id/scsi-200173800013420cd
In multi-path environments the device ID can be used to find all paths to the device.
# udevadm info --export-db |grep disk/by-id/scsi-200173800013420cd\ \ | cut -d\ -f 4 /dev/disk/by-path/pci-0000:0b:00.0-fc-0x5001738001340160:0x000000 /dev/disk/by-path/pci-0000:0c:00.0-fc-0x5001738001340161:0x000000
- Map the device to the guest using the path using the device path.
# virsh attach-disk guest_3 \ /dev/disk/by-path/pci-0000:0b:00.0-fc-0x5001738001340160:0x000000 vdb Disk attached successfully # virsh attach-disk guest_3 \ /dev/disk/by-path/pci-0000:0c:00.0-fc-0x5001738001340161:0x000000 vdc Disk attached successfully
- Make the mapping persistent by re-defining the guest.
# virsh dumpxml guest_3 > /tmp/guest_3.xml # virsh define /tmp/guest_3.xml