Customer experience with hypervisors untested by VSI

[marty.stu]

Dear OpenVMS users,

Please use this thread to report your experience with different hypervisors not listed by VSI as compatible with the latest OpenVMS release. For the list of the hypervisors that were proven to be compatible by VSI staff, refer to this document (Section 1.2. Tested Platforms).

[blackbird]

Tried to setup a node as a guest in FreeBSD 13 using bhyve as hypervisor.
Suitable disks created, iso mounted and accessed the guest via vnc and serial port.

Bootmanager is loaded but no interaction possible via mouse or keyboard, serial port shows no activity.

[mike632t]

I've managed to get VMS 9.2-1 installed on qemu on Debian (Buster)

Unfortunately I am unable to get the installer to start when using Debian (Bullseye).

Code: Select all

$ virsh version
Compiled against library: libvirt 7.0.0
Using library: libvirt 7.0.0
Using API: QEMU 7.0.0
Running hypervisor: QEMU 5.2.0

$ kvm --version
QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-11+deb11u2)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
$ 

Rather then executing the VMS boot manager the boot process drops into the shell, and any attempts to execute the VMS boot manager fail with the error message 'access denied'... (which I think is why it drops into the shell in the first place).

Code: Select all

UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
      FS0: Alias(s):CD0c65535a0:;BLK1:
          PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)/CDROM(0x0)
     BLK0: Alias(s):
          PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
     BLK2: Alias(s):
          PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Scsi(0x0,0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell> map FS0: 
Mapping table
      FS0: Alias(s):CD0c65535a0:;BLK1:
          PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)/CDROM(0x0)
Shell> FS0:\EFI\VMS\VMS_BOOTMGR.EFI
Command Error Status: Access Denied
Shell> 

Something has obviously changed between QEMU versions. However, on a more positive note an existing virtual machine built on a Debian 10 host works as expected.

Any ideas welcome...

Mike T.

[hb]

Is "Secure Boot" enabled?

You also may want to compare the XML files (which you can dump with virsh dumpxml).

[mike632t]

Unfortunately I am unable to get the installer to start when using Debian (Bullseye).

I'm not sure what the problem actually is but it is but I managed to resolve it by uninstalling the ovmf package that is included with Debian 11 (bullseye) (2020.11-2+deb11u1) and replacing it with the ovmf package from Debian 10 (buster) (0~20181115.85588389-3+deb10u3).

For this change to be permanent you need to pin the older version to prevent apt from upgrading it the next time you run 'apt-get upgrade'.

Code: Select all

#nano /etc/apt/preferences.d/10-pinned-packages

Code: Select all

#Package: ovmf
#Pin: version 0~20181115.85588389-3+deb10u3
#Pin-Priority: 999
#

If there is a better solution let me know - Thanks