Virtualization (Part 2)

LINUXLPIC-1

On my host machine, I'm using KVM for AMD:

$ lsmod | grep -i kvm

kvm_amd 200704 0

kvm 1343488 1 kvm_amd

irqbypass 12288 1 kvm

ccp 159744 2 i2c_designware_platform,kvm_amd

Check the CPU extensions on your host system:

$ grep ^flags /proc/cpuinfo | grep vmx

If you get a response, then you are most likely running on a host system that will support virtualization and has an Intel chip.

Perform another check of the CPU extensions on your system:

$ grep ^flags /proc/cpuinfo | grep svm

If you get a response, then you are most likely running on a host system that will support virtualization and has an AMD chip.

Perform one more check of the CPU extensions:

$ grep ^flags /proc/cpuinfo | grep -i hypervisor

If you get a response, then most likely you are running your Linux system as a guest VM.

You may find the following two types of files for your VM: Open Virtualization Format (OVF) file or Open Virtualization Application (OVA) file.

You can create a clone of the VM* or a template, however, the template is not bootable.

Cloud-init

It is the industry-standard open-source tool for initializing and customizing Linux/Unix virtual machines (VMs) in cloud computing. You can use it to automatically generate all the items after cloning a VM. When you launch a VM, Cloud-init looks for a special file called user-data (usually a YAML file). Every clone gets a unique UUID, unique SSH keys, and a unique hostname automatically.

Notes:

* For a checklist of items to consider when cloning a VM, visit this page.

For more information on Virtualization, check Part 1.

Contact

Email

hello@unixtips.eu