From: Helge Deller <deller@gmx.de>
To: Bruno Haible <bruno@clisp.org>,
"Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: "René Rebe" <rene@t2-project.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: hppa64 Linux in QEMU
Date: Fri, 29 Dec 2023 17:53:02 +0100 [thread overview]
Message-ID: <27c830f0-36b9-4e7d-8540-dbf2fe415b5c@gmx.de> (raw)
In-Reply-To: <3574571.ElGaqSPkdT@nimes>
On 12/29/23 17:15, Bruno Haible wrote:
> Nelson H. F. Beebe wrote:
>> I'm going to look at building a VM for the 64-bit variant.
>
> I tried it, but couldn't complete the installation.
>
> The only Linux distro with HPPA64 binaries that I know of
Debian and Gentoo can install a 64-bit kernel as well.
The userspace binaries are 32-bit on ALL distributions, since
we don't have a 64-bit glibc yet.
> I don't want to build everything myself — is T2-SDE. Here's what I tried:
>
> Download: http://dl.t2sde.org/binary/2023/t2-23.12-hppa64-minimal-firefox-gcc-glibc.iso
>
> Use qemu-8.2.0 (because it support 64-bit CPUs)
> % PATH=$HOME/inst-qemu/8.2.0/bin:$PATH
>
>
> Create empty disk:
> % qemu-img create -f qcow2 t2sde.qcow2 10G
>
> Pull kernel and initrd out of the installation CD:
> % sudo mount -r -t iso9660 -o loop t2-23.12-hppa64-minimal-firefox-gcc-glibc.iso /mnt
> % mkdir boot
> % cp -a /mnt/boot/* boot/
> % sudo umount /mnt
>
>
> Run installer:
> Doc says: Start 64-bit machine with "-machine C3700" and 32-bit CPU with "-machine B160L"
> % machine_args="-M C3700 -m 256"
> % disk_args="-drive file=t2sde.qcow2,format=qcow2,id=hd0"
> % net_args=""
> % display_args="-nographic"
> % common_args="$machine_args $disk_args $net_args $display_args"
> % qemu-system-hppa $common_args \
> -kernel boot/vmlinux-6.6.7-t2 -initrd boot/initrd-6.6.7-t2 \
> -drive file=t2-23.12-hppa64-minimal-firefox-gcc-glibc.iso,if=scsi,bus=0,unit=2,media=cdrom
>
> Serial terminal: <Enter> or console
> # install
> Partition:
> fdisk
> n p 1 <Enter> <Enter>
> w
> On /dev/sda1: Create filesystem of type ext3 [why not ext4?] with mount point /
> --------------------------------------------------- HERE it hangs
> handle_break: 2921306 callbacks suppressed
> handle_break: 2923362 callbacks suppressed
> handle_break: 2919859 callbacks suppressed
> handle_break: 2944852 callbacks suppressed
> handle_break: 2933621 callbacks suppressed
> handle_break: 2948476 callbacks suppressed
> handle_break: 2952380 callbacks suppressed
> handle_break: 2869013 callbacks suppressed
> handle_break: 2800234 callbacks suppressed
> handle_break: 2908121 callbacks suppressed
> handle_break: 2825626 callbacks suppressed
> handle_break: 2899328 callbacks suppressed
> handle_break: 2916401 callbacks suppressed
> handle_break: 2886012 callbacks suppressed
> handle_break: 2942498 callbacks suppressed
> handle_break: 2925950 callbacks suppressed
> handle_break: 2923203 callbacks suppressed
> ...
> ---------------------------------------------------
>
> Any ideas, what one could try, to get further?
There still seems a problem in qemu when running a 64-bit kernel.
This shows up when kernel modules are used, esp. e.g. with ext4.
As a work-around for now I suggest to use the 32-bit kernel and do the
installation. Then, after installation, install a 64-bit kernel
(a manually built one which does not use kernel modules) and boot
that one.
Beside that, at least Debian will install a 32-bit kernel by default
since the SeaBIOS-hppa firmware is still 32-bit only and will report
back to the installers to "install a 32-bit kernel".
This will change as soon as I can come up with a 64-bit SeaBIOS-hppa,
but currently I'll try to focus on fixing the 64-bit kernel (modules)
issue and fixing booting 32-bit HP-UX.
Helge
next parent reply other threads:[~2023-12-29 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CMM.0.95.0.1703805969.beebe@gamma.math.utah.edu>
[not found] ` <3574571.ElGaqSPkdT@nimes>
2023-12-29 16:53 ` Helge Deller [this message]
2023-12-29 18:02 ` hppa64 Linux in QEMU Bruno Haible
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=27c830f0-36b9-4e7d-8540-dbf2fe415b5c@gmx.de \
--to=deller@gmx.de \
--cc=beebe@math.utah.edu \
--cc=bruno@clisp.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rene@t2-project.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 read-only IMAP folder(s) and NNTP newsgroup(s).