Fedora ppc64 install fails on qemu-system-ppc64

[Richard W.M. Jones]

Does anyone have a working recipe for installing Fedora on
qemu-system-ppc64 (host is x86-64)?  I've been trying it for about a
day now, and just keep hitting bugs.

I can get the Fedora 19 netinst and DVD to boot fine using upstream
qemu from git and the following command:

./ppc64-softmmu/qemu-system-ppc64 \
  -cpu POWER7 \
  -M pseries \
  -m 4096 \
  -hda /dev/fedora/f20ppc64 \
  -cdrom /tmp/Fedora-19-ppc64-DVD.iso \
  -netdev user,id=usernet,net=169.254.0.0/16 \
  -device virtio-net-pci,netdev=usernet

However X11 cannot render anything:
https://bugzilla.redhat.com/show_bug.cgi?id=1002030
What graphics device does qemu emulate?  Are there alternatives
I could try?

Using a text-mode non-LVM Anaconda install proceeds a little further,
although is still buggy:
https://bugzilla.redhat.com/show_bug.cgi?id=1001792
https://bugzilla.redhat.com/show_bug.cgi?id=966289#c37

Finally it fails with "script error with package [some package name]":
https://bugzilla.redhat.com/show_bug.cgi?id=1002077

And that's as far as I've got.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

[Tony Breeds]

On Wed, Aug 28, 2013 at 02:28:09PM +0100, Richard W.M. Jones wrote:
>  
>  Does anyone have a working recipe for installing Fedora on
>  qemu-system-ppc64 (host is x86-64)?  I've been trying it for about a
>  day now, and just keep hitting bugs.
>  
>  I can get the Fedora 19 netinst and DVD to boot fine using upstream
>  qemu from git and the following command:
>  
>  ./ppc64-softmmu/qemu-system-ppc64 \
>    -cpu POWER7 \
>    -M pseries \
>    -m 4096 \
>    -hda /dev/fedora/f20ppc64 \
>    -cdrom /tmp/Fedora-19-ppc64-DVD.iso \
>    -netdev user,id=usernet,net=169.254.0.0/16 \
>    -device virtio-net-pci,netdev=usernet 
You can try chaning the -cpu to 970 or other options.  F19 installed on
my G5 so 970 /should/ work.
 
>  However X11 cannot render anything:
>  https://bugzilla.redhat.com/show_bug.cgi?id=1002030
>  What graphics device does qemu emulate?  Are there alternatives
>  I could try? 
I think you're best option is a vnc install.  As I understand it it's
just a simple OpenFirmware FB (OFFB) and the appropriate xorg driver.
 
>  Using a text-mode non-LVM Anaconda install proceeds a little
> further,
>  although is still buggy:
>  https://bugzilla.redhat.com/show_bug.cgi?id=1001792
>  https://bugzilla.redhat.com/show_bug.cgi?id=966289#c37
>  
>  Finally it fails with "script error with package [some package name]":
>  https://bugzilla.redhat.com/show_bug.cgi?id=1002077 
I'm pretty sure this will come down to the gcc in Ferdora is generating
VSX instructions but qemu doesn't emulate them.  Short of writing that
emulation code I think you're sunk with the std. images.

Yours Tony

[Richard W.M. Jones]

On Fri, Aug 30, 2013 at 01:09:23PM +1000, Tony Breeds wrote:
>  On Wed, Aug 28, 2013 at 02:28:09PM +0100, Richard W.M. Jones wrote:
>  > Finally it fails with "script error with package [some package name]":
>  > https://bugzilla.redhat.com/show_bug.cgi?id=1002077
>  
>  I'm pretty sure this will come down to the gcc in Ferdora is generating
>  VSX instructions but qemu doesn't emulate them.  Short of writing that
>  emulation code I think you're sunk with the std. images. 
That's presumably this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=887978

Wouldn't either the guest or the host fail in a more obvious way
(eg. seeing traps in the guest) if VSX instructions are being used?

To test this, I unpacked a large selection of RPMs from the Fedora 19
ppc64 install DVD and I ran '/usr/powerpc64-linux-gnu/bin/objdump
--disassemble' on all of the binaries and libraries found in /usr/bin
and /usr/lib64 of the RPMs.  This produced 3383381+3997721 lines of
output.

