Agama Unattended installation openSUSE Tumbleweed via profile.json on remote host (bare metal )

Unattended openSUSE Tumbleweed deployments on bare metal are critical because they eliminate manual intervention, ensure configuration consistency, and drastically reduce provisioning time across physical infrastructure. While Tumbleweed is a rolling-release distribution - traditionally favored by developers and power users on personal machines - deploying it at scale on bare metal using unattended methods providing by Agama Installer serves several vital engineering and operational purposes:

• Elimination of Human Error: Manual OS installations introduce variances in disk partitioning, package selection, and initial network setups. Unattended installations use a version-controlled configuration file (like profile.json) to guarantee
that server is an exact clone of the intended specification.
• Declarative Infrastructure: Treating your bare-metal OS installation as code aligns your physical infrastructure with modern DevOps practices, making state drift easier to prevent and audit. 

 After booting via USB pen on target box,right after you see the first screen  for selection of desired OS . You are supposed to press CTRL+ALT+F3 without any other input into the first page of Agama Web UI. You would see in terminal  IP-TARGET of target host and root password. From another box launch your browser to https://IP-TARGET. This step will bring you to Agama WEB UI and prompt for root "password".

After entering WEB UI environment select OS (Tumbleweed for instance) manage  as usual until creating root account. You should have SSH trusted pair already generated prior to configuring
root's credentials on target box. I've selected password and SSH public key.
Cut and paste SSH Public key into corresponding field on Agama
Configuration been created via Anaconda Web UI will be available via clicking small circle in right upper corner of the page. When you finished disk layout config, DE selection, packages selection, user's and root credentials along with ssh public key for root you may copy and paste your configuration into ~/Downloads/profile.json. 

You may also download file system_name.json and copy to profile.json. Next step is just cut and paste ~/Downloads/profile.json into /tmp/profile.json inside Agama Live Instance via open by root ssh session with Live Instance on target box

CTRL+ALT+F3 has already created Live Agama instance on target host . Live Agama instance was created with sshd service already up and running. SSH to target host via known temp-password for root. After logging into Agama Live instance on target host you will appear on prompt agama~#

You are supposed to issue from agama:~# prompt following commands :

agama:~ # agama config load /tmp/profile.json
Ready to start the installation.
agama:~ # agama install 

The expected result is running Tumbleweed deployment on target box, actually, in Agama Live instance environment. (*)

Speed of downloading 4894 packages would be pretty high except  several packages like kernel-default and final one related to plasma setup on tumbleweed.

When done you should see a message in terminal 

agama:~ # agama install
The installation finished successfully.

Next go ahead and reboot target box 

agama:~ # systemctl reboot.

Broken SDDM login prompt may be fixed remotely via root login using injected ssh-public-key been written into profile.json   

# systemctl disable sddm.service --force
# systemctl set-default multi-user.target
# mkdir -p /etc/systemd/system/getty@tty1.service.d
# nano /etc/systemd/system/getty@tty1.service.d/override.conf
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin user1 --noclear %I $TERM
CTRL+O; CTRL+X

# su - user1
======================
$ nano ~/.bash_profile
======================
# Source the user1's primary bash configuration if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi
# Automatically launch KDE Plasma Wayland if logging in on TTY1
if [ -z "${DISPLAY}" ] && [ "${XDG_VTNR}" -eq 1 ]; then
    exec /usr/bin/startplasma-wayland
fi

Final configuration on openSUSE Tumbleweed instance been installed on target box in unattended mode using profile.json been generated in Agama Web UI environment on remote workstation and injecting profile.json into Agama Live Instance created by pressing CTRL+ALT+F3 on target host almost silently with no additional information provided to you 

boris@localhost:~> fastfetch
         ,...,                                 boris@localhost
    .,:lloooooc;.                              ---------------
  ,ool'     oo,;oo:                            OS: openSUSE Tumbleweed x86_64
