From: Amit Shah <amit.shah@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: tielian <tielian@163.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Latest CVS build of qemu-system-ppc not boot debian_lenny_powerpc_small.qcow
Date: Tue, 9 Mar 2010 11:53:54 +0530 [thread overview]
Message-ID: <20100309062354.GB18898@amit-x200.redhat.com> (raw)
In-Reply-To: <20100308113837.GA17632@hall.aurel32.net>
On (Mon) Mar 08 2010 [12:38:37], Aurelien Jarno wrote:
> On Sun, Mar 07, 2010 at 11:07:40AM +0800, tielian wrote:
> > qemu-system-ppc -hda debian_lenny_powerpc_small.qcow
> > qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000
> >
> > NIP 00000000 LR 00000000 CTR 00000000 XER 00000000
> > MSR 00000000 HID0 00000300 HF 00000000 idx 0
> > Segmentation fault
> >
>
> It has been broken by the following patch:
>
> commit 977b6b91cee1132f8c7b12d22f4b273091598e44
> Author: Amit Shah <amit.shah@redhat.com>
> Date: Thu Feb 25 19:26:11 2010 +0530
>
> ppc440_bamboo: Add 0.12 and 0.13 machine types for backward compat
>
> Add a 0.12 machine type for compatibility with older versions. Mark the
> default one as 0.13.
>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>
> This patch change the default PPC machine to bamboo, while it was
> previously g3beige. I haven't noticed the problem, as my test script
> sets the machine with the -M argument.
BTW, as in the s390 case, does this patch make sense for powerpc? If no
one uses such a thing, those two patches should be reverted..
Amit
next prev parent reply other threads:[~2010-03-09 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 3:07 [Qemu-devel] Latest CVS build of qemu-system-ppc not boot debian_lenny_powerpc_small.qcow tielian
2010-03-08 11:38 ` Aurelien Jarno
2010-03-09 6:23 ` Amit Shah [this message]
2010-03-09 14:36 ` Aurelien Jarno
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=20100309062354.GB18898@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=tielian@163.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).