Part 2 of update to F43

This commit is contained in:
Peter Boy 2025-12-04 00:16:53 +01:00
commit f7b4ea414f
8 changed files with 38 additions and 15 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 80 KiB

After

Width:  |  Height:  |  Size: 68 KiB

Before After
Before After

Binary file not shown.

Before

Width:  |  Height:  |  Size: 72 KiB

After

Width:  |  Height:  |  Size: 72 KiB

Before After
Before After

Binary file not shown.

Before

Width:  |  Height:  |  Size: 71 KiB

After

Width:  |  Height:  |  Size: 132 KiB

Before After
Before After

Binary file not shown.

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 117 KiB

Before After
Before After

Binary file not shown.

After

Width:  |  Height:  |  Size: 68 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

View file

@ -125,8 +125,8 @@ A lot of messages then scroll across the screen. If the network interface doesn'
[source,]
----
Starting install...
Running text console command: virsh --connect qemu:///system console vm1-test
Connected to domain 'vm1-test'
Running text console command: virsh --connect qemu:///system console rbox03
Connected to domain 'rbox03'
Escape character is ^] (Ctrl + ])
...
[ OK ] Reached target User and Group Name Lookups.
@ -155,34 +155,57 @@ We continue with this form in the step after describing the Cockpit way of insta
=== Alternative 2: Import comfortably via Cockpit
1. Open Cockpit on your __host system__. The import expects the virtual hard disk at the final location. Therefore, copy the prepared customized disk image into the disk image pool, as you did in alternative 1 (CLI import). Select _Terminal_ in the left navigation column to perform this step.
1. Open Cockpit on your __host system__. The import expects the virtual hard disk at the final location. Therefore, select terminal at the bottom of the left navigation column and copy the prepared customized disk image into the disk image pool, as you did in alternative 1 (CLI import).
+
image::virtualization/diskimg-fedoraserver-01.png[Cockpit initial terminal]
.Cockpit initial terminal
image::virtualization/diskimg-fedoraserver-01.png[]
2. Select "__Virtual Machines__" in the left navigation column and select "__Import VM__" at the right top of the central window area.
+
image::virtualization/diskimg-fedoraserver-02.png[Cockpit import screen]
.Cockpit import screen
image::virtualization/diskimg-fedoraserver-02.png[]
+
Fill in the input fields as appropriate and leave "__Connection__" on "__System__" as preselected.
3. If the VM to be created should only have one network interface connected to the internal libvirt bridge (virbr0), select __Import and run__. In __all other cases__, select _Import and edit_ to set up the correct network connection before the first boot.
+
.Cockpit new virtual machine overview screen
image::virtualization/diskimg-fedoraserver-03.png[]
4. Adjust the network connection setup. The screen changes and the VM overview page. Scroll down to __Network interfaces__. You see one Interface with Source default, i.e. virbr0. In order to easily manage the default route, this interface - the first one created - should connect to the public external network. Select _Edit_ to modify the Source.
4. Scroll down to get to the network and devices section
+
image::virtualization/diskimg-fedoraserver-03.png[Network re-configuration]
.Network and devices screen
image::virtualization/diskimg-fedoraserver-04.png[]
+
Modify Interface type to Direct attachment and Source to the physical host external interface. Leave Model and MAC address unchanged! Save brings you back to the Overview screen.
In the network section, you see one Interface with Source default, i.e. virbr0. In order to easily manage the default route, this interface - the first one created - should connect to the public external network. Therefore, we start with changing this interface into the public one. Important: To keep the intended order of interfaces, do nothing else at tis point as to edit this interface!
5. In the row "Network interfaces" select Add network interface on the right side.
5. Select the _Edit_ button to adjust the network connection setup.
+
image::virtualization/diskimg-fedoraserver-04.png[Add network interface]
.Network re-configuration screen
image::virtualization/diskimg-fedoraserver-05.png[]
+
In the window that opens, the internal virtual network is already selected and correctly configured. Select Add to add the interface.
Modify Interface type to Direct attachment and Source to the physical host external interface (enp1s0) and select bridge mode. Leave Model and MAC address unchanged!
+
Finally, select __Save__. You will return to Network and devices.
6. Scroll up and select _Run_ In the console window you will see the creation and startup of the virtual machine. Expand the console window.
6. In the row "Network interfaces" select _Add network interface_ on the right side.
+
image::virtualization/diskimg-fedoraserver-05.png[Final User Configuration]
.Add network interface
image::virtualization/diskimg-fedoraserver-06.png[]
+
The form opening already has Network Type selected and correctly configured. Leave all settings unchanged and close the form with the Add button.
7. The network and devices part of the screen now contains 2 network interfaces in the correct order.
+
.Two network interfaces configured
image::virtualization/diskimg-fedoraserver-07.png[]
+
8. Scroll up and select _Start_ in the middle of the central window. In the console window you will see the creation and startup of the virtual machine. Expand the console window.
+
.Minimal initial configuration form
image::virtualization/diskimg-fedoraserver-08.png[]
+
Finally, the screen displays the same configuration menu as with a CLI setup. Continue with the minimal initial configuration.
@ -278,8 +301,8 @@ Another "c" continues with the execution of the entire configuration process. Th
Starting Record Runlevel Change in UTMP...
[ OK ] Finished Record Runlevel Change in UTMP.
Fedora Linux 41 (Server Edition)
Kernel 6.11.4-301.fc41.x86_64 on an x86_64 (ttyS0)
Fedora Linux 43 (Server Edition)
Kernel 6.17.1-300.fc43.x86_64 on an x86_64 (ttyS0)
Web console: https://localhost:9090/ or https://192.168.158.155:9090/