DEV Community: Christian Bueno

Install windows 11 virtual machine on KVM, libvirt, qemu, virt-manager in Linux, fedora 36/37, RPM based distribution

Christian Bueno — Fri, 25 Nov 2022 22:10:31 +0000

The following tutorial will tech you how to create a virtual machine on Linux, first we are going to install the virtual machine tools.

Install and configure the virtual machine tools

Install the virtual machine tools grouped in @virtualization, some packages are: virt-manager, libvirt, qemu-kvm, etc. Source, full virtualization on fedora workstation linux.

sudo dnf install @virtualization

Edit the libvirtd configuration to enable a regular user the system administration privileges.

sudo vim /etc/libvirt/libvirtd.conf

Set the domain socket group ownership to libvirt.

unix_sock_group = "libvirt"

Adjust the UNIX socket permissions for the R/W socket.

unix_sock_rw_perms = "0770"

Start and enable the libvirtd service.

sudo systemctl start libvirtd
sudo systemctl enable libvirtd

Add your user to the libvirt group.

sudo usermod -aG libvirt $(whoami)

Install the secure boot tool package

It is needed when you are configuring the virtual machine, windows 11 need it. To install run the following command.

sudo dnf install edk2-ovmf

Source, secure boot

Install TPM

We need to install the Software Trusted Platform Module Emulator it will be used when being customizing the virtual machine configuration, close virt-manager and got to the link below, download and install swtpm-tools-0.7.3-1.20220427gitf2268ee.fc36.x86_64.rpm, select according your distribution number, will select that for fedora 36 and today its the last version.

swtpm-tools rpm fedora centos redhat

Go to the directory where you downloaded the package and install it with dnf package manager.

cd Downloads
sudo dnf install ./swtpm-tools-0.7.3-1.20220427gitf2268ee.fc36.x86_64.rpm

Create a Pool to store the virtual machines

Before create a virtual machine first we will create a pool. A pool is a directory and you can use a partition for example. You can create the virtual machine in the default directory, but if you are thinking format your root directory in the future and want to preserve the virtual machine , save it in a new pool is a good option.

Source, new pool using a partition.

We will use a LVM partition forvm-vmtest and You do not need to mount the partition.

  ~                                                                                                                                                                       
❯ lsblk
NAME             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                8:0    0 447.1G  0 disk 
└─sda1             8:1    0   100G  0 part 
  └─forvm-vmtest 253:0    0   100G  0 lvm  
sdb                8:16   0   1.8T  0 disk 
├─sdb1             8:17   0   839G  0 part /run/media/chris/New Volume
├─sdb2             8:18   0  27.9G  0 part 
└─sdb3             8:19   0  93.2G  0 part 
  └─vg2-vms      253:1    0  93.2G  0 lvm  
sdc                8:32   0 223.6G  0 disk 
├─sdc1             8:33   0   100M  0 part /boot/efi
├─sdc2             8:34   0    16M  0 part 
├─sdc3             8:35   0   100G  0 part 
├─sdc4             8:36   0   123G  0 part /
└─sdc5             8:37   0   509M  0 part 
sdd                8:48   1     0B  0 disk 
sr0               11:0    1  1024M  0 rom  
zram0            252:0    0     8G  0 disk [SWAP]

Select the QEMU/KVM drop-dawn tab then in the menu select Edit>Connection Details.

Click in the Storage tab, click in bottom left corner the Add Pool plus symbol button.

Type and select the following data.

In Name type any name you like, in my case vmtest.

In the type select fs:Pre-Formatted Block Device.

In target path, you can create a directory in your home or any place of your directory system it will be the mount point, if it doesn’t exist yet it will be created, in my case it will be mounted in my root "/" directory with the following name. /vmtest.

in Format auto.

In the source path, select the device partition, in my case can use /dev/mapper/forvm-vmtest or /dev/forvm/vmtest.

Click in Finish.

You can enable Autostart On Boot option of the new pool vmtest created if you like.

If the State of the pool is Inactive, click in the bottom left side the play button to start the pool. Click in Apply.

Create the windows 11 virtual machine

Click in the create a new virtual machine button.

Select Local install media, click in Forward.

Select the ISO image file, click in Browse, Click in Browse Local, select your windows 11 image iso file, click Open.

Enable automatically detect from the installation media. So far windows 11 is not an option there, but windows 10 option works fine for now. Then click in Forward.

Select the memory and cpu, its depent of your host machine capacity. For memory you can use 8192MiB which is equivalent to 8GiB, for cpu 2. Click Forward.

Enable storage for the virtual machine, select Select or Create custom storage, click in manage.

Select the new pool in my case vmtest, click in the plus symbol to Create a new volume . Its important to use as capacity a minimum value of 65GiB.

As name. you can use win11, in format qcow2, as capacity 65GiB.
Click in Finish.

Select the new created volume win11.qcow2, click in Choose Volume.

Then click Forward.

Fix the name to win11 if you like. Enable customize configuration before install, click Finish.

