From c371adeaf85d31dc0f6d3701780ca611c7fc2c16 Mon Sep 17 00:00:00 2001 From: Dayle Parker Date: Thu, 14 Dec 2017 11:15:54 +0530 Subject: [PATCH] Add module 2- 2. Enabling hardware virtualization support --- ...c_enabling_hardware_virtualization_support | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 en-US/modules/proc_enabling_hardware_virtualization_support diff --git a/en-US/modules/proc_enabling_hardware_virtualization_support b/en-US/modules/proc_enabling_hardware_virtualization_support new file mode 100644 index 0000000..32f0bcf --- /dev/null +++ b/en-US/modules/proc_enabling_hardware_virtualization_support @@ -0,0 +1,32 @@ +[[installing-and-configuring-fedora-for-virtualized-guests]] +== Installing and configuring Fedora for virtualized guests + +This section covers setting up `libvirt` on your system. After setting up `libvirt`, you can create +virtualized guest operating systems, also known as virtual machines. + + +[[system-requirements]] +=== System requirements + +To run virtualization on Fedora, you need: + +* At least 600MB of hard disk storage per guest. A minimal command-line +Fedora system requires 600MB of storage. Standard Fedora desktop guests +require at least 3GB of space. +* At least 256MB of RAM per guest, plus 256MB for the base operating system. At least +756MB is recommended for each guest of a modern operating system. A good way to estimate this is to think about how much memory is required for the +operating system normally, and allocate that amount to the virtualized +guest. + +KVM requires a CPU with virtualization extensions, found on most +consumer CPUs. These extensions are called Intel VT or AMD-V. +To check whether you have CPU support, run the following +command: + +---- +$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo +---- + +If this command results in nothing printed, your system does not support the relevant virtualization +extensions. You can still use QEMU/KVM, but the emulator will fall +back to software virtualization, which is much slower.