linux_wiki:kernel-based_virtual_machine_kvm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
linux_wiki:kernel-based_virtual_machine_kvm [2015/02/25 22:47]
billdozor
linux_wiki:kernel-based_virtual_machine_kvm [2019/05/25 23:50] (current)
Line 1: Line 1:
 ====== Kernel-based Virtual Machine (KVM) ====== ====== Kernel-based Virtual Machine (KVM) ======
  
-Description: KVM is "a full virtualization solution for Linux on x86 hardware containing virtualization extensions." ([[http://www.linux-kvm.org/page/Main_Page|KVM Main Page]]) It can be run on the desktop with GUI managers or on a headless server.+**General Information**
  
-Assumptions:  +KVM is "a full virtualization solution for Linux on x86 hardware containing virtualization extensions.([[http://www.linux-kvm.org/page/Main_Page|KVM Main Page]]) It can be run on the desktop with GUI managers or on a headless server.
-  * Some Red Hat based distro is already installed. (CentOS, Scientific, RHEL, etc) +
-  * This page was written using CentOS 6.6 with GNOME desktop (headless KVM is on the to do list!)+
  
-2015-02-13: These are rough notes and in progress as I learn KVM.+**Checklist**  
 +  * Distro(s): Enterprise Linux 6 
 +  * Other: This page was written using CentOS 6.6 with GNOME desktop (headless KVM is on the to do list!) 
 +  * 2015-02-13: These are rough notes and in progress as I learn KVM.
  
-===== Installation =====+---- 
 + 
 +====== Installation ======
  
 ==== Install: Required Virtualization Packages (CLI) ==== ==== Install: Required Virtualization Packages (CLI) ====
Line 47: Line 50:
 ---- ----
  
-===== Verify Installation and Start Services =====+====== Verify Installation and Start Services ======
  
   * Ensure that the KVM kernel module is loaded   * Ensure that the KVM kernel module is loaded
Line 83: Line 86:
 ---- ----
  
-===== Setup Networking =====+====== Setup Networking ======
 By default, VMs will be on a private network with no access to the outside world unless they use a physical host network interface as a bridge. By default, VMs will be on a private network with no access to the outside world unless they use a physical host network interface as a bridge.
  
Line 165: Line 168:
 ---- ----
  
-===== SELinux =====+====== SELinux ======
 If SELinux is on and in Enforcing mode, there is additional configuration if you change the default directory for VM images. If SELinux is on and in Enforcing mode, there is additional configuration if you change the default directory for VM images.
  
Line 184: Line 187:
 </code> </code>
  
-  * Install the following package to enable use of the "semanage" utility. +  * Set the context of the new directory, referencing the default
 <code bash> <code bash>
-yum install policycoreutils-python+chcon -R --reference /var/lib/libvirt/images /vm-images
 </code> </code>
  
-  * Set security context for the vm-images directory and everything that is created under it. +  * Verify
 <code bash> <code bash>
-semanage fcontext -a -t virt_image_t "/vm-images(/.*)?"+ls -/vm-images
 </code> </code>
  
-  * Restore the security context (I don't know why you have to do this yet...but you do) +  * Create a symlink to the new location to ensure that is survives a SELinux relabel.
 <code bash> <code bash>
-restorecon -/vm-images +rmdir /var/lib/libvirt/images 
-</code> +ln -/vm-images /var/lib/libvirt/images
- +
-  * Verify +
- +
-<code bash> +
-ls -Z /vm-images+
 </code> </code>
  
 ---- ----
  
-===== Creating VMs =====+====== Creating VMs ======
  
 VMs can be installed via a command line tool (virt-install) or a GUI (virt-manager). VMs can be installed via a command line tool (virt-install) or a GUI (virt-manager).
Line 302: Line 297:
     * Step 5 =>     * Step 5 =>
       * Ready to install: Confirm settings, set advanced options such as Host network device.       * Ready to install: Confirm settings, set advanced options such as Host network device.
 +
 +----
 +
 +====== Disabling virbr0 NAT Interface ======
 +
 +On some desktop installations, a NAT interface "virbr0" is auto created.
 +
 +To disable this interface:
 +  * View the interface<code bash>virsh net-list</code>
 +  * Turn off the interface<code bash>virsh net-destroy default</code>
 +  * Disable auto start on the interface<code bash>virsh net-autostart default –disable</code>
 +  * Verify State is "inactive" and Autostart is "no", then ensure virbr0 is not in the interface list<code bash>virsh net-list --all
 +ip addr show</code>
 +  * Restart the network service
 +    * EL6<code bash>service network restart</code>
 +    * EL7<code bash>systemctl restart network</code>
 +
 +----
 +
  • linux_wiki/kernel-based_virtual_machine_kvm.1424922471.txt.gz
  • Last modified: 2019/05/25 23:50
  • (external edit)