Hi all,
currently I'm trying to tailor a solution to make testimage.bbclass use
wic images with EFI bootloader.
As the code internally is using runqemu, adding the wic and ovmf options
wasn't that hard, but now
it seems to be stuck in the bootloader
That's the log:
[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[2J[01;01H[=3h[2J[01;01H[0m[37m[40m[2J[01;01H[01;01HUEFI
Interactive Shell v2.2
EDK II
UEFI v2.60 (EDK II, 0x00010000)
[1m[33m[40mMapping table[0m[37m[40m
[1m[33m[40m FS0:[0m[37m[40m
[1m[37m[40mAlias(s):[0m[37m[40mHD1a0b:;BLK3:
PciRoot(0x0)/Pci(0x6,0x0)/Scsi(0x0,0x0)/HD(1,GPT,3B615D71-1C90-43E7-8B1E-50B8684C27A9,0x800,0xBD94)
[1m[33m[40m BLK0:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x0)
[1m[33m[40m BLK1:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x1)
[1m[33m[40m BLK2:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x6,0x0)/Scsi(0x0,0x0)
[1m[33m[40m BLK4:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x6,0x0)/Scsi(0x0,0x0)/HD(2,GPT,74BEADE6-EBE3-4773-BB1F-6DCD513A6BA4,0xC800,0x2B69DE)
[1m[33m[40m BLK5:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x6,0x0)/Scsi(0x0,0x0)/HD(3,GPT,41D81223-0D78-4BD4-BFC8-D8C233C10C69,0x2C3800,0x2B69DE)
[1m[33m[40m BLK6:[0m[37m[40m [1m[37m[40mAlias(s):[0m[37m[40m
PciRoot(0x0)/Pci(0x6,0x0)/Scsi(0x0,0x0)/HD(4,GPT,6FBC37F2-D83C-43DA-91C5-A02396D224F7,0x57A800,0xBB8000)
[23;01HPress [1m[37m[40mESC[0m[37m[40m in 5 seconds to skip
[1m[33m[40mstartup.nsh[0m[37m[40m or any other key to
continue.[23;01HPress [1m[37m[40mESC[0m[37m[40m in 4 seconds to skip
[1m[33m[40mstartup.nsh[0m[37m[40m or any other key to
continue.[23;01HPress [1m[37m[40mESC[0m[37m[40m in 3 seconds to skip
[1m[33m[40mstartup.nsh[0m[37m[40m or any other key to
continue.[23;01HPress [1m[37m[40mESC[0m[37m[40m in 2 seconds to skip
[1m[33m[40mstartup.nsh[0m[37m[40m or any other key to
continue.[23;01HPress [1m[37m[40mESC[0m[37m[40m in 1 seconds to skip
[1m[33m[40mstartup.nsh[0m[37m[40m or any other key to continue.
[24;01H[1m[33m[40mShell> [0m[37m[40m
On the bitbake console you'll see
| WARNING: Qemu ended unexpectedly, dump data from host is in
/work/test/build/tmp/log/runtime-hostdump/202004011124_qemu
| DEBUG: Stopping logging thread
| DEBUG: Stop event received
| DEBUG: Tearing down logging thread
| DEBUG: Sending SIGTERM to runqemu
| ERROR: testimage received SIGTERM, shutting down...
| ERROR: test-image - FAILED - tests were interrupted during execution
| DEBUG: Python function do_testimage finished
| ERROR: Function failed: do_testimage
After removing the tcpserial option for testing the boot continued and I
could see the kernel being booted.
I tried a lot of different options to add to the qemu command line found
in different mailing lists, but none of them is able to make tcpserial
catch the correct console.
Did anyone ever tried such a thing?
Am I thinking in the wrong direction by trying to attach tcpserial to
the framebuffer device?
Or would it be enough to just skip the bootloader shell by either typing
some magic command or just by ignoring something?
-> If so can someone point me to the code where this is actually
happening?
Thanks in advance
Konrad
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#136933):
https://lists.openembedded.org/g/openembedded-core/message/136933
Mute This Topic: https://lists.openembedded.org/mt/72702863/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