.lo'        oo.   oo:                          Kernel: Linux 7.3.1-1-default
.oo.         oo.    oo:                         Uptime: 1 hour, 50 mins
:ol          oo.    'oo                         Packages: 2464 (rpm)
:oo         .oo.    .oo.                        Shell: bash 5.3.20
.oooooooooooooo.    .oo.                        Display (E215A): 1920x1080 in 21", 60 Hz [External]
;oo.               .oo.                        Desktop Environment: KDE Plasma 6.8.2
 'oo,              .oo.                        Window Manager: KWin (Wayland)
   "ooc,',,,,,,,,,,:ooc,,,,,,,,,,,             WM Theme: Breeze
      ':cooooooooooooooooooooooooool;.         Theme: Breeze (Classic) [Qt], Breeze [GTK2/3]
                   .oo.             .oo;       Icons: breeze [Qt], breeze [GTK2/3/4]
                   .oo.               .oo.     Font: Noto Sans (12pt) [Qt], Noto Sans (12pt) [GTK2/3/4]
                   .oo.    'oooooooooo:ooo.    Cursor: breeze (24px)
                   .oo.    'oo.         col    Terminal: konsole 26.8.3
                   .oo'    'oo          col    Terminal Font: Hack (17pt)
                    coo    'oo          oo'    CPU: Intel(R) Xeon(R) E5-2690 v3 (24) @ 3.50 GHz
                     coc   'oo        .lo,     GPU: AMD Radeon HD 6450/7450/8450 / R5 230 OEM
                      `oo, 'oo      .:oo       Memory: 2.71 GiB / 31.24 GiB (9%)
                        'ooooc,, ,:lol         Swap: Disabled
                           `''"clc"'           Disk (/): 7.01 GiB / 128.00 GiB (5%) - btrfs
                                               Disk (/opt): 4.93 GiB / 255.88 GiB (2%) - xfs
                                               Local IP (bridge0): 192.168.0.57/24
                                               Locale: en_US.UTF-8
                                                
                                                                        
                                                                        
boris@localhost:~> df -Th
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sda3      btrfs     128G  7.1G  120G   6% /
devtmpfs       devtmpfs   16G     0   16G   0% /dev
tmpfs          tmpfs      16G     0   16G   0% /dev/shm
efivarfs       efivarfs  256K  111K  141K  44% /sys/firmware/efi/efivars
tmpfs          tmpfs     6.3G  2.0M  6.3G   1% /run
none           tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs      16G  8.0K   16G   1% /tmp
/dev/sda3      btrfs     128G  7.1G  120G   6% /.snapshots
/dev/sda3      btrfs     128G  7.1G  120G   6% /usr/local
/dev/sda3      btrfs     128G  7.1G  120G   6% /srv
/dev/sda3      btrfs     128G  7.1G  120G   6% /var
/dev/sda3      btrfs     128G  7.1G  120G   6% /home
/dev/sda3      btrfs     128G  7.1G  120G   6% /root
/dev/sda4      xfs       256G  5.0G  251G   2% /opt
/dev/sda2      ext4      2.3G  107M  2.0G   5% /boot
/dev/sda1      vfat      953M  101M  852M  11% /boot/efi
none           tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     3.2G   76K  3.2G   1% /run/user/1000
boris@localhost:~> lsblk -f
NAME        FSTYPE  FSVER            LABEL                   UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                               
├─sda1      vfat    FAT32                                    B4E0-5428                             851.4M    11% /boot/efi
├─sda2      ext4    1.0                                      f2aa55cd-cdcd-4dbc-a5bb-a5d30380c474      2G     5% /boot
├─sda3      btrfs                                            1c6c08f5-3d5c-4d00-b5d0-15779f5a5ea8                /etc/libvirt/qemu
│                                                                                                                /root
│                                                                                                                /home
│                                                                                                                /var
│                                                                                                                /srv
│                                                                                                                /usr/local
│                                                                                                                /.snapshots
│                                                                                                                /
└─sda4      xfs                                              d81d8fb0-1d1e-429f-bdea-d5c72ebd3606  250.9G     2% /opt

boris@localhost:~> findmnt -t btrfs
TARGET              SOURCE                              FSTYPE OPTIONS
/                   /dev/sda3[/@/.snapshots/1/snapshot] btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=263,subvol=/@/.snapshots/1/
├─/home             /dev/sda3[/@/home]                  btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=261,subvol=/@/home
├─/root             /dev/sda3[/@/root]                  btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=260,subvol=/@/root
├─/.snapshots       /dev/sda3[/@/.snapshots]            btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=262,subvol=/@/.snapshots
├─/srv              /dev/sda3[/@/srv]                   btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=259,subvol=/@/srv
├─/usr/local        /dev/sda3[/@/usr/local]             btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=258,subvol=/@/usr/local
├─/var              /dev/sda3[/@/var]                   btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=257,subvol=/@/var
└─/etc/libvirt/qemu /dev/sda3[/@qemu]                   btrfs  rw,relatime,seclabel,space_cache=v2,subvolid=270,subvol=/@qemu

   boris@localhost:~> lsblk -d -o NAME,VENDOR,MODEL,SIZE,SERIAL|grep 596
