From: David Gibson <david@gibson.dropbear.id.au>
To: Erlon Cruz <sombrafam@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 08/13] pseries: Update SLOF for NVRAM support
Date: Wed, 5 Dec 2012 11:13:49 +1100 [thread overview]
Message-ID: <20121205001349.GC5217@truffula.fritz.box> (raw)
In-Reply-To: <CAF+Cadtu1oG9kBE-beCxtJuMD3D0WxSrZx1GS7562vzqBmew3g@mail.gmail.com>
On Tue, Dec 04, 2012 at 09:27:54PM -0200, Erlon Cruz wrote:
> Em 04/12/2012 20:58, "David Gibson" <david@gibson.dropbear.id.au> escreveu:
> >
> > On Tue, Dec 04, 2012 at 11:20:03AM -0200, Erlon Cruz wrote:
> > > On Tue, Dec 4, 2012 at 12:42 AM, David Gibson
> > > <david@gibson.dropbear.id.au>wrote:
> > >
> > > > Now that we have implemented PAPR compatible NVRAM interfaces in
> qemu, this
> > > > updates the SLOF firmware to actually initialize and use the NVRAM as
> a
> > > > PAPR guest firmware is expected to do.
> > > >
> > > > This SLOF update also includes an ugly but useful workaround for a
> bug in
> > > > the SLES11 installer which caused it to fail under KVM.
> > > >
> > > >
> > > I had a problem when installing SLES, when the installer et at 23%, a
> get:
> > >
> > > Installation of package ./suse/ppc64/vim-base-7.2-8.15.2.ppc64.rpm
> failed.
> > > Subprocess failed. Error: RPM failed: error:
> > > %post(vim-base-7.2-8.15.2.ppc64.rpm)
> > >
> > > Is this the same problem?
> >
> > No, I don't think so. The NVRAM failure, I believe happens at the end
> > when it's doing the yaboot setup. Although, I haven't met it myself,
> > so I'm not certain.
>
> Have you succeed installing any SLES on QEMU pSeries? This is the first
> system I'm trying to install in an lpar. The guests I have I've installed
> in a power machine and then use the roots.
I haven't personally tried installing SLES, only Fedora and Debian
(and not very recently for those). Some others in IBM have tried
installing SLES - it used to fail because of this bug and another, I'm
not sure if they've had a chance to try again since this fix.
Failing suddenly in the post script for vim-base seems a really
unlikely problem to be caused by qemu/host bugs, though anything's
possible. First thing I'd try is to triple-check your install media.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-12-05 0:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 2:42 [Qemu-devel] [0/13] Pending pseries/ppc patches as at 1.3 release David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 01/13] pseries: Fix incorrect initialization of interrupt controller David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 02/13] pseries: Use #define for XICS base irq number David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 03/13] pseries: Return the token when we register an RTAS call David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 04/13] pseries: Allow RTAS tokens without a qemu handler David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 05/13] pseries: Add tracepoints to the XICS interrupt controller David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 06/13] pseries: Split xics irq configuration from state information David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 07/13] pseries: Implement PAPR NVRAM David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 08/13] pseries: Update SLOF for NVRAM support David Gibson
2012-12-04 13:20 ` Erlon Cruz
2012-12-04 22:54 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-12-04 23:27 ` Erlon Cruz
2012-12-05 0:13 ` David Gibson [this message]
2012-12-05 2:27 ` [Qemu-devel] " Alexander Graf
2012-12-05 14:09 ` Erlon Cruz
2012-12-05 14:35 ` Alexander Graf
2012-12-05 14:37 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2012-12-05 14:39 ` Alexander Graf
2012-12-06 19:41 ` Erlon Cruz
2012-12-06 19:41 ` Erlon Cruz
2012-12-06 19:41 ` [Qemu-devel] " Erlon Cruz
2012-12-07 8:10 ` [Qemu-devel] [Qemu-ppc] " Nikunj A Dadhania
2012-12-07 11:48 ` Erlon Cruz
2012-12-07 11:55 ` Alexander Graf
2012-12-04 2:42 ` [Qemu-devel] [PATCH 09/13] pseries: Don't allow TCE (iommu) tables to be registered with duplicate LIOBNs David Gibson
2012-12-04 2:42 ` [Qemu-devel] [PATCH 10/13] target-ppc: Don't use hwaddr to represent hardware state David Gibson
2012-12-13 12:51 ` Alexander Graf
2012-12-04 2:42 ` [Qemu-devel] [PATCH 11/13] pseries: Fixes and enhancements to L1 cache properties David Gibson
2012-12-13 12:50 ` Alexander Graf
2012-12-17 2:32 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-12-17 10:10 ` Alexander Graf
2012-12-17 23:00 ` David Gibson
2012-12-17 23:49 ` Alexander Graf
2012-12-19 4:34 ` David Gibson
2012-12-19 22:40 ` Alexander Graf
2012-12-20 3:38 ` David Gibson
2012-12-20 9:32 ` Alexander Graf
2012-12-04 2:42 ` [Qemu-devel] [PATCH 12/13] pseries: Increase default NVRAM size David Gibson
2012-12-13 12:51 ` Alexander Graf
2012-12-04 2:42 ` [Qemu-devel] [PATCH 13/13] target-ppc: Give a meaningful error if too many threads are specified David Gibson
2012-12-04 3:11 ` David Gibson
2012-12-13 12:57 ` Alexander Graf
2012-12-13 13:17 ` David Gibson
2012-12-13 13:19 ` Alexander Graf
2012-12-13 14:17 ` Peter Maydell
2012-12-13 14:18 ` Peter Maydell
2012-12-17 2:13 ` David Gibson
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=20121205001349.GC5217@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sombrafam@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).