Linux KVM Virtualization Guest Operations: Difference between revisions
| Line 52: | Line 52: | ||
=Cloning and Snapshotting= | =Cloning and Snapshotting= | ||
==Clone a Guest Virtual Machine== | |||
The goal of a ''cloning'' operation is to create an entirely new guest, based on the configuration of an existing guest. Entirely new storage must be provisioned during the cloning operation, and the O/S image must be transferred on the new storage and updated as described below. Also, care should be taken to avoid conflict while accessing shared resources - memory, CPUs, network devices. | The goal of a ''cloning'' operation is to create an entirely new guest, based on the configuration of an existing guest. Entirely new storage must be provisioned during the cloning operation, and the O/S image must be transferred on the new storage and updated as described below. Also, care should be taken to avoid conflict while accessing shared resources - memory, CPUs, network devices. | ||
{{Internal|Linux Virtualization Cloning a KVM Guest Virtual Machine|Cloning a Guest Virtual Machine}} | |||
== | ==Snapshot Guest Virtual Machine== | ||
The goal of a ''snapshotting'' operation is to preserve the state of the guest, at a certain moment in time, so it can be reverted to, later, possibly after the guest was removed for a while from the virtualization host. For more theoretical considerations concerning guest snapshots, see "[[Linux_Virtualization_Concepts#KVM_Virtual_Machine_Snapshot|Linux Virtualization Concepts - KVM Virtual Machine Snapshot]]". | |||
* [[Linux KVM Virtualization Manual Low-Level Guest Snapshot Procedure|Manual Low-Level Guest Snapshot Procedure]] | |||
* [[Linux KVM Virtualization Guest Snapshot Using virsh snapshot Functionality|Guest Snapshot Using virsh snapshot Functionality]] | |||
{{Internal|Linux Virtualization Snapshot a KVM Guest Virtual Machine|Snapshot a Guest Virtual Machine}} | {{Internal|Linux Virtualization Snapshot a KVM Guest Virtual Machine|Snapshot a Guest Virtual Machine}} | ||
Revision as of 19:15, 3 November 2017
Internal
Overview
List Available Guests
virsh list [--all]
Information about a Guest
Guest Configuration
The following command provides details, about:
- the amount of virtual memory and virtual CPU allocated to the guest.
- guest disk devices, their type (qcow, raw, etc.), their mapping on external storage volumes, etc.
- guest network devices.
- etc.
virsh dumpxml <guest-name>
Filesystems
virt-filesystems --all -lh -d <guest-name>
Start/Stop Guest Virtual Machines
virsh start [--console] <vm-name>
virsh shutdown <vm-name>
Connect to the Guest Virtual Machine
virsh console
Create a Guest Virtual Machine
Can I name a guest "ose36.master", or "environment-name.host-in-environment-name"?. It would be useful in virsh list.
Virtualization host storage and host-level networking must be configured as a prerequisite to creating guest virtual machines. Once storage pools and storage volumes are made available, and the networking is configured, guest virtual machines can be created with
virt-install
If the XML definition of a virtual machine is available, it can be created with:
virsh define
Add Storage to Guests
Cloning and Snapshotting
Clone a Guest Virtual Machine
The goal of a cloning operation is to create an entirely new guest, based on the configuration of an existing guest. Entirely new storage must be provisioned during the cloning operation, and the O/S image must be transferred on the new storage and updated as described below. Also, care should be taken to avoid conflict while accessing shared resources - memory, CPUs, network devices.
Snapshot Guest Virtual Machine
The goal of a snapshotting operation is to preserve the state of the guest, at a certain moment in time, so it can be reverted to, later, possibly after the guest was removed for a while from the virtualization host. For more theoretical considerations concerning guest snapshots, see "Linux Virtualization Concepts - KVM Virtual Machine Snapshot".