Displaying 20 results from an estimated 6000 matches similar to: "Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working"
2015 May 14
0
Bug#785187: [Xen-devel] Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
>
2015 May 13
3
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
> > 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
2015 May 13
0
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
2015 May 15
2
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
2015 May 19
3
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
> >
2018 Sep 19
4
how to update ucode with xen
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
--
------
Greetz
2018 Sep 19
1
how to update ucode with xen
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
2015 May 14
0
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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 initrd are
>> > part of Debian. The command ?cpio -i <
2015 May 13
0
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
On Wed, 2015-05-13 at 11:57 -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 initrd are
> > > part of Debian. The command ?cpio -i <
2015 May 27
0
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
>.
2015 May 19
0
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
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
> kernel/x86/microcode
> kernel/x86/microcode/GenuineIntel.bin
> 16 blocks
2012 Jan 04
2
Xen 4.1: x86/ucode: fix for AMD Fam15 CPUs
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:
2012 Sep 10
3
[PATCH] docs: document "ucode=" hypervisor command line option
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -785,6 +785,19 @@ Specify the per-cpu trace buffer size in
> `= unstable | skewed`
### ucode
+> `= <integer>`
+
+Specify the CPU microcode update blob module index. When positive, this
+specifies the n-th module (in the GrUB entry, zero based)
2018 Feb 26
4
How to update modules in iniramfs fastly
> -----Original Messages-----
> From: "Steven Tardy" <sjt5atra at gmail.com>
> Sent Time: 2018-02-26 10:48:48 (Monday)
> To: "CentOS mailing list" <centos at centos.org>
> Cc:
> Subject: Re: [CentOS] How to update modules in iniramfs fastly
>
> On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>
> wrote:
2015 Jul 01
2
Bug#785187: [PATCH] xen: earlycpio: Pull in latest linux earlycpio.[ch]
AFAICT our current version does not correspond to any version in the
Linux history. This commit resynchronised to the state in Linux
commit 598bae70c2a8e35c8d39b610cca2b32afcf047af.
Differences from upstream: find_cpio_data is __init, printk instead of
pr_*.
This appears to fix Debian bug #785187. "Appears" because my test box
happens to be AMD and the issue is that the (valid) cpio
2018 Jan 24
2
/lib/firmware/microcode.dat update on CentOS 6
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
2019 May 16
2
centos-virt CPU microcode updates?
Hi,
is there any guide for CPU microcode updates on CentOS6, Xen 4.10,
kernel 4.9 ?
Thanks
Karel
2019 May 16
1
centos-virt CPU microcode updates?
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
2018 Sep 19
0
how to update ucode with xen
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
2014 Apr 28
4
[PATCH v3 6/9] drm/nouveau/graph: enable when using external firmware
On Fri, Apr 25, 2014 at 5:19 PM, Alexandre Courbot <acourbot at nvidia.com> wrote:
> nvc0_graph_ctor() would only let the graphics engine be enabled if its
> oclass has a proper microcode linked to it. This prevents GR from being
> enabled at all on chips that rely exclusively on external firmware, even
> though such a use-case is valid.
>
> Relax the conditions enabling