[Info-vax] Current limitations os VMS X86?

Jan-Erik Söderholm jan-erik.soderholm at telia.com
Sat Dec 9 08:40:34 EST 2023


Den 2023-12-09 kl. 10:47, skrev Stefan Möding:
> Hi Hans!
> 
> Hans Bachner <hans at bachner.priv.at> writes:
> 
>> My latest informations says, that you can't use a shared SCSI disk as
>> a system disk when running under VMware.
> 
> That's also what I understand from the installation manual.  The
> clustering manual is also only referring to Alpha or Itanium.
> 
>> I think you *can* use a fibre channel disk as a shared system disk.
> 
> And this would be on bare metal or also on VMware (using a raw device
> instead of a VMDK)?
> 
> 
>> No, (acess to) a serial port on the ESXi host is not required. You
>> define a serial port for the VM you want to use for VMS, and connect
>> to that via a raw TCP/IP port.
> 
> I was referring to the TCP/IP port.  But this would force the VM to stay
> on the same ESXi host.  I could live with that if it was only necessary
> during installation.
> 
> A VMware cluster normally migrates VMs between ESXi hosts to optimize
> resources.  Even restarting the VM on a different ESXi host after hardware
> failure would be more complicated if the console would have to be
> "rewired" on the new host first.
> 
> There seems to be a serial port concentrator software for VMware that
> allows VM migration.  But that's a licenced product from yet another
> company.
> 
> Thanks!
> 

But for a configured and running OpenVMS system, there is
really no need for a "consol".

And if properly setup with "auto-boot", it should boot just
fine without a connection to the console IP port.



More information about the Info-vax mailing list