qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PReP currently broken (Was Re: [Qemu-devel] Booting AIX / First try


From: Natalia Portillo
Subject: Re: PReP currently broken (Was Re: [Qemu-devel] Booting AIX / First try w/QEMU)
Date: Fri, 16 Oct 2009 00:54:08 +0100

This IS a bug.

Indeed, that's the first of all bugs/lack-of-feature trying to boot AIX:

PReP machine emulation is broken, with IRQ conflicts in the ISA bus.
OpenBIOS is not recognizing the PReP boot scheme (MBR partition, /ppc/ bootfile.txt)

Tested using G3 Beige machine:
Indicating boot /pci/pci-ata/ata-1/cdrom:1,\ppc\bootfile.txt does nothing Indicating boot /pci/pci-ata/ata-1/cdrom:,\ppc\bootfile.txt loads the file, says ok, no booting. Indicating boot /pci/pci-ata/ata-1/cdrom:,\ppc\chrp\bootfile.exe (the real kernel) loads the file (takes longer), says ok, no booting.
Indicating -kernel bootfile.exe, qemu ABORTS execution inmediately.

So these are the bugs preventing AIX from being emulated as for today's GIT.


El 16/10/2009, a las 00:43, IT2 Stuart Blake Tener, USNR escribió:

Natalia,


On 10/15/09 5:26 PM, "Natalia Portillo" <address@hidden> wrote:

As of today, qemu-system-ppc -M prep inmediately quits saying "isa irq
13 already assigned"

Are you saying you fixed or this is a bug or what? I am confused by your
email.


V/R,

Stuart



El 14/10/2009, a las 14:40, IT2 Stuart Blake Tener, USNR escribió:

Lauren,

Please be cognizant of the fact that yesterday was the first time I
downloaded, compiled, and ever tried QEMU, so I apologize for the
"ID-10T" questions.

BUG 1:

When you say that booting AIX 6.1 impels the requisite of emulating
a "CHRP with at least a POWER4"", are you saying QEMU cannot do
this, or I need to assert different command line arguments?

What requisites would booting AIX 5.3 impel?

My goal would be to try to have access to both via an emulated
environment, if possible.

If the OpenBIOS will not work, what BIOS would work?


BUG 2:

How do I get the OpenBIOS updates and integrate them into
recompiling QEMU, or can I just somehow get a compiled update of
OpenBIOS and drop it in the correct QEMU directory?

I am not too familiar with SVN or its command structure either.


V/R,

Stuart


Quoting "Laurent Vivier" <address@hidden>:

To whom it shall concern,

I have absolutely no time for mailing lists or to spend much time on
this other than to report the bug, so please understand I am just
here
to report this, and have little time for continued testing of it. I
leave that to you, the developers.

I ran into two different bugs attempting to try QEMU 0.11, under
CentOS 5.3 64bit (fully updated), QEMU compiled from source
flawlessly, while under under VirtualBox on a Lenvo T400 laptop.

My goal was to try to boot an AIX CDROM from QEMU 0.11 (AIX 6.1), I
never got that far due to these bugs.


Bug #1:

It seems to complain about some 1MB BIOS file being missing or
dysfunctional, really I did not see any BIOS files that big, so, I
gave up with this type of boot. Then I tried below, "Bug #2", met
with
more problems, so I gave up entirely as I had no more time to play
with it.

/usr/local/bin/qemu-system-ppc -nographic -hda aix.raw -cdrom
./Image_091013_1359.iso -M prep
qemu: hardware error: PowerPC 601 / 620 / 970 need a 1MB BIOS

CPU #0:
NIP fff00100   LR 00000000 CTR 00000000 XER 00000000
MSR 00000040 HID0 00000000  HF 00000000 idx 1
TB 00000000 00000000 DECR ffffffff
GPR00 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR04 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR08 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR12 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR16 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR20 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR24 0000000000000000 0000000000000000 0000000000000000
0000000000000000
GPR28 0000000000000000 0000000000000000 0000000000000000
0000000000000000
CR 00000000  [ -  -  -  -  -  -  -  -  ]             RES ffffffff
FPR00 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR04 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR08 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR12 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR16 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR20 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR24 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPR28 0000000000000000 0000000000000000 0000000000000000
0000000000000000
FPSCR 00000000
SRR0 00000000 SRR1 00000000 SDR1 00000000
t: line 5: 11668 Aborted
/usr/local/bin/qemu-system-ppc -nographic -hda aix.raw -cdrom
./Image_091013_1359.iso -M prep
address@hidden qemu]#

To boot AIX6.1, you must emulate a CHRP with at least a POWER4.
Moreover, AIX6.1 needs the hypervisor support in OpenFirmware
(which is not the case of OpenBIOS).


Bug #2: never even tries to boot from CD-ROM and gives some wildly
odd
error and display messages.


/usr/local/bin/qemu-system-ppc -nographic -hda aix.raw -cdrom
./Image_091013_1359.iso -M g3beige

=============================================================
OpenBIOS 1.0 [Jul 5 2009 17:36]
Configuration device id QEMU version 1 machine id 2
CPUs: 1
Memory: 128M
UUID: 00000000-0000-0000-0000-000000000000
CPU type PowerPC,750
Welcome to OpenBIOS v1.0 built on Jul 5 2009 17:36

*** Boot failure! No secondary bootloader specified ***

0 > boot cdrom
partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

partition 2 does not exist

This should be corrected in OpenBIOS HEAD SVN repository.

*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
*** Boot failure! No secondary bootloader specified ***
ok

Regards,
Laurent
--
--------------------- address@hidden  ---------------------
"Tout ce qui est impossible reste à accomplir"    Jules Verne
"Things are only impossible until they're not" Jean-Luc Picard




--
IT2 Stuart Blake Tener, USNR, N3GWG (Extra), MROP
Beverly Hills, CA / Las Vegas, NV / Philadelphia, PA / Washington, DC
mobile: (310) 358-0202
Nextel: 124*233172*14 (direct connect)
e-mail: address@hidden








--

Very Respectfully,

IT2 Stuart Blake Tener, USNR
Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC
Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP)
email: address@hidden (also carbon copies to my Blackberry)
phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone)
phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only)
E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway)

Military emails (checked monthly until remote NMCI access is secured)
NIPRNET: address@hidden
NIPRNET: address@hidden
NRO:     address@hidden
TS/SCI:  address@hidden (GWAN)

Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the originate message.









reply via email to

[Prev in Thread] Current Thread [Next in Thread]