KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

OpenVMS virtualization: OpenVMS on VirtualBox, VMWare, Hyper-V, KVM, and more.
Post Reply

Topic author
scotty
Visitor
Posts: 1
Joined: Thu Apr 13, 2023 8:42 am
Reputation: 0
Status: Offline

KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

Post by scotty » Thu Apr 13, 2023 9:25 am

UEFI shell:
I see FS0 with the X86E921EO.iso CDROM.
I see 3 BLK devices mentioned in docs.
VMS install:
No target devices are available for install.

Is there a missing step to map storage for VMS?

From the UEFI Shell:

Code: Select all

EFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EFI Development Kit II / OVMF, 0x00010000)
Mapping table
      FS0: Alias(s):CD0c0:;BLK1:
          PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)/CDROM(0x0)
     BLK2: Alias(s):
          PciRoot(0x0)/Pci(0x7,0x0)/Sata(0x1,0xFFFF,0x0)
     BLK3: Alias(s):
          PciRoot(0x0)/Pci(0x7,0x0)/Sata(0x2,0xFFFF,0x0)
     BLK0: Alias(s):
          PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell> map -b
Mapping table
      FS0: Alias(s):CD0c0:;BLK1:
          PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)/CDROM(0x0)
     BLK2: Alias(s):
          PciRoot(0x0)/Pci(0x7,0x0)/Sata(0x1,0xFFFF,0x0)
     BLK3: Alias(s):
          PciRoot(0x0)/Pci(0x7,0x0)/Sata(0x2,0xFFFF,0x0)
     BLK0: Alias(s):
          PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
Shell> 


From BOOTMGR:

BOOTMGR> DEVICES FS 

UEFI FILE SYSTEM DISKS:

  FS0   (DVD) = FS0        Part:0, UEFI: E9_2_1           OpenVMS Disk

2/14/2023  11:26 <DIR>         2,048  .

VSI OpenVMS Boot Manager: V9.2-1, Build 122

  ENABLED:  Symmetric Multi-Processing
  ENABLED:  Crash Dump Processing
  ENABLED:  Console output to Legacy COM 1 Port

  Checking Required Processor Features:
  PASSED
%VMS_BOOTMGR-W-DEVICE, Ignoring ATAPI device...

  BOOT MANAGER DEVICE:  FS0
  DEFAULT BOOT COMMAND: BOOT FS0 0 00000000

  VIRTUAL MACHINE GUEST: 
  KVM (tm) No Mouse support; Use Command or Arrow Keys


  CONNECT A REMOTE TERMINAL SESSION NOW.

BOOTMGR>

BOOTMGR> BOOT 
Booting...
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
100%

%VMS_BOOTMGR-I-HWRPB,   Unable to determine System Serial Number


%%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%


_______________________________________________

      GRAPHICAL OUTPUT HAS BEEN SUSPENDED
      USE A TERMINAL UTILITY FOR ACCESS
_______________________________________________
No ACPI MCFG table was found.  This processor may not have a PCIe configuration space.

VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45

%SYSBOOT-I-VMTYPE, Booting as a KVM (tm) Guest


        VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-1  
                    Copyright 2023 VMS Software, Inc.

  MDS Mitigation active, variant verw(MD_CLEAR)

%SMP-I-CPUTRN, CPU #1 has joined the active set.



    Installing required known files...

    Configuring devices...



    ****************************************************************

    You can install or upgrade the OpenVMS X86-64 operating system
    or you can install or upgrade layered products that are included
    on the OpenVMS X86-64 distribution media.

    You can also execute DCL commands and procedures to perform
    "standalone" tasks, such as backing up the system disk.

    Please choose one of the following:

        1)  Upgrade, install or reconfigure OpenVMS X86-64 Version E9.2-1
        2)  Display layered products that this procedure can install
        3)  Install or upgrade layered products
        4)  Show installed products
        5)  Reconfigure installed products
        6)  Remove installed products
        7)  Find, Install or Undo patches; Show or Delete Recovery Data
        8)  Execute DCL commands and procedures
        9)  Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1
    ***********************************************************

    This procedure will ask a series of questions.

          () - encloses acceptable answers
          [] - encloses default answers

    Type your response and press the <Return> key.  Type:

          ? - to repeat an explanation
          ^ - to change prior input (not always possible)
          Ctrl/Y - to exit the installation procedure

    This procedure installs the OpenVMS X86-64 operating system.

    All software and data files that were previously on the
        target disk will be removed.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE] initialize


    You must enter the device name for the target disk on which
    OpenVMS X86-64 will be installed.

Enter device name for target disk: (? for choices) ?

  Device Name       Device Type Name        Volume Label     Size (blocks/xB)  
  ------------  -------------------------  --------------  --------------------

  No devices named * found


Enter device name for target disk: (? for choices)


jfp
Contributor
Posts: 16
Joined: Wed Jun 17, 2020 6:34 am
Reputation: 0
Status: Offline

Re: KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

Post by jfp » Thu Apr 13, 2023 9:41 am

Hi,

How do you create your disk under Proxmox ?

On my OpenVMS VM I see 2 disks:
Hard disk sata0
EFI disk

I have successfully install OVMS on Proxmox.

But, currently, no network...

JF


smirk
Newbie
Posts: 3
Joined: Mon Apr 24, 2023 6:28 pm
Reputation: 0
Status: Offline

Re: KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

Post by smirk » Mon Apr 24, 2023 6:38 pm

I managed to get 9.2.1 installed in Proxmox (7.4-3) with networking. In terms of creating the virtual disks they're just created as SATA disks through the UI, making sure the chipset for the VM is the Q35 version (the i440fx boots the VMS installation media but does not present any disks for installation). The main "trick" that I had to do was create two NICs: first NIC (net0) is something like virtio/realtek/vmware and the second NIC (net1) is the working adaptor. If I try with a single NIC then VMS won't boot past the trying to detect and configure devices. Initially I thought it was hanging when trying to active the CPUs but it appears to "hang" (100% CPU usage) when detecting devices. Using two NICS with the first being a "sacrifical" one appears to work.


jfp
Contributor
Posts: 16
Joined: Wed Jun 17, 2020 6:34 am
Reputation: 0
Status: Offline

Re: KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

Post by jfp » Tue Apr 25, 2023 2:46 am

@smirk, Correct creating 2 nics fix the boot problem, the fist one as a VMware vmxnet3, the second one as a E1000.
Then a "mc lancp sh dev /cha" correctly show the second nic.

Thanks for the tip.

JF


motk
Member
Posts: 7
Joined: Fri Dec 08, 2023 5:13 am
Reputation: 0
Status: Offline

Re: KVM on Proxmox cluster: BLK and FS devices seen on UEFI. No target devices on VMS install

Post by motk » Sat Apr 06, 2024 7:16 am

smirk wrote:
Mon Apr 24, 2023 6:38 pm
Initially I thought it was hanging when trying to active the CPUs but it appears to "hang" (100% CPU usage) when detecting devices. Using two NICS with the first being a "sacrifical" one appears to work.
This is a symptom of the vm getting confused regarding hpet initialising, You can add

args: -no-hpet

to you qemu-server/xxx.cfg file and it should work fine.

Using proxmox 8.1 with the 6.5.x kernel.

Post Reply