In the new window select in firmware option:

UEFI x86_64:/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd

Click the Apply button to save the current change.

In the left side bar, click in Boot options. In Boot device order enable SATA CDROM 1 and set that as the highest boot priority using the up arrow next to it.

Click Apply.

In the left side bar in the bottom click in Add Hardware, in the new window add a virtual TPM module, click in TPM, in Type select Emulated, click in Advanced options drop-dawn, in Model select CRB, in Version select 2.0. Click Finish.

Click the Apply button if you haven’t saved the changes yet.
Then in the top left corner click in Begin Installation button.

Installing Windows 11, soon the tutorial

Go to the web

Install Guest tools in the virtual machine

Install spice-guest-tools

After install the windows 11 virtual machine, you can install spice-guest-tools to enable copy and paste, drag and drop files from host to guest, and fix screen resolution.

Power on the virtual machine and from inside the windows 11 virtual machine, go to here and download spice-guest-tools and install inside the virtual machine.

Bonus: Enable Auto resize VM with window if it isn’t enable

If the Auto resize VM with window is not enable, you can install the latest virtio-win-guest-tools. Go to this direct link and download it, run it and install inside the virtual machine.

Source getlabsdone website, install windows 11 vm on KVM

How to create a WordPress containerization environment with podman(a docker alternative) in fedora 36/37 Workstation GNU/Linux

Christian Bueno — Mon, 24 Oct 2022 09:08:42 +0000

Hello to everyone, today we are going to learn how to create a WordPress containerization environment with podman a docker alternative.
We need podman, the WordPress image, and a database image MySQL or MariaDB
First we are going to download the images, using the following command.

podman pull WordPress:6.0.3-php8.0-apache
podman pull mariadb:10.7.6-focal

Now we are going to create a Container file in order to build a customized WordPress image.

But , What is the problem if we use the normal WordPress image?

Well, we are not being able to install themes, because WordPress won’t be able to connect to internet. It’s relate to different port in the mapped port.

We will create a pod and inside it will create the wordpress and database containers and we have to export or map the container port with a host port.
For example we can use in the port mapping option 8080:80 when create the pod.

--publish host-port:container-port
--publish 8080:80

podman pod create --name ${pod_name} --infra --publish 8080:80 --publish 3306:3306 --network bridge

That will raise the following errors.

The REST API encountered an error
Error: cURL error 28: Failed to connect to localhost port >8080: Connection timed out (http_request_failed)
Your site could not complete a loopback request
Error: cURL error 28: Failed to connect to localhost port >8080: Connection time out (http_request_failed)

To fix that we are going to add the port 8080 for example in the Apache server config of the wordpress image, you can use any port you like. This way when we create the pod in the bellow script we can use in the port mapping 8080 as the port of the wordpress container.

#Containerfile

ARG wordpress_image=wordpress:6.0.3-php8.0-apache
FROM $wordpress_image
ARG port=8080
LABEL maintainer="Christian Bueno <chmabuen@espol.edu.ec>" 
#add port
RUN cd /etc/apache2/; \
sed -i "/Listen 80/aListen $port" ports.conf; \
cd /etc/apache2/sites-available/; \
sed -i "s/:80/*:*/" 000-default.conf
EXPOSE $port
CMD ["apache2-foreground"]
# podman build --build-arg port=<port> --build-arg wordpress_image=<wordpress_image> -t <wordpress_name_and_tag> -f Containerfile
# podman build --build-arg port=8082 --build-arg wordpress_image=wordpress:6.0.2-php7.4-apache -t christianbueno1/wordpress:602-8082 -f Containerfile
# podman build -t christianbueno1/wordpress:602-8080 -f Containerfile
# podman build -t <new_image_name:version> -f Containerfile

Now to buil the new worpress image, run the following command, you can use for example the following values.

In port 8080
In the wordpress_image wordpress:6.0.3-php8.0-apache
In the tag name use your DockerHub user and any name you like e.g.dockeHubUser/image-name:version-number this way you will can upload the image to DockerHub in the future.

podman build –build-arg port=8080 –build-arg wordpress_image=wordpress:6.0.3-php8.0-apache -t christianbueno1/wordpress:603-8080

After that, then we are going to create a pod and inside that we are going to create the wordpress and database container.

We will create 2 directories var-www-html and var-lib-mysql to store all the work and avoid lost it.

mkdir var-www-html var-lib-mysql

Because we are going to mount a directory(volume) to the containers we need to map the UID:GID of your user with the UID:GID of the container. This way the container will can modify those files and directories.

The directory /var/www/html have a UID:GID of 33(www-data) , will use the tool podman unshare. The directory /var/lib/mysql have an UID:GID of 999(mysql).

podman unshare chown 33:33 -R var-www-html
podman unshare chown 999:999 -R var-lib-mysql

But an important thing is can be able to edit files from the host, in this case files in the directory var-www-html, for that reason, we will use Permissions to add write rights to Others. This way our users can be able to edit those files. Obviously it will be done after run the wordpress container.

