novaBBS - comp.os.vms - OpenVMS x86 and qemu/kvm

OpenVMS x86 and qemu/kvm - boot problems.

<mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com>

https://www.novabbs.com/computers/article-flat.php?id=27479&group=comp.os.vms#27479

Path: i2pn2.org!i2pn.org!eternal-september.org!feeder.eternal-september.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!kishost2.serverpowered.net!not-for-mail
From: fsword...@gmail.com (Timothy Stark)
Newsgroups: comp.os.vms
Subject: OpenVMS x86 and qemu/kvm - boot problems.
Date: Wed, 12 Apr 2023 08:49:53 -0400
Lines: 17
Message-ID: <mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com>
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Injection-Info: solani.org;
logging-data="3556191"; mail-complaints-to="abuse@news.solani.org"
To: "comp.os.vms to email gateway" <info-vax@rbnsn.com>
Cancel-Lock: sha1:oWq4/J2qZknhYI8F5HVkPr0bb5g=
X-Spam-Flag: NO
X-Content-Filtered-By: Mailman/MimeDel 2.1.39
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112; t=1681303806; x=1683895806;
h=to:subject:message-id:date:from:mime-version:x-gm-message-state
:from:to:cc:subject:date:message-id:reply-to;
bh=9BwRSoryEt2/xjhaVSSFbbBrAYcX3m/LF/7BHbg/DDU=;
b=kVgCWBsEfGLmwrvA3lnwX61ZVecrMYq7UDGSMC73laXBVsXlJaDpgKP478oCg5BJ9s
XZ2LVFUYfEhQrOx3++2wOBDQz6mTcgsMA1/z/bSyPRdaUjZOfgSZBmt8LvmMZzOC6bSX
LykFMFjJ8H+uRNjMXB4KEcBlnIMPgM0r9nKroSb+0xMDgw8d2ez9v2F1zhU5cehv9l0C
p3tEGe70DOuJqK0DvxfWV1+4BFIlEaMTdbEyXafelK+nCueieJk34LAA3/bgZKzp1hhH
B7ybgXS97qmD98wptQgqn3l/KihnG2C0RtvFIOjYM+bCWcSSGroofFQ2GnxShdyS8kS5
2mvA==
Precedence: list
X-Mailman-Version: 2.1.39
X-Received: by 2002:a63:1905:0:b0:507:68f8:4369 with SMTP id
z5-20020a631905000000b0050768f84369mr3830570pgl.12.1681303804559; Wed, 12 Apr
2023 05:50:04 -0700 (PDT)
X-Ham-Report: Spam detection software,
running on the system "kishost2.serverpowered.net",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
root\@localhost for details.
Content preview: I watched a video clip on YouTube about installing OpenVMS
on x86_64. I followed instructions from that. It did not work well. He did
not show how to set bridge br0 for kvm. It crashed during booting. I got
two error messages said unable determine serial number in HWPB block and bug
check message said that high IPL during pagefault exception. I think that
I got wrong UEFI [...]
Content analysis details: (3.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.0 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends
in digit [fsword007[at]gmail.com]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider [fsword007[at]gmail.com]
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from
envelope-from domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
X-Spam-Bar: +++
X-Spam-Status: No, score=3.1
X-BeenThere: info-vax@rbnsn.com
X-Spam-Score: 31
List-Archive: <http://rbnsn.com/pipermail/info-vax_rbnsn.com/>
X-Google-Smtp-Source: AKy350YnOHJWoZWGryjp4dHIJK6CgXPFEDo4/iiMxpsgRAIdWp0hpx6hop9fYqFMgad1hQrPVg0LWdEABLxhOjrIteI=
List-Id: "comp.os.vms to email gateway" <info-vax.rbnsn.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20221208; t=1681303806; x=1683895806;
h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
:date:message-id:reply-to;
bh=9BwRSoryEt2/xjhaVSSFbbBrAYcX3m/LF/7BHbg/DDU=;
b=WsWGv1xGoXIQ0uWZXlseNlpGfBoAXGa7N1Jdd7ytjjMGHt9jmxTQRyEYJxh/on72ZT
oNwe4bARk5RXDclaZBsTRQedkqGnu79vI+Jc8HJosZveMWt9aCmWMlFdCnSIvpgYwlQl
CC7pzLReUdYoPm9TDda+wtgmWA/H6EP8fPvqBr+8tGRv7AgewY4q2zg6JJq5B/h6pWmw
g5+rFUlQ9jNxdThoQF2C88WoiBii5s7NU69LKlfOqXyL0dkPMaBwzV3UkAy6TaHF6e2D
00y5pD2XAGnSxsb+1+3x4a+ncyGgsiFSEzpSqylwl4fkCp72Vj782qiikTSozqGWdkf7
WFYQ==
X-User-ID: eJwNxMEBwCAIA8CVQCSh4zRF9h/B3uMy4Pi4kdg5OTFtNn3sMbEm0EJKyjfkh3SylmvW/u+oCyflESY=
X-Mailman-Original-Message-ID: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
List-Subscribe: <http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com>,
<mailto:info-vax-request@rbnsn.com?subject=subscribe>
List-Post: <mailto:info-vax@rbnsn.com>
List-Help: <mailto:info-vax-request@rbnsn.com?subject=help>
X-Gm-Message-State: AAQBX9euD9P0u3phgsdIneiSShcPc340CQK6aOd0LXDbUmse/ehF6HMd
E7hkHLITbE0kDq2iRQuTrP6INIk1algh11Cy6OLo/CpM
List-Unsubscribe: <http://rbnsn.com/mailman/options/info-vax_rbnsn.com>,
<mailto:info-vax-request@rbnsn.com?subject=unsubscribe>

by: Timothy Stark - Wed, 12 Apr 2023 12:49 UTC

I watched a video clip on YouTube about installing OpenVMS on x86_64. I
followed instructions from that. It did not work well. He did not show how
to set bridge br0 for kvm.

It crashed during booting. I got two error messages said unable determine
serial number in HWPB block and bug check message said that high IPL during
pagefault exception. I think that I got wrong UEFI firmware from
/usr/share/qemu. Does anyone have good UEFI firmware?

I tried to configure br0 but I got error said that they can't find bridge
file (-net bridge,br0). Does anyone have configuration info for setting
br0 device on Ubuntu 22.10?

I successfully installed OpenVMS on virtual box under windows 11. It
recognized 82450EM and assigned EIA0 to that. However it can't access the
Internet so that I can't upload layered products into. Does anyone have
any good network configuration for VirtualBox 7.x?

Re: OpenVMS x86 and qemu/kvm - boot problems.

<8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=27483&group=comp.os.vms#27483

copy link Newsgroups: comp.os.vms

Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!Xl.tags.giganews.com!local-1.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 12 Apr 2023 15:51:47 +0000
Sender: Dennis Boone <drb@yagi.h-net.org>
From: drb...@ihatespam.msu.edu (Dennis Boone)
Subject: Re: OpenVMS x86 and qemu/kvm - boot problems.
Newsgroups: comp.os.vms
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com> <mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com>
User-Agent: tin/2.6.1-20211226 ("Convalmore") (FreeBSD/13.1-RELEASE-p2 (amd64))
Message-ID: <8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
Date: Wed, 12 Apr 2023 15:51:47 +0000
Lines: 22
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-banzNOGAdXt9mGxmIjCVNWfCIPveDyyezeBDM+MV10eK4qXMcDvkuhWRGkRl5lCuwmdaXaqExzDEpzJ!2ktSOaYaF480XSzHiedKkIqp6XaDQVSBE3Zpr6X3iRuha7ivOXAGKo+Y80lG1VspjZUNcjU=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40

by: Dennis Boone - Wed, 12 Apr 2023 15:51 UTC

> It crashed during booting. I got two error messages said unable determine
> serial number in HWPB block and bug check message said that high IPL during
> pagefault exception. I think that I got wrong UEFI firmware from
> /usr/share/qemu. Does anyone have good UEFI firmware?

I have 2022.11-6 of the ovmf package and qemu 7.2.on a Debian Sid box.

ozymandias 1643 # sha256sum /usr/share/ovmf/OVMF.fd
d996e65015d52ad21ec4014c4f6f80038dbfd63463106e39eb66b81282ab8dbf /usr/share/ovmf/OVMF.fd

-rw-r--r-- 1 root root 2097152 mar 5 15:36 OVMF.fd

Make sure you're not trying to boot in secure mode.

I get the serial number message too, but it doesn't seem to prevent
booting and installation.

I can reliably induce a crash (high IPL, page fault) by trying to
mount the ISO image. I'm also getting random crashes I haven't
diagnosed yet. I.e. ymmv.

Re: OpenVMS x86 and qemu/kvm - boot problems.

<0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=27672&group=comp.os.vms#27672

copy link Newsgroups: comp.os.vms

X-Received: by 2002:ac8:5713:0:b0:3ef:3541:4359 with SMTP id 19-20020ac85713000000b003ef35414359mr542970qtw.1.1682007107553;
Thu, 20 Apr 2023 09:11:47 -0700 (PDT)
X-Received: by 2002:a05:620a:8582:b0:746:75f7:c8a2 with SMTP id
pf2-20020a05620a858200b0074675f7c8a2mr667907qkn.4.1682007107013; Thu, 20 Apr
2023 09:11:47 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.vms
Date: Thu, 20 Apr 2023 09:11:46 -0700 (PDT)
In-Reply-To: <8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7c:d0ca:6000:d9cc:11eb:d832:e6ba;
posting-account=Jc8lggoAAADpqbPc4tHcztc81YNnWd1x
NNTP-Posting-Host: 2a02:c7c:d0ca:6000:d9cc:11eb:d832:e6ba
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
<mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com> <8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com>
Subject: Re: OpenVMS x86 and qemu/kvm - boot problems.
From: iai...@issinoho.com (issinoho)
Injection-Date: Thu, 20 Apr 2023 16:11:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2765

by: issinoho - Thu, 20 Apr 2023 16:11 UTC

On Wednesday, 12 April 2023 at 16:51:58 UTC+1, Dennis Boone wrote:
> > It crashed during booting. I got two error messages said unable determine
> > serial number in HWPB block and bug check message said that high IPL during
> > pagefault exception. I think that I got wrong UEFI firmware from
> > /usr/share/qemu. Does anyone have good UEFI firmware?
> I have 2022.11-6 of the ovmf package and qemu 7.2.on a Debian Sid box.
>
> ozymandias 1643 # sha256sum /usr/share/ovmf/OVMF.fd
> d996e65015d52ad21ec4014c4f6f80038dbfd63463106e39eb66b81282ab8dbf /usr/share/ovmf/OVMF.fd
>
> -rw-r--r-- 1 root root 2097152 mar 5 15:36 OVMF.fd
>
> Make sure you're not trying to boot in secure mode.
>
> I get the serial number message too, but it doesn't seem to prevent
> booting and installation.
>
> I can reliably induce a crash (high IPL, page fault) by trying to
> mount the ISO image. I'm also getting random crashes I haven't
> diagnosed yet. I.e. ymmv.
>
> De
Today I've finally got this working on QEMU/KVM using the virt-manager GUI rather than an enormous command line of switches. Everything work perfectly, albeit I'm running in NAT mode. Bridging looks to be a world of pain so I'm next going to look at NAT forwarding through the Ubuntu host - will report back.

X86VMS::sh cpu

System: X86VMS, QEMU Standard PC (Q35 + ICH9, 2009)

Re: OpenVMS x86 and qemu/kvm - boot problems.

<u1s0i6$i9vb$1@dont-email.me>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=27673&group=comp.os.vms#27673

copy link Newsgroups: comp.os.vms

Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: new...@cct-net.co.uk (Chris Townley)
Newsgroups: comp.os.vms
Subject: Re: OpenVMS x86 and qemu/kvm - boot problems.
Date: Thu, 20 Apr 2023 19:33:41 +0100
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <u1s0i6$i9vb$1@dont-email.me>
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
<mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com>
<8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
<0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 20 Apr 2023 18:33:42 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="c138407f22640d08ddca967beb33bfac";
logging-data="600043"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18/U60mDkoMh6TnmNdyNMcbNNGtxHKBprY="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.10.0
Cancel-Lock: sha1:6Mbq6/5GzsQScKag4xfDPha3Y68=
In-Reply-To: <0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com>
Content-Language: en-GB

by: Chris Townley - Thu, 20 Apr 2023 18:33 UTC

On 20/04/2023 17:11, issinoho wrote:
> On Wednesday, 12 April 2023 at 16:51:58 UTC+1, Dennis Boone wrote:
>>> It crashed during booting. I got two error messages said unable determine
>>> serial number in HWPB block and bug check message said that high IPL during
>>> pagefault exception. I think that I got wrong UEFI firmware from
>>> /usr/share/qemu. Does anyone have good UEFI firmware?
>> I have 2022.11-6 of the ovmf package and qemu 7.2.on a Debian Sid box.
>>
>> ozymandias 1643 # sha256sum /usr/share/ovmf/OVMF.fd
>> d996e65015d52ad21ec4014c4f6f80038dbfd63463106e39eb66b81282ab8dbf /usr/share/ovmf/OVMF.fd
>>
>> -rw-r--r-- 1 root root 2097152 mar 5 15:36 OVMF.fd
>>
>> Make sure you're not trying to boot in secure mode.
>>
>> I get the serial number message too, but it doesn't seem to prevent
>> booting and installation.
>>
>> I can reliably induce a crash (high IPL, page fault) by trying to
>> mount the ISO image. I'm also getting random crashes I haven't
>> diagnosed yet. I.e. ymmv.
>>
>> De
> Today I've finally got this working on QEMU/KVM using the virt-manager GUI rather than an enormous command line of switches. Everything work perfectly, albeit I'm running in NAT mode. Bridging looks to be a world of pain so I'm next going to look at NAT forwarding through the Ubuntu host - will report back.
>
> X86VMS::sh cpu
>
> System: X86VMS, QEMU Standard PC (Q35 + ICH9, 2009)

Much easier in the GUI, bit it needs too many tweaks.

A bridge network is pretty easy to set up. I have a second NIC (USB)
that I have bridged to. Setup took me a while, but when I recreated my
KVM/QEMU VM I got it working fine just by selecting Bridged, and
choosing the br0 device I had previously created.

Sadly I didn't note the exact way I created a br0 device on the host,
but plenty of examples on the net.

Have you managed to get he serial console accessible over ssh? So far I
have been stuck with the Virtual Machine builder serial console, which
is pretty carp.

--
Chris

Re: OpenVMS x86 and qemu/kvm - boot problems.

<df7f4e22-f3c1-4ec0-9c62-08ede89ced58n@googlegroups.com>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=27674&group=comp.os.vms#27674

copy link Newsgroups: comp.os.vms

X-Received: by 2002:ac8:5a54:0:b0:3ef:3da0:5de7 with SMTP id o20-20020ac85a54000000b003ef3da05de7mr852251qta.12.1682026026215;
Thu, 20 Apr 2023 14:27:06 -0700 (PDT)
X-Received: by 2002:a05:620a:149a:b0:74e:17da:5d7d with SMTP id
w26-20020a05620a149a00b0074e17da5d7dmr596244qkj.13.1682026025958; Thu, 20 Apr
2023 14:27:05 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!newsfeed.hasname.com!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.vms
Date: Thu, 20 Apr 2023 14:27:05 -0700 (PDT)
In-Reply-To: <u1s0i6$i9vb$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7c:d0ca:6000:85bb:6c56:89f7:64c6;
posting-account=Jc8lggoAAADpqbPc4tHcztc81YNnWd1x
NNTP-Posting-Host: 2a02:c7c:d0ca:6000:85bb:6c56:89f7:64c6
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
<mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com> <8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
<0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com> <u1s0i6$i9vb$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <df7f4e22-f3c1-4ec0-9c62-08ede89ced58n@googlegroups.com>
Subject: Re: OpenVMS x86 and qemu/kvm - boot problems.
From: iai...@issinoho.com (issinoho)
Injection-Date: Thu, 20 Apr 2023 21:27:06 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4105

by: issinoho - Thu, 20 Apr 2023 21:27 UTC

On Thursday, 20 April 2023 at 19:33:46 UTC+1, Chris Townley wrote:
> On 20/04/2023 17:11, issinoho wrote:
> > On Wednesday, 12 April 2023 at 16:51:58 UTC+1, Dennis Boone wrote:
> >>> It crashed during booting. I got two error messages said unable determine
> >>> serial number in HWPB block and bug check message said that high IPL during
> >>> pagefault exception. I think that I got wrong UEFI firmware from
> >>> /usr/share/qemu. Does anyone have good UEFI firmware?
> >> I have 2022.11-6 of the ovmf package and qemu 7.2.on a Debian Sid box.
> >>
> >> ozymandias 1643 # sha256sum /usr/share/ovmf/OVMF.fd
> >> d996e65015d52ad21ec4014c4f6f80038dbfd63463106e39eb66b81282ab8dbf /usr/share/ovmf/OVMF.fd
> >>
> >> -rw-r--r-- 1 root root 2097152 mar 5 15:36 OVMF.fd
> >>
> >> Make sure you're not trying to boot in secure mode.
> >>
> >> I get the serial number message too, but it doesn't seem to prevent
> >> booting and installation.
> >>
> >> I can reliably induce a crash (high IPL, page fault) by trying to
> >> mount the ISO image. I'm also getting random crashes I haven't
> >> diagnosed yet. I.e. ymmv.
> >>
> >> De
> > Today I've finally got this working on QEMU/KVM using the virt-manager GUI rather than an enormous command line of switches. Everything work perfectly, albeit I'm running in NAT mode. Bridging looks to be a world of pain so I'm next going to look at NAT forwarding through the Ubuntu host - will report back.
> >
> > X86VMS::sh cpu
> >
> > System: X86VMS, QEMU Standard PC (Q35 + ICH9, 2009)
> Much easier in the GUI, bit it needs too many tweaks.
>
> A bridge network is pretty easy to set up. I have a second NIC (USB)
> that I have bridged to. Setup took me a while, but when I recreated my
> KVM/QEMU VM I got it working fine just by selecting Bridged, and
> choosing the br0 device I had previously created.
>
> Sadly I didn't note the exact way I created a br0 device on the host,
> but plenty of examples on the net.
>
> Have you managed to get he serial console accessible over ssh? So far I
> have been stuck with the Virtual Machine builder serial console, which
> is pretty carp.
>
> --
> Chris
On NAT port forwarding, this works beautifully, https://blog.wirelessmoves.com/2022/04/bare-metal-cloud-part-2-kvm-and-nat-port-forwarding.html

On console, I'm using 'virsh console vm-name' just enough to get the OpenVMS networking up then using SSH from that point on, initially from the host, but once you use that ^^^ script from anywhere on your network.

Re: OpenVMS x86 and qemu/kvm - boot problems.

<359a8b50-3d8e-4f11-8960-bac60e63f5fen@googlegroups.com>

copy mid

https://www.novabbs.com/computers/article-flat.php?id=27677&group=comp.os.vms#27677

copy link Newsgroups: comp.os.vms

X-Received: by 2002:a05:620a:1479:b0:74e:37dd:61a6 with SMTP id j25-20020a05620a147900b0074e37dd61a6mr239205qkl.13.1682070498613;
Fri, 21 Apr 2023 02:48:18 -0700 (PDT)
X-Received: by 2002:a05:620a:148a:b0:74d:f7af:b238 with SMTP id
w10-20020a05620a148a00b0074df7afb238mr889663qkj.14.1682070498316; Fri, 21 Apr
2023 02:48:18 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.vms
Date: Fri, 21 Apr 2023 02:48:17 -0700 (PDT)
In-Reply-To: <df7f4e22-f3c1-4ec0-9c62-08ede89ced58n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=90.196.187.205; posting-account=Jc8lggoAAADpqbPc4tHcztc81YNnWd1x
NNTP-Posting-Host: 90.196.187.205
References: <CACk2-37raJ+xqvxWycza_b6Sk8CU0iWhBTivMhrnCb3X24j54A@mail.gmail.com>
<mailman.4.1681303848.29276.info-vax_rbnsn.com@rbnsn.com> <8kednbMRV7cOTqv5nZ2dnZfqn_SdnZ2d@giganews.com>
<0c9ba8ce-f2a5-42b3-8bb6-97b98a875e2an@googlegroups.com> <u1s0i6$i9vb$1@dont-email.me>
<df7f4e22-f3c1-4ec0-9c62-08ede89ced58n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <359a8b50-3d8e-4f11-8960-bac60e63f5fen@googlegroups.com>
Subject: Re: OpenVMS x86 and qemu/kvm - boot problems.
From: iai...@issinoho.com (issinoho)
Injection-Date: Fri, 21 Apr 2023 09:48:18 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4523

by: issinoho - Fri, 21 Apr 2023 09:48 UTC

On Thursday, 20 April 2023 at 22:27:07 UTC+1, issinoho wrote:
> On Thursday, 20 April 2023 at 19:33:46 UTC+1, Chris Townley wrote:
> > On 20/04/2023 17:11, issinoho wrote:
> > > On Wednesday, 12 April 2023 at 16:51:58 UTC+1, Dennis Boone wrote:
> > >>> It crashed during booting. I got two error messages said unable determine
> > >>> serial number in HWPB block and bug check message said that high IPL during
> > >>> pagefault exception. I think that I got wrong UEFI firmware from
> > >>> /usr/share/qemu. Does anyone have good UEFI firmware?
> > >> I have 2022.11-6 of the ovmf package and qemu 7.2.on a Debian Sid box.
> > >>
> > >> ozymandias 1643 # sha256sum /usr/share/ovmf/OVMF.fd
> > >> d996e65015d52ad21ec4014c4f6f80038dbfd63463106e39eb66b81282ab8dbf /usr/share/ovmf/OVMF.fd
> > >>
> > >> -rw-r--r-- 1 root root 2097152 mar 5 15:36 OVMF.fd
> > >>
> > >> Make sure you're not trying to boot in secure mode.
> > >>
> > >> I get the serial number message too, but it doesn't seem to prevent
> > >> booting and installation.
> > >>
> > >> I can reliably induce a crash (high IPL, page fault) by trying to
> > >> mount the ISO image. I'm also getting random crashes I haven't
> > >> diagnosed yet. I.e. ymmv.
> > >>
> > >> De
> > > Today I've finally got this working on QEMU/KVM using the virt-manager GUI rather than an enormous command line of switches. Everything work perfectly, albeit I'm running in NAT mode. Bridging looks to be a world of pain so I'm next going to look at NAT forwarding through the Ubuntu host - will report back.
> > >
> > > X86VMS::sh cpu
> > >
> > > System: X86VMS, QEMU Standard PC (Q35 + ICH9, 2009)
> > Much easier in the GUI, bit it needs too many tweaks.
> >
> > A bridge network is pretty easy to set up. I have a second NIC (USB)
> > that I have bridged to. Setup took me a while, but when I recreated my
> > KVM/QEMU VM I got it working fine just by selecting Bridged, and
> > choosing the br0 device I had previously created.
> >
> > Sadly I didn't note the exact way I created a br0 device on the host,
> > but plenty of examples on the net.
> >
> > Have you managed to get he serial console accessible over ssh? So far I
> > have been stuck with the Virtual Machine builder serial console, which
> > is pretty carp.
> >
> > --
> > Chris
> On NAT port forwarding, this works beautifully, https://blog.wirelessmoves.com/2022/04/bare-metal-cloud-part-2-kvm-and-nat-port-forwarding.html
>
> On console, I'm using 'virsh console vm-name' just enough to get the OpenVMS networking up then using SSH from that point on, initially from the host, but once you use that ^^^ script from anywhere on your network.
This is starting to take shape nicely. VM now autostarting on Ubuntu with persistent firewall rules port forwarding SSH and HTTP, and X sessions tunneling nicely back to a Windows desktop.

Breadth-first search is the bulldozer of science. -- Randy Goebel

computers / comp.os.vms / OpenVMS x86 and qemu/kvm - boot problems.

Subject	Author
OpenVMS x86 and qemu/kvm - boot problems.	Timothy Stark
Re: OpenVMS x86 and qemu/kvm - boot problems.	Dennis Boone
Re: OpenVMS x86 and qemu/kvm - boot problems.	issinoho
Re: OpenVMS x86 and qemu/kvm - boot problems.	Chris Townley
Re: OpenVMS x86 and qemu/kvm - boot problems.	issinoho
Re: OpenVMS x86 and qemu/kvm - boot problems.	issinoho