VSI said in their presentation of 2022 Accomplishments webinar that they hoped to have the x86 version added to the CLP sometime in the first quarter. They also said that if you enrolled in the CLP you would automatically get the access information. They only missed by 3 days. Today I got an email from VSI with instructions on how to log into their Service Portal and access the OpenVMS x86 V9.2-0 software kits. So now I'm busy downloading all the V9.2 OE files and updates, patches and layered and Open Source kits. This should be an exciting few days. I think I need some vacation days.

John H. Reinhardt

On Mon, 2023-04-03 at 15:56 -0500, John H Reinhardt wrote:
> VSI said in their presentation of 2022 Accomplishments webinar that
> they hoped to have the x86 version added to the CLP sometime in the
> first quarter.  They also said that if you enrolled in the CLP you
> would automatically get the access information.  They only missed by
> 3 days.  Today I got an email from VSI with instructions on how to
> log into their Service Portal and access the OpenVMS x86 V9.2-0
> software kits.  So now I'm busy downloading all the V9.2 OE files and
> updates, patches and layered and Open Source kits.  This should be an
> exciting few days.  I think I need some vacation days.

I applied for the Alpha licence last year. Can't wait for my e-mail!
--
Tactical Nuclear Kittens

On 03/04/2023 23:16, Single Stage to Orbit wrote:
> On Mon, 2023-04-03 at 15:56 -0500, John H Reinhardt wrote:
>> VSI said in their presentation of 2022 Accomplishments webinar that
>> they hoped to have the x86 version added to the CLP sometime in the
>> first quarter.  They also said that if you enrolled in the CLP you
>> would automatically get the access information.  They only missed by
>> 3 days.  Today I got an email from VSI with instructions on how to
>> log into their Service Portal and access the OpenVMS x86 V9.2-0
>> software kits.  So now I'm busy downloading all the V9.2 OE files and
>> updates, patches and layered and Open Source kits.  This should be an
>> exciting few days.  I think I need some vacation days.
>
> I applied for the Alpha licence last year. Can't wait for my e-mail!

Not that I can do anything until AMD is support is added, which they say
will be in V9.2-1

I went to the CLP registration page, but the X-86 option is still
disabled. Also haven't had any emails
--
Chris

> went to the CLP registration page, but the X-86 option is still
> disabled. Also haven't had any emails

Same here. I'm holding my breath. On the bright side, my Mac Pro
(Late 2013) collection is immediately suitable for use with VMware
Fusion Player ("Licensed for non-commercial use only.", priced
accordingly):

proe% sysctl -n machdep.cpu.brand_string
Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz

I got into a Field Test E9.2 trial (whose PAKs terminated
30-SEP-2022), so I have some confidence in V9.2 working at least as
well.

On 4/3/2023 9:08 PM, Steven Schweda wrote:
>> went to the CLP registration page, but the X-86 option is still
>> disabled. Also haven't had any emails
>
> Same here. I'm holding my breath. On the bright side, my Mac Pro
> (Late 2013) collection is immediately suitable for use with VMware
> Fusion Player ("Licensed for non-commercial use only.", priced
> accordingly):
>
> proe% sysctl -n machdep.cpu.brand_string
> Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
>
> I got into a Field Test E9.2 trial (whose PAKs terminated
> 30-SEP-2022), so I have some confidence in V9.2 working at least as
> well.

Interesting. The email I got had the subject of "x86 Community License Program Announcement", but inside it did say "Welcome to the VMS Software, Inc. OpenVMS on x86 Field Test Program!". I have a vague recollection of checking a box on some page saying I'd be interested in a field test, if so, it was quite a while ago. I was pretty early in registering for the CLP so maybe ey are going by order of registration. No clue.

John H. Reinhardt

> [...] No clue.

Same here. The E9.2 Field Test announcement seems to have been back
in early April '22, but:

[...] The field test is open to all VSI customers and partners
with current support contracts [...]

which seemed intended to exclude peons like me. However, in mid-May,
when I got my first Mac Pro (Late 2013), and found VMware Fusion Player,
I asked "info@" what the then-current availability status was. The
reply said "currently provided only to selected customers with a
contract with VSI who participate in the field test program.", and
suggested waiting for V9.2-1, which was (then) expected around
end-of-2022.

