elemental-toolkit
elemental-toolkit copied to clipboard
Test orange/blue flavors in x86_64 and arm64
We should at least have a manual test for both flavors+arches to see if they boot from iso/install from iso/boot disk after install to discover and write down any issues that we find.
We are currently pushing the artifacts, and they may as well be broken, so in that case, we should stop pushing them or fix them.
- [ ] Orange x86_64 - boot from iso
- [ ] Orange x86_64 - install from iso
- [ ] Orange x86_64 - boot from hd after install
- [x] Orange arm64 - boot from iso
- [ ] Orange arm64 - install from iso
- [ ] Orange arm64 - boot from hd after install
- [ ] Blue x86_64 - boot from iso
- [ ] Blue x86_64 - install from iso
- [ ] Blue x86_64 - boot from hd after install
- [x] Blue arm64 - boot from iso
- [x] Blue arm64 - install from iso
- [ ] Blue arm64 - boot from hd after install
We support only the green flavor, the other flavors (blue, orange) are published on a best-effort basis, any contribution is welcomed as we don't actively tests them.
My feeling about adding automated tests is that we are going book extra time with CI for something that is not really worth it, and potentially can also block us (many parallel jobs)...
No no, dont get me wrong @mudler , Im not talknig about automated tests here. Just a good old fashioned couple of hours running the isos in vms to see that the basic functionality works at least. So we are aware that the basics at least work and what is published has a baseline of "yes it runs from iso and you can installl it to hd and boot from there. Nothing else is tested"
So just the basics. Otherwise, for me it doesnt even warrant the build time in the CI to publish those artifacts without knowing the rough state of them.
Orange arm64 iso (build from master, git hash c8d6ad5f7f7f9e3eb9d3e552982e0ce507ef6fef):
Doesnt even boot from iso, stuck on booting with no info on whats going on
[ 48.276959] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 48.277836] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
[ 48.317016] scsi 0:0:0:0: CD-ROM QEMU QEMU CD-ROM 2.5+ PQ: 0 ANSI: 5
[ 48.328659] xhci_hcd 0000:02:00.0: hcc params 0x00087001 hci version 0x100 quirks 0x0000000000000010
[ 48.360575] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 48.361896] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 48.362307] usb usb1: Product: xHCI Host Controller
[ 48.362507] usb usb1: Manufacturer: Linux 5.8.0-63-generic xhci-hcd
[ 48.362859] usb usb1: SerialNumber: 0000:02:00.0
[ 48.373298] hub 1-0:1.0: USB hub found
[ 48.374929] hub 1-0:1.0: 15 ports detected
[ 48.387029] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 48.387368] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 48.387919] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 48.389643] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 48.390954] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[ 48.394091] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 48.394434] usb usb2: Product: xHCI Host Controller
[ 48.394655] usb usb2: Manufacturer: Linux 5.8.0-63-generic xhci-hcd
[ 48.394885] usb usb2: SerialNumber: 0000:02:00.0
[ 48.397306] hub 2-0:1.0: USB hub found
[ 48.398170] hub 2-0:1.0: 15 ports detected
[ 48.417351] virtio_blk virtio3: [vda] 314572800 512-byte logical blocks (161 GB/150 GiB)
[ 48.417945] vda: detected capacity change from 0 to 161061273600
[ 48.758226] sr 0:0:0:0: Power-on or device reset occurred
[ 48.760815] sr 0:0:0:0: [sr0] scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray
[ 48.761526] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 48.771219] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 49.681110] virtio_net virtio0 enp1s0: renamed from eth0
[ 60.834349] overlayfs: "xino" feature enabled using 2 upper inode bits.
[ 541.938569] hrtimer: interrupt took 212218784 ns
Blue arm64 iso (build from master, git hash c8d6ad5):
-
[X] Blue arm64 - boot from iso
-
Seems to boot normally no issues that I could see
-
[x] Blue arm64 - install from iso
-
Cannot install grub2 due to
Installing GRUB..
grub2-install: error: this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot.
Probably need to install the shim package so it installs the shim which is supposed to be signed.
Looks like for fedora efi we cannot use grub-install we have to install the shim packages and copy those: https://fedoraproject.org/wiki/GRUB_2