Clone KVM-based Virtual Machines on Redhat / CentOS Linux Rumi, February 24, 2020 Prerequisite: Operating System and Software Versions Operating System: – Redhat 7.3 Software: – libvirtd (libvirt) 2.0.0 Obtain Source Virtual Machine’s information Before we begin cloning any virtual machine we first need to obtain some basic information about it. The absolute minimum information required about the source virtual machine we are about to clone would be its name and number of disk in use. To get virtual machines name run: # virsh list Id Name State ---------------------------------------------------- 1 server1.local running Next, we may would like to know the number of disk our source virtual machines is using as well as its location. The information about disks location is optional as it only provides us with a hint on where to store new clone disk files for the sake of consistency: # virsh dumpxml server1.local | grep "source file" <source file='/var/lib/libvirt/images/server1.local.qcow2'/> <source file='/var/lib/libvirt/images/server1.local-1.qcow2'/> <source file='/var/lib/libvirt/images/server1.local-2.qcow2'/> From the above output we can see that our original virtual machine has three disks stored in location /var/lib/libvirt/images/. Suspend Source Virtual Machine Before cloning can take place our source virtual machine needs to pause/suspended: # virsh suspend server1.local Domain server1.local suspended Auto-Clone Virtual Machine One way of cloning KVM-based Virtual Machines on Redhat Linux is to use –auto-clone switch. The main advantage of –auto-clone switch is that it automatically clones any number of source disks hence the user does not necessary need to know the location and number of the disk attached to the original virtual machine. The disadvantage is that the user is unable to specify disk names and pride an alternative location to new cloned virtual disks. The following linux command will clone original virtual machine server1.local to new clone virtual machine server2.local automatically using –auto-clone switch. # virt-clone --original=server1.local --name=server2.local --auto-clone WARNING Setting the graphics device port to autoport, in order to avoid conflicting. Allocating 'server2.local.qcow2' | 10 GB 00:00:00 Allocating 'server1.local-1-clone.qcow2' | 5.0 GB 00:00:07 Allocating 'server1.local-2-clone.qcow2' | 5.0 GB 00:00:00 Clone 'server2.local' created successfully. As we can see from the above output the –auto-clone automatically cloned all virtual disks attached to the original virtual machine and appended clone keyword to any additional disks. New cloned virtual machine should be now waiting in shut off state to be started: # virsh list --all Id Name State ---------------------------------------------------- 1 server1.local paused - server2.local shut off Clone Manually Multiple Disk To gain more control over the new cloned disk location and name we can omit the –auto-clone switch and supply all new cloned disk name and destination path using –file switch. Note the number of –file arguments supplied must be equal to the number of disks attached to the original virtual machine. Example: # virt-clone --original=server1.local --name=server2.linuxconfig.org --file /var/lib/libvirt/images/server2.linuxconfig.org.img --file /var/lib/libvirt/images/server2.linuxconfig.org-1.img --file /var/lib/libvirt/images/server2.linuxconfig.org-2.img WARNING Setting the graphics device port to autoport, in order to avoid conflicting. Allocating 'server2.local.img' | 10 GB 00:00:00 Allocating 'server2.local-1.img' | 5.0 GB 00:00:07 Allocating 'server2.local-2.img' | 5.0 GB 00:00:00 Clone 'server2.local' created successfully. Resume/Start At this stage we are ready to resume our original virtual machine server1.local:# virsh resume server1.linuxconfig.org Domain server1.local resumed and also start the newly cloned virtual machine server2.local: # virsh start server2.local Domain server2.local started Check the state of all virtual machines: # virsh list --all Id Name State ---------------------------------------------------- 1 server1.local running 3 server2.local running Related Administrations KVM CentOS 7KVM
Fixing Vesta CP Exim Email Incoming error with T=local_delivery defer (-1): Malformed value “0MM” December 24, 2021December 25, 2021 ******** Applicable for vesta cp 1.0.0-5 version) ******** If you lately encounter an issue with mail incoming with vesta cp after an auto update took place, your /var/log/exim/main.log shows something similar below- 2021-12-19 03:39:42 1mxheU-000374-0o == mail@domain.com R=localuser T=local_delivery defer (-1): Malformed value “0MM” (expansion of “${extract{6}{:}{${lookup{$l$…. Step-1 Finding vesta… Read More
How to clear the yum cache October 20, 2013 When a package is downloaded, installed and is removed there is a chance that the package may still be saved/stored in the yum’s cache. So to clean all the cached packages from the enabled repository cache directory, login as root and execute the following: yum clean packages To purge the… Read More
The lousy Brainer Drainer November 22, 2023February 26, 2024 Hi, I am Hasan T. Emdad Rumi, an IT Project Manager & Consultant, Virtualization & Cloud Savvyfrom Dhaka, Bangladesh. I have prior experience in managing numerous local and international projects in the area of Telco VAS & NMC, National Data Center & PKI Naitonal Root and CA Infrastructure. Also engaged… Read More