An important environment variable is PODMAN_USERNS it is used to set the user namespace mode for all the containers in a pod. You can set this variable to ”” to make sure map your user to the root user in the container. By the way it is the default value.

--userns=mode

export PODMAN_USERNS=""

Now is the time to run the shell script. It will create a pod and inside it create the mariadb container and the wordpress container. In the variable section in the script you can edit the values of the user, password, database name, etc. The script need 2 arguments wordpress_image and pod_name if you don’t pass it the default values will be taken.

#!/bin/bash
# create_blog.sh

set -e   #exit on most errors

##variables
wordpress_image=${1:-christianbueno1/wordpress:603-php80-8080}
database_image=mariadb:10.7.6-focal
pod_name=${2:-blog}
user=chris
password=maGazine1!ec
database_name=company
#use your directories name
database_volume=var-lib-mysql
wordpress_volume=var-www-html
#
database_container_name=mariadb-${pod_name}
wordpress_container_name=wordpress-${pod_name}
##

echo "Creating the pod"
podman pod create --name ${pod_name} --infra --publish 8080:8080 --publish 3306:3306 --network bridge

echo "Creating the mariadb container"
podman run --pod ${pod_name} --name ${database_container_name} \
-e MARIADB_USER=${user} \
-e MARIADB_PASSWORD=${password} \
-e MARIADB_DATABASE=${database_name} \
-e MARIADB_ROOT_PASSWORD=${password} \
--volume ./${database_volume}:/var/lib/mysql:Z \
-d ${database_image}

echo "Creating the wordpress container"
podman run --pod ${pod_name} --name ${wordpress_container_name} \
-e WORDPRESS_DB_HOST=${database_container_name}:3306 \
-e WORDPRESS_DB_USER=${user} \
-e WORDPRESS_DB_PASSWORD=${password} \
-e WORDPRESS_DB_NAME=${database_name} \
--volume ./${wordpress_volume}:/var/www/html:Z \
-d ${wordpress_image}

#export PODMAN_USERNS=keep-id
#
#run the script
#
#./create_blog.sh <wordpress_image> <pod_name>
#./create_blog.sh christianbueno1/wordpress:602-8080 podman-blog
#use the default wordpress_image=christianbueno1/wordpress:603-php80-8080 in the first argument.
#./create_blog.sh "" podman-blog
#use the default wordpress_image and pod_name arguments
#./create_blog.sh

Run the scripts.

./create_blog.sh <new_wordpress_image> <pod_name>

In my case

./create_blog.sh christianbueno1/wordpress:603-php80-apache podman-blog

Go to the browser localhost:<port> and remember to use your configured port, in my case 8080, https://localhost:8080.

Last but not least add write rights to others in var-www-html from inside the wordpress container so you can edit files from the host using any text editor for example vscode.

Go into the wordpress container.

podman exec -it wordpress-<pod_name> /bin/bash

In my case

podman exec -it wordpress-podman-blog /bin/bash

You will be as root user. Add write rights to Others.

cd /var/www
chmod o+w -R html

That’s all.
If it has helped you, ask for your support and be able to continue writing tutorials, any amount will be welcome. paypal.me/podmanblog

podman rootless volume
debug-rootless-podman-mounted-volumes

Help me with Themes problems in WordPress on fedora 35 Linux

Christian Bueno — Thu, 28 Apr 2022 15:42:30 +0000

I have installed WordPress in my f35 workstation following this tutorial from fedora-magazine web
That was yesterday, now today after login to the WordPress local installation, URL: localhost/wordpress/wp-admin , there is a problem charging the themes.

I have edited this file: /etc/wordpress/wp-config.php

define('DISALLOW_FILE_MODS', false);

This fixed the problem yesterday and was able to install ASTRA theme and a template.
source: wordpress.stackexchange

But today the problem persists.

can it be permissions issue?

information

[root@fedora chris]# getsebool -a | grep -P "httpd.+--> on"
httpd_builtin_scripting --> on
httpd_can_network_connect_db --> on
httpd_can_sendmail --> on
httpd_enable_cgi --> on
[root@fedora chris]# ^C
[root@fedora chris]#

❯ ll -d /etc/wordpress /usr/share/wordpress 
drwxr-x---. 1 root apache  26 Apr 27 16:04 /etc/wordpress
drwxr-xr-x. 1 root root   480 Apr 27 01:10 /usr/share/wordpress

[root@fedora chris]# ll /usr/share/wordpress/wp-content/
total 4
-rw-r--r--. 1 root   root  28 Jan  8  2012 index.php
drwxrwsr-x. 1 apache ftp  264 Apr 27 03:18 plugins
drwxrwsr-x. 1 apache ftp  112 Apr 27 03:11 themes
drwxrwsr-x. 1 apache ftp    0 Apr 27 03:18 upgrade
drwxrwsr-x. 1 apache ftp  612 Apr 27 03:31 uploads
[root@fedora chris]#