sda     ATA      WDC WD6401AALS-00E3A0           596.2G WD-WCATR4549247

====================== 

Batch mode version (*)

====================== 

#!/bin/bash
# # openSUSE Tumbleweed Minimal Remote Provisioner
# Run from Workstation (192.168.0.17) targeting Host (192.168.0.88)
# 

set -e

TARGET_IP="192.168.0.88"
TEMP_PASSWORD="p646kPZy"
LOCAL_PROFILE="/home/boris/Downloads/profile.json"

# Export password for sshpass to run hands-off
export SSHPASS=$TEMP_PASSWORD

echo "1. Flushing target host key signature..."
ssh-keygen -f "$HOME/.ssh/known_hosts" -R "$TARGET_IP" 2>/dev/null || true

echo "2. Copying profile.json to target RAM filesystem..."
sshpass -e scp -o StrictHostKeyChecking=no "$LOCAL_PROFILE" root@$TARGET_IP:/tmp/profile.json

echo "3. Ingesting profile and executing installation on target..."
sshpass -e ssh -o StrictHostKeyChecking=no root@$TARGET_IP bash << 'EOF'
  set -e
  agama config load /tmp/profile.json
  agama install
  systemctl reboot
EOF

echo "Deployment triggered successfully. Target box is rebooting."
 

REFERENCES

(*) Assisted by Google AI 

Agama Unattended installation via profile.json of Tumbleweed's KVM Guests

 Tumbleweed updates continuously, manual interactive installations frequently break due to rapid package, installer (Agama), or kernel shifts. Unattended automation ensures predictable, reproducible, and verifiable states for disaster recovery and testing.

• Mitigating Rolling-Release Fluctuation: Tumbleweed moves extremely fast. An unattended deployment via structured templates (profile.json) ensures that the initial bootstrap bypasses manual package selection errors and unpredictable installer UI changes.
• Disaster Recovery Validation Loop: For continuous integration or automated DR testing, environments must be torn down and rebuilt from scratch. Unattended installation scripts (using virt-install) allow you to programmatically verify that guest configurations, volume management definitions, and baseline application profiles work under the latest upstream packages without human intervention. (*)

=================================================================

The sample of profile.json file ( generated via Agama Web UI )

=================================================================