But someone did ask what I'd be doing if I did get access to the E9.2
Field Test stuff, and when I pointed to my web site, it was decided to
sneak me in despite my lack of official status.

But no one has begged me to take anything newer, so I've just been
biding my time like every other peon. (And setting the clock back on
the E9.2 system, as needed, when I want to do anything with it.)

On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
> > I applied for the Alpha licence last year. Can't wait for my e-
> > mail!
>
> Not that I can do anything until AMD is support is added, which they
> say will be in V9.2-1

That's interesting as I'm pretty sure I read that AMD is now supported.
--
Tactical Nuclear Kittens

On Tuesday, 4 April 2023 at 09:02:27 UTC+1, Single Stage to Orbit wrote:
> On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
> > > I applied for the Alpha licence last year. Can't wait for my e-
> > > mail!
> >
> > Not that I can do anything until AMD is support is added, which they
> > say will be in V9.2-1
> That's interesting as I'm pretty sure I read that AMD is now supported.
> --
> Tactical Nuclear Kittens

Big day - OpenVMS V9.2 on x86 installed and working on an Intel Core i7 running Windows 10 & VMware Workstation Player.
Flawless experience thus far. Many thanks to VSI - I truly never thought this would happen.
Going to move to Ubuntu & QEMU this weekend.

> Going to move to Ubuntu & QEMU this weekend.

I was not successful with QEMU yesterday. More tinkering required.
If you succeed, please share your recipe?

De

I enrolled in CLP but have not received license pak for x86 yet.

Tim

-----Original Message-----
From: Info-vax <info-vax-bounces@rbnsn.com> On Behalf Of John H Reinhardt
via Info-vax
Sent: Monday, April 3, 2023 4:56 PM
To: info-vax@rbnsn.com
Cc: John H Reinhardt <johnhreinhardt@thereinhardts.org>
Subject: [Info-vax] VSI Community License Program - x86

VSI said in their presentation of 2022 Accomplishments webinar that they
hoped to have the x86 version added to the CLP sometime in the first
quarter. They also said that if you enrolled in the CLP you would
automatically get the access information. They only missed by 3 days.
Today I got an email from VSI with instructions on how to log into their
Service Portal and access the OpenVMS x86 V9.2-0 software kits. So now I'm
busy downloading all the V9.2 OE files and updates, patches and layered and
Open Source kits. This should be an exciting few days. I think I need some
vacation days.

John H. Reinhardt
_______________________________________________
Info-vax mailing list
Info-vax@rbnsn.com
http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com

On Thu, 2023-04-06 at 08:56 -0400, fsword007@gmail.com wrote:
> I enrolled in CLP but have not received license pak for x86 yet.

I did, last year. Hoping they'll get to us soon.
--
Tactical Nuclear Kittens

Software and PAKs download and going to give it a go with Qemu.

Does anyone know if this release will run on a HPE DL380? I appreciate that the VSI focus is on hypervisors, but I saw that this hardware was apparently supported as of an earlier release. Of course, it would be even more fun to have this running on bare metal.

Andrew

On Thursday, 6 April 2023 at 01:46:35 UTC+1, Dennis Boone wrote:
> > Going to move to Ubuntu & QEMU this weekend.
> I was not successful with QEMU yesterday. More tinkering required.
> If you succeed, please share your recipe?

It's working fine for me on Ubuntu 20.04. The steps were:

1. Install Linux packages

$ sudo apt -y install bridge-utils cpu-checker libvirt-clients libvirt-daemon qemu qemu-kvm

2. Create disk images

qemu-img create hd1.img 64G

qemu-img create hd2.img 64G

Or whatever size you'd like...

3. Check KVM is operational

$ kvm-ok

4. Run Qemu

$ qemu-system-x86_64 -machine type=q35,accel=kvm -cpu host -smp 2 -m 8G -bios /usr/share/ovmf/OVMF.fd -serial pty -cdrom X86E921OE.ISO -drive file=hd1.img,index=0,media=disk,format=raw -drive file=hd2.img,index=1,media=disk,format=raw -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::5555-:22

5. Connect a terminal for console

$ screen /dev/pts/1 115200

(you may get a different device to use output when Qemu starts)

6. Follow the steps provided by VSI

https://docs.vmssoftware.com/vsi-openvms-x86-64-v92-installation-guide/#d0e32

Obviously ignoring the stuff about other hypervisors and with Qemu connecting console as per the previous step, instead of telnet.

7. Load the OE base licence

Did this via cut and paste into the console terminal.

8. Configure TCP/IP and OpenSSH

As per VSI instructions.

9. Copy the complete license file across

I renamed the .txt file to LIC.COM and then from Linux:

$ scp -P 5555 LIC.COM system@localhost:

10. Log in via SSH

$ ssh system@localhost -p 5555

11. Install all the licences etc.

Executed LIC.COM and then amused myself by running:

$ write sys$output f$getsyi("hw_name")

Also can't believe how fast everything runs on my Thinkpad! Kind of wish I could have it the other way round and boot VMS on it, then run Linux virtual machines.

Andrew

> It's working fine for me on Ubuntu 20.04. The steps were:

Thanks for this. Your incantations are slightly different than what
I was doing, so I have more things to try.

De

On Friday, 7 April 2023 at 03:21:05 UTC+1, Dennis Boone wrote:
> > It's working fine for me on Ubuntu 20.04. The steps were:
> Thanks for this. Your incantations are slightly different than what
> I was doing, so I have more things to try.
>
> De

Any tips on getting bridged networking properly configured on Ubuntu to support the VM?

On 2023-04-06, Andrew Back <andrew@carrierdetect.com> wrote:
> Software and PAKs download and going to give it a go with Qemu.
>

I wonder what the criteria is for people being offered access ?

I have also received nothing, but it's clear others have. (Not that it
matters at the moment anyway because I am currently way too busy with
other things. :-))

I wonder if VSI are manually selecting a few people to offer it to
before making it generally available to hobbyists ?

It's certainly not just being a member of the community program
because I've been registered there since HPE stopped offering
hobbyist licences.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On Friday, 7 April 2023 at 12:31:26 UTC+1, Simon Clubley wrote:
> On 2023-04-06, Andrew Back <and...@carrierdetect.com> wrote:
> > Software and PAKs download and going to give it a go with Qemu.
> >
> I wonder what the criteria is for people being offered access ?
>
> I have also received nothing, but it's clear others have. (Not that it
> matters at the moment anyway because I am currently way too busy with
> other things. :-))
>
> I wonder if VSI are manually selecting a few people to offer it to
> before making it generally available to hobbyists ?
>
> It's certainly not just being a member of the community program
> because I've been registered there since HPE stopped offering
> hobbyist licences.
>
> Simon.
>
> --
> Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
> Walking destinations on a map are further away than they appear.

VSI TCP/IP Services for OpenVMS x86_64 Version X6.0
on a VMware, Inc. VMware7,1 running OpenVMS E9.2-1

I've found the DHCP functionality pretty broken in this - I'm assuming it's TCPIP 6 rather than anything to do with x86, but who knows...

DHCP assigns the interface address and routing fine, but Bind doesn't get Configured or Enabled. Doing this manually gets things working, however as soon as a reboot kicks off the DHCP process again, Bind loses it's settings. Strangely, this also means that the result of a "show network" command displays an unconfigured IP stack even when it's working.

Moving to static IP fixes all of the above.

On 4/7/2023 10:52 AM, issinoho wrote:

> I've found the DHCP functionality pretty broken in this - I'm
> assuming it's TCPIP 6 rather than anything to do with x86, but who
> knows...
>
> DHCP assigns the interface address and routing fine, but Bind doesn't
> get Configured or Enabled. Doing this manually gets things working,
> however as soon as a reboot kicks off the DHCP process again, Bind
> loses it's settings. Strangely, this also means that the result of a
> "show network" command displays an unconfigured IP stack even when
> it's working.

Submit a trouble ticket

--
-- Rob

> I wonder what the criteria is for people being offered access ?

A somewhat tardy and incomplete explanation of what they is was
provided recently:

https://forum.vmssoftware.com/viewtopic.php?f=37&t=8595#p18051

issinoho <iain@issinoho.com> wrote:
> VSI TCP/IP Services for OpenVMS x86_64 Version X6.0
> on a VMware, Inc. VMware7,1 running OpenVMS E9.2-1
>
> I've found the DHCP functionality pretty broken in this - I'm assuming
> it's TCPIP 6 rather than anything to do with x86, but who knows...
>
> DHCP assigns the interface address and routing fine, but Bind doesn't get
> Configured or Enabled. Doing this manually gets things working, however
> as soon as a reboot kicks off the DHCP process again, Bind loses it's
> settings. Strangely, this also means that the result of a "show network"
> command displays an unconfigured IP stack even when it's working.
>
> Moving to static IP fixes all of the above.

Last night, I brought up TCPIP with DHCP, and was able to connect to the
system just fine. So at least very basic DHCP seemed to work. Having said
that one of the first things I did this morning was to convert to a Static
IP, as I have DNS setup for my home network.

I did have quite a bit of trouble getting everything setup, but everything
was related to configuring the VM to run VMS. I'm running on a VMware
cluster on ESXI 6.7, and my HP DL380 Gen7 is too old to run VMS. I ended up
having to use a "HP ProDesk 600 G1 SFF" that is one of the other two nodes
as the physical machine to run the VM. After that, the key issue I ran into
was configuring a Serial Port, and to do that I had to log into the ESXI
server directly, as I was unable to add a serial port to the VM from
vSphere.

Zane

Hi.

So, got the files downloaded.
Now, have anyone tried with VitualBox so far?

On 4/9/23 9:32 AM, Jan-Erik Söderholm wrote:
> Hi.
>
> So, got the files downloaded.
> Now, have anyone tried with VitualBox so far?

Yes, and there have been reports that it's what at least some VSI
developers use. If you happen to be on macOS Ventura, you'll need a
pre-release install of 7.0.7 because 7.0.6 (the current release) doesn't
work with EFI-enabled booting.

On 4/9/2023 10:39 AM, Craig A. Berry wrote:
>
> On 4/9/23 9:32 AM, Jan-Erik Söderholm wrote:
>> Hi.
>>
>> So, got the files downloaded.
>> Now, have anyone tried with VitualBox so far?
>
> Yes, and there have been reports that it's what at least some VSI
> developers use.  If you happen to be on macOS Ventura, you'll need a
> pre-release install of 7.0.7 because 7.0.6 (the current release) doesn't
> work with EFI-enabled booting.

I haven't downloaded it yet but I hope to get to it this week.
I will probably try VirtualBox on Windows10.
Can anyone tell me what compilers come with it as that is what I
would be most interested in trying out.

bill

Den 2023-04-09 kl. 16:56, skrev bill:
> On 4/9/2023 10:39 AM, Craig A. Berry wrote:
>>
>> On 4/9/23 9:32 AM, Jan-Erik Söderholm wrote:
>>> Hi.
>>>
>>> So, got the files downloaded.
>>> Now, have anyone tried with VitualBox so far?
>>
>> Yes, and there have been reports that it's what at least some VSI
>> developers use.  If you happen to be on macOS Ventura, you'll need a
>> pre-release install of 7.0.7 because 7.0.6 (the current release) doesn't
>> work with EFI-enabled booting.
>
> I haven't downloaded it yet but I hope to get to it this week.
> I will probably try VirtualBox on Windows10.
> Can anyone tell me what compilers come with it as that is what I
> would be most interested in trying out.
>
> bill
>

C, C++ and Fortran.
They are separate downloads, so it is very clear when you have
logged in and have the list of kits in front of you.

Den 2023-04-09 kl. 16:39, skrev Craig A. Berry:
>
> On 4/9/23 9:32 AM, Jan-Erik Söderholm wrote:
>> Hi.
>>
>> So, got the files downloaded.
>> Now, have anyone tried with VitualBox so far?
>
> Yes, and there have been reports that it's what at least some VSI
> developers use.  If you happen to be on macOS Ventura, you'll need a
> pre-release install of 7.0.7 because 7.0.6 (the current release) doesn't
> work with EFI-enabled booting.

Just upgrades VitrualBox from some 6-version to 7.0.6 (Win10).

Now I just need a rainy day to get some time...