Bug 1222874 - Feedback to openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2
Summary: Feedback to openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Installation (show other bugs)
Version: Current
Hardware: x86-64 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-16 07:55 UTC by Martin Abele
Modified: 2024-04-16 07:56 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Abele 2024-04-16 07:55:29 UTC
User-Agent:       Mozilla/5.0 (Windows NT 10.0; rv:124.0) Gecko/20100101 Firefox/124.0
Build Identifier: 

I installed the Aeon prototype in a Gnome Box VM. Here is my feedback...

Installer
- On the first try I didn't increase the disk size with 'qemu-img resize', I thought that selecting 25GB in Gnome Boxes would d the trick
  - The installation stopped at a black screen on first boot
  - On second boot, the installer was loaded I the installation went through
  - Firefox installation failed due to lack of disk space
  - That's when I checked the disk and realized it was only around 7 GB
- On second try I used 'qemu-img resize' before adding the VM to Gnome Boxes
  - The installation started on first boot and went through without problem
  - Firefox was installed successfully
  - No issues or hick-ups
  
Impressions
- Partitioning seems unusual: 2MB BIOS boot, 3.9GB /boot/efi
- Podman and distrobox are not installed
- Personally I would prefer to have the following packages installed: zsh nano (and starship, but that's probably too specific)
- No Grub: how can one boot a previous snapshot in case something breaks, e.g. caused by an update? Automatic rollback does not always work in my experience...

Log entries that stud out
- Secure boot disabled
- X.509 certs loaded but no TPM chip found     (probably due to VM configuration)
- Some GPT errors found on disk
- systemd-gpt-auto-generator[776]: Failed to create symlink "/run/systemd/generator.late/local-fs.target.wants/systemd-remount-fs.service": No such file or directory
  (sd-exec-[768]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.
- bootctl[959]: ! Mount point '/boot/efi' which backs the random seed file is world accessible, which is a security hole! !
  bootctl[959]: ! Random seed file '/boot/efi/loader/.#bootctlrandom-seed1024526e3cc2fae4' is world accessible, which is a security hole! !


Reproducible: Always

Steps to Reproduce:
Installation
- Download image from https://download.opensuse.org/repositories/devel:/microos:/aeon:/installer/aeon/openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2.raw.xz
- $> xz -d openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2.raw.xz
- $> qemu-img convert openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2.raw -O qcow2 openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2.qcow2
- $> qemu-img resize openSUSE-Aeon-Installer.x86_64-0.1.0-Build3.2.qcow2 +20G
- Open Gnome Boxes and add a new VM using 'Install from file', 6 GB RAM
- Run the VM



I will probably do some more testing later
Comment 1 Richard Brown 2024-04-16 07:56:53 UTC
The "Aeon Installer" is not the image I posted for testing. Closing INVALID.

Please test the image I asked for people to test.