From: "Muolo Vincenzo (S.I.)" <vincenzo.muolo@angelcompany.com>
To: "david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] issue related to boot aix 7.1 when I try to use qemu ppc64
Date: Wed, 11 Sep 2019 15:58:14 +0000 [thread overview]
Message-ID: <VI1PR08MB439957EF8E072A9A2A96B58DE5B10@VI1PR08MB4399.eurprd08.prod.outlook.com> (raw)
Hi to all
I try to use ( into VM debian 10 running into VMWARE virtualization environment ) qemu ppc64 version to simulate an AIX 7.1 TL04 OS
root@vkvm-acmm:/AIX# qemu-system-ppc64 -version
QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-8+deb10u2)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
I run the following commands into my linux DEB but after few time i have to following issue ( trap interrupt kernel see to end .. ):
qemu-system-ppc64 -cpu POWER8 -machine pseries -m 4096 -serial stdio -drive file=disk.img,if=none,id=drive-virtio-disk0 -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=drive-virtio-disk0 -cdrom aix.iso -prom-env "boot-command=dev / 0 0 s\" ibm,aix-diagnostics\" property boot cdrom:\ppc\chrp\bootfile.exe -s verbose" -net nic -net tap -display vnc=:1
W: /etc/qemu-ifup: no bridge for guest interface found
SLOF **********************************************************************
QEMU Starting
Build Date = Dec 28 2018 13:55:34
FW Version = buildd@ release 20180702
Press "s" to enter Open Firmware.
Populating /vdevice methods
Populating /vdevice/vty@71000000
Populating /vdevice/nvram@71000001
Populating /vdevice/l-lan@71000002
Populating /vdevice/v-scsi@71000003
SCSI: Looking for devices
8200000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
Populating /pci@800000020000000
00 0000 (D) : 1234 1111 qemu vga
00 0800 (D) : 1033 0194 serial bus [ usb-xhci ]
00 1000 (D) : 1af4 1004 virtio [ scsi ]
Populating /pci@800000020000000/scsi@2
SCSI: Looking for devices
100000000000000 DISK : "QEMU QEMU HARDDISK 2.5+"
Installing QEMU fb
Scanning USB
XHCI: Initializing
USB Keyboard
USB mouse
No console specified using screen & keyboard
Welcome to Open Firmware
Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php
Trying to load: -s verbose from: /vdevice/v-scsi@71000003/disk@8200000000000000:\ppc\chrp\bootfile.exe ... Successfully loaded
AIX
StarLED{814}
AIX Version 7.1
exec(/etc/init){1,0}
INIT: EXECUTING /sbin/rc.boot 1
exec(/usr/bin/sh,-c,/sbin/rc.boot 1){1179684,1}
exec(/sbin/rc.boot,/sbin/rc.boot,1){1179684,1}
+ PHASE=1
+ + bootinfo -p
exec(/usr/sbin/bootinfo,-p){1245222,1179684}
PLATFORM=chrp
+ [ ! -x /usr/lib/boot/bin/bootinfo_chrp ]
+ [ 1 -eq 1 ]
+ 1> /usr/lib/libc.a
+ init -c unlink /usr/lib/boot/bin/!(*_chrp)
exec(/etc/init,-c,unlink /usr/lib/boot/bin/!(*_chrp)){1245224,1179684}
+ chramfs -t
exec(/usr/sbin/chramfs,-t){1245226,1179684}
+ init -c unlink /usr/sbin/chramfs
+ 1> /dev/null
exec(/etc/init,-c,unlink /usr/sbin/chramfs){1245228,1179684}
+ + bootinfo -t
exec(/usr/sbin/bootinfo,-t){1245230,1179684}
BOOTYPE=3
+ [ 0 -ne 0 ]
+ [ -z 3 ]
+ unset pdev_to_ldev undolt native_netboot_cfg
+ unset disknet_odm_init config_ATM
+ /usr/lib/methods/showled 0x510 DEV CFG 1 START
exec(/usr/lib/methods/showled,0x510,DEV CFG 1 START){1245232,1179684}
+ cfgmgr -f -v
exec(/usr/sbin/cfgmgr,-f,-v){1245234,1179684}
cfgmgr is running in phase 1
----------------
Time: 0 LEDS: 0x538
Invoking top level program -- "/etc/methods/defsys"
exec(/bin/sh,-c,/etc/methods/defsys ){1310760,1245234}
exec(/etc/methods/defsys){1310760,1245234}
exec(/bin/sh,-c,/usr/lib/methods/define_rspc -n -c sys -s node -t chrp){1376298,1310760}
exec(/usr/lib/methods/define_rspc,-n,-c,sys,-s,node,-t,chrp){1376298,1310760}
Time: 0 LEDS: 0x539
Return code = 0
***** stdout *****
sys0
***** stderr *****
MS 1376298 1310760 /usr/lib/methods/define_rspc -n -c sys -s node -t chrp
M4 1376298 Defining device: uniquetype=sys/node/chrp parent= connection=
M4 1376298 ..define_dvc()
M4 1376298 ..generate_name()
M4 1376298 Generated name: sys0
M4 1376298 ..create_cudv()
M4 1376298 Adding new CuDv
M4 1376298 Defined device sys0
----------------
Attempting to configure device 'sys0'
Time: 0 LEDS: 0x811
Invoking /usr/lib/methods/cfgsys_chrp -1 -l sys0
exec(/bin/sh,-c,/usr/lib/methods/cfgsys_chrp -1 -l sys0){1310762,1245234}
Number of running methods: 1
exec(/usr/lib/methods/cfgsys_chrp,-1,-l,sys0){1310762,1245234}
LED{A20}
Illegal Trap Instruction Interrupt in Kernel
05911ACC tweqi r0,0 r0=0
KDB(0)>
So how can I to proceed ? I must to try to use an different kernel AIX ( 7.2 ? ) or it's possibile to fix this one ?
I'll available to take a dump and so on ....
Awaiting an feedback
Thanks to all
Vincenzo
next reply other threads:[~2019-09-11 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:58 Muolo Vincenzo (S.I.) [this message]
2019-09-12 0:07 ` [Qemu-devel] issue related to boot aix 7.1 when I try to use qemu ppc64 david
2019-09-12 13:47 ` [Qemu-devel] R: " Muolo Vincenzo (S.I.)
2019-09-12 14:14 ` Peter Maydell
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=VI1PR08MB439957EF8E072A9A2A96B58DE5B10@VI1PR08MB4399.eurprd08.prod.outlook.com \
--to=vincenzo.muolo@angelcompany.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 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).