similar to: Microcode update for Xen in Wheezy (Was: Re: ANNOUNCEMENT: Intel/AMD x86 CPU microcode update system in non-free)

x86/ucode: fix for AMD Fam15 CPUs Remove hardcoded maximum size a microcode patch can have. This is dynamic now. The microcode patch for family15h can be larger than 2048 bytes and gets silently truncated. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Backport from xen-unstable changeset 24411:ca5f588bd203 to Xen 4.1 -- ---to satisfy European Law for business letters:

86/ucode: fix for AMD Fam15 CPUs Remove hardcoded maximum size a microcode patch can have. This is dynamic now. The microcode patch for family15h can be larger than 2048 bytes and gets silently truncated. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Backport from xen-unstable changeset 24411:ca5f588bd203 to Xen 3.3 -- ---to satisfy European Law for business letters:

flight 10504 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10504/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail REGR. vs. 10491 test-amd64-i386-win 7 windows-install fail REGR. vs. 10491 test-amd64-amd64-xl-winxpsp3 7 windows-install fail REGR. vs. 10491

On Wed, Jan 24, 2018 at 4:41 PM, Leon Fauster <leonfauster at googlemail.com> wrote: ... > > Comparing microcode-20171117 with microcode-20180108 shows that > from the 94 ucode files only 19 where updated > > $ diff -r --brief microcode-20171117 microcode-20180108 > Files microcode-20171117/intel-ucode/06-3c-03 and microcode-20180108/intel-ucode/06-3c-03 differ > Files

> Am 24.01.2018 um 22:22 schrieb Chris Adams <linux at cmadams.net>: > > Once upon a time, Chris Murphy <lists at colorremedies.com> said: >> "We recommend that OEMs, cloud service providers, system >> manufacturers, software vendors and end users stop deployment of >> current versions." Current versions of what? Microcode? > > Well,

flight 10511 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10511/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail in 10504 REGR. vs. 10491 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-sedf 13 guest-localmigrate.2 fail pass in 10504 test-i386-i386-win

Not sure about CentOS 6, but this was covered previously (at least for 7...not sure how much they differ)...not that I can find the message now, but here's what I recall/pieced together from bash history that works on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum

On 5/16/19 2:12 AM, Karel Hendrych wrote: > Hi, > > is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? I'm not sure off the top of my head. You can add ucode=scan to the xen command line, add a file /path/to/microcode_file as the last item in your boot list, and generate that microcode file using something like: iucode_tool --write-earlyfw

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > "We recommend that OEMs, cloud service providers, system > manufacturers, software vendors and end users stop deployment of > current versions." Current versions of what? Microcode? Well, that's the only thing Intel provides for CPUs, so that's all it can be. > What these means for people who

I think I remember some discussion of something in this area not too long ago on xen-devel. CC-s added. Konrad, do you know of any issues with ucode=scan in 4.4? On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote: > Package: xen-hypervisor-4.5-amd64 > Version: 4.5.0-1 > Severity: normal > > Dear Maintainer, > > according to the documentation the option ucode=scan

Hi! System: Debian/testing with selfcompiled kernel 3.5.5 (same error with 3.4 or 3.6) XEN: 4.1.3 After booting the Dom0 I notice the following errors: [ 2.939078] microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.991998] microcode: CPU0 update to revision 0xa0b failed [ 2.992035] microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.995882] microcode: CPU1 update to

On Tue, May 19, 2015 at 12:47:51PM +0100, Ian Campbell wrote: >The reconcatenate bit is easy, just: > $ cat initrd.ucode initrd.real > initrd.img >With initrd.real extracted above. > >initrd.ucode creation I'm a little unsure about but something like: > >$ mkdir initrd.ucode.tree >$ cd initrd.ucode.tree >$ cat /boot/initrd.img | cpio -id >$ find >.

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

it is working thx a lot... but it has included the GenuineIntel.bin only in actually used kernel... do I need to reinstall microcode_ctl every time I update the kernel? And second question, I quess I still need the ucode = scan as xen parameter right? Am 2018-09-19 20:08, schrieb Kevin Stange: > On 9/19/18 1:55 AM, Christoph wrote: >> >> Hi >> >> can someone say me

Thanks Atom2, thanks for the refs, I've added the Debian bug and the submitter back to the CC. On Wed, 2015-05-13 at 22:11 +0200, Atom2 wrote: > Am 13.05.15 um 15:41 schrieb Ian Campbell: > > I think I remember some discussion of something in this area not too > > long ago on xen-devel. CC-s added. > I assume you refer to this discussion which happend to be on the >

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

Package: xen-hypervisor-4.5-amd64 Version: 4.5.0-1 Severity: normal Dear Maintainer, according to the documentation the option ucode=scan should tell XEN to look for a microcode update in an uncompressed initrd. While I don?t use the Debian kernel the tools to generate the initrd are part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? creates the directory structure

On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the

On 9/19/18 1:55 AM, Christoph wrote: > > Hi > > can someone say me how to update the ?code of the cpu with xen? > > I have added the ucode=scan parameter to xen but it does not seem to > work... > > the ?code version of my xeon is really old :/ > > model name??? : Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz > microcode??? : 0x10 > There is a

Dear All, An update just brought on my CenOS 6 boxes updated microcode.dat files: /lib/firmware/microcode.dat Does anybody know off hand what (how critical) is that, as, if it is related to most famous these days trouble with CPU hardware, I will need to reboot relevant boxes to have new microcode loaded. But if it is not that critical, it can wait till next reboot. Thanks a lot and