Lucas,

Thanks for the pointers.

Few comments/questions:

1) Just curious: do you create firmware rpm with all fw files in linux-firmware 
or cherry pick what you know you need?

2) I just looked at sample/git_kernel.srv job definition, very nice - is that 
what you were referring to below? Indeed in that case it would be easy to add 
an rpm install firmware step just in test job

3) If you think it is reasonable I could explore adding support to 
server/kernel implementation.  But given simple solution in the test 
job/provisioning seems like overkill. Let me know what you think.


Julius

-----Original Message-----
From: Lucas Meneghel Rodrigues [mailto:[email protected]] 
Sent: Friday, September 14, 2012 6:28 AM
To: Gawlas, Julius
Cc: [email protected]
Subject: Re: [Autotest] Handling of neccessary firmware when testing kernels 
with autotest

On 09/13/2012 12:26 PM, Gawlas, Julius wrote:
> We have the following scenario to deal with:
>
> - we have setup autotest/cobbler ring with several test clients
>
> - in the test pool there are new machines that have hardware requiring 
> firmware updates, that firmware is not part of the upstream kernel but 
> it is in 
> git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware
>
> - we get autotest job request with source based kernels (tar.gz2) that 
> are basically slightly modified upstream kernels (the job submitter 
> git clones from Linux-stable and makes some modifications to it)
>
> The result is that on the SUT kernel is rebuild and when booting into new 
> kernel it does not come up bc it is missing necessary firmware.
>
> What is a good way to handle this? Any ideas would be greatly appreciated.

I can tell you about our experience running kvm upstream tests (that require 
building kernels based on git). As we run such tests on Fedora, we prepared a 
recent kernel-firmware rpm and install it in the box as part of the test job 
and that usually solves our problem.

Not sure whether this is a valid solution for you, but I believe it's worth a 
try. If not we could consider adding firmware build steps to autotest kernel 
build procedure.

Lucas

_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel

Reply via email to