From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@debian.org>
Cc: 785187@bugs.debian.org, xen-devel <xen-devel@lists.xen.org>,
Stephan Seitz <stse+debianbugs@fsing.rootsland.net>
Subject: Re: [Pkg-xen-devel] Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
Date: Wed, 13 May 2015 11:57:55 -0400 [thread overview]
Message-ID: <20150513155755.GC15812@l.oracle.com> (raw)
In-Reply-To: <1431524470.8263.276.camel@debian.org>
> > 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 „kernel/x86/microcode/GenuineIntel.bin”,
> > so I think the initrd is allright.
Is the initramfs compressed? The scanning code can't deal if the initramfs
is compressed - so you either have to glue the compressed initramfs and
the cpio with the microcode together (where the microcode has to go first).
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-05-13 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150513T101737.GA.80186.stse@fsing.rootsland.net>
2015-05-13 13:41 ` [Pkg-xen-devel] Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working Ian Campbell
2015-05-13 15:57 ` Konrad Rzeszutek Wilk [this message]
2015-05-13 18:03 ` Ian Campbell
2015-05-14 20:45 ` Stephan Seitz
[not found] ` <20150514T224249.GA.bb576.stse@fsing.rootsland.net>
2015-05-15 7:26 ` Ian Campbell
2015-05-19 11:31 ` Stephan Seitz
[not found] ` <20150519T132815.GA.6f97a.stse@fsing.rootsland.net>
2015-05-19 11:47 ` Ian Campbell
[not found] ` <1432036071.12989.89.camel@debian.org>
2015-05-27 20:43 ` Stephan Seitz
2015-07-01 11:09 ` Stephan Seitz
2015-05-13 20:11 ` Atom2
2015-05-14 8:41 ` Ian Campbell
2015-05-14 20:56 ` Atom2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150513155755.GC15812@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=785187@bugs.debian.org \
--cc=ijc@debian.org \
--cc=stse+debianbugs@fsing.rootsland.net \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.