boris@localhost:~/Downloads> cat profile.json
{
 "product": {
   "id": "Tumbleweed"
 },
 "software": {
   "patterns": {
     "add": [
       "kvm_tools",
       "kde",
       "cockpit",
       "selinux"
     ],
     "remove": [
       "office"
     ]
   }
 },
 "storage": {
   "boot": {
     "configure": true
   },
   "drives": [
     {
       "partitions": [
         {
           "filesystem": {
             "mountOptions": [],
             "path": "/boot/efi",
             "reuseIfPossible": false,
             "type": "vfat"
           },
           "id": "esp",
           "size": {
             "max": 1000000000,
             "min": 1000000000
           }
         },
         {
           "filesystem": {
             "mountOptions": [],
             "path": "/boot",
             "reuseIfPossible": false,
             "type": "ext4"
           },
           "size": {
             "max": 2500000000,
             "min": 2500000000
           }
         },
         {
           "filesystem": {
             "mountOptions": [],
             "path": "/",
             "reuseIfPossible": false,
             "type": {
               "btrfs": {
                 "snapshots": true
               }
             }
           },
           "size": {
             "max": 55000000000,
             "min": 55000000000
           }
         },
         {
           "filesystem": {
             "mountOptions": [],
             "path": "/opt",
             "reuseIfPossible": false,
             "type": "xfs"
           },
           "size": {
             "max": 67000000000,
             "min": 67000000000
           }
         },
         {
           "delete": true,
           "search": {
             "ifNotFound": "skip"
           }
         }
       ],
       "search": {
         "condition": {
           "name": "/dev/vda"
         },
         "ifNotFound": "error"
       }
     }
   ],
   "mdRaids": [],
   "volumeGroups": []
 },
 "user": {
   "fullName": "boris",
   "password": "***********",
   "hashedPassword": false,
   "userName": "boris",
   "sshPublicKeys": []
 },
 "root": {
   "password": "************",
   "hashedPassword": false,
   "sshPublicKeys": [
     "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK+XwCy1t95wJD0eErIpkeeXc9qGN/rwX1hAkEKJoOGQ name@example.com"
   ]
 }

Python3 -m http.server 8080 --bind 192.168.0.23 starts a basic local web server that shares the files in your current working directory over the network. Port 8080 been opened requires some additional tuning (*)

$ sudo firewall-cmd --zone=trusted --remove-interface=bridge0 --permanent
OR if you added the port explicitly to a public/home zone:
$ sudo firewall-cmd --zone=public --remove-port=8080/tcp --permanent
$ sudo firewall-cmd --reload

boris@localhost:~/Downloads> python3 -m http.server 8080 --bind 192.168.0.23  Serving HTTP on 192.168.0.23 port 8080 (http://192.168.0.23:8080/) ...
192.168.0.51 - - [09/Nov/2026 08:25:19] "GET /profile.json HTTP/1.1" 200 -

Virt-install command line for unattended deploying Tumbleweed KVM Guest (*)
 #!/bin/bash
virt-install \
  --name tw-unattended-Guest03 \
  --memory 10000 \
  --vcpus 4 \
  --osinfo opensusetumbleweed \
  --disk pool=default,size=125,bus=virtio,format=qcow2 \
  --network bridge=bridge0,model=virtio \
  --graphics vnc,listen=127.0.0.1 \
  --location /home/boris/Downloads/agama-installer.x86_64-25.0.0-openSUSE-Build8.23.iso,kernel=boot/x86_64/loader/linux,initrd=boot/x86_64/loader/initrd \
  --extra-args "inst.auto=http://192.168.0.23:8080/profile.json"

Virt-install Guest startup and Guest's Console

localhost:~ # ./virtInst03.sh
WARNING  No display detected. Not running virt-viewer.
WARNING  No console to launch for the guest, defaulting to --wait -1

Starting install...
Retrieving 'linux'                        |  17 MB  00:00:00
Retrieving 'initrd'                       | 128 MB  00:00:00
Allocating 'tw-unattended-Guest03.qcow2'   |         00:00:00
Creating domain...                                                                                             
Domain is still running. Installation may be in progress.
Waiting for the installation to complete.
Domain has shutdown. Continuing.
Domain creation completed.
Restarting guest. 

 

(*) Enabling audio via switching to Spice Console

Inside VM issue

#1. Access the guest OS command line to spin up the virtualization channels
$ sudo systemctl start qemu-guest-agent
$ sudo systemctl start spice-vdagentd
# 2. Verify the active background execution status of both services
$ sudo systemctl status qemu-guest-agent spice-vdagentd 

Shutdown VM and update XML-profile as follows 

$ sudo EDITOR=nano virsh edit tw-unattended-guest01 

 <sound model='ich9'>
  <audio id='1'/>
  <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</sound>
<audio id='1' type='spice'/>

Detached VNC Console created using Cockpit Web interface

REFERENCES

(*) Assisted by Google AI 

 

Online setup openSUSE Leap 16.1 on bare metal and tuning correct resolution for HDMI Monitor

What is Agama's SSH Injection Advantage: By injecting public key into Agama during the network deployment phase, the very first boot of the newly installed operating system will have the OpenSSH daemon (sshd) active and your authorized keys populated.This gives you a guaranteed SSH hook into the target host. You don't have to look at the unreadable HDMI screen to execute the configuration script below you can run it smoothly from a remote machine, cleanly stripping away the problematic
SDDM prompt and tailoring the Wayland desktop profile securely. 

Online setup openSUSE Leap 16.1 on bare metal may be performed via Leap-16.1-online-installer-x86_64.install.iso with same Web UI as Agama installer. Installation phase is almost the same as described in Install Tumbleweed via Agama Installer and automated detection of HDMI ports   However , on Leap 16.1 the block marked in blue is critical on Leap 16.1

"You should have SSH trusted pair already generated prior to configuring root's credentials on target box. I've selected password and SSH public key. Cut and paste SSH Public key into corresponding field on Agama Web UI. Save and start installation" which would be initiated remotely from your workstation.
Agama follows standard transactional schema when preparing desired disk layout, selection of DE, user's and root's credentials until you press "Install".  In particular user1 credentials were also injected into Agama Web UI before installation started.

Upon system reboot instead of struggling with poor quality SDDM login you better issue from host initiated Agama Web UI and having ssh trusted connection to target box (*) :

# systemctl disable sddm.service --force
# systemctl set-default multi-user.target
# mkdir -p /etc/systemd/system/getty@tty1.service.d
# nano /etc/systemd/system/getty@tty1.service.d/override.conf
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin user1 --noclear %I $TERM
CTRL+O; CTRL+X

# su - user1 

======================
$ nano ~/.bash_profile
====================== 

# Source the user1's primary bash configuration if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi
# Automatically launch KDE Plasma Wayland if logging in on TTY1
if [ -z "${DISPLAY}" ] && [ "${XDG_VTNR}" -eq 1 ]; then
    exec /usr/bin/startplasma-wayland
fi

Verification step

user1@localhost:~> systemctl cat getty@tty1.service | grep "autologin"
ExecStart=-/sbin/agetty --autologin user1 --noclear %I $TERM

Upon next reboot of target box you would avoid SDDM login prompt and automatically start KDE Plasma 6.6.4 session.

I also have to notice that dracut hook like this 

$ echo 'hostonly="no"' | sudo tee /etc/dracut.conf.d/00-generic.conf

$ sudo dracut -f --regenerate-all 

won't help you under kernel 6.12 ( vs 7.2-7.3 kernels on Tumbleweed) 

  

 References

(*) Assisted by Google AI 

Simulation Agama Web UI in Virtual environment as KVM Guest (Assisted by Google AI)

 Start deploying your VM via Virtual-manager. When Spice console would pop up just press the button "Send key" from horizontal menu and select CTL+ALT+F3.  Spice console becomes a text terminal providing you IP-ADDRESS of your KVM guest and root password. Launch browser of KVM Host machine to IP-ADDRESS of your Agama VM .  This action will bring you to Agama Web UI and you will be prompted for root password, which may be picked up from text terminal. Log into Agama Web UI running on your Host machine and responsible for deployment selected Suse flavor on KVM Guest. 

After entering WEB UI environment select OS (Tumbleweed for instance) manage  as usual until creating root account. You should have SSH trusted pair already generated prior to configuring root's credentials on VM. I've selected password and SSH public key. Cut and paste SSH Public key into corresponding field on Agama Web UI. Save and start installation which was initiated via KVM host on KVM guest.
Agama follows standard transactional schema when preparing desired disk layout, selection of DE, user's and root's credentials until you press "Install".

Upon reboot of VM with installed tumbleweed instance Agama installer will bring you to text terminal with login prompt for user1 (for instance).

Now switch to root's terminal of Host machine and connect to VM via trusted ssh connection. Inside VM proceed as follows (actually same action may be undertaken on bare metal from the host completed Agama Web UI which was responsible for deploying Suse flavor on target host )  :

# systemctl disable sddm.service --force
# systemctl set-default multi-user.target
# mkdir -p /etc/systemd/system/getty@tty1.service.d
# nano /etc/systemd/system/getty@tty1.service.d/override.conf
Input
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin user1 --noclear %I $TERM
CTRL+O; CTRL+X

# su - user1 

======================
$ nano ~/.bash_profile
====================== 

# Source the user1's primary bash configuration if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi
# Automatically launch KDE Plasma Wayland if logging in on TTY1
if [ -z "${DISPLAY}" ] && [ "${XDG_VTNR}" -eq 1 ]; then
    exec /usr/bin/startplasma-wayland
fi

Verification step

user1@localhost:~> systemctl cat getty@tty1.service | grep "autologin"
ExecStart=-/sbin/agetty --autologin user1 --noclear %I $TERM

You are all set .
Now reboot you VM . You will be brought right into
KDE Plasma 6.8.2  running on your VM (KVM Guest )

Install Tumbleweed via Agama Installer and automated detection of HDMI ports (bare metal)

UPDATE as of 11/04/26  ( Google AI ) 

Auto login to KDE Plasma 6.8.2 on Tumbleweed

sudo systemctl disable sddm.service --force
sudo systemctl set-default multi-user.target
sudo mkdir -p /etc/systemd/system/getty@tty1.service.d
sudo nano /etc/systemd/system/getty@tty1.service.d/override.conf
Input
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin boris --noclear %I $TERM
==================
nano ~/.bash_profile
==================

# Source the user's primary bash configuration if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi
# Automatically launch KDE Plasma Wayland if logging in on TTY1
if [ -z "${DISPLAY}" ] && [ "${XDG_VTNR}" -eq 1 ]; then
    exec /usr/bin/startplasma-wayland
fi

Verification step

boris@localhost:~> systemctl cat getty@tty1.service | grep "autologin"
ExecStart=-/sbin/agetty --autologin boris --noclear %I $TERM

System reboot

END UPDATE

UPDATE as of 11/03/26  

Reproduced with no issues on SATA SSD ( the same Intel Haswell Xeon box ).  I have to notice that Agama installer in phase of deployment packages on target drive demonstrates extremely high speed. Thin XFS LVM  Provisioning and Libvirt hooks implementation may be done only in post installation phase via CLI. 

END UPDATE 

 After booting via USB pen on target box,right after you see the first screen  
for selection of desired OS . You are supposed to press CTRL+ALT+F3 without any other input into the first page of Agama Web UI

You would see in terminal  IP-TARGET of target host and root password.

From another box ( in my case no IP:443 ) launch your browser to https://IP-TARGET. 
This step will bring you to Agama WEB UI and prompt for root "password". 
After entering WEB UI environment select OS (Tumbleweed for instance)
manage  as usual until creating root account. 
You should have SSH trusted pair already generated prior to configuring
root's credentials on target box. I've selected password and SSH public key. 

Cut and paste SSH Public key into corresponding field on Agama Web UI. 
Save and start installation which was initiated remotely from your workstation.

Agama follows standard transactional schema when preparing desired disk layout, 
selection of DE, user's and root's credentials until you press "Install".

Upon reboot installed tumbleweed instance would properly detect HDMI port 
and Monitor of target box. Booting up brought me to text console 
with resolution 1920x1080. After logging into text mode terminal 
I've just issued /usr/bin/startplasma-wayland and get into 
KDE Plasma 6.8.2  environment. I believe that slow WD 596 GB HDD,
as the only one empty drive was just too slow to bring up Plasma itself.

In my case I was ready to log into target box via SSH and run:
$ echo 'hostonly="no"' | sudo tee /etc/dracut.conf.d/00-generic.conf

  If you want a small ramdisk but want to force legacy drivers to include anyway
  
$ echo 'add_drivers+=" nouveau amdgpu radeon i915 "'| \
sudo tee /etc/dracut.conf.d/00-generic.conf
$ sudo cat /etc/dracut.conf.d/00-generic.conf
$ sudo dracut -f --regenerate-all

to rebuild initrd-7.3.0-1-default  with required legacy drivers as after YaST installation.
But resolution of HDMI Monitor/port were already detected by Agama Installer

boris@localhost:~> df -Th
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sda3      btrfs     140G  7.1G  132G   6% /
devtmpfs       devtmpfs   16G     0   16G   0% /dev
tmpfs          tmpfs      16G     0   16G   0% /dev/shm
efivarfs       efivarfs  256K   94K  158K  38% /sys/firmware/efi/efivars
tmpfs          tmpfs     6.3G  2.0M  6.3G   1% /run
none           tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs          tmpfs      16G  8.0K   16G   1% /tmp
/dev/sda3      btrfs     140G  7.1G  132G   6% /.snapshots
/dev/sda3      btrfs     140G  7.1G  132G   6% /srv
/dev/sda3      btrfs     140G  7.1G  132G   6% /home
/dev/sda3      btrfs     140G  7.1G  132G   6% /usr/local
/dev/sda3      btrfs     140G  7.1G  132G   6% /var
/dev/sda3      btrfs     140G  7.1G  132G   6% /root
/dev/sda4      xfs       233G  4.5G  229G   2% /opt
/dev/sda2      ext4      1.8G  105M  1.6G   7% /boot
/dev/sda1      vfat      477M  100M  378M  21% /boot/efi
none           tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     3.2G   72K  3.2G   1% /run/user/1000