From 79d28a1b6738afcd44d0d7c311ba05f95ae5d646 Mon Sep 17 00:00:00 2001 From: Jarek Prokop Date: Mon, 25 Mar 2024 16:50:30 +0100 Subject: [PATCH] Revert "Fill sections to individual content files (#532)" This reverts commit 3650563830b16c21fd5c80f006bc09a1f757c7b3. --- deployment/copr/copr-cli.md | 1 - deployment/flatpak/flatpak-install.md | 1 - deployment/flatpak/flatpak-usage.md | 1 - .../maintain/rebase-helper-integration.md | 6 +- deployment/maintain/rebase-helper.md | 4 +- deployment/maintain/static-analysis.md | 1 - deployment/secondary_architectures/powerpc.md | 5 +- deployment/secondary_architectures/s390.md | 7 +- start/sw/web-app/apache.md | 9 ++- start/sw/web-app/django.md | 18 ++--- start/sw/web-app/hugo.md | 1 - start/sw/web-app/jekyll.md | 1 - start/sw/web-app/laravel5.md | 13 ++-- start/sw/web-app/nginx.md | 1 - start/sw/web-app/php-symfony.md | 2 +- start/sw/web-app/php-zend.md | 2 +- start/sw/web-app/rails.md | 1 - tech/languages/c/autotools.md | 1 - tech/languages/c/cmake.md | 3 +- tech/languages/c/cpp_installation.md | 1 - tech/languages/c/gtk.md | 11 ++- tech/languages/c/static-analysis.md | 1 - tech/languages/dotnet/dotnet-ide.md | 3 +- tech/languages/dotnet/dotnet-sig.md | 2 +- tech/languages/dotnet/dotnetcore.md | 1 - tech/languages/dotnet/mono-sig.md | 2 +- tech/languages/dotnet/mono.md | 1 - tech/languages/go/go-packages.md | 1 - tech/languages/go/go-programs.md | 3 +- tech/languages/haskell/cabal.md | 1 - tech/languages/haskell/leksah.md | 5 +- tech/languages/haskell/sig.md | 1 - .../java/java-build-tools-installation.md | 5 +- tech/languages/java/java-sig.md | 1 - tech/languages/julia/julia-installation.md | 4 +- tech/languages/nodejs/SIG.md | 1 - tech/languages/nodejs/modules.md | 7 +- tech/languages/ocaml/dune.md | 1 - tech/languages/perl/perl-modules.md | 1 - tech/languages/php/pear-installation.md | 1 - tech/languages/php/php-frameworks.md | 1 - tech/languages/php/php-sig.md | 1 - tech/languages/python/django-installation.md | 1 - tech/languages/python/fastapi-installation.md | 1 - tech/languages/python/flask-installation.md | 1 - tech/languages/python/micropython.md | 5 +- tech/languages/python/multiple-pythons.md | 11 ++- tech/languages/python/pipenv.md | 1 - tech/languages/python/pygobject.md | 1 - tech/languages/python/pypi-installation.md | 1 - tech/languages/python/python-sig.md | 1 - tech/languages/python/scipy.md | 1 - tech/languages/python/sphinx.md | 5 +- tech/languages/r/blas-lapack.md | 1 - tech/languages/r/r-ide.md | 1 - tech/languages/r/r-packages.md | 1 - tech/languages/r/r-sig.md | 1 - tech/languages/ruby/bundler-installation.md | 1 - tech/languages/ruby/gems-installation.md | 9 ++- tech/languages/ruby/ror-installation.md | 1 - tech/languages/ruby/ruby-sig.md | 1 - tech/languages/ruby/sinatra-installation.md | 1 - tech/languages/rust/format-rust-code.md | 1 - tech/languages/rust/further-reading.md | 2 +- tech/languages/rust/rust-cargo.md | 1 - tech/languages/rust/rust-sig.md | 1 - tools/docker/compose.md | 1 - tools/docker/docker-configuration.md | 1 - tools/docker/docker-images.md | 2 +- tools/docker/docker-installation.md | 1 - tools/docker/docker-interactive-management.md | 1 - tools/docker/docker-usage.md | 1 - ...ching-ovmf-uefi-from-the-correct-source.md | 21 +++--- ...ibvirt-and-virt-install-on-fedora-linux.md | 11 ++- .../installing-qemu-on-fedora-linux.md | 11 ++- ...a-virtualised-guest-port-to-a-host-port.md | 37 +++++----- ...ole-with-custom-kernel-initramfs-images.md | 37 +++++----- ...e-with-original-kernel-initramfs-images.md | 43 ++++++------ ...aying-around-with-various-vga-providers.md | 53 +++++++-------- ...up-fedora-workstation-domain-on-libvirt.md | 51 +++++++------- ...edora-workstation-vm-on-qemu-using-bios.md | 57 ++++++++-------- ...edora-workstation-vm-on-qemu-using-uefi.md | 67 +++++++++---------- ...etting-up-intrinsic-vnc-server-with-vms.md | 25 ++++--- ...ing-viewport-resolution-using-ovmf-bios.md | 35 +++++----- ...ng-memory-chunk-as-video-memory-in-qemu.md | 15 ++--- 85 files changed, 295 insertions(+), 360 deletions(-) diff --git a/deployment/copr/copr-cli.md b/deployment/copr/copr-cli.md index fe415c24..63fe3cf9 100644 --- a/deployment/copr/copr-cli.md +++ b/deployment/copr/copr-cli.md @@ -1,6 +1,5 @@ --- title: Copr command line interface -section: deployment subsection: copr --- diff --git a/deployment/flatpak/flatpak-install.md b/deployment/flatpak/flatpak-install.md index deb563f9..690e09fb 100644 --- a/deployment/flatpak/flatpak-install.md +++ b/deployment/flatpak/flatpak-install.md @@ -1,7 +1,6 @@ --- title: Installing Flatpak subsection: flatpak -section: deployment order: 2 --- diff --git a/deployment/flatpak/flatpak-usage.md b/deployment/flatpak/flatpak-usage.md index 90c6bc23..a307dd0c 100644 --- a/deployment/flatpak/flatpak-usage.md +++ b/deployment/flatpak/flatpak-usage.md @@ -1,7 +1,6 @@ --- title: Flatpak Usage subsection: flatpak -section: deployment order: 4 --- diff --git a/deployment/maintain/rebase-helper-integration.md b/deployment/maintain/rebase-helper-integration.md index 36706650..6b799538 100644 --- a/deployment/maintain/rebase-helper-integration.md +++ b/deployment/maintain/rebase-helper-integration.md @@ -1,20 +1,19 @@ --- title: Rebase helper integration subsection: maintain -section: deployment order: 3 --- # Integrating rebase-helper with an upstream monitoring service -This chapter demonstrates how to include rebase-helper in your upstream monitoring service. +This chapter demonstrates how to include rebase-helper in your upstream monitoring service. If you would like to integrate rebase-helper into your upstream monitoring services, this chapter is for you. Rebase-helper provides an API which you can use either directly from Python, or directly from the command line. ## Patch new upstream version and start scratch builds Example of patching new sources and starting scratch builds with fedpkg. This returns task_ids. The bash equivalents are included for comparison: - + ### Python API ```python3 @@ -46,3 +45,4 @@ rh.get_rebasehelper_data() # Get all information about the results ```sh rebase-helper --non-interactive --builds-nowait --buildtool fedpkg --build-tasks old_id,new_id ``` + diff --git a/deployment/maintain/rebase-helper.md b/deployment/maintain/rebase-helper.md index 1cc28f9c..dc39b604 100644 --- a/deployment/maintain/rebase-helper.md +++ b/deployment/maintain/rebase-helper.md @@ -1,7 +1,6 @@ --- title: Rebase helper subsection: maintain -section: deployment order: 2 --- @@ -42,6 +41,7 @@ $ cd $HOME/rpmbuild/REPOS/foobar $ rebase-helper 1.2.1 ``` -If you do not want to be bothered, add the ``--non-interactive`` option to rebase-helper's command line +If you do not want to be bothered, add the ``--non-interactive`` option to rebase-helper's command line After rebase-helper finishes, check the output. + diff --git a/deployment/maintain/static-analysis.md b/deployment/maintain/static-analysis.md index 0c293e89..05b6dce4 100644 --- a/deployment/maintain/static-analysis.md +++ b/deployment/maintain/static-analysis.md @@ -1,7 +1,6 @@ --- title: Static Analysis subsection: maintain -section: deployment order: 4 --- diff --git a/deployment/secondary_architectures/powerpc.md b/deployment/secondary_architectures/powerpc.md index 93077517..0e06f785 100644 --- a/deployment/secondary_architectures/powerpc.md +++ b/deployment/secondary_architectures/powerpc.md @@ -1,7 +1,7 @@ --- title: PowerPC subsection: secondary_architectures -section: deployment + order: 2 --- @@ -63,3 +63,6 @@ If you face any difficulty reach out to us for help: ## More documentation - More Fedora PowerPC specific details cane be found at [fedoraproject wiki](https://fedoraproject.org/wiki/Architectures/PowerPC) + + + diff --git a/deployment/secondary_architectures/s390.md b/deployment/secondary_architectures/s390.md index a757c483..b2e5ccfb 100644 --- a/deployment/secondary_architectures/s390.md +++ b/deployment/secondary_architectures/s390.md @@ -1,7 +1,7 @@ --- title: s390(x) subsection: secondary_architectures -section: deployment + order: 3 --- @@ -39,7 +39,7 @@ The following example will demonstrate how to build an application for s390(x) a ``` # Initiate iprutils package build for s390(x) architecture -$ s390-koji build --scratch rawhide iprutils-2.4.11.1-1.fc25.src.rpm +$ s390-koji build --scratch rawhide iprutils-2.4.11.1-1.fc25.src.rpm Created task: 2183374 Task info: http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2183374 .... @@ -63,3 +63,6 @@ If you face any difficulty reach out to us for help: ## More documentation More Fedora s390(x) specific details can be found at [Fedora Project wiki](https://fedoraproject.org/wiki/Architectures/s390x) + + + diff --git a/start/sw/web-app/apache.md b/start/sw/web-app/apache.md index 5204c6ac..a5e92a7b 100644 --- a/start/sw/web-app/apache.md +++ b/start/sw/web-app/apache.md @@ -1,6 +1,5 @@ --- title: Apache HTTP Server -section: start-sw subsection: web-app order: 2 --- @@ -28,7 +27,7 @@ To run the Apache server immediately, type: sudo systemctl start httpd.service ``` -To try if your Apache server is running, visit your localhost page at [http://localhost](http://localhost). +To try if your Apache server is running, visit your localhost page at [http://localhost](http://localhost). If everything goes as expected, you will see the Fedora Test Page: @@ -36,9 +35,9 @@ If everything goes as expected, you will see the Fedora Test Page: # How to run your own web presentation -The root directory of your web server is now situated at ```/var/www/html/```. +The root directory of your web server is now situated at ```/var/www/html/```. -**WARNING: The owner of this directory is the root user!** +**WARNING: The owner of this directory is the root user!** To disable rendering the Fedora Test Page, comment out all the lines in ```/etc/httpd/conf.d/welcome.conf```. After that, create an ```index.html``` file with your customized content in the ```/var/www/html/``` directory, for example: @@ -71,5 +70,5 @@ sudo systemctl restart httpd.service # More information -For more information about the Apache HTTP Server in Fedora you can visit [Fedora Wiki page](https://fedoraproject.org/wiki/Apache_HTTP_Server). +For more information about the Apache HTTP Server in Fedora you can visit [Fedora Wiki page](https://fedoraproject.org/wiki/Apache_HTTP_Server). For general information about the Apache HTTP Server you can visit [Apache HTTP Server documentation page](https://httpd.apache.org/docs/current/). diff --git a/start/sw/web-app/django.md b/start/sw/web-app/django.md index 0c46fba8..b6eef4fb 100644 --- a/start/sw/web-app/django.md +++ b/start/sw/web-app/django.md @@ -1,14 +1,13 @@ --- -title: Python Django +title: Python Django subsection: web-app -section: start-sw order: 3 --- # What's Django? -Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. -Django is one of the most popular Python Web Frameworks. It has very useful web page. Visit it by clicking on [this link](https://www.djangoproject.com/). +Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. +Django is one of the most popular Python Web Frameworks. It has very useful web page. Visit it by clicking on [this link](https://www.djangoproject.com/). Because you will need to work with Python packages, write this command to your command line. ``` @@ -19,7 +18,7 @@ $ sudo dnf install python3-pip ### How to install virtualenv -It's recommended to keep your project inside virtual environment. But you can skip this step if you want. +It's recommended to keep your project inside virtual environment. But you can skip this step if you want. Enter this command to your command line for installation: ``` @@ -47,7 +46,7 @@ $ cd venv $ source bin/activate ``` -When it's activated we will see indicator of same name as our virtualenv. +When it's activated we will see indicator of same name as our virtualenv. Now we will check if we really have empty environment: ``` @@ -58,7 +57,7 @@ It will return nothing. ### How to install Django -Now if you installed `virtualenv` do not leave it, we will install Django now. If you installed `virtualenv` use this command +Now if you installed `virtualenv` do not leave it, we will install Django now. If you installed `virtualenv` use this command inside your working directory with activated `virtualenv`: ``` @@ -84,7 +83,7 @@ and when it's finished use following command to start your first project called $ django-admin startproject mysite ``` -Now if you will check your directory using ls you will see new directory called mysite. We +Now if you will check your directory using ls you will see new directory called mysite. We will go inside that directory and we will run our project by following commands: ``` @@ -92,7 +91,7 @@ $ cd mysite/ $ python3 manage.py runserver ``` -You will see message with information about your development server. When you insert URL into your browser, +You will see message with information about your development server. When you insert URL into your browser, you will see welcome page (default URL for development server is http://127.0.0.1:8000/). And you successfully started your first Django project. @@ -110,3 +109,4 @@ $ mkvirtualenv env2 $ workon env1 $ workon env2 ``` + diff --git a/start/sw/web-app/hugo.md b/start/sw/web-app/hugo.md index f2d5d02d..5fb38a21 100644 --- a/start/sw/web-app/hugo.md +++ b/start/sw/web-app/hugo.md @@ -1,7 +1,6 @@ --- title: Hugo subsection: web-app -section: start-sw order: 8 --- diff --git a/start/sw/web-app/jekyll.md b/start/sw/web-app/jekyll.md index 22e8e13b..8119cf81 100644 --- a/start/sw/web-app/jekyll.md +++ b/start/sw/web-app/jekyll.md @@ -1,7 +1,6 @@ --- title: Jekyll subsection: web-app -section: start-sw order: 5 --- diff --git a/start/sw/web-app/laravel5.md b/start/sw/web-app/laravel5.md index a648bd19..bb45faa5 100644 --- a/start/sw/web-app/laravel5.md +++ b/start/sw/web-app/laravel5.md @@ -1,14 +1,13 @@ --- title: PHP Laravel 5 subsection: web-app -section: start-sw order: 4 --- ## Laravel 5 > The PHP Framework For Web Artisans -Laravel is a high-level PHP MVC framework. It is also the most used PHP framework today. For more information, [click here](https://laravel.com/). +Laravel is a high-level PHP MVC framework. It is also the most used PHP framework today. For more information, [click here](https://laravel.com/). This guide will help you setup your local development environment for Laravel, and it applies to setting up Lumen as well. @@ -34,17 +33,17 @@ $ sudo dnf install composer Your web server needs to be restarted after installing PHP package. #### Install Valet Linux -We will need to set it up for easier development. Valet is original designed for MacOS by the Laravel Team; Valet Linux is a port to that. It setups up the neccesary environments for PHP Development, including a test domain. Please do not run valet as root. -For More Information, you can check them out here: +We will need to set it up for easier development. Valet is original designed for MacOS by the Laravel Team; Valet Linux is a port to that. It setups up the neccesary environments for PHP Development, including a test domain. Please do not run valet as root. +For More Information, you can check them out here: [Valet Linux](https://cpriego.github.io/valet-linux/) and [Laravel Valet](https://laravel.com/docs/5.7/valet) You can also setup Laravel using [Vagrant](/tools/vagrant/about.html), [Docker](/tools/docker/about.html). ```bash -# Place the ~/.config/composer/vendor/bin directory in your PATH so the composer +# Place the ~/.config/composer/vendor/bin directory in your PATH so the composer # global executable can be located by your system. $ echo 'export PATH="$PATH:$HOME/.config/composer/vendor/bin"' >> ~/.bashrc -# Install valet +# Install valet $ composer global require cpriego/valet-linux # Initialize valet $ valet install @@ -66,7 +65,7 @@ $ laravel new ProjectName $ cd ProjectName $ cp .env.example .env #Editing your environment file -$ gedit .env +$ gedit .env ``` Edit the .env file with DB_* lines with the correct info diff --git a/start/sw/web-app/nginx.md b/start/sw/web-app/nginx.md index ac266627..a60cd903 100644 --- a/start/sw/web-app/nginx.md +++ b/start/sw/web-app/nginx.md @@ -1,7 +1,6 @@ --- title: NGINX HTTP Server subsection: web-app -section: start-sw order: 7 --- diff --git a/start/sw/web-app/php-symfony.md b/start/sw/web-app/php-symfony.md index 521db47c..696a46c5 100644 --- a/start/sw/web-app/php-symfony.md +++ b/start/sw/web-app/php-symfony.md @@ -1,7 +1,6 @@ --- title: PHP Symfony subsection: web-app -section: start-sw order: 8 --- @@ -12,3 +11,4 @@ To install the latest upstream version of Symfony, type: ``` $ sudo dnf install php-symfony ``` + diff --git a/start/sw/web-app/php-zend.md b/start/sw/web-app/php-zend.md index e992824d..caeef816 100644 --- a/start/sw/web-app/php-zend.md +++ b/start/sw/web-app/php-zend.md @@ -1,7 +1,6 @@ --- title: PHP Zend Framework 2 subsection: web-app -section: start-sw order: 9 --- @@ -12,3 +11,4 @@ To install the latest upstream version of Zend Framework 2, type: ``` $ sudo dnf install php-ZendFramework2 ``` + diff --git a/start/sw/web-app/rails.md b/start/sw/web-app/rails.md index aefa8e05..fb7ea551 100644 --- a/start/sw/web-app/rails.md +++ b/start/sw/web-app/rails.md @@ -1,7 +1,6 @@ --- title: Ruby on Rails subsection: web-app -section: start-sw order: 6 --- diff --git a/tech/languages/c/autotools.md b/tech/languages/c/autotools.md index 4bc20eb4..388be7b2 100644 --- a/tech/languages/c/autotools.md +++ b/tech/languages/c/autotools.md @@ -1,7 +1,6 @@ --- title: Autotools subsection: c -section: tech-languages order: 3 --- diff --git a/tech/languages/c/cmake.md b/tech/languages/c/cmake.md index fcbbeaa4..15719f5c 100644 --- a/tech/languages/c/cmake.md +++ b/tech/languages/c/cmake.md @@ -1,7 +1,6 @@ --- title: CMake subsection: c -section: tech-languages order: 4 --- @@ -40,7 +39,7 @@ The beauty of CMake is that after you create a simple CMakeLists.txt file you on This command should be used in a directory where you want to have the Makefile for your project. It will create all necessary Makefiles and configuration files needed to compile your project. -It is considered good practice to build outside of the source tree (i.e. do not execute the above command from within your source code directory). This will help to keep your source code free from any build artifacts and it also makes it easier to clean up if things go wrong. +It is considered good practice to build outside of the source tree (i.e. do not execute the above command from within your source code directory). This will help to keep your source code free from any build artifacts and it also makes it easier to clean up if things go wrong. Than after using the command `make` your project is built and ready for use. diff --git a/tech/languages/c/cpp_installation.md b/tech/languages/c/cpp_installation.md index fb07ec67..8c31e39f 100644 --- a/tech/languages/c/cpp_installation.md +++ b/tech/languages/c/cpp_installation.md @@ -1,7 +1,6 @@ --- title: C++ subsection: c -section: tech-languages order: 2 --- diff --git a/tech/languages/c/gtk.md b/tech/languages/c/gtk.md index 9961219e..cb63b739 100644 --- a/tech/languages/c/gtk.md +++ b/tech/languages/c/gtk.md @@ -1,7 +1,6 @@ --- title: Gtk+ subsection: c -section: tech-languages order: 7 --- @@ -28,20 +27,20 @@ To begin our introduction to Gtk+, we will start with the simplest program possi ```c #include -int +int main(int argc, char *argv[]) { GtkWidget *window; - + gtk_init (&argc, &argv); - + window = gtk_window_new (GTK_WINDOW_TOPLEVEL); gtk_window_set_title (GTK_WINDOW (window), "Hello World"); gtk_widget_show (window); - + gtk_main (); - + return 0; } ``` diff --git a/tech/languages/c/static-analysis.md b/tech/languages/c/static-analysis.md index dcd0ff0e..a2ad3028 100644 --- a/tech/languages/c/static-analysis.md +++ b/tech/languages/c/static-analysis.md @@ -1,7 +1,6 @@ --- title: Static Analysis subsection: c -section: tech-languages order: 6 --- diff --git a/tech/languages/dotnet/dotnet-ide.md b/tech/languages/dotnet/dotnet-ide.md index eb05cb31..456ffbcc 100644 --- a/tech/languages/dotnet/dotnet-ide.md +++ b/tech/languages/dotnet/dotnet-ide.md @@ -1,7 +1,6 @@ --- title: IDEs subsection: dotnet -section: tech-languages order: 4 --- @@ -38,7 +37,7 @@ order: 4 ```console $ sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc ``` - + Then, we need to create a repo file `/etc/yum.repos.d/vscode.repo` with the following content: ``` [code] diff --git a/tech/languages/dotnet/dotnet-sig.md b/tech/languages/dotnet/dotnet-sig.md index 0c02021b..51cf2511 100644 --- a/tech/languages/dotnet/dotnet-sig.md +++ b/tech/languages/dotnet/dotnet-sig.md @@ -1,7 +1,6 @@ --- title: DotNet SIG subsection: dotnet -section: tech-languages order: 5 --- @@ -12,3 +11,4 @@ The [DotNet SIG](https://fedoraproject.org/wiki/SIGs/DotNet) is a group of Fedor ## .NET Foundation You can contribute to the .NET Core upstream on [GitHub.com/dotnet](https://github.com/dotnet) + diff --git a/tech/languages/dotnet/dotnetcore.md b/tech/languages/dotnet/dotnetcore.md index 10d604ce..c5e8639b 100644 --- a/tech/languages/dotnet/dotnetcore.md +++ b/tech/languages/dotnet/dotnetcore.md @@ -1,7 +1,6 @@ --- title: .NET subsection: dotnet -section: tech-languages order: 2 version: 7.8.4 --- diff --git a/tech/languages/dotnet/mono-sig.md b/tech/languages/dotnet/mono-sig.md index fdeb75b5..48bb6068 100644 --- a/tech/languages/dotnet/mono-sig.md +++ b/tech/languages/dotnet/mono-sig.md @@ -1,10 +1,10 @@ --- title: Mono SIG subsection: dotnet -section: tech-languages order: 6 --- # Mono SIG The [Mono SIG](https://fedoraproject.org/wiki/SIGs/Mono) is a group of Fedora contributors that maintain Mono (and related) packages in Fedora. The goal of the Mono SIG is to provide high-quality and usable Mono software packages to Fedora users and developers and to support others in creating and maintaining Mono packages. + diff --git a/tech/languages/dotnet/mono.md b/tech/languages/dotnet/mono.md index d67bbb62..27481d67 100644 --- a/tech/languages/dotnet/mono.md +++ b/tech/languages/dotnet/mono.md @@ -1,7 +1,6 @@ --- title: Mono subsection: dotnet -section: tech-languages order: 3 --- diff --git a/tech/languages/go/go-packages.md b/tech/languages/go/go-packages.md index 7ae90e14..ccffcce5 100644 --- a/tech/languages/go/go-packages.md +++ b/tech/languages/go/go-packages.md @@ -1,7 +1,6 @@ --- title: Go packages subsection: go -section: tech-languages order: 3 --- diff --git a/tech/languages/go/go-programs.md b/tech/languages/go/go-programs.md index 404b8408..08b285a5 100644 --- a/tech/languages/go/go-programs.md +++ b/tech/languages/go/go-programs.md @@ -1,7 +1,6 @@ --- title: Writing Go programs subsection: go -section: tech-languages order: 2 --- @@ -80,4 +79,4 @@ Hello, Fedora! ## References -- [Go Documentation: Create a Go module](https://go.dev/doc/tutorial/create-module) +- [Go Documentation: Create a Go module](https://go.dev/doc/tutorial/create-module) \ No newline at end of file diff --git a/tech/languages/haskell/cabal.md b/tech/languages/haskell/cabal.md index a2f6e2c5..37dce5c4 100644 --- a/tech/languages/haskell/cabal.md +++ b/tech/languages/haskell/cabal.md @@ -1,7 +1,6 @@ --- title: Cabal subsection: haskell -section: tech-languages order: 2 --- diff --git a/tech/languages/haskell/leksah.md b/tech/languages/haskell/leksah.md index 030aaa7b..ab7e24db 100644 --- a/tech/languages/haskell/leksah.md +++ b/tech/languages/haskell/leksah.md @@ -1,13 +1,12 @@ --- title: Leksah subsection: haskell -section: tech-languages order: 4 --- # Leksah -[Leksah](http://leksah.org/) is a Haskell IDE written in Haskell using Gtk. It offers workspaces for complex project with multiple +[Leksah](http://leksah.org/) is a Haskell IDE written in Haskell using Gtk. It offers workspaces for complex project with multiple packages with automatic build of dependencies. It enables standard IDE features (debugging, auto completition etc.). To install Leksah run command: @@ -60,3 +59,5 @@ $ leksah ``` NOTE: It might happen that you need to reboot the system before using Leksah. + + diff --git a/tech/languages/haskell/sig.md b/tech/languages/haskell/sig.md index b8e2177c..1a16485d 100644 --- a/tech/languages/haskell/sig.md +++ b/tech/languages/haskell/sig.md @@ -1,7 +1,6 @@ --- title: Haskell SIG subsection: haskell -section: tech-languages order: 3 --- diff --git a/tech/languages/java/java-build-tools-installation.md b/tech/languages/java/java-build-tools-installation.md index 6c07c5e6..7906c1c0 100644 --- a/tech/languages/java/java-build-tools-installation.md +++ b/tech/languages/java/java-build-tools-installation.md @@ -1,7 +1,6 @@ --- title: Java build tools subsection: java -section: tech-languages order: 2 --- @@ -39,13 +38,13 @@ The project that is created follows the [Maven Project Structure](https://maven. The sample application created by the Maven archetype contains a single "Hello World" application (jar). -The `target` directory will be created after the first compilation: run +The `target` directory will be created after the first compilation: run ``` $ mvn compile ``` -This directory is where your compiled artifacts, or generated outputs (from builds) are stored. Its best to think of this directory as a temp space, used to store the outputs from a build. +This directory is where your compiled artifacts, or generated outputs (from builds) are stored. Its best to think of this directory as a temp space, used to store the outputs from a build. ### Creating a git repo diff --git a/tech/languages/java/java-sig.md b/tech/languages/java/java-sig.md index 17b41d31..4da780ab 100644 --- a/tech/languages/java/java-sig.md +++ b/tech/languages/java/java-sig.md @@ -1,7 +1,6 @@ --- title: Java SIG subsection: java -section: tech-languages order: 3 --- diff --git a/tech/languages/julia/julia-installation.md b/tech/languages/julia/julia-installation.md index e196fdbe..a4228241 100644 --- a/tech/languages/julia/julia-installation.md +++ b/tech/languages/julia/julia-installation.md @@ -28,7 +28,7 @@ $ julia _/ |\__'_|_|_|\__'_| | Fedora 36 build |__/ | -julia> +julia> ``` @@ -38,7 +38,7 @@ Now, you can run julia commands inside the REPL. julia> 1+1 2 -julia> +julia> ``` diff --git a/tech/languages/nodejs/SIG.md b/tech/languages/nodejs/SIG.md index 066af16b..9992a775 100644 --- a/tech/languages/nodejs/SIG.md +++ b/tech/languages/nodejs/SIG.md @@ -1,7 +1,6 @@ --- title: Node.js SIG subsection: nodejs -section: tech-languages order: 3 --- diff --git a/tech/languages/nodejs/modules.md b/tech/languages/nodejs/modules.md index 3d87502e..3a9937dd 100644 --- a/tech/languages/nodejs/modules.md +++ b/tech/languages/nodejs/modules.md @@ -1,7 +1,6 @@ --- title: Node.js modules subsection: nodejs -section: tech-languages order: 2 --- @@ -17,7 +16,7 @@ To install additional modules from Fedora repositories, use: $ sudo dnf install nodejs- ``` -or +or ``` $ sudo dnf install 'npm(module-name)' @@ -29,7 +28,7 @@ For example, to install `express`, you need to type: $ sudo dnf install nodejs-express ``` -or +or ``` $ sudo dnf install 'npm(express)' @@ -49,7 +48,7 @@ npm allows using `require()` only on locally installed modules. If you want to ` $ npm link express ``` -or to load global modules by default, you can set $NODE_PATH as follows: +or to load global modules by default, you can set $NODE_PATH as follows: ``` $ export NODE_PATH=/usr/lib/node_modules diff --git a/tech/languages/ocaml/dune.md b/tech/languages/ocaml/dune.md index 242d1319..6dbbfb7c 100644 --- a/tech/languages/ocaml/dune.md +++ b/tech/languages/ocaml/dune.md @@ -1,7 +1,6 @@ --- title: Dune subsection: ocaml -section: tech-languages order: 2 --- diff --git a/tech/languages/perl/perl-modules.md b/tech/languages/perl/perl-modules.md index 41373ee1..3d34fd39 100644 --- a/tech/languages/perl/perl-modules.md +++ b/tech/languages/perl/perl-modules.md @@ -1,7 +1,6 @@ --- title: Perl modules subsection: perl -section: tech-languages order: 2 --- diff --git a/tech/languages/php/pear-installation.md b/tech/languages/php/pear-installation.md index 1fb0f551..65314669 100644 --- a/tech/languages/php/pear-installation.md +++ b/tech/languages/php/pear-installation.md @@ -1,7 +1,6 @@ --- title: PEAR subsection: php -section: tech-languages order: 2 --- diff --git a/tech/languages/php/php-frameworks.md b/tech/languages/php/php-frameworks.md index 0019c5ec..b5323264 100644 --- a/tech/languages/php/php-frameworks.md +++ b/tech/languages/php/php-frameworks.md @@ -1,7 +1,6 @@ --- title: Frameworks subsection: php -section: tech-languages order: 3 --- diff --git a/tech/languages/php/php-sig.md b/tech/languages/php/php-sig.md index 1d673707..7f2c850d 100644 --- a/tech/languages/php/php-sig.md +++ b/tech/languages/php/php-sig.md @@ -1,7 +1,6 @@ --- title: PHP SIG subsection: php -section: tech-languages order: 4 --- diff --git a/tech/languages/python/django-installation.md b/tech/languages/python/django-installation.md index f5600e69..fafbe43e 100644 --- a/tech/languages/python/django-installation.md +++ b/tech/languages/python/django-installation.md @@ -1,7 +1,6 @@ --- title: Django subsection: python -section: tech-languages order: 4 --- diff --git a/tech/languages/python/fastapi-installation.md b/tech/languages/python/fastapi-installation.md index c1f7b105..a45bd1ae 100644 --- a/tech/languages/python/fastapi-installation.md +++ b/tech/languages/python/fastapi-installation.md @@ -1,7 +1,6 @@ --- title: FastApi subsection: python -section: tech-languages order: 5 --- diff --git a/tech/languages/python/flask-installation.md b/tech/languages/python/flask-installation.md index 7c29e512..84b25223 100644 --- a/tech/languages/python/flask-installation.md +++ b/tech/languages/python/flask-installation.md @@ -1,7 +1,6 @@ --- title: Flask subsection: python -section: tech-languages order: 5 --- diff --git a/tech/languages/python/micropython.md b/tech/languages/python/micropython.md index 62bbd70d..d2228771 100644 --- a/tech/languages/python/micropython.md +++ b/tech/languages/python/micropython.md @@ -1,7 +1,6 @@ --- title: MicroPython subsection: python -section: tech-languages order: 6 --- @@ -197,8 +196,8 @@ noreset is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -imap is : -omap is : +imap is : +omap is : emap is : crcrlf,delbs, Terminal ready diff --git a/tech/languages/python/multiple-pythons.md b/tech/languages/python/multiple-pythons.md index 23fe1234..f8479558 100644 --- a/tech/languages/python/multiple-pythons.md +++ b/tech/languages/python/multiple-pythons.md @@ -1,7 +1,6 @@ --- title: Multiple Pythons subsection: python -section: tech-languages order: 3 --- @@ -15,7 +14,7 @@ Fedora includes all Python versions which are [supported upstream](https://devgu At the time of this writing, Fedora has the following Pythons ready for you in the repositories: - + * CPython 3.11 * CPython 3.10 * CPython 3.9 @@ -46,10 +45,10 @@ CPython 3.6: ```console $ python3.6 -Python 3.6.12 (default, Aug 19 2020, 00:00:00) +Python 3.6.12 (default, Aug 19 2020, 00:00:00) [GCC 10.2.1 20200723 (Red Hat 10.2.1-1)] on linux Type "help", "copyright", "credits" or "license" for more information. ->>> +>>> ``` **Warning:** For production purposes you should use the `python3` @@ -161,7 +160,7 @@ $ source env/bin/activate # activate it (env)$ python -m pip install requests # install a package with pip ... (env)$ python # run python from that environment -Python 3.9.0 (default, Oct 6 2020, 00:00:00) +Python 3.9.0 (default, Oct 6 2020, 00:00:00) [GCC 10.2.1 20200723 (Red Hat 10.2.1-1)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import requests @@ -189,7 +188,7 @@ $ source env/bin/activate # activate it (env)$ python -m pip install requests # install a package with pip ... (env)$ python # run python from that virtualenv -Python 2.7.11 (default, Jul 8 2016, 19:45:00) +Python 2.7.11 (default, Jul 8 2016, 19:45:00) [GCC 5.3.1 20160406 (Red Hat 5.3.1-6)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import requests diff --git a/tech/languages/python/pipenv.md b/tech/languages/python/pipenv.md index 6a541feb..d0f20740 100644 --- a/tech/languages/python/pipenv.md +++ b/tech/languages/python/pipenv.md @@ -1,7 +1,6 @@ --- title: Pipenv subsection: python -section: tech-languages order: 11 --- diff --git a/tech/languages/python/pygobject.md b/tech/languages/python/pygobject.md index ec6a9ef6..925a3e18 100644 --- a/tech/languages/python/pygobject.md +++ b/tech/languages/python/pygobject.md @@ -1,7 +1,6 @@ --- title: PyGObject subsection: python -section: tech-languages order: 8 --- diff --git a/tech/languages/python/pypi-installation.md b/tech/languages/python/pypi-installation.md index 0a893a5f..38af8dd7 100644 --- a/tech/languages/python/pypi-installation.md +++ b/tech/languages/python/pypi-installation.md @@ -1,7 +1,6 @@ --- title: Pip & PyPI subsection: python -section: tech-languages order: 2 --- diff --git a/tech/languages/python/python-sig.md b/tech/languages/python/python-sig.md index d74ca1ce..184d4cb1 100644 --- a/tech/languages/python/python-sig.md +++ b/tech/languages/python/python-sig.md @@ -1,7 +1,6 @@ --- title: Python SIG subsection: python -section: tech-languages order: 7 --- diff --git a/tech/languages/python/scipy.md b/tech/languages/python/scipy.md index 03b0729d..986d7bb5 100644 --- a/tech/languages/python/scipy.md +++ b/tech/languages/python/scipy.md @@ -1,7 +1,6 @@ --- title: Scientific Python Stack subsection: python -section: tech-languages order: 10 --- diff --git a/tech/languages/python/sphinx.md b/tech/languages/python/sphinx.md index 8a033acb..e1928a3d 100644 --- a/tech/languages/python/sphinx.md +++ b/tech/languages/python/sphinx.md @@ -1,7 +1,6 @@ --- title: Sphinx subsection: python -section: tech-languages order: 9 --- @@ -71,7 +70,7 @@ You will probably want to use `html` for local testing purposes and `dirhtml` fo ## latexpdf -Sphinx allows you to render your work in PDF format. +Sphinx allows you to render your work in PDF format. In order to be able to run the `latexpdf` target, you will need to install the following dependencies: @@ -91,7 +90,7 @@ After that, you can continue building the target: make latexpdf ``` -You will see a lot of output showing the process of producing the PDF file and, finally; if successful, find the rendered PDF at `build/latex/.pdf`; along with many other files used to produce it. +You will see a lot of output showing the process of producing the PDF file and, finally; if successful, find the rendered PDF at `build/latex/.pdf`; along with many other files used to produce it. ## What next - See working examples to get an inspiration [Sphinx examples](http://sphinx-doc.org/examples.html) diff --git a/tech/languages/r/blas-lapack.md b/tech/languages/r/blas-lapack.md index 23a27780..621b72e4 100644 --- a/tech/languages/r/blas-lapack.md +++ b/tech/languages/r/blas-lapack.md @@ -1,7 +1,6 @@ --- title: BLAS/LAPACK switching subsection: r -section: tech-languages order: 3 --- diff --git a/tech/languages/r/r-ide.md b/tech/languages/r/r-ide.md index 746fa55a..cd6beeed 100644 --- a/tech/languages/r/r-ide.md +++ b/tech/languages/r/r-ide.md @@ -1,7 +1,6 @@ --- title: R IDE subsection: r -section: tech-languages order: 4 --- diff --git a/tech/languages/r/r-packages.md b/tech/languages/r/r-packages.md index 30ae99a3..f21bba13 100644 --- a/tech/languages/r/r-packages.md +++ b/tech/languages/r/r-packages.md @@ -1,7 +1,6 @@ --- title: R packages subsection: r -section: tech-languages order: 2 --- diff --git a/tech/languages/r/r-sig.md b/tech/languages/r/r-sig.md index aaccf351..25294cf2 100644 --- a/tech/languages/r/r-sig.md +++ b/tech/languages/r/r-sig.md @@ -1,7 +1,6 @@ --- title: R SIG subsection: r -section: tech-languages order: 5 --- diff --git a/tech/languages/ruby/bundler-installation.md b/tech/languages/ruby/bundler-installation.md index 72f0199c..0efe9acc 100644 --- a/tech/languages/ruby/bundler-installation.md +++ b/tech/languages/ruby/bundler-installation.md @@ -1,7 +1,6 @@ --- title: Bundler subsection: ruby -section: tech-languages order: 3 --- diff --git a/tech/languages/ruby/gems-installation.md b/tech/languages/ruby/gems-installation.md index ca2fdb8c..5066978d 100644 --- a/tech/languages/ruby/gems-installation.md +++ b/tech/languages/ruby/gems-installation.md @@ -1,7 +1,6 @@ --- title: Gems subsection: ruby -section: tech-languages order: 2 --- @@ -70,11 +69,11 @@ Note that system gems are installed into `/usr/share/gems` and this path needs t ## Configuring RubyGems -Fedora configures ruby to install gems on your user's directory; as opposed to the system's, by default. The gems get installed at: `$HOME/.local/share/gem`. +Fedora configures ruby to install gems on your user's directory; as opposed to the system's, by default. The gems get installed at: `$HOME/.local/share/gem`. You can check the defaults [here](https://src.fedoraproject.org/rpms/ruby/blob/rawhide/f/operating_system.rb). -You can change these defaults by creating `$HOME/.gemrc`. +You can change these defaults by creating `$HOME/.gemrc`. For example, to disable documentation generation at install time, you can do the following: @@ -89,9 +88,9 @@ Or, in order to override the system's default, use: ``` gem: --user-install ``` -Remember to add: `$HOME/.local/share/gem/ruby/bin` to your `$PATH` if you choose to use `gem: ...` since all default settings would be overriden if you do. +Remember to add: `$HOME/.local/share/gem/ruby/bin` to your `$PATH` if you choose to use `gem: ...` since all default settings would be overriden if you do. -One way of doing this is adding the following to `$HOME/.bash_profile`: +One way of doing this is adding the following to `$HOME/.bash_profile`: ``` # my path diff --git a/tech/languages/ruby/ror-installation.md b/tech/languages/ruby/ror-installation.md index ba6d482c..59619001 100644 --- a/tech/languages/ruby/ror-installation.md +++ b/tech/languages/ruby/ror-installation.md @@ -1,7 +1,6 @@ --- title: Ruby on Rails subsection: ruby -section: tech-languages order: 4 --- diff --git a/tech/languages/ruby/ruby-sig.md b/tech/languages/ruby/ruby-sig.md index a363379a..9c7d9525 100644 --- a/tech/languages/ruby/ruby-sig.md +++ b/tech/languages/ruby/ruby-sig.md @@ -1,7 +1,6 @@ --- title: Ruby SIG subsection: ruby -section: tech-languages order: 6 --- diff --git a/tech/languages/ruby/sinatra-installation.md b/tech/languages/ruby/sinatra-installation.md index b1470c77..5cba8bcd 100644 --- a/tech/languages/ruby/sinatra-installation.md +++ b/tech/languages/ruby/sinatra-installation.md @@ -1,7 +1,6 @@ --- title: Sinatra subsection: ruby -section: tech-languages order: 5 --- diff --git a/tech/languages/rust/format-rust-code.md b/tech/languages/rust/format-rust-code.md index acba7ee2..eee51956 100644 --- a/tech/languages/rust/format-rust-code.md +++ b/tech/languages/rust/format-rust-code.md @@ -1,7 +1,6 @@ --- title: Format Rust code subsection: rust -section: tech-languages order: 3 --- diff --git a/tech/languages/rust/further-reading.md b/tech/languages/rust/further-reading.md index 698987e8..f5acfd37 100644 --- a/tech/languages/rust/further-reading.md +++ b/tech/languages/rust/further-reading.md @@ -1,7 +1,6 @@ --- title: Further reading subsection: rust -section: tech-languages order: 4 --- @@ -88,3 +87,4 @@ If you want to start with some web applications, a list of useful frameworks is If you are brave enough and you want to try the nightly compiler edition (or you just want to try the awesome [Rocket framework](https://rocket.rs/)), it is recommended to use rustup: [rustup.rs](https://rustup.rs/) + diff --git a/tech/languages/rust/rust-cargo.md b/tech/languages/rust/rust-cargo.md index 6c78d3fc..a421dea0 100644 --- a/tech/languages/rust/rust-cargo.md +++ b/tech/languages/rust/rust-cargo.md @@ -1,7 +1,6 @@ --- title: Cargo subsection: rust -section: tech-languages order: 2 --- diff --git a/tech/languages/rust/rust-sig.md b/tech/languages/rust/rust-sig.md index 1490dae0..e2d0cc46 100644 --- a/tech/languages/rust/rust-sig.md +++ b/tech/languages/rust/rust-sig.md @@ -1,7 +1,6 @@ --- title: Rust SIG subsection: rust -section: tech-languages order: 5 --- diff --git a/tools/docker/compose.md b/tools/docker/compose.md index 27f0390a..f6417736 100644 --- a/tools/docker/compose.md +++ b/tools/docker/compose.md @@ -1,7 +1,6 @@ --- title: Docker Compose subsection: docker -section: tools order: 5 --- diff --git a/tools/docker/docker-configuration.md b/tools/docker/docker-configuration.md index 00c3fb88..2909acba 100644 --- a/tools/docker/docker-configuration.md +++ b/tools/docker/docker-configuration.md @@ -1,7 +1,6 @@ --- title: Configuring Docker subsection: docker -section: tools order: 3 --- diff --git a/tools/docker/docker-images.md b/tools/docker/docker-images.md index 8e7da2d2..c7318bed 100644 --- a/tools/docker/docker-images.md +++ b/tools/docker/docker-images.md @@ -1,7 +1,6 @@ --- title: Docker images subsection: docker -section: tools order: 4 --- @@ -95,3 +94,4 @@ To download them just run `docker pull IMAGE_NAME`. | openshift/python-33-centos7 | Python 3.3 platform for building and running applications | | openshift/nodejs-010-centos7 | NodeJS 0.10 platform for building and running applications | | openshift/perl-516-centos7 | Perl 5.16 platform for building and running applications | + diff --git a/tools/docker/docker-installation.md b/tools/docker/docker-installation.md index 2548ace6..c80031d0 100644 --- a/tools/docker/docker-installation.md +++ b/tools/docker/docker-installation.md @@ -1,7 +1,6 @@ --- title: Getting started with Docker on Fedora subsection: docker -section: tools order: 1 --- diff --git a/tools/docker/docker-interactive-management.md b/tools/docker/docker-interactive-management.md index e933ab36..9906ada9 100644 --- a/tools/docker/docker-interactive-management.md +++ b/tools/docker/docker-interactive-management.md @@ -1,7 +1,6 @@ --- title: sen — interactive management subsection: docker -section: tools description: Manage your containers interactively! --- diff --git a/tools/docker/docker-usage.md b/tools/docker/docker-usage.md index f8039cd6..d650a9c8 100644 --- a/tools/docker/docker-usage.md +++ b/tools/docker/docker-usage.md @@ -1,7 +1,6 @@ --- title: Docker basics subsection: docker -section: tools order: 2 --- diff --git a/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.md b/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.md index 6983134c..ae8f7c0e 100644 --- a/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.md +++ b/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.md @@ -1,26 +1,25 @@ --- -title: Fetching OVMF UEFI from the correct source -subsection: virtualization -section: tools -order: 2 +title: Fetching OVMF UEFI from the correct source +subsection: virtualization +order: 2 --- # Fetching OVMF UEFI from the correct source -1. On the host device, execute either of the following commands to install OVMF, if not already installed. - 1. **Stable builds from Fedora repos** - Since June 2016, OVMF is available in the default Fedora repositories as a part of the `edk2-ovmf` package. It would most likely be installed already on a default Fedora installation and the package also includes the firmware for secureboot. +1. On the host device, execute either of the following commands to install OVMF, if not already installed. + 1. **Stable builds from Fedora repos** + Since June 2016, OVMF is available in the default Fedora repositories as a part of the `edk2-ovmf` package. It would most likely be installed already on a default Fedora installation and the package also includes the firmware for secureboot. ```console $ sudo dnf install edk2-ovmf -y ``` - 2. **Nightly builds from custom repo** - The nightly builds of OVMF can be found in a custom repository maintained by Gerd Hoffmann on his personal site where a collection of QEMU/KVM firmware, including EDK2/OVMF can be found. Due to their experimental nature, these builds can be occasionally broken. + 2. **Nightly builds from custom repo** + The nightly builds of OVMF can be found in a custom repository maintained by Gerd Hoffmann on his personal site where a collection of QEMU/KVM firmware, including EDK2/OVMF can be found. Due to their experimental nature, these builds can be occasionally broken. ```console $ sudo dnf install dnf-plugins-core $ sudo dnf config-manager --add-repo http://www.kraxel.org/repos/firmware.repo $ sudo dnf install edk2.git-ovmf-x64 ``` -2. Navigate to the following directory where the OVMF assets are installed. +2. Navigate to the following directory where the OVMF assets are installed. ```console $ cd /usr/share/edk2/ovmf $ ls @@ -32,4 +31,4 @@ order: 2 Shell.efi UefiShell.iso ``` -3. Assets from this folder would be continually referred to in the dealings with QEMU. +3. Assets from this folder would be continually referred to in the dealings with QEMU. diff --git a/tools/virtualization/installing-libvirt-and-virt-install-on-fedora-linux.md b/tools/virtualization/installing-libvirt-and-virt-install-on-fedora-linux.md index d5336eb9..b0c9163a 100644 --- a/tools/virtualization/installing-libvirt-and-virt-install-on-fedora-linux.md +++ b/tools/virtualization/installing-libvirt-and-virt-install-on-fedora-linux.md @@ -1,8 +1,7 @@ --- -title: Installing libvirt and virt-install on Fedora Linux -subsection: virtualization -section: tools -order: 3 +title: Installing libvirt and virt-install on Fedora Linux +subsection: virtualization +order: 3 --- # Installing libvirt and virt-install on Fedora Linux @@ -13,7 +12,7 @@ order: 3 Libvirt is an open-source API, daemon and management tool for managing platform virtualization. It can be used to manage KVM, Xen, VMware ESXi, QEMU and other virtualization technologies. These APIs are widely used in the orchestration layer of hypervisors in the development of a cloud-based solution. -The Libvirt project: +The Libvirt project: - is a toolkit to manage virtualization platforms - is accessible from C, Python, Perl, Go and more - supports KVM, QEMU, Xen, Virtuozzo, VMWare ESX, LXC, BHyve and more @@ -36,7 +35,7 @@ Given suitable command line arguments, "virt-install" is capable of running comp ## Installing steps -1. Execute the following command to install libvirt on the host device, if not already installed. +1. Execute the following command to install libvirt on the host device, if not already installed. ```console $ sudo dnf install libvirt -y ``` diff --git a/tools/virtualization/installing-qemu-on-fedora-linux.md b/tools/virtualization/installing-qemu-on-fedora-linux.md index 6138236f..091a0d63 100644 --- a/tools/virtualization/installing-qemu-on-fedora-linux.md +++ b/tools/virtualization/installing-qemu-on-fedora-linux.md @@ -1,15 +1,14 @@ --- -title: Installing QEMU on Fedora Linux -subsection: virtualization -section: tools -order: 1 +title: Installing QEMU on Fedora Linux +subsection: virtualization +order: 1 --- # Installing QEMU ## Common terms -### QEMU +### QEMU QEMU is a generic and open source machine & userspace emulator and virtualizer. @@ -31,7 +30,7 @@ Using KVM, one can run multiple virtual machines running unmodified Linux or Win ## Installing steps -1. Execute the following command to install QEMU on the host device, if not already installed. +1. Execute the following command to install QEMU on the host device, if not already installed. ```console $ sudo dnf install qemu -y ``` diff --git a/tools/virtualization/mapping-a-virtualised-guest-port-to-a-host-port.md b/tools/virtualization/mapping-a-virtualised-guest-port-to-a-host-port.md index 7867fbde..7d37b82b 100644 --- a/tools/virtualization/mapping-a-virtualised-guest-port-to-a-host-port.md +++ b/tools/virtualization/mapping-a-virtualised-guest-port-to-a-host-port.md @@ -1,17 +1,16 @@ --- -title: Mapping a virtualized guest port to a host port -subsection: virtualization -section: tools -order: 10 +title: Mapping a virtualized guest port to a host port +subsection: virtualization +order: 10 --- # Mapping a virtualized guest port to a host port -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Start a virtual machine for mapping a virtualized guest port to a host port for the live ISO and there is no need for a virtual disk image here. +2. Start a virtual machine for mapping a virtualized guest port to a host port for the live ISO and there is no need for a virtual disk image here. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -23,31 +22,31 @@ order: 10 -net nic \ -net user,hostfwd=tcp::2323-:22 ``` -3. Wait for the virtual machine to boot up. - ![01](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/01.png) -4. In a new terminal session on the guest, execute the following command to the enable the `OpenSSH` service. +3. Wait for the virtual machine to boot up. + ![01](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/01.png) +4. In a new terminal session on the guest, execute the following command to the enable the `OpenSSH` service. ```console $ sudo systemctl enable --now sshd.service ``` - ![02](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/02.png) -5. Now change the password of the current user by executing the following command in the terminal session on the guest. + ![02](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/02.png) +5. Now change the password of the current user by executing the following command in the terminal session on the guest. ```console $ passwd ``` - ![03](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/03.png) -6. In a new terminal session on the host, execute the following command to connect to the guest using `SSH`. + ![03](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/03.png) +6. In a new terminal session on the host, execute the following command to connect to the guest using `SSH`. ```console $ ssh liveuser@localhost -p 2323 ``` - ![04](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/04.png) - OR - In a new terminal session on a device connected to the same network, execute the following command to connect to the guest using `SSH`. + ![04](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/04.png) + OR + In a new terminal session on a device connected to the same network, execute the following command to connect to the guest using `SSH`. ```console $ ssh liveuser@ -p 2323 ``` - ![05](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/05.png) -7. Execute the following command in to logout of the session. + ![05](/content/tools/virtualization/images/mapping-a-virtualised-guest-port-to-a-host-port/05.png) +7. Execute the following command in to logout of the session. ```console $ logout ``` -8. This was an example of mapping port 22 of the virtualized guest with port 2323 of the host with TCP for the purposes of SSH and this can be reused with slight changes to accommodate other use-cases. +8. This was an example of mapping port 22 of the virtualized guest with port 2323 of the host with TCP for the purposes of SSH and this can be reused with slight changes to accommodate other use-cases. diff --git a/tools/virtualization/offloading-domain-tty-output-to-console-with-custom-kernel-initramfs-images.md b/tools/virtualization/offloading-domain-tty-output-to-console-with-custom-kernel-initramfs-images.md index 4dfe16eb..df04953b 100644 --- a/tools/virtualization/offloading-domain-tty-output-to-console-with-custom-kernel-initramfs-images.md +++ b/tools/virtualization/offloading-domain-tty-output-to-console-with-custom-kernel-initramfs-images.md @@ -1,8 +1,7 @@ --- -title: Offloading domain TTY output to console with custom kernel/initramfs images -subsection: virtualization -section: tools -order: 12 +title: Offloading domain TTY output to console with custom kernel/initramfs images +subsection: virtualization +order: 12 --- # Offloading domain TTY output to console with custom kernel/initramfs images @@ -13,7 +12,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu ## Steps -1. Navigate to the `/boot` directory of the Fedora installation of the host to grab some kernel and initramfs images. +1. Navigate to the `/boot` directory of the Fedora installation of the host to grab some kernel and initramfs images. ```console $ cd /boot $ ls -l vmlinuz-* @@ -22,12 +21,12 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -rwxr-xr-x. 1 root root 10851312 Jul 25 22:05 vmlinuz-5.13.5-200.fc34.x86_64 -rwxr-xr-x. 1 root root 10850800 Jul 28 21:17 vmlinuz-5.13.6-200.fc34.x86_64 ``` -2. With appropriate permissions, copy the kernel images to a reference directory `linxkrnl` and the initramfs images to a reference directory `initrmfs`. +2. With appropriate permissions, copy the kernel images to a reference directory `linxkrnl` and the initramfs images to a reference directory `initrmfs`. ```console $ sudo cp /boot/vmlinux-* linxkrnl/ $ sudo cp /boot/initramfs-* initrmfs/ ``` -3. Take up the ownership of the copied kernel images and kernel images by executing the following command on the reference directories `linxkrnl` and `initrmfs` respectively. +3. Take up the ownership of the copied kernel images and kernel images by executing the following command on the reference directories `linxkrnl` and `initrmfs` respectively. ```console $ sudo chown $(whoami):$(whoami) linxkrnl/ --recursive $ sudo chown $(whoami):$(whoami) initrmfs/ --recursive @@ -48,7 +47,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -rw-------. 1 t0xic0der t0xic0der 33002599 Aug 2 15:36 initramfs-5.13.5-200.fc34.x86_64.img -rw-------. 1 t0xic0der t0xic0der 32910001 Aug 2 15:36 initramfs-5.13.6-200.fc34.x86_64.img ``` -4. Reuse the domain with the custom partitioning based on EXT4 that was created by the end of the [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) and start it up by executing the following command. +4. Reuse the domain with the custom partitioning based on EXT4 that was created by the end of the [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) and start it up by executing the following command. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -58,12 +57,12 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -drive file=datadrct/fedobios.raw,format=raw \ -accel kvm ``` -5. In a new terminal session inside the virtualized domain, execute the following command to fetch the parameters passed to the kernel during boot. +5. In a new terminal session inside the virtualized domain, execute the following command to fetch the parameters passed to the kernel during boot. ```console $ cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.11.12-300.fc34.x86_64 root=UUID=0fa356e9-9509-4e18-8283-8983254c79d1 ro rhgb quiet ``` - Take a note of the UUID for the root partition and the same can be confirmed by executing the following command in a terminal session inside the virtualized domain. + Take a note of the UUID for the root partition and the same can be confirmed by executing the following command in a terminal session inside the virtualized domain. ```console $ cat /etc/fstab # @@ -79,7 +78,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu UUID=0fa356e9-9509-4e18-8283-8983254c79d1 / ext4 defaults 1 1 UUID=2d2863bb-527b-4477-bae5-5955bdb44d7b /boot ext4 defaults 1 2 ``` -6. Power off the virtualized domain and start it up again by executing the following command with the correct UUID for the root partition. +6. Power off the virtualized domain and start it up again by executing the following command with the correct UUID for the root partition. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -93,7 +92,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -initrd initrmfs/ \ -append "root=UUID= rw console=ttyS0" ``` -7. A lot of `systemd` prompts would show up on the console and the virtualized domain would boot up. The following is an example output for the above command. +7. A lot of `systemd` prompts would show up on the console and the virtualized domain would boot up. The following is an example output for the above command. ``` ... [ OK ] Started Network Manager Script Dispatcher Service. @@ -109,24 +108,24 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu Starting GNOME Display Manager... Starting Hold until boot process finishes up... [ OK ] Started GNOME Display Manager. - + Fedora 34 (Workstation Edition) Kernel 5.13.6-200.fc34.x86_64 on an x86_64 (ttyS0) - + fedorable login: t0xic0der - Password: + Password: Last login: Tue Aug 3 09:31:12 on tty2 [t0xic0der@fedorable ~]$ ``` -8. As the kernel image and initramfs image versions that we used here are dissimilar from the version of the firmware installed on the virtualized domain, there can be kernel modules which are broken or incompletely loaded. +8. As the kernel image and initramfs image versions that we used here are dissimilar from the version of the firmware installed on the virtualized domain, there can be kernel modules which are broken or incompletely loaded. ```console $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever - inet6 ::1/128 scope host + inet6 ::1/128 scope host valid_lft forever preferred_lft forever ``` - As evidenced by the output of the above command executed inside the console of the virtualized domain, the kernel modules for network are apparently broken and the hostname of the host is taken up by the virtualized domain due to the mismatch of kernel images, initramfs images and installed firmware versions. -9. For best compatibility, keep the versions for kernel image, initramfs image and installed firmware inline with each other. Instructions for the same have been provided in the [**Offloading domain TTY output to console with original kernel/initramfs images**](/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.html) documentation. + As evidenced by the output of the above command executed inside the console of the virtualized domain, the kernel modules for network are apparently broken and the hostname of the host is taken up by the virtualized domain due to the mismatch of kernel images, initramfs images and installed firmware versions. +9. For best compatibility, keep the versions for kernel image, initramfs image and installed firmware inline with each other. Instructions for the same have been provided in the [**Offloading domain TTY output to console with original kernel/initramfs images**](/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.html) documentation. diff --git a/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.md b/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.md index cac0e4d0..c0509c55 100644 --- a/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.md +++ b/tools/virtualization/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images.md @@ -1,8 +1,7 @@ --- -title: Offloading domain TTY output to console with original kernel/initramfs images -subsection: virtualization -section: tools -order: 13 +title: Offloading domain TTY output to console with original kernel/initramfs images +subsection: virtualization +order: 13 --- # Offloading domain TTY output to console with original kernel/initramfs images @@ -15,7 +14,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu ## Steps -1. Reuse the domain with the custom partitioning based on EXT4 that was created by the end of the [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) and start it up by executing the following command. +1. Reuse the domain with the custom partitioning based on EXT4 that was created by the end of the [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) and start it up by executing the following command. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -27,12 +26,12 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -drive file=datadrct/fedobios.raw,format=raw \ -accel kvm ``` -2. In a new terminal session of the virtualized domain, execute the following command to fetch details about the currently used kernel image version. +2. In a new terminal session of the virtualized domain, execute the following command to fetch details about the currently used kernel image version. ```console $ uname -a ``` ![01](/content/tools/virtualization/images/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images/01.png) -3. With appropriate permissions, copy the kernel image and the initramfs image of the aforementioned version to the home directory of the default user in the virtualized domain. +3. With appropriate permissions, copy the kernel image and the initramfs image of the aforementioned version to the home directory of the default user in the virtualized domain. ```console $ ls -la /boot ``` @@ -43,19 +42,19 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu $ ls -lh . ``` ![03](/content/tools/virtualization/images/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images/03.png) -4. Take up the ownership of the copied kernel images and kernel images by executing the following command in a terminal session in the virtualized domain. +4. Take up the ownership of the copied kernel images and kernel images by executing the following command in a terminal session in the virtualized domain. ```console $ sudo chown $(whoami):$(whoami) $ sudo chown $(whoami):$(whoami) $ ls -lh . ``` ![04](/content/tools/virtualization/images/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images/04.png) -5. Start an HTTP server in the same directory by executing the following command in a terminal session in the virtualized domain. +5. Start an HTTP server in the same directory by executing the following command in a terminal session in the virtualized domain. ```console $ python3 -m http.server 8080 ``` ![05](/content/tools/virtualization/images/offloading-domain-tty-output-to-console-with-original-kernel-initramfs-images/05.png) -6. In a new terminal session of the host, execute the following command to pull the kernel image and initramfs image into reference directories `linxkrnl` and `initrmfs` respectively. +6. In a new terminal session of the host, execute the following command to pull the kernel image and initramfs image into reference directories `linxkrnl` and `initrmfs` respectively. ```console $ wget http://localhost:6969/vmlinuz-x.yy.zz-aaa.fcRR.x86_64 -O linxkrnl/vmlinuz-x.yy.zz-aaa.fcRR.x86_64 $ wget http://localhost:6969/initramfs-x.yy.zz-aaa.fcRR.x86_64.img -O initrmfs/initramfs-x.yy.zz-aaa.fcRR.x86_64.img @@ -74,12 +73,12 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -rw-------. 1 t0xic0der t0xic0der 32M Aug 2 15:36 initramfs-5.13.5-200.fc34.x86_64.img -rw-------. 1 t0xic0der t0xic0der 32M Aug 2 15:36 initramfs-5.13.6-200.fc34.x86_64.img ``` -7. Execute the following command to fetch the parameters passed to the kernel during boot in a terminal session in the virtualized domain. +7. Execute the following command to fetch the parameters passed to the kernel during boot in a terminal session in the virtualized domain. ```console $ cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.11.12-300.fc34.x86_64 root=UUID=0fa356e9-9509-4e18-8283-8983254c79d1 ro rhgb quiet ``` - Take a note of the UUID for the root partition and the same can be confirmed by executing the following command in a terminal session inside the virtualized domain. + Take a note of the UUID for the root partition and the same can be confirmed by executing the following command in a terminal session inside the virtualized domain. ```console $ cat /etc/fstab # @@ -95,7 +94,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu UUID=0fa356e9-9509-4e18-8283-8983254c79d1 / ext4 defaults 1 1 UUID=2d2863bb-527b-4477-bae5-5955bdb44d7b /boot ext4 defaults 1 2 ``` -8. Power off the virtualized domain and start it up again by executing the following command with the correct UUID for the root partition, correct names for kernel image and initramfs image which were recently fetched. +8. Power off the virtualized domain and start it up again by executing the following command with the correct UUID for the root partition, correct names for kernel image and initramfs image which were recently fetched. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -109,7 +108,7 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu -initrd initrmfs/ \ -append "root=UUID= rw console=ttyS0" ``` -9. A lot of `systemd` prompts would show up on the console and the virtualized domain would boot up. The following is an example output for the above command. +9. A lot of `systemd` prompts would show up on the console and the virtualized domain would boot up. The following is an example output for the above command. ``` ... [ OK ] Started Network Manager Script Dispatcher Service. @@ -125,32 +124,32 @@ In a headless virtual machine hosts accessible by SSH, the activities on a virtu Starting GNOME Display Manager... Starting Hold until boot process finishes up... [ OK ] Started GNOME Display Manager. - + Fedora 34 (Workstation Edition) Kernel 5.13.6-200.fc34.x86_64 on an x86_64 (ttyS0) - + fedora login: t0xic0der - Password: + Password: Last login: Tue Aug 3 10:31:46 on tty2 [t0xic0der@fedora ~]$ ``` -10. As the kernel image and initramfs image versions that we used here are similar to the version of the firmware installed on the virtualized domain, there can be kernel modules work just fine. +10. As the kernel image and initramfs image versions that we used here are similar to the version of the firmware installed on the virtualized domain, there can be kernel modules work just fine. ```console $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever - inet6 ::1/128 scope host + inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute ens3 valid_lft 86298sec preferred_lft 86298sec - inet6 fec0::26ff:70eb:26b2:5923/64 scope site dynamic noprefixroute + inet6 fec0::26ff:70eb:26b2:5923/64 scope site dynamic noprefixroute valid_lft 86302sec preferred_lft 14302sec - inet6 fe80::486a:c7b3:ca0a:43cf/64 scope link noprefixroute + inet6 fe80::486a:c7b3:ca0a:43cf/64 scope link noprefixroute valid_lft forever preferred_lft forever ``` - As evidenced by the output of the above command executed inside the console of the virtualized domain, the kernel modules for network now work just fine and the hostname of the virtualized host has been retained as the kernel images, initramfs images and installed firmware versions correspond with each other. + As evidenced by the output of the above command executed inside the console of the virtualized domain, the kernel modules for network now work just fine and the hostname of the virtualized host has been retained as the kernel images, initramfs images and installed firmware versions correspond with each other. diff --git a/tools/virtualization/playing-around-with-various-vga-providers.md b/tools/virtualization/playing-around-with-various-vga-providers.md index e1b849f3..b79d3a8e 100644 --- a/tools/virtualization/playing-around-with-various-vga-providers.md +++ b/tools/virtualization/playing-around-with-various-vga-providers.md @@ -1,17 +1,16 @@ --- -title: Playing around with various VGA providers -subsection: virtualization -section: tools -order: 11 +title: Playing around with various VGA providers +subsection: virtualization +order: 11 --- # Playing around with various VGA providers -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Execute the following command to know about the VGA providers available at disposal. +2. Execute the following command to know about the VGA providers available at disposal. ```console $ qemu-system-x86_64 -vga help none no graphic card @@ -22,7 +21,7 @@ order: 11 qxl QXL VGA virtio Virtio VGA ``` -3. Start a virtual machine for playing around with various VGA providers for the live ISO and there is no need for a virtual disk image here. +3. Start a virtual machine for playing around with various VGA providers for the live ISO and there is no need for a virtual disk image here. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -32,12 +31,12 @@ order: 11 -cdrom cdromimg/ \ -accel kvm ``` -4. Open up `Settings` inside the VM and head over to the `About` section. Information about the `Graphics` can be seen here. -5. Open up `Terminal` inside the VM and execute the `lspci` commands in regards with the current VGA controller to find more information on it. +4. Open up `Settings` inside the VM and head over to the `About` section. Information about the `Graphics` can be seen here. +5. Open up `Terminal` inside the VM and execute the `lspci` commands in regards with the current VGA controller to find more information on it. -We will test out each VGA provider one-by-one and list the information for each now. +We will test out each VGA provider one-by-one and list the information for each now. -1. Standard VGA (Default) +1. Standard VGA (Default) ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -48,11 +47,11 @@ We will test out each VGA provider one-by-one and list the information for each -accel kvm \ -vga std ``` - 1. `Settings` -> `About` + 1. `Settings` -> `About` ![01](/content/tools/virtualization/images/playing-around-with-various-vga-providers/01.png) - 2. `lspci` + 2. `lspci` ![02](/content/tools/virtualization/images/playing-around-with-various-vga-providers/02.png) -2. No graphic card +2. No graphic card ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -64,7 +63,7 @@ We will test out each VGA provider one-by-one and list the information for each -vga none ``` ![03](/content/tools/virtualization/images/playing-around-with-various-vga-providers/03.png) -3. Cirrus VGA +3. Cirrus VGA ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -75,11 +74,11 @@ We will test out each VGA provider one-by-one and list the information for each -accel kvm \ -vga cirrus ``` - 1. `Settings` -> `About` + 1. `Settings` -> `About` ![04](/content/tools/virtualization/images/playing-around-with-various-vga-providers/04.png) - 2. `lspci` + 2. `lspci` ![05](/content/tools/virtualization/images/playing-around-with-various-vga-providers/05.png) -4. VMware SVGA +4. VMware SVGA ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -90,11 +89,11 @@ We will test out each VGA provider one-by-one and list the information for each -accel kvm \ -vga vmware ``` - 1. `Settings` -> `About` + 1. `Settings` -> `About` ![06](/content/tools/virtualization/images/playing-around-with-various-vga-providers/06.png) - 2. `lspci` + 2. `lspci` ![07](/content/tools/virtualization/images/playing-around-with-various-vga-providers/07.png) -5. Xen paravirtualized framebuffer +5. Xen paravirtualized framebuffer ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -106,7 +105,7 @@ We will test out each VGA provider one-by-one and list the information for each -vga xenfb ``` ![08](/content/tools/virtualization/images/playing-around-with-various-vga-providers/08.png) -6. QXL VGA +6. QXL VGA ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -117,11 +116,11 @@ We will test out each VGA provider one-by-one and list the information for each -accel kvm \ -vga qxl ``` - 1. `Settings` -> `About` + 1. `Settings` -> `About` ![09](/content/tools/virtualization/images/playing-around-with-various-vga-providers/09.png) - 2. `lspci` + 2. `lspci` ![10](/content/tools/virtualization/images/playing-around-with-various-vga-providers/10.png) -7. VirtIO VGA +7. VirtIO VGA ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -132,9 +131,9 @@ We will test out each VGA provider one-by-one and list the information for each -accel kvm \ -vga virtio ``` - 1. `Settings` -> `About` + 1. `Settings` -> `About` ![11](/content/tools/virtualization/images/playing-around-with-various-vga-providers/11.png) - 2. `lspci` + 2. `lspci` ![12](/content/tools/virtualization/images/playing-around-with-various-vga-providers/12.png) ## References diff --git a/tools/virtualization/setting-up-fedora-workstation-domain-on-libvirt.md b/tools/virtualization/setting-up-fedora-workstation-domain-on-libvirt.md index 2fd57e02..cdc1008d 100644 --- a/tools/virtualization/setting-up-fedora-workstation-domain-on-libvirt.md +++ b/tools/virtualization/setting-up-fedora-workstation-domain-on-libvirt.md @@ -1,21 +1,20 @@ --- -title: Setting up Fedora Workstation domain on libvirt -subsection: virtualization -section: tools -order: 8 +title: Setting up Fedora Workstation domain on libvirt +subsection: virtualization +order: 8 --- # Setting up Fedora Workstation domain on libvirt -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. +2. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. ```console $ qemu-img create -f raw datadrct/fedovirt.raw 16G ``` -3. Invoke virt-install session for installing Fedora Workstation using BIOS on the virtual disk image by executing the following command on the host. +3. Invoke virt-install session for installing Fedora Workstation using BIOS on the virtual disk image by executing the following command on the host. ```console $ virt-install \ --virt-type kvm \ @@ -28,8 +27,8 @@ order: 8 --network default,mac=00:00:00:00:03:00 \ --noautoconsole \ ``` - OR - Invoke virt-install session for installing Fedora Workstation using UEFI on the virtual disk image by executing the following command on the host. + OR + Invoke virt-install session for installing Fedora Workstation using UEFI on the virtual disk image by executing the following command on the host. ```console $ virt-install \ --virt-type kvm \ @@ -43,56 +42,56 @@ order: 8 --noautoconsole \ --boot uefi ``` - The following is an example output for the above command. + The following is an example output for the above command. ``` Starting install... - + Domain is still running. Installation may be in progress. You can reconnect to the console to complete the installation process. ``` -4. Execute the following command on the host to list currently defined domains. The `--all` flag lists all domains - even if they are running or not. +4. Execute the following command on the host to list currently defined domains. The `--all` flag lists all domains - even if they are running or not. ```console $ virsh list --all Id Name State ------------------------------- 1 fedoraXX-mstr running ``` -5. Visit https://www.realvnc.com/en/connect/download/viewer/ in an internet browser of choice, download and install the VNC viewer application either on the host device or another device in the same network. -6. Switch to the VNC Viewer window and type in `0.0.0.0:5920` from the host device (or `:5920` if accessed from another device in the same network) to continue installing. -7. A greeting window would open up inside the VNC Viewer, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. - ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-domain-on-libvirt/01.png) -8. Now, follow either the instructions [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) guide if BIOS is being used or [**Setting up Fedora Workstation VM on QEMU using UEFI**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.html) guide if UEFI is being used to complete the installation. -9. Once the installation is completed, power off the domain. It would show up like the following when listed on the host. +5. Visit https://www.realvnc.com/en/connect/download/viewer/ in an internet browser of choice, download and install the VNC viewer application either on the host device or another device in the same network. +6. Switch to the VNC Viewer window and type in `0.0.0.0:5920` from the host device (or `:5920` if accessed from another device in the same network) to continue installing. +7. A greeting window would open up inside the VNC Viewer, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. + ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-domain-on-libvirt/01.png) +8. Now, follow either the instructions [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html) guide if BIOS is being used or [**Setting up Fedora Workstation VM on QEMU using UEFI**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.html) guide if UEFI is being used to complete the installation. +9. Once the installation is completed, power off the domain. It would show up like the following when listed on the host. ```console $ virsh list --all Id Name State ------------------------------- 1 fedoraXX-mstr shut off ``` -10. It can be started up again by executing the following command on the host. +10. It can be started up again by executing the following command on the host. ```console $ virsh start fedoraXX-mstr Domain 'fedoraXX-mstr' started ``` - Switch to the VNC Viewer window and type in `0.0.0.0:5920` from the host device (or `:5920` if accessed from another device in the same network) to continue using the domain. -11. To power off a domain externally, simply execute the following command from the host. + Switch to the VNC Viewer window and type in `0.0.0.0:5920` from the host device (or `:5920` if accessed from another device in the same network) to continue using the domain. +11. To power off a domain externally, simply execute the following command from the host. ```console $ virsh shutdown fedoraXX-mstr Domain 'fedoraXX-mstr' is being shutdown ``` -12. If the domain has become unresponsive to the shutdown command, it can be forcibly turned off by executing the following command from the host. +12. If the domain has become unresponsive to the shutdown command, it can be forcibly turned off by executing the following command from the host. ```console $ virsh destroy fedoraXX-mstr Domain 'fedora34-mstr' destroyed ``` -13. If the domain is no longer required, it can be unlisted by executing the following command from the host. +13. If the domain is no longer required, it can be unlisted by executing the following command from the host. ```console $ virsh undefine fedoraXX-mstr Domain 'fedora34-mstr' has been undefined ``` - Note that this would not remove the virtual disk image, the installation sources and other related elements for the domain and they must be removed manually. -14. To edit the configuration of the domain, execute the following command from the host. + Note that this would not remove the virtual disk image, the installation sources and other related elements for the domain and they must be removed manually. +14. To edit the configuration of the domain, execute the following command from the host. ```console $ virsh edit fedoraXX-mstr ``` - This would open up the domain's XML configuration specification in the default text editor of the host. Follow https://libvirt.org/formatdomain.html to learn more about it. + This would open up the domain's XML configuration specification in the default text editor of the host. Follow https://libvirt.org/formatdomain.html to learn more about it. diff --git a/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.md b/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.md index fce6f919..e1d8ea51 100644 --- a/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.md +++ b/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.md @@ -1,21 +1,20 @@ --- -title: Setting up Fedora Workstation VM on QEMU using BIOS -subsection: virtualization -section: tools -order: 4 +title: Setting up Fedora Workstation VM on QEMU using BIOS +subsection: virtualization +order: 4 --- # Setting up Fedora Workstation VM on QEMU using BIOS -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. +2. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. ```console $ qemu-img create -f raw datadrct/fedobios.raw 16G ``` -3. Start a virtual machine for installing Fedora Workstation on the virtual disk image by executing the following command on the host. +3. Start a virtual machine for installing Fedora Workstation on the virtual disk image by executing the following command on the host. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -26,30 +25,30 @@ order: 4 -drive file=datadrct/fedobios.raw,format=raw \ -accel kvm ``` - ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/01.png) - ![02](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/02.png) -4. A greeting window would open up, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. - Click on the `Install to Hard Drive` button to open up the installer application. - ![03](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/03.png) -5. Pick the language of choice to proceed with the installation on the installer application. - ![04](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/04.png) -6. Configure the installation to liking and then click on `Begin Installation` on the installer application to start. - ![05](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/05.png) - 1. BTRFS partitioning is recommended and the partitioning scheme is configured to consider it as a default. Proceed with the automatic partitioning scheme as illustrated in the following screenshot to apply the recommended partitioning. - ![06](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/06.png) - 2. In case of a requirement of a custom partitioning scheme, toggle the `Custom` radio button under `Storage Configuration` and click on `Done` button to move to the page where custom partitioning scheme can be selected. - ![07](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/07.png) - For the sake of simplicity, the partitions are configured in the following manner. - + ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/01.png) + ![02](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/02.png) +4. A greeting window would open up, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. + Click on the `Install to Hard Drive` button to open up the installer application. + ![03](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/03.png) +5. Pick the language of choice to proceed with the installation on the installer application. + ![04](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/04.png) +6. Configure the installation to liking and then click on `Begin Installation` on the installer application to start. + ![05](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/05.png) + 1. BTRFS partitioning is recommended and the partitioning scheme is configured to consider it as a default. Proceed with the automatic partitioning scheme as illustrated in the following screenshot to apply the recommended partitioning. + ![06](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/06.png) + 2. In case of a requirement of a custom partitioning scheme, toggle the `Custom` radio button under `Storage Configuration` and click on `Done` button to move to the page where custom partitioning scheme can be selected. + ![07](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/07.png) + For the sake of simplicity, the partitions are configured in the following manner. + | Partition | Desired Capacity | File System | Mount Point | Device Type | Reformat? | Encrypt? | |-----------|------------------|------------------------|-------------|--------------------|-----------|----------| | /dev/sda1 | 1GiB | EXT4 | /boot | Standard Partition | Yes | No | | /dev/sda2 | 15GiB | EXT4 | / | Standard Partition | Yes | No | - - ![08](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/08.png) -7. Let the installation finish, click the `Finish Installation` button to exit the installer application and then power off the virtualized guest. - ![09](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/09.png) -8. Start a virtual machine where Fedora Workstation was just installed by executing the following command on the host. + + ![08](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/08.png) +7. Let the installation finish, click the `Finish Installation` button to exit the installer application and then power off the virtualized guest. + ![09](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/09.png) +8. Start a virtual machine where Fedora Workstation was just installed by executing the following command on the host. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -59,5 +58,5 @@ order: 4 -drive file=datadrct/fedobios.raw,format=raw \ -accel kvm ``` -9. Set up the Fedora Workstation according to preferences. - ![10](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/10.png) +9. Set up the Fedora Workstation according to preferences. + ![10](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-bios/10.png) diff --git a/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.md b/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.md index 427b1ad1..f4d64952 100644 --- a/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.md +++ b/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-uefi.md @@ -1,22 +1,21 @@ --- -title: Setting up Fedora Workstation VM on QEMU using UEFI -subsection: virtualization -section: tools -order: 5 +title: Setting up Fedora Workstation VM on QEMU using UEFI +subsection: virtualization +order: 5 --- # Setting up Fedora Workstation VM on QEMU using UEFI -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Source OVMF UEFI assets by following the **Fetching OVMF UEFI from the correct source** guide, if not done already. -3. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. +2. Source OVMF UEFI assets by following the **Fetching OVMF UEFI from the correct source** guide, if not done already. +3. Create a virtual disk image of type `16GB` and of format `RAW` in a reference directory `datadrct` by executing the following command. ```console $ qemu-img create -f raw datadrct/fedouefi.raw 16G ``` -4. Start a virtual machine for installing Fedora Workstation on the virtual disk image by executing the following command on the host. +4. Start a virtual machine for installing Fedora Workstation on the virtual disk image by executing the following command on the host. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -28,37 +27,37 @@ order: 5 -bios /usr/share/edk2/ovmf/OVMF_CODE.fd \ -accel kvm ``` - ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/01.png) - ![02](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/02.png) -5. A greeting window would open up, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. - Close the window for now. - ![03](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/03.png) -6. In a new terminal session inside the virtualized guest, execute the following command to confirm UEFI boot. + ![01](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/01.png) + ![02](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/02.png) +5. A greeting window would open up, providing with two options - Either to `Try Fedora` or `Install to Hard Drive`. + Close the window for now. + ![03](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/03.png) +6. In a new terminal session inside the virtualized guest, execute the following command to confirm UEFI boot. ```console $ ls -la /sys/firmware/efi/efivars/ ``` - ![04](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/04.png) -7. Open up the installer application by clicking on the `Install to Hard Drive` icon from the GNOME drawer inside the virtualized guest. - ![05](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/05.png) -8. Pick the language of choice to proceed with the installation on the installer application. - ![06](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/06.png) -9. Configure the installation to liking and then click on `Begin Installation` on the installer application to start. - ![07](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/07.png) - 1. BTRFS partitioning is recommended and the partitioning scheme is configured to be considered as a default. Proceed with the automatic partitioning scheme as illustrated in the following screenshot to apply the recommended partitioning. - ![08](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/08.png) - 2. In case of a requirement of a custom partitioning scheme, toggle the `Custom` radio button under `Storage Configuration` and click on `Done` button to move to the page where custom partitioning scheme can be selected. - ![09](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/09.png) - For the sake of simplicity, the partitions are configured in the following manner. - + ![04](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/04.png) +7. Open up the installer application by clicking on the `Install to Hard Drive` icon from the GNOME drawer inside the virtualized guest. + ![05](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/05.png) +8. Pick the language of choice to proceed with the installation on the installer application. + ![06](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/06.png) +9. Configure the installation to liking and then click on `Begin Installation` on the installer application to start. + ![07](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/07.png) + 1. BTRFS partitioning is recommended and the partitioning scheme is configured to be considered as a default. Proceed with the automatic partitioning scheme as illustrated in the following screenshot to apply the recommended partitioning. + ![08](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/08.png) + 2. In case of a requirement of a custom partitioning scheme, toggle the `Custom` radio button under `Storage Configuration` and click on `Done` button to move to the page where custom partitioning scheme can be selected. + ![09](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/09.png) + For the sake of simplicity, the partitions are configured in the following manner. + | Partition | Desired Capacity | File System | Mount Point | Device Type | Reformat? | Encrypt? | |-----------|------------------|------------------------|-------------|--------------------|-----------|----------| | /dev/sda1 | 1GiB | EFI Standard Partition | /boot/efi | Standard Partition | Yes | No | | /dev/sda2 | 15GiB | EXT4 | / | Standard Partition | Yes | No | - - ![10](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/10.png) -10. Let the installation finish, click the `Finish Installation` button to exit the installer application and then power off the virtualized guest. - ![11](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/11.png) -11. Start a virtual machine where Fedora Workstation was just installed by executing the following command on the host. + + ![10](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/10.png) +10. Let the installation finish, click the `Finish Installation` button to exit the installer application and then power off the virtualized guest. + ![11](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/11.png) +11. Start a virtual machine where Fedora Workstation was just installed by executing the following command on the host. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -69,5 +68,5 @@ order: 5 -bios /usr/share/edk2/ovmf/OVMF_CODE.fd \ -accel kvm ``` -12. Set up the Fedora Workstation according to preferences. - ![12](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/12.png) +12. Set up the Fedora Workstation according to preferences. + ![12](/content/tools/virtualization/images/setting-up-fedora-workstation-vm-on-qemu-using-uefi/12.png) diff --git a/tools/virtualization/setting-up-intrinsic-vnc-server-with-vms.md b/tools/virtualization/setting-up-intrinsic-vnc-server-with-vms.md index 56158580..e81582a3 100644 --- a/tools/virtualization/setting-up-intrinsic-vnc-server-with-vms.md +++ b/tools/virtualization/setting-up-intrinsic-vnc-server-with-vms.md @@ -1,17 +1,16 @@ --- -title: Setting up intrinsic VNC server with VMs -subsection: virtualization -section: tools -order: 6 +title: Setting up intrinsic VNC server with VMs +subsection: virtualization +order: 6 --- # Setting up intrinsic VNC server with VMs -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Start a virtual machine for setting up intrinsic VNC server for the live ISO and there is no need for a virtual disk image here. +2. Start a virtual machine for setting up intrinsic VNC server for the live ISO and there is no need for a virtual disk image here. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -25,10 +24,10 @@ order: 6 ``` ``` QEMU 5.2.0 monitor - type 'help' for more information - (qemu) + (qemu) ``` -3. Visit [https://www.realvnc.com/en/connect/download/viewer/](https://www.realvnc.com/en/connect/download/viewer/) in an internet browser of choice, download and install the VNC viewer application either on the host device or another device in the same network. -4. Head back to the prompt where the VM was started and type in the following command in the `(qemu)` console to change the default VNC password. +3. Visit [https://www.realvnc.com/en/connect/download/viewer/](https://www.realvnc.com/en/connect/download/viewer/) in an internet browser of choice, download and install the VNC viewer application either on the host device or another device in the same network. +4. Head back to the prompt where the VM was started and type in the following command in the `(qemu)` console to change the default VNC password. ``` change vnc password ``` @@ -37,13 +36,13 @@ order: 6 (qemu) change vnc password Password: ******** ``` -5. Switch to the VNC Viewer window and type in `0.0.0.0:5959` from the host device (or `:5959` if accessed from another device in the same network) - `59` from the command referring to the offset from `5900` which is the default VNC port. +5. Switch to the VNC Viewer window and type in `0.0.0.0:5959` from the host device (or `:5959` if accessed from another device in the same network) - `59` from the command referring to the offset from `5900` which is the default VNC port. ![01](/content/tools/virtualization/images/setting-up-intrinsic-vnc-server-with-vms/01.png) -6. A window would appear warning about the nature of the connection being unencrypted. This is fine for a closed network so click on the `Continue` button. +6. A window would appear warning about the nature of the connection being unencrypted. This is fine for a closed network so click on the `Continue` button. ![02](/content/tools/virtualization/images/setting-up-intrinsic-vnc-server-with-vms/02.png) -7. Another window would appear which would ask for password. Enter the password that was set in the step #5 and then click on the `OK` button. +7. Another window would appear which would ask for password. Enter the password that was set in the step #5 and then click on the `OK` button. ![03](/content/tools/virtualization/images/setting-up-intrinsic-vnc-server-with-vms/03.png) -8. Finally a window showing the virtual desktop of the live environment would show up and it can be used to interact with the VM. +8. Finally a window showing the virtual desktop of the live environment would show up and it can be used to interact with the VM. ![04](/content/tools/virtualization/images/setting-up-intrinsic-vnc-server-with-vms/04.png) ## References diff --git a/tools/virtualization/setting-viewport-resolution-using-ovmf-bios.md b/tools/virtualization/setting-viewport-resolution-using-ovmf-bios.md index 326a1a34..9410a3a8 100644 --- a/tools/virtualization/setting-viewport-resolution-using-ovmf-bios.md +++ b/tools/virtualization/setting-viewport-resolution-using-ovmf-bios.md @@ -1,18 +1,17 @@ --- -title: Setting viewport resolution using OVMF BIOS -subsection: virtualization -section: tools -order: 7 +title: Setting viewport resolution using OVMF BIOS +subsection: virtualization +order: 7 --- # Setting viewport resolution using OVMF BIOS -1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. +1. Download the Fedora Workstation ISO file from website and store it in a reference directory `cdromimg`. ``` https://getfedora.org ``` -2. Source OVMF UEFI assets by following the [**Fetching OVMF UEFI from the correct source**](/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.html) guide, if not done already. -3. Start a virtual machine for playing around with setting viewport resolution for the live ISO and there is no need for a virtual disk image here. +2. Source OVMF UEFI assets by following the [**Fetching OVMF UEFI from the correct source**](/tools/virtualization/fetching-ovmf-uefi-from-the-correct-source.html) guide, if not done already. +3. Start a virtual machine for playing around with setting viewport resolution for the live ISO and there is no need for a virtual disk image here. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -23,29 +22,29 @@ order: 7 -cdrom cdromimg/ \ -accel kvm ``` -4. Press `ESC` key when the following screen is visible during the startup to navigate into the OVMF UEFI settings. +4. Press `ESC` key when the following screen is visible during the startup to navigate into the OVMF UEFI settings. ![01](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/01.png) -5. Once inside the OVMF UEFI settings, just use the arrow keys to point at `Continue` and press `ENTER` to resume booting. +5. Once inside the OVMF UEFI settings, just use the arrow keys to point at `Continue` and press `ENTER` to resume booting. ![02](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/02.png) -6. QEMU would now boot into the live environment of Fedora Workstation so use the arrow keys to point at the first option and press `ENTER` to boot up. +6. QEMU would now boot into the live environment of Fedora Workstation so use the arrow keys to point at the first option and press `ENTER` to boot up. ![03](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/03.png) -7. Once the live environment of Fedora Workstation has booted up, open up a terminal instance. +7. Once the live environment of Fedora Workstation has booted up, open up a terminal instance. ![04](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/04.png) -8. Execute the following command to install `xrandr` on the live environment. +8. Execute the following command to install `xrandr` on the live environment. ```console $ sudo dnf install xrandr ``` -9. Once `xrandr` is installed on the live environment, execute it to find a list of supported resolutions and refresh rates for the current renderer. +9. Once `xrandr` is installed on the live environment, execute it to find a list of supported resolutions and refresh rates for the current renderer. ```console $ xrandr ``` ![05](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/05.png) -10. Restart the live environment and press the `ESC` key during the startup to navigate into the OVMF UEFI settings. +10. Restart the live environment and press the `ESC` key during the startup to navigate into the OVMF UEFI settings. ![06](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/06.png) -11. Use the arrow keys to point at `Device Manager`, press `ENTER` and then select the `OVMF Platform Configuration` option. +11. Use the arrow keys to point at `Device Manager`, press `ENTER` and then select the `OVMF Platform Configuration` option. ![07](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/07.png) -12. Observe that the `Preferred Resolution at Next Boot` is `UNSET`. Open up the popup for `Change Preferred Resolution for Next Boot` and select `1280x720`. +12. Observe that the `Preferred Resolution at Next Boot` is `UNSET`. Open up the popup for `Change Preferred Resolution for Next Boot` and select `1280x720`. ![08](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/08.png) -13. Press `F10` key and then press `Y` to confirm saving the configuration. Press `Ctrl` + `Alt` + `Del` to reboot the VM. +13. Press `F10` key and then press `Y` to confirm saving the configuration. Press `Ctrl` + `Alt` + `Del` to reboot the VM. ![09](/content/tools/virtualization/images/setting-viewport-resolution-using-ovmf-bios/09.png) -14. Once the booting into the live environment, the set resolution would be made available to select from the list of all other resolution. +14. Once the booting into the live environment, the set resolution would be made available to select from the list of all other resolution. diff --git a/tools/virtualization/sharing-memory-chunk-as-video-memory-in-qemu.md b/tools/virtualization/sharing-memory-chunk-as-video-memory-in-qemu.md index eed0f968..2c93ea84 100644 --- a/tools/virtualization/sharing-memory-chunk-as-video-memory-in-qemu.md +++ b/tools/virtualization/sharing-memory-chunk-as-video-memory-in-qemu.md @@ -1,13 +1,12 @@ --- -title: Sharing a chunk of memory as video memory in QEMU -subsection: virtualization -section: tools -order: 9 +title: Sharing a chunk of memory as video memory in QEMU +subsection: virtualization +order: 9 --- # Sharing a chunk of memory as video memory in QEMU -1. Continuing on from the end of the guide about [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html), start up the same VM by executing the following command. +1. Continuing on from the end of the guide about [**Setting up Fedora Workstation VM on QEMU using BIOS**](/tools/virtualization/setting-up-fedora-workstation-vm-on-qemu-using-bios.html), start up the same VM by executing the following command. ```console $ qemu-system-x86_64 \ -boot menu=on \ @@ -19,7 +18,7 @@ order: 9 -vga std \ -device VGA,vgamem_mb=512 ``` -2. Execute the following command inside the console of the VM to view the list of the emulated PCI hardware attached. +2. Execute the following command inside the console of the VM to view the list of the emulated PCI hardware attached. ```console $ lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) @@ -29,7 +28,7 @@ order: 9 00:02.0 VGA compatible controller: Device 1234:1111 (rev 02) 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03) ``` -3. Probe into the output of `00:02.0` by executing the following command as it seems to be an emulated VGA controller. +3. Probe into the output of `00:02.0` by executing the following command as it seems to be an emulated VGA controller. ```console $ lspci -v -s 00:02.0 00:02.0 VGA compatible controller: Device 1234:1111 (rev 02) (prog-if 00 [VGA controller]) @@ -41,4 +40,4 @@ order: 9 Kernel driver in use: bochs-drm Kernel modules: bochs_drm ``` -4. There are many providers like `qxl`, `virtio`, `vmware` etc. that can be used in place of `std`. +4. There are many providers like `qxl`, `virtio`, `vmware` etc. that can be used in place of `std`.