I grepped the output for: /xsd/, /xvd/ (so hopefully I would find
instructions such as lxsdux lxvd2ux lxvw4ux stxsdux stxvd2ux
stxvw4ux).  However there were no matches.  From this I conclude that
VSX instructions are not being generated or are being generated only
extremely rarely.

Am I looking for the right thing?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

[Brent Baude]

Yes, you should only see those instructions in the ppc64p7 RPMs.  Those
RPMs should only be getting selected by rpm/yum when it detects a POWER7
system, which isn't the case here as I understand it.  There is something
else going on.


Brent J. Baude
Linux Technology Center
3605 Hwy 52N
Rochester, MN  55901

http://www.ibm.com/linux/ltc/
507.253-0708




From:	"Richard W.M. Jones" <rjones(a)redhat.com&gt;
To:	ppc(a)lists.fedoraproject.org,
Date:	08/30/2013 04:48 AM
Subject:	Re: Fedora ppc64 install fails on qemu-system-ppc64
Sent by:	ppc-bounces(a)lists.fedoraproject.org



On Fri, Aug 30, 2013 at 01:09:23PM +1000, Tony Breeds wrote:
>  On Wed, Aug 28, 2013 at 02:28:09PM +0100, Richard W.M. Jones wrote:
>  > Finally it fails with "script error with package [some package name]":
>  > https://bugzilla.redhat.com/show_bug.cgi?id=1002077
>
>  I'm pretty sure this will come down to the gcc in Ferdora is generating
>  VSX instructions but qemu doesn't emulate them.  Short of writing that
>  emulation code I think you're sunk with the std. images. 
That's presumably this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=887978

Wouldn't either the guest or the host fail in a more obvious way
(eg. seeing traps in the guest) if VSX instructions are being used?

To test this, I unpacked a large selection of RPMs from the Fedora 19
ppc64 install DVD and I ran '/usr/powerpc64-linux-gnu/bin/objdump
--disassemble' on all of the binaries and libraries found in /usr/bin
and /usr/lib64 of the RPMs.  This produced 3383381+3997721 lines of
output.

I grepped the output for: /xsd/, /xvd/ (so hopefully I would find
instructions such as lxsdux lxvd2ux lxvw4ux stxsdux stxvd2ux
stxvw4ux).  However there were no matches.  From this I conclude that
VSX instructions are not being generated or are being generated only
extremely rarely.

Am I looking for the right thing?

Rich.

--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
_______________________________________________
ppc mailing list
ppc(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ppc

[Richard W.M. Jones]

On Fri, Aug 30, 2013 at 07:27:51AM -0500, Brent Baude wrote:
>  
>  Yes, you should only see those instructions in the ppc64p7 RPMs.  Those
>  RPMs should only be getting selected by rpm/yum when it detects a POWER7
>  system, which isn't the case here as I understand it.  There is something
>  else going on. 
Originally I was giving it a POWER7 (virtual) CPU.

The install CD contains a small number of *.ppc64p7.rpm files (see
below), so it's plausible that some were installed and then some RPM
%post script failed because it used that code.  I notice glibc is in
the list.

Unfortunately other -cpu types don't get very far booting.  POWER7
gets all the way into Anaconda.  Everything else I've tried fails to
even enter the kernel.

I'll have a working G5 system shortly, although it'd still be nice if
qemu-system-ppc64 was a supported option.  Physical hardware (or
remote) sucks for occasional use.

Rich.

Packages/b/bzip2-1.0.6-8.fc19.ppc64p7.rpm
Packages/b/bzip2-devel-1.0.6-8.fc19.ppc64p7.rpm
Packages/b/bzip2-libs-1.0.6-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-2.1.26-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-devel-2.1.26-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-gssapi-2.1.26-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-lib-2.1.26-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-md5-2.1.26-8.fc19.ppc64p7.rpm
Packages/c/cyrus-sasl-plain-2.1.26-8.fc19.ppc64p7.rpm
Packages/g/glibc-2.17-4.fc19.ppc64p7.rpm
Packages/g/glibc-common-2.17-4.fc19.ppc64p7.rpm
Packages/g/glibc-devel-2.17-4.fc19.ppc64p7.rpm
Packages/g/glibc-headers-2.17-4.fc19.ppc64p7.rpm
Packages/h/httpd-2.4.4-6.fc19.ppc64p7.rpm
Packages/h/httpd-tools-2.4.4-6.fc19.ppc64p7.rpm
Packages/k/kernel-3.9.5-301.fc19.ppc64p7.rpm
Packages/k/kernel-bootwrapper-3.9.5-301.fc19.ppc64p7.rpm
Packages/k/kernel-devel-3.9.5-301.fc19.ppc64p7.rpm
Packages/k/kernel-headers-3.9.5-301.fc19.ppc64p7.rpm
Packages/k/kernel-modules-extra-3.9.5-301.fc19.ppc64p7.rpm
Packages/l/libxml2-2.9.1-1.fc19.ppc64p7.rpm
Packages/l/libxml2-devel-2.9.1-1.fc19.ppc64p7.rpm
Packages/l/libxml2-python-2.9.1-1.fc19.ppc64p7.rpm
Packages/m/mariadb-5.5.31-1.fc19.ppc64p7.rpm
Packages/m/mariadb-embedded-5.5.31-1.fc19.ppc64p7.rpm
Packages/m/mariadb-libs-5.5.31-1.fc19.ppc64p7.rpm
Packages/m/mariadb-server-5.5.31-1.fc19.ppc64p7.rpm
Packages/m/mod_ssl-2.4.4-6.fc19.ppc64p7.rpm
Packages/o/openssl-1.0.1e-4.fc19.ppc64p7.rpm
Packages/o/openssl-devel-1.0.1e-4.fc19.ppc64p7.rpm
Packages/o/openssl-libs-1.0.1e-4.fc19.ppc64p7.rpm
Packages/p/pam-1.1.6-11.fc19.1.ppc64p7.rpm
Packages/p/pam-devel-1.1.6-11.fc19.1.ppc64p7.rpm
Packages/p/pcre-8.32-7.fc19.ppc64p7.rpm
Packages/p/pcre-devel-8.32-7.fc19.ppc64p7.rpm
Packages/p/php-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-bcmath-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-cli-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-common-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-devel-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-gd-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-imap-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-ldap-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-mbstring-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-mcrypt-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-mysqlnd-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-pdo-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-pgsql-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-process-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-soap-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/php-xml-5.5.0-1.fc19.ppc64p7.rpm
Packages/p/postgresql-9.2.4-1.fc19.ppc64p7.rpm
Packages/p/postgresql-libs-9.2.4-1.fc19.ppc64p7.rpm
Packages/p/postgresql-server-9.2.4-1.fc19.ppc64p7.rpm
Packages/p/python-2.7.5-1.fc19.ppc64p7.rpm
Packages/p/python-devel-2.7.5-1.fc19.ppc64p7.rpm
Packages/p/python-libs-2.7.5-1.fc19.ppc64p7.rpm
Packages/p/python3-3.3.2-2.fc19.ppc64p7.rpm
Packages/p/python3-libs-3.3.2-2.fc19.ppc64p7.rpm
Packages/s/sendmail-8.14.7-1.fc19.ppc64p7.rpm
Packages/t/tkinter-2.7.5-1.fc19.ppc64p7.rpm
Packages/x/xz-5.1.2-4alpha.fc19.ppc64p7.rpm
Packages/x/xz-devel-5.1.2-4alpha.fc19.ppc64p7.rpm
Packages/x/xz-libs-5.1.2-4alpha.fc19.ppc64p7.rpm
Packages/z/zlib-1.2.7-10.fc19.ppc64p7.rpm
Packages/z/zlib-devel-1.2.7-10.fc19.ppc64p7.rpm


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

[Richard W.M. Jones]

On Fri, Aug 30, 2013 at 01:09:23PM +1000, Tony Breeds wrote:
>  You can try chaning the -cpu to 970 or other options.  F19 installed
> on
>  my G5 so 970 /should/ work. 
-cpu 970 doesn't work.  It hangs at "returning from prom_init"
(ie. it never gets into the kernel).

On the other hand, should I be using -cpu 970 and -M pseries together?
This whole business of ppc64 machine types is incredibly confusing
(ARM too ...).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)