InfoScale™ 9.0 Virtualization Guide - Linux
- Section I. Overview of InfoScale solutions used in Linux virtualization
- Overview of supported products and technologies
- About InfoScale support for Linux virtualization environments
- About KVM technology
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- InfoScale solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring VCS in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing InfoScale an OpenStack environment
- Section IV. 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 Hyper-V environment
- Virtual to virtual clustering in an OVM environment
- 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
- Section V. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Configure Storage Foundation components as backend storage for virtual machines
Arctera supports extension of Storage Foundation (SF) components from the host to guest virtual machines as generic SCSI-3 disks, where SF components are the backing storage for virtual machines. After installing the SFCFSHA cluster, you can configure SF components on individual virtual machines through RHEV-M, which is enabled by the VRTSrhevm CLI package. The guest virtual machines use the exported SCSI-3 disks as backend storage and these must be visible across the cluster.
Live migration of virtual machines is required for cases of workload management, host failure, or a network issue. You can configure VCS on the host to ensure a coordinated live migration in the event of a disruption or maintenance. Without VCS configured on the host, you need to manually run the VRTSrhevm
CLI to perform live migration of the virtual machine.