CentOS virt - Jul 2015 - missing bnx2x firmware files in Xen4CentOS CentOS6 kernel 3.18.12-11

Hi all

On 07/07/2015 10:30 PM, Johnny Hughes wrote:
> On 07/07/2015 12:20 PM, Johnny Hughes wrote:
[.... loads of stuff deleted .... ]
>> OH .. I see, I did not get the firmware files, but their git pointer
info :)
>>
>> I will rebuild and repost.
>>
> Please try the packages that are now in the same location.
>
> http://people.centos.org/hughesjr/xen-kernel/x86_64/Packages/
Yes, I can confirm the first packages were broken. I'll try those 
tomorrow, when I am back at work. However, they look fine. First of all, 
all required files are present and I extracted and md5sum-ed them 
against the ones from my kernel ( of which I know they work ). All 
md5sums are fine.

Thanks a lot for the quick fix.

Are you going to push these packages to the Xen4CentOS repo? The reason 
I ask, is that I use Xen4CentOS at work, where I run a fairly large 
infrastructure on Xen4CentOS in a production environment. Mixing bug 
fixes with minor updates - repo version is at 3.18.12 while you provide 
3.18.17 - is a bit of a problem, as I need to validate the new kernel 
version before pushing it into production (read: run some tests, check 
if everything works).
I recon that updated versions of LTS kernels incorporate bugfixes, which 
are desirable anyway. But i'd rather wait until they are pushed to 
Xen4CentOS before "arguing them into production". Hence my question on
the timeline.
I'll give the packages a spin anyway tomorrow and come back to report my 
results.

Again, thanks a lot. And, by the way, rest assured that the whole 
Xen4CentOS effort is very much appreciated and matters a lot.

Regards
Thomas

On 07/07/2015 04:03 PM, T.Weyergraf wrote:
> 
> Hi all
> 
> On 07/07/2015 10:30 PM, Johnny Hughes wrote:
>> On 07/07/2015 12:20 PM, Johnny Hughes wrote:
> [.... loads of stuff deleted .... ]
>>> OH .. I see, I did not get the firmware files, but their git
pointer
>>> info :)
>>>
>>> I will rebuild and repost.
>>>
>> Please try the packages that are now in the same location.
>>
>> http://people.centos.org/hughesjr/xen-kernel/x86_64/Packages/
> Yes, I can confirm the first packages were broken. I'll try those
> tomorrow, when I am back at work. However, they look fine. First of all,
> all required files are present and I extracted and md5sum-ed them
> against the ones from my kernel ( of which I know they work ). All
> md5sums are fine.
> 
> Thanks a lot for the quick fix.
> 
> Are you going to push these packages to the Xen4CentOS repo? The reason
> I ask, is that I use Xen4CentOS at work, where I run a fairly large
> infrastructure on Xen4CentOS in a production environment. Mixing bug
> fixes with minor updates - repo version is at 3.18.12 while you provide
> 3.18.17 - is a bit of a problem, as I need to validate the new kernel
> version before pushing it into production (read: run some tests, check
> if everything works).
> I recon that updated versions of LTS kernels incorporate bugfixes, which
> are desirable anyway. But i'd rather wait until they are pushed to
> Xen4CentOS before "arguing them into production". Hence my
question on
> the timeline.
> I'll give the packages a spin anyway tomorrow and come back to report
my
> results.
> 
> Again, thanks a lot. And, by the way, rest assured that the whole
> Xen4CentOS effort is very much appreciated and matters a lot.
Either this Kernel, or one built from the same SRPM and a newer kernel
version, will get rolled in soon.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20150707/92a51791/attachment-0002.sig>

On 07/08/2015 01:10 AM, Johnny Hughes wrote:
> [...loads deleted....]
> Either this Kernel, or one built from the same SRPM and a newer kernel
> version, will get rolled in soon.
Sorry for the late reply, but the testsystem I use to test
"xen-things"
at work died. Took me a few days to test on a replacement.

Your current kernel-3.18.17-13 works fine. Proper bnx2x firmware files 
are contained in the associated kernel-firmware package and the driver 
picks the correct ones.
As far as I am concerned, the issue is fixed.

Thanks again for the re-packaging.

Regards,
Thomas Weyergraf