qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Richard Henderson <richard.henderson@linaro.org>,
	thierry.briot@gmail.com
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Virtualizing HP PA-RISC unix station other than B160L
Date: Sun, 5 Sep 2021 22:32:08 +0200	[thread overview]
Message-ID: <2db9d592-8115-1206-68e4-71a9fd25b45d@gmx.de> (raw)
In-Reply-To: <CAFXwXrmt-u9iO_xY3y=ite1rPsvdm77w_s3Fw1G5C=fag0KP1w@mail.gmail.com>

Hi Thierry,

On 9/5/21 3:24 PM, Richard Henderson wrote:
> On Sun, 5 Sep 2021, 10:30 , <thierry.briot@gmail.com <mailto:thierry.briot@gmail.com>> wrote:
> For my company (Nexter Systems, France), I am using qemu-system-hppa
> for virtualizing HP PA-RISC workstations. That works well. You have
> made a very good job !

Thanks.

> But my machines are other than B160L (for example B180L), and I have
> to completely reinstall HP-UX on each emulated machine.
> If I do an iso system disk image of my B180L, this iso isn't bootable
> on qemu-system-hppa.
>
> Thus, my questions are :
>
> * Is it planned to emulate other HP unix workstations than B160L (for
> example B180L) ?

Maybe at some point a 64-bit capable system, e.g. C3000, and maybe
an older 32-bit system, e.g. 715/64.
For the 64bit system additions to the emulated firmware and additional
64-bit qemu support is necessary,
and for the 715/64 we need an additional NCR710 SCSI driver.
Both are lots of work.

The B180L is exactly the same as the B160L, with just a faster CPU:
https://www.openpa.net/systems/hp-visualize_b132l_b160l_b180l.html

> * Or, what changes should I make to my iso image to do it usable ? If
> I replace the /boot filesystem of the B180L image with the B160L one,
> I get a kernel panic at boot time.

I don't know HP-UX so well. I could imagine that your physical machines
have different SCSI controller cards which are used by HP-UX, and which
aren't emulated in qemu yet. That's maybe why qemu can't boot your already
installed images.
If you post the output I maybe can give more info.

> Helge is the one that did all the hw support, I just did the CPU.
> There are no real plans to do another machine. I'm not familiar with
> the specs between the HP machines to know how much work that would
> be.

There is a very good overview of the various HP machines at openPA:
https://www.openpa.net/systems/

Helge


  reply	other threads:[~2021-09-05 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00d401d7a230$56842630$038c7290$@gmail.com>
2021-09-05 13:24 ` Virtualizing HP PA-RISC unix station other than B160L Richard Henderson
2021-09-05 20:32   ` Helge Deller [this message]
2021-09-05 22:38     ` thierry.briot
2021-09-06  3:49       ` Warner Losh

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=2db9d592-8115-1206-68e4-71a9fd25b45d@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thierry.briot@gmail.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).