[coreboot] subscribe

[Igor Skochinsky via coreboot]

subscribe
 
 
WBR, Igor
mailto:skochin...@mail.ru___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: [solved] Unable to run KolibriOS in QEMU with coreboot and SeaBIOS

[Paul Menzel]

Dear Mike,


Thank you for your answer.


Am 04.03.21 um 18:15 schrieb Mike Banon:

Hi Paul, as for me I could successfully run KolibriOS in QEMU/i440fx
4MB with coreboot and SeaBIOS. Here's my sequence of actions:

git clone https://review.coreboot.org/coreboot/
cd ./coreboot/
make crossgcc-i386
run a csb_patcher script from
https://review.coreboot.org/c/coreboot/+/33509 , mainly for the
SeaBIOS multiple floppies patch and to auto-download the floppy
collection
make menuconfig , then choose QEMU/i440fx and 4 MB (0x0040 CBFS size)
make
./csb_patcher.sh flop
add all the floppies that you'd like, then run a command
qemu-system-x86_64 -L . -m 256 -vga vmware -net nic,model=rtl8139 -net user 
-soundhw ac97 -usb -usbdevice tablet -bios ./build/coreflop.rom -serial stdio

As you see I'm not using KVM - that's because I don't have this kernel
module installed on a PC I'm at the moment. I believe your problem is
related to the QEMU flags - please start with my set of flags which is
more-or-less guaranteed to work, and slowly change one-by-one to your
liking. For your testing purposes,

Here's my coreflop image - https://www.sendspace.com/file/j4idzp , sha256 sums
68bfb64a68e37df0e8939391ee70aef41c7cd03d8de624b2a6d836d7e1ac8d55
./coreflop.tar.gz
dec8577a76bf190c72f69a4b7fe4f8ef53d53af19ac6890485311da7dd6eb2d5  ./coreflop.rom
coreboot revision - b77cf2299c516a7f5a9a4eccad2b21157278a283


I can successfully run your image with my QEMU command line.

qemu-system-i386 -bios coreflop.rom -L /dev/shm -enable-kvm -smp 
cpus=2 -m 512M -serial stdio -nic none


After several hours of testing old versions, I read your script again 
and the SeaBIOS documentation, and then my error became clear.


As a floppy image the KolibriOS file has to be added with the prefix 
`floppyimg/` in CBFS instead of `img/`.


build/cbfstool build/coreboot.rom add -n floppyimg/kolibrios.lzma 
-f kolibri.img -t raw -c lzma



You may also play with the other floppies inside if you'd like - it's fun!


It indeed was fun, and it’s great to see what’s possible to accomplish 
with such small programs.



Kind regards,

Paul


[1]: https://seabios.org/Runtime_config
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Running QEMU targets in Jenkins

[Paul Menzel]

Dear Julius,


Am 04.03.21 um 23:20 schrieb Julius Werner:


https://qa.coreboot.org/job/coreboot-boot-test/ sends off ToT builds to
9esec's Lava system where they are run on some virtual and real devices.
See for example the comments to
https://review.coreboot.org/c/coreboot/+/51189 where Lava reports passing
on 5 qemu configs and 3 real devices.



Right, but that's different... those tests only run on patches after they
are merged (and IIRC they do get broken occasionally and I don't think many
people pay attention to them. When I see those broken on one of my patches
I tend to just assume there was an existing breakage in the tree already).

I understand that there may be good reasons why we can't run the real
hardware tests on every patch set and make them block Verified+1. But for
QEMU that shouldn't be too hard? We already build images for the emulation
boards anyway, running QEMU to boot them just takes a second, and it
shouldn't require anything that isn't already available on the machines
that do all the compiling. Why can't we do that as part of that step
already?


I pinged you on #coreb...@irc.freenode.net, but looks like you didn’t 
see it.


I think the reason is, nobody has finished setting it up. Martin’s 
change-set CB:20877 (WIP: Add extended tests) [1] from 2017 adds basic 
QEMU tests, but wasn’t finished.



Kind regards,

Paul


[1]: https://review.coreboot.org/c/coreboot/+/20877
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Running QEMU targets in Jenkins

[Julius Werner]

>
> https://qa.coreboot.org/job/coreboot-boot-test/ sends off ToT builds to
> 9esec's Lava system where they are run on some virtual and real devices.
> See for example the comments to
> https://review.coreboot.org/c/coreboot/+/51189 where Lava reports passing
> on 5 qemu configs and 3 real devices.
>
> 
>
Right, but that's different... those tests only run on patches after they
are merged (and IIRC they do get broken occasionally and I don't think many
people pay attention to them. When I see those broken on one of my patches
I tend to just assume there was an existing breakage in the tree already).

I understand that there may be good reasons why we can't run the real
hardware tests on every patch set and make them block Verified+1. But for
QEMU that shouldn't be too hard? We already build images for the emulation
boards anyway, running QEMU to boot them just takes a second, and it
shouldn't require anything that isn't already available on the machines
that do all the compiling. Why can't we do that as part of that step
already?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Unable to run KolibriOS in QEMU with coreboot and SeaBIOS

[Mike Banon]

Hi Paul, as for me I could successfully run KolibriOS in QEMU/i440fx
4MB with coreboot and SeaBIOS. Here's my sequence of actions:

git clone https://review.coreboot.org/coreboot/
cd ./coreboot/
make crossgcc-i386
run a csb_patcher script from
https://review.coreboot.org/c/coreboot/+/33509 , mainly for the
SeaBIOS multiple floppies patch and to auto-download the floppy
collection
make menuconfig , then choose QEMU/i440fx and 4 MB (0x0040 CBFS size)
make
./csb_patcher.sh flop
add all the floppies that you'd like, then run a command
qemu-system-x86_64 -L . -m 256 -vga vmware -net nic,model=rtl8139 -net
user -soundhw ac97 -usb -usbdevice tablet -bios ./build/coreflop.rom
-serial stdio

As you see I'm not using KVM - that's because I don't have this kernel
module installed on a PC I'm at the moment. I believe your problem is
related to the QEMU flags - please start with my set of flags which is
more-or-less guaranteed to work, and slowly change one-by-one to your
liking. For your testing purposes,

Here's my coreflop image - https://www.sendspace.com/file/j4idzp , sha256 sums
68bfb64a68e37df0e8939391ee70aef41c7cd03d8de624b2a6d836d7e1ac8d55
./coreflop.tar.gz
dec8577a76bf190c72f69a4b7fe4f8ef53d53af19ac6890485311da7dd6eb2d5  ./coreflop.rom
coreboot revision - b77cf2299c516a7f5a9a4eccad2b21157278a283

You may also play with the other floppies inside if you'd like - it's fun!
-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Running QEMU targets in Jenkins

[Christian Walter]

Hi Julius,

you can also check this out: https://lava.9esec.io/scheduler/alljobs

It currently runs on:
* Various QEmu Targets
* HP Z220
* HP8200
* Lenovo T500

we are about to add another target (Prodrive Hermes / CFL).

If you have more ideas what could be added with little effort - feel 
free to ping us. :)


Best,

Chris

On 3/4/21 11:14 AM, Patrick Georgi via coreboot wrote:

Hi Julius,

https://qa.coreboot.org/job/coreboot-boot-test/ 
 sends off ToT builds 
to 9esec's Lava system where they are run on some virtual and real 
devices. See for example the comments to 
https://review.coreboot.org/c/coreboot/+/51189 
 where Lava reports 
passing on 5 qemu configs and 3 real devices.



Regards,
Patrick

Am Do., 4. März 2021 um 02:42 Uhr schrieb Julius Werner 
mailto:jwer...@chromium.org>>:


I'm just curious... have we ever considered booting some of our QEMU
targets as part of the Jenkins CI? I know they don't do a lot but they
do cover some stuff (e.g. CBFS). I randomly happened to boot one of my
in-flight patch trains on qemu-i440fx recently and discovered that I
accidentally broke rmodule loading. Would be nice if Jenkins could
just do that for you automatically.

Just wanted to know whether this had been discussed before and people
have come up with good reasons not to do it, or if it's just a matter
of nobody had time to implement it yet. (And if someone wanted to
implement it, what would be the best hook point? Put it into abuild?)



--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der 
Gesellschaft: Hamburg

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

--
*Christian Walter*
*Head of Firmware Development / Cyber Security *



9elements GmbH, Kortumstraße 19-21, 44787 Bochum, Germany
Email: christian.wal...@9elements.com
Phone: _+49 234 68 94 188 _
Mobile: _+49 176 70845047 _

Sitz der Gesellschaft: Bochum
Handelsregister: Amtsgericht Bochum, HRB 17519
Geschäftsführung: Sebastian Deutsch, Eray Basar

Datenschutzhinweise nach Art. 13 DSGVO 
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Running QEMU targets in Jenkins

[Patrick Georgi via coreboot]

Hi Julius,

https://qa.coreboot.org/job/coreboot-boot-test/ sends off ToT builds to
9esec's Lava system where they are run on some virtual and real devices.
See for example the comments to
https://review.coreboot.org/c/coreboot/+/51189 where Lava reports passing
on 5 qemu configs and 3 real devices.


Regards,
Patrick

Am Do., 4. März 2021 um 02:42 Uhr schrieb Julius Werner <
jwer...@chromium.org>:

> I'm just curious... have we ever considered booting some of our QEMU
> targets as part of the Jenkins CI? I know they don't do a lot but they
> do cover some stuff (e.g. CBFS). I randomly happened to boot one of my
> in-flight patch trains on qemu-i440fx recently and discovered that I
> accidentally broke rmodule loading. Would be nice if Jenkins could
> just do that for you automatically.
>
> Just wanted to know whether this had been discussed before and people
> have come up with good reasons not to do it, or if it's just a matter
> of nobody had time to implement it yet. (And if someone wanted to
> implement it, what would be the best hook point? Put it into abuild?)
>


-- 
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft:
Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org