Manjaro Difference between revisions of "Virt-manager"

Difference between revisions of "Virt-manager"

From Manjaro
m (added languages and translate tags)
m (Using the verb rather than the noun)
 
(20 intermediate revisions by 7 users not shown)
Line 2: Line 2:
__TOC__
__TOC__
<translate>
<translate>
= Overview =
= Overview = <!--T:1-->


<!--T:2-->
[[file:topbar_logo.png|left]]
[[file:topbar_logo.png|left]]
<br clear="all" />
<br clear="all" />
{{tip|Have you heard about Virtualbox to virtualize operating systems like Linux and Windows or Mac? It 'a good software, but not the only one! Don't forget VMware, Gnome Boxes and ...virt-manager. }}
{{BoxSuccess|tip|Have you heard about Virtualbox to virtualize operating systems like Linux and Windows or Mac? It 'a good software, but not the only one! Don't forget VMware, Gnome Boxes and ...virt-manager. }}




<!--T:3-->
----
----


'''[https://virt-manager.org/ Virt-manager]''' uses '''[http://libvirt.org/ libvirt]''' and it's a manager of many hypervisors, including the one that we want to use here: QEMU/KVM.  
<!--T:4-->
'''[https://virt-manager.org/ Virt-manager]''' uses '''[http://libvirt.org/ libvirt]''' and it's a manager of many '''[https://libvirt.org/drivers.html hypervisors]''', including the one that we want to use here: QEMU/KVM.  


<!--T:5-->
----
----


 
<!--T:6-->
{{note|Now from 1.2.1 release switch to spice-gtk3 '''so you need to have: Cinnamon/Gnome (Mate-gtk3/Xfce-gtk3 > not yet)'''}}
 
<br clear="all" />
<br clear="all" />


<!--T:7-->
'''Why do I need to virtualize?'''
'''Why do I need to virtualize?'''


<!--T:8-->
* To learn about a new O.S.
* To learn about a new O.S.


<!--T:9-->
* To configure a hardware that has a setup only for that operating system
* To configure a hardware that has a setup only for that operating system


<!--T:10-->
* To use a software that only works on another
* To use a software that only works on another


= I want to know more =
= I want to know more = <!--T:11-->


<!--T:12-->
[[file:Hypervisor_1.png|left]]
[[file:Hypervisor_1.png|left]]
<br clear="all" />
<br clear="all" />
Line 39: Line 46:
<br clear="all" />
<br clear="all" />


= What we absolutely must know =
= What we absolutely must know = <!--T:13-->
<br clear="all" />
<br clear="all" />
1. What is my CPU. Identify it and make sure it's at least a quad core. '''TAKE A LOOK AT''' '''[http://www.cpu-world.com/CPUs/CPU.html CPU-World]'''
1. What is my CPU. Identify it and make sure it's at least a quad core. '''TAKE A LOOK AT''' '''[http://www.cpu-world.com/CPUs/CPU.html CPU-World]'''
<br clear="all" />
<br clear="all" />
2. Check if the 'virtualization parameters' are enabled on BIOS
2. Check if the 'virtualization parameters' are enabled on BIOS using
<br clear="all" />
{{UserCmd|command=LC_ALL=C lscpu | grep Virtualization}}
3. How much memory I have. Check the RAM and verify that is at least 4GB.
3. How much memory I have. Check the RAM and verify that is at least 4GB.
<br clear="all" />
<br clear="all" />
4. The amount of free space on my HDD.Launch gparted and make sure you have a partition with at least 20GB free. While you're there add a label to the partitions to better recognize them even by name.
4. The amount of free space on my hard drive. The virtual machine can use a disk image file so extra partitions are not necessary.
<br clear="all" />
{{note|You can also use raw partition specific for virtual machines. See [https://wiki.archlinux.org/title/Partitioning partitioning] for more information}}
5. The minimum hardware requirements of the operating system you want to install as a virtual machine.
5. The minimum hardware requirements of the operating system you want to install as a virtual machine.
<br clear="all" />
<br clear="all" />


= Install virt-manager, qemu and all dependencies= <!--T:16-->
<br clear="all" />
From terminal:
From terminal:
sudo pacman -S inxi dmidecode gparted && sudo inxi -Fxm
{{UserCmd|command=sudo pacman -S --needed virt-manager qemu-desktop libvirt edk2-ovmf dnsmasq iptables-nft}}
For TPM support:
{{UserCmd|command=sudo pacman -S --asdeps swtpm}}
Enable and start service
{{UserCmd|command=sudo systemctl enable libvirtd.service}}
Add user to ''libvirt,'' ''libvirt-qemu'' and ''kvm'' groups to use the '''system'''-level virtual machines (qemu:///system).
{{UserCmd|command=sudo usermod -a -G libvirt,libvirt-qemu,kvm $USER}}
Note that you will need to restart userspace for the groups to become active.  To restart userspace
{{UserCmd|command=systemctl soft-reboot}}
{{note|
# You don't need this step to run system-level virtual machines. However, virt-manager will prompt for sudoer's password when launch if the user is not in the ''libvirt'' group 
# You can also create '''user'''-level virtual machines (qemu:///session) and use without sudoer's privelige. However, some features such as [https://libvirt.org/kbase/virtiofs.html VirtioFS file sharing] may be unavailable in qemu:///session}}


[[File:Inxi_1.png|thumb|left|375px]] [[File:Gparted_1.png|thumb|center|375px]]
= Using Virt-Manager for guest creation= <!--T:17-->
<br clear="all" />
 
<!--T:25-->
0. Prepare installation image. If you're going to install Windows, prepare the [https://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers Virtio driver] image too.
{{tip|You can also find the [https://aur.archlinux.org/packages/virtio-win virtio-win] package in AUR. The image is located in '''/var/lib/libvirt/images''', which is the default [https://libvirt.org/storage.html#StorageBackendDir directory pool] of qemu:///system}}
 
<!--T:26-->
1. Launch menu Virtual Machine Manager. It should already have a [https://libvirt.org/drvlxc.html LXC] connection. You can disconnect and remove it if you don't use LXC.
 
<!--T:27-->
2. Go to File, choose Add Connection and choose hypervisor QEMU/KVM, or QEMU/KVM user session if you don't want '''system'''-level virtual machines. Click on connect.
 
<!--T:28-->
3. You need directory pools to store the disk images of virtual machines or the ISO file of CD/DVD. Double click qemu/kvm, go on storage and add by clicking + the path to the folder where you have the iso and the folder where create the virtual machine.


= Install virt-manager, qemu and all dependencies=
<!--T:29-->
<br clear="all" />
{{BoxInfo|tip|Advice: use a different partition than the root. In case you need to reinstall your operating system you don't lose the VM that already ready-to-start.}}
From terminal:
4. Click on create a new virtual machine: select '''Local install media (ISO image or CDROM)''', and select the installation ISO image and OS type (if not detected).
sudo pacman -S virt-manager qemu vde2 ebtables dnsmasq bridge-utils openbsd-netcat
Enable and start service
sudo systemctl enable libvirtd.service
sudo systemctl start libvirtd.service
<br clear="all" />


= Using Virt-Manager=
<!--T:30-->
<br clear="all" />
1. Launch menu Virtual Machine Manager,  check that it is connected.
<br clear="all" />
2. Go to File, choose Add Connection and choose hypervisor QEMU/KVM user session. Click on connect.From the screen select the first qemu / kvm, Right click, disconnect and delete it.
<br clear="all" />
3. You need the HDD space in which to create the virtual machine and copy the ISO file of the operating system (but you can also use a burned cd/dvd ). Double click qemu/kvm, go on storage and add by clicking + the path to the folder where you have the iso and the folder where create the virtual machine.
<br clear="all" />
{{tip|My advice: use a different partition than the root. If you can, make a new one with gparted or recover new space with a resize. In case you need to reinstall your operating system you don't lose the VM that already ready-to-start.}}
4. Click on create a new virtual machine: select cdrom or iso (first path maked to put the iso file)
<br clear="all" />
5. How many CPU assign and how much memory? (check the recommended requirements of O.S. that you are installing)
5. How many CPU assign and how much memory? (check the recommended requirements of O.S. that you are installing)
<!--T:31-->
6. Create the file system of the virtual machine by selecting '''Select or create custom storage''' and click '''Manage...'''. Under your desired directory pool, create the volume of the virtual machine (default in qcow2 format).  How many GB? Check the recommended requirements O.S. you install.
<!--T:32-->
7.Assign a name to the machine and flag '''customize configuration before install'''. You have access to the screen with all the hardware that will be virtualized, do a check if there is all that is needed to initialize and launch the installer.
<!--T:33-->
8. In ''Overview'', change the firmware to UEFI for future-proof capacity.
<!--T:34-->
9. Change the type of SATA Disk 1 (the disk image of the creating virtual machine) to ''virtio'' for better performance. Change discard mode to ''unmap'', and then apply the change. You should notice the device name would change from SATA Disk 1 to VirtIO Disk 1.
{{BoxWarning|Warning|If you're installing Windows, make sure to create a new SATA CDROM device and select the '''virtio-win''' image as the media, so that the Windows Installer can load the driver to recognize the disk. The virtio storage driver should be located at somewhere like ''E:\viostor\w10\amd64''}}
10. Set the NIC type to virtio too for better network performance.
{{BoxInfo|Note|If you're installing Windows, once the system if ready, make sure to install all the virtio drivers so that your virtIO network can work normally}}
11. Add TPM chip, select '''TIS''' model through '''Emulated device''' backend.
<!--T:35-->
12. Add a watchdog to reboot the guest when it hangs. Leave the settings as default.
<!--T:36-->
13. And a hardware RNG, to get entropy from the host.
<!--T:37-->
14. Click on the top to start installation.
<!--T:38-->
{{BoxWarning|Warning|'''All these steps are visible on youtube.''' '''[https://youtu.be/DiUG_hlLk3c >>> PLAY THIS] [[File:YouTube_1.png|thumb|center|300px]]'''}}
==Install guest additions== <!--T:21-->
Once the VM is started and running you have to install the [https://www.spice-space.org/download.html spice guest tools].
<!--T:39-->
For Windows is a single package: spice-guest-tools-xxxx.exe
<!--T:40-->
For linux are: spice-vdagent and xf86-video-qxl. If you visrtualize a linux distro you can install them with their package manager
<!--T:41-->
Visit: '''[http://www.spice-space.org/download.html Spice download]'''
==Tune the display settings== <!--T:22-->
The default model of display card is QXL. If your virtual machine is Linux system, you can change it to virtio and enable 3D acceleration for better graphic performance.
<br clear="all" />
<br clear="all" />
6. Create the file system of the virtual machine by selecting managed or other storage and create the volume of the virtual machine. How many GB? Check the recommended requirements O.S. you install.
Windows virtual machine, however doesn't support virtio display yet. Nevertheless, we can increase its VGA memory from the default 16 MB to 64 MB to allow higher display resolution and slightly better 2D graphical performance.
<br clear="all" />
<br clear="all" />
7.Assign a name to the machine and flag customize before installing. You have access to the screen with all the hardware that will be virtualized, do a check if there is all that is needed to initialize and launch the installer.
To do so, we need to edit the XML file of the virtual machine.
# In virt-manager, go to edit > preference, and check '''Enable XML edit'''.
# In virtual machine details, go to display card. Under the XML tab, change the value of '''vgamem''' to 65536, then apply the change.
<br clear="all" />
<br clear="all" />
8. Click on the top to start.
 
==File sharing between host and guest== <!--T:23-->
For Linux guests, Virtio-FS and 9p are available for file sharing. See [https://wiki.archlinux.org/title/Libvirt#Sharing_data_between_host_and_guest ArchWiki] for more information.
<br clear="all" />
<br clear="all" />
{{warning|'''All these steps are visible on youtube.''' '''[https://youtu.be/DiUG_hlLk3c >>> PLAY THIS] [[File:YouTube_1.png|thumb|center|300px]]'''}}
For Windows guest, the easiest way to share file between host and guest is through [https://wiki.manjaro.org/index.php/Using_Samba_in_your_File_Manager SAMBA].
==Install guest additions==
# Create a SAMBA usershare
Once the VM is started and running you have to install the guest spice tools.
# In Windows guest, enter '''\\192.168.122.1''' in the file explorer, and you should be able to see the usershare on your host.
# Map that SAMBA usershare to a new drive, and connect to it with the appropriate credential. That's it.
Check [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/sharing-files-between-the-host-and-its-virtual-machines_configuring-and-managing-virtualization#sharing-files-between-the-host-and-windows-virtual-machines_sharing-files-between-the-host-and-its-virtual-machines this article] for more information.
<br clear="all" />
<br clear="all" />
For Windows is a single package: spice-guest-tools-xxxx.exe
 
==Optimize vCPU== <!--T:24-->
Check [https://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/ch25s06.html this article] to customize vCPU topology for better performance.
<br clear="all" />
<br clear="all" />
For linux are: spice-vdagent and xf86-video-qxl. If you visrtualize a linux distro you can install them with their package manager
For example, my CPU has 1 socket, 8 cores, and 16 threads in total. The automatic topology assigns 4 sockets, 1 core, and 1 thread to my guest. After changing it to 1 socket, 4 cores, and 1 thread, the performance increases significantly.
<br clear="all" />
<br clear="all" />
Visit: '''[http://www.spice-space.org/download.html Spice download]'''


= References =
=Lab: Windows 11= <!--T:42-->
Windows Setup provides for setting up virtual Windows system for lab purpose. It can be for testing software or for pentesting.
 
<!--T:43-->
For a continued use of Windows you will need a valid license key to run a virtualized Windows.
 
==Prepare== <!--T:44-->
 
<!--T:45-->
* Create a new virtual machine
* Select a Windows 11 ISO file
* Accept the defaults clicking Next until you reach the final screen
* Tick the box Customize configuration before install and click Finish
* In the Overview pane - set vm firmware to BIOS and click Apply
* Click the button Begin Installation
 
==Install== <!--T:46-->
 
<!--T:47-->
Before starting the installer press ShiftF10 so launch the Windows Cmd utility and launch regedit.
 
<!--T:48-->
* Expand HKEY_LOCAL_MACHINE\SYSTEM\Setup
* Add new key named LabConfig
* Add new DWORD value with name BypassTPMCheck and change the value to 1.
* Add new DWORD value with name BypassRAMCheck and change the value to 1.
* Add new DWORD value with name BypassSecureBootCheck and change the value to 1.
 
<!--T:49-->
Close the registry editor and exit the shell, then continue the installer
 
==Final Setup== <!--T:50-->
During last stage the installer will insist in network access but you may want use a local account instead of the required Microsoft account.
 
<!--T:51-->
This can be disabled using the Cmd utility ShiftF10
 
<!--T:53-->
* enter OOBE\BYPASSNRO and press Enter
* close the Cmd utility
* back in the setup window click I don't have internet
 
= References = <!--T:18-->


<!--T:19-->
'''[https://virt-manager.org/ Virt-manager]'''
'''[https://virt-manager.org/ Virt-manager]'''
<br clear="all" />
<br clear="all" />

Latest revision as of 16:33, 1 November 2024

Other languages:
English • ‎Türkçe • ‎русский

Overview

Topbar logo.png


tip
Have you heard about Virtualbox to virtualize operating systems like Linux and Windows or Mac? It 'a good software, but not the only one! Don't forget VMware, Gnome Boxes and ...virt-manager.


Virt-manager uses libvirt and it's a manager of many hypervisors, including the one that we want to use here: QEMU/KVM.


Why do I need to virtualize?

  • To learn about a new O.S.
  • To configure a hardware that has a setup only for that operating system
  • To use a software that only works on another

I want to know more

Hypervisor 1.png


1. Virtualization
2. Hypervisor
3. Virtual machine

What we absolutely must know


1. What is my CPU. Identify it and make sure it's at least a quad core. TAKE A LOOK AT CPU-World
2. Check if the 'virtualization parameters' are enabled on BIOS using

user $ LC_ALL=C lscpu COPY TO CLIPBOARD


3. How much memory I have. Check the RAM and verify that is at least 4GB.
4. The amount of free space on my hard drive. The virtual machine can use a disk image file so extra partitions are not necessary.

Note
You can also use raw partition specific for virtual machines. See partitioning for more information

5. The minimum hardware requirements of the operating system you want to install as a virtual machine.

Install virt-manager, qemu and all dependencies


From terminal:

user $ sudo pacman -S --needed virt-manager qemu-desktop libvirt edk2-ovmf dnsmasq iptables-nft COPY TO CLIPBOARD


For TPM support:

user $ sudo pacman -S --asdeps swtpm COPY TO CLIPBOARD


Enable and start service

user $ sudo systemctl enable libvirtd.service COPY TO CLIPBOARD


Add user to libvirt, libvirt-qemu and kvm groups to use the system-level virtual machines (qemu:///system).

user $ sudo usermod -a -G libvirt,libvirt-qemu,kvm $USER COPY TO CLIPBOARD


Note that you will need to restart userspace for the groups to become active. To restart userspace

user $ systemctl soft-reboot COPY TO CLIPBOARD


Note
  1. You don't need this step to run system-level virtual machines. However, virt-manager will prompt for sudoer's password when launch if the user is not in the libvirt group
  2. You can also create user-level virtual machines (qemu:///session) and use without sudoer's privelige. However, some features such as VirtioFS file sharing may be unavailable in qemu:///session

Using Virt-Manager for guest creation

0. Prepare installation image. If you're going to install Windows, prepare the Virtio driver image too.


Tip
You can also find the virtio-win package in AUR. The image is located in /var/lib/libvirt/images, which is the default directory pool of qemu:///system

1. Launch menu Virtual Machine Manager. It should already have a LXC connection. You can disconnect and remove it if you don't use LXC.

2. Go to File, choose Add Connection and choose hypervisor QEMU/KVM, or QEMU/KVM user session if you don't want system-level virtual machines. Click on connect.

3. You need directory pools to store the disk images of virtual machines or the ISO file of CD/DVD. Double click qemu/kvm, go on storage and add by clicking + the path to the folder where you have the iso and the folder where create the virtual machine.


tip
Advice: use a different partition than the root. In case you need to reinstall your operating system you don't lose the VM that already ready-to-start.

4. Click on create a new virtual machine: select Local install media (ISO image or CDROM), and select the installation ISO image and OS type (if not detected).

5. How many CPU assign and how much memory? (check the recommended requirements of O.S. that you are installing)

6. Create the file system of the virtual machine by selecting Select or create custom storage and click Manage.... Under your desired directory pool, create the volume of the virtual machine (default in qcow2 format). How many GB? Check the recommended requirements O.S. you install.

7.Assign a name to the machine and flag customize configuration before install. You have access to the screen with all the hardware that will be virtualized, do a check if there is all that is needed to initialize and launch the installer.

8. In Overview, change the firmware to UEFI for future-proof capacity.

9. Change the type of SATA Disk 1 (the disk image of the creating virtual machine) to virtio for better performance. Change discard mode to unmap, and then apply the change. You should notice the device name would change from SATA Disk 1 to VirtIO Disk 1.

Warning
If you're installing Windows, make sure to create a new SATA CDROM device and select the virtio-win image as the media, so that the Windows Installer can load the driver to recognize the disk. The virtio storage driver should be located at somewhere like E:\viostor\w10\amd64

10. Set the NIC type to virtio too for better network performance.

Note
If you're installing Windows, once the system if ready, make sure to install all the virtio drivers so that your virtIO network can work normally

11. Add TPM chip, select TIS model through Emulated device backend.

12. Add a watchdog to reboot the guest when it hangs. Leave the settings as default.

13. And a hardware RNG, to get entropy from the host.

14. Click on the top to start installation.


Warning
All these steps are visible on youtube. >>> PLAY THIS
YouTube 1.png

Install guest additions

Once the VM is started and running you have to install the spice guest tools.

For Windows is a single package: spice-guest-tools-xxxx.exe

For linux are: spice-vdagent and xf86-video-qxl. If you visrtualize a linux distro you can install them with their package manager

Visit: Spice download

Tune the display settings

The default model of display card is QXL. If your virtual machine is Linux system, you can change it to virtio and enable 3D acceleration for better graphic performance.
Windows virtual machine, however doesn't support virtio display yet. Nevertheless, we can increase its VGA memory from the default 16 MB to 64 MB to allow higher display resolution and slightly better 2D graphical performance.
To do so, we need to edit the XML file of the virtual machine.

  1. In virt-manager, go to edit > preference, and check Enable XML edit.
  2. In virtual machine details, go to display card. Under the XML tab, change the value of vgamem to 65536, then apply the change.


File sharing between host and guest

For Linux guests, Virtio-FS and 9p are available for file sharing. See ArchWiki for more information.
For Windows guest, the easiest way to share file between host and guest is through SAMBA.

  1. Create a SAMBA usershare
  2. In Windows guest, enter \\192.168.122.1 in the file explorer, and you should be able to see the usershare on your host.
  3. Map that SAMBA usershare to a new drive, and connect to it with the appropriate credential. That's it.

Check this article for more information.

Optimize vCPU

Check this article to customize vCPU topology for better performance.
For example, my CPU has 1 socket, 8 cores, and 16 threads in total. The automatic topology assigns 4 sockets, 1 core, and 1 thread to my guest. After changing it to 1 socket, 4 cores, and 1 thread, the performance increases significantly.

Lab: Windows 11

Windows Setup provides for setting up virtual Windows system for lab purpose. It can be for testing software or for pentesting.

For a continued use of Windows you will need a valid license key to run a virtualized Windows.

Prepare

  • Create a new virtual machine
  • Select a Windows 11 ISO file
  • Accept the defaults clicking Next until you reach the final screen
  • Tick the box Customize configuration before install and click Finish
  • In the Overview pane - set vm firmware to BIOS and click Apply
  • Click the button Begin Installation

Install

Before starting the installer press ShiftF10 so launch the Windows Cmd utility and launch regedit.

  • Expand HKEY_LOCAL_MACHINE\SYSTEM\Setup
  • Add new key named LabConfig
  • Add new DWORD value with name BypassTPMCheck and change the value to 1.
  • Add new DWORD value with name BypassRAMCheck and change the value to 1.
  • Add new DWORD value with name BypassSecureBootCheck and change the value to 1.

Close the registry editor and exit the shell, then continue the installer

Final Setup

During last stage the installer will insist in network access but you may want use a local account instead of the required Microsoft account.

This can be disabled using the Cmd utility ShiftF10

  • enter OOBE\BYPASSNRO and press Enter
  • close the Cmd utility
  • back in the setup window click I don't have internet

References

Virt-manager
Libvirt
Qemu
x86 virtualization
Intel-vt
Amd-v

Retrieved from "https://wiki.manjaro.org/index.php?title=Virt-manager&oldid=53651"
Cookies help us deliver our services. By using our services, you agree to our use of cookies.