Customer experience with hypervisors untested by VSI
-
Topic author - Site Admin
- Valued Contributor
- Posts: 92
- Joined: Tue May 21, 2019 6:56 am
- Reputation: 0
- Status: Offline
Customer experience with hypervisors untested by VSI
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).
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).
-
- Visitor
- Posts: 1
- Joined: Tue May 09, 2023 2:44 pm
- Reputation: 0
- Location: Zwolle, The Netherlands
- Status: Offline
Re: Customer experience with hypervisors untested by VSI
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.
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.
Re: Customer experience with hypervisors untested by VSI
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
$
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>
Any ideas welcome...
Mike T.
Re: Customer experience with hypervisors untested by VSI
Is "Secure Boot" enabled?
You also may want to compare the XML files (which you can dump with virsh dumpxml).
You also may want to compare the XML files (which you can dump with virsh dumpxml).
Re: Customer experience with hypervisors untested by VSI
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
#
-
- Visitor
- Posts: 1
- Joined: Mon Jul 31, 2023 8:51 am
- Reputation: 0
- Location: Hamburg, Germany
- Status: Offline
UTM qemu on Apple MAC M1
I installed UTM virtual machines (V4.2.5 in App Store, latest V4.3.3 from github) with qemu x86 emulation on my MacBook M1.
Boot stucks at the very end of sysinit after mount of the system disk.
Maybe drivers are switching at this time, drive is sata (ahci).
Don't know how to investigate further !
As marked, %SYSINIT-I-CLRERL does not appear but should be there, also the pagefile is available.
It seems that the system disk could not be read at this time (also rms error)
Same behavior by booting distribution iso-image.
I converted an existing vmdk from my windows virtualbox to qcow2 on my Mac for booting.
Boot stucks at the very end of sysinit after mount of the system disk.
Maybe drivers are switching at this time, drive is sata (ahci).
Don't know how to investigate further !
As marked, %SYSINIT-I-CLRERL does not appear but should be there, also the pagefile is available.
It seems that the system disk could not be read at this time (also rms error)
Same behavior by booting distribution iso-image.
I converted an existing vmdk from my windows virtualbox to qcow2 on my Mac for booting.
Code: Select all
VSI OpenVMS Boot Manager: V9.2-1 Build 128
ENABLED: Symmetric Multi-Processing
ENABLED: Crash Dump Processing
ENABLED: Console output to Legacy COM 1 Port
ENABLED: Using Environment ROM
Checking Required Processor Features:
PASSED
BOOT MANAGER DEVICE: DKA0
DEFAULT BOOT COMMAND: BOOT DKA0 0x01 0x00000081
VIRTUAL MACHINE GUEST:
KVM (tm) No Mouse support; Use Command or Arrow Keys
CONNECT A REMOTE TERMINAL SESSION NOW.
BOOTMGR> B
Booting...
%VMS_BOOTMGR-I-ACPI, No HPET (Clock). Using fallback clock source.
%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
_______________________________________________
VSI Primary Kernel SYSBOOT May 16 2023 13:21:17
%SYSBOOT-I-VMTYPE, Booting as a KVM (tm) Guest
SYSBOOT> SET VAXCLUSTER 0
SYSBOOT> C
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, V9.2-1
Copyright 2023 VMS Software, Inc.
MDS Mitigation active, variant knight(KNIGHTS LANDING/KNIGHTS MILL)
%SWAPPER-I-SHUFFLE, executing SWAPPER initialization code
%SWAPPER-I-POOL, initializing paged pool
%SWAPPER-I-INIT, calling initialization routines
%SWAPPER-I-RSDM, joining system resource domain
%SWAPPER-I-P1, initializing SWAPPER P1 cells
%SWAPPER-I-PAGED, paged system initialization
%SWAPPER-I-HASH, creating the logical name hash tables
%SWAPPER-I-DEFINE, defining the system logical names
%SWAPPER-I-CREPRC, creating the SYSINIT process
%SWAPPER-I-MAINLOOP, entering SWAPPER main loop
%SWAPPER-I-INSWAP, inswapped process EPID: 00000082 PID: 00010002 PCB: FFFFFFFF81CB6280
%SYSINIT-I-START, SYSINIT process execution begins
%SYSINIT-I-UNLOAD, unloading EXEC_INIT
%SYSINIT-I-ENTROPY, starting entropy harvest collector
%ENTROPY-I-HWRANDEN, RDRAND instruction enabled for entropy services.
%SYSINIT-I-AUDIT, initializing security auditing
%SYSINIT-I-LOAD, loading RECOVERY_UNIT_SERVICES.EXE
%SYSINIT-I-LOAD, loading DDIF$RMS_EXTENSION.EXE
%SYSINIT-I-LOAD, loading SYSMSG.EXE
%SYSINIT-I-LOAD, loading VMS_EXTENSION.EXE
%SYSINIT-I-LOAD, loading NT_EXTENSION.EXE
%SYSINIT-I-LOAD, loading MULTIPATH(_MON).EXE
%SYSINIT-I-ALTLOAD, loading site specific execlets
Loaded Image List:
Seq Image Name Base End Link Base
5E [SYS$LDR]MULTIPATH.EXE FFFF8300.07ADC100 FFFF8300.07AEC830 00000000.80000000
5C [SYS$LDR]NT_EXTENSION.EXE FFFF8300.07AD2000 FFFF8300.07AD7850 00000000.80000000
5A [SYS$LDR]VMS_EXTENSION.EXE FFFF8300.07ACBF00 FFFF8300.07ACF780 00000000.80000000
56 [SYS$LDR]DDIF$RMS_EXTENSION.EX FFFF8300.07AC5E00 FFFF8300.07AC9428 00000000.80000000
54 [SYS$LDR]RECOVERY_UNIT_SERVICE FFFF8300.07AC1D00 FFFF8300.07AC38D0 00000000.80000000
50 SYS$LDDRIVER FFFF8300.08782A00 FFFF8300.087A8310 00000000.80000000
4E SYS$SRDRIVER FFFF8300.08774700 FFFF8300.0877CF10 00000000.80000000
4C SYS$DKDRIVER FFFF8300.08741E00 FFFF8300.08768CB8 00000000.80000000
4A SYS$PKDDRIVER FFFF8300.08704F00 FFFF8300.08731578 00000000.80016000
48 SYS$DMDRIVER FFFF8300.086EA700 FFFF8300.086EDF68 00000000.80000000
46 SYS$TTDRIVER FFFF8300.086B9F00 FFFF8300.086DE028 00000000.80000000
44 SYS$ISA_SUPPORT FFFF8300.086B3D00 FFFF8300.086B6910 00000000.80000000
42 SYS$PCIE_SUPPORT FFFF8300.08699500 FFFF8300.086AB2C8 00000000.80000000
40 SWIS$DEBUG FFFF8300.08693300 FFFF8300.08696108 00000000.80000000
3E ACME FFFF8300.08678F00 FFFF8300.0868C6C0 00000000.80000000
3C SYS$MME_SERVICES FFFF8300.08674E00 FFFF8300.08676C08 00000000.80000000
3A SYSLDR_DYN FFFF8300.0864A000 FFFF8300.08667948 00000000.80000000
38 SYS$IPC_SERVICES FFFF8300.08562A00 FFFF8300.08611910 00000000.80000000
34 SYS$UTC_SERVICES FFFF8300.08558600 FFFF8300.0855BC38 00000000.80000000
32 SYS$TRANSACTION_SERVICES FFFF8300.084F5200 FFFF8300.08533D80 00000000.80018000
30 SYSLICENSE FFFF8300.084C2D00 FFFF8300.084D5F60 00000000.80006000
2E MESSAGE_ROUTINES FFFF8300.0848E200 FFFF8300.084B3968 00000000.80000000
2C SYS$VM FFFF8300.08313600 FFFF8300.08446FF8 00000000.80000000
2A SYS$XFCACHE FFFF8300.08265200 FFFF8300.082E3FF0 00000000.80000000
28 SYSGETSYI FFFF8300.08248C00 FFFF8300.0825C688 00000000.80000000
26 SECURITY FFFF8300.081D5D00 FFFF8300.0822B200 00000000.80000000
24 IMAGE_MANAGEMENT FFFF8300.08180500 FFFF8300.081BFBD8 00000000.80000000
22 RMS FFFF8300.07FAF700 FFFF8300.08115538 00000000.80002000
20 F11BXQP FFFF8300.07E89400 FFFF8300.07F66270 00000000.80000000
1E LOGICAL_NAMES FFFF8300.07E68E00 FFFF8300.07E809E8 00000000.80000000
1C SHELL8K FFFF8300.07E5EB00 FFFF8300.07E65308 00000000.80000000
1A LOCKING FFFF8300.07E17F00 FFFF8300.07E4CA40 00000000.80000000
18 PROCESS_MANAGEMENT FFFF8300.07CE5300 FFFF8300.07DCB190 00000000.80000000
16 SYSDEVICE FFFF8300.07CD3000 FFFF8300.07CDE480 00000000.80000000
14 IO_ROUTINES FFFF8300.07BF4A00 FFFF8300.07C946C8 00000000.80000000
12 EXCEPTION FFFF8300.07B32200 FFFF8300.07BCFB50 00000000.80000000
0E SYS$OPDRIVER FFFF8300.07AB3A00 FFFF8300.07ABC030 00000000.80000000
0C SYSTEM_SYNCHRONIZATION_UNI FFFF8300.07A74A00 FFFF8300.07A9F920 00000000.80000000
0A SYSTEM_PRIMITIVES_7_MIN FFFF8300.07965E00 FFFF8300.07968F68 00000000.80000000
08 SYS$ACPI FFFF8300.0788A300 FFFF8300.07910C60 00000000.80000000
06 ERRORLOG FFFF8300.07882000 FFFF8300.07887310 00000000.80000000
04 SYS$PLATFORM_SUPPORT FFFF8300.07814200 FFFF8300.078640D8 00000000.80000000
02 SYS$BASE_IMAGE FFFF8300.07802100 FFFF8300.078101C0 00000000.80000000
00 SYS$PUBLIC_VECTORS FFFF8300.07800000 FFFF8300.07800028 00000000.80000000
%SYSINIT-I-TIME, setting the system time
%SYSINIT-I-SYSDISK, checking status of system disk
%SYSINIT-I-STACONFIG, STACONFIG finished
%SYSINIT-I-INIT, initializing the XQP
%SYSINIT-I-CLUSTER, cluster/lock manager initialization
%SYSINIT-I-SHADOW, shadow driver initialization
%SYSINIT-I-DEFINE, defining system logical names
%SYSINIT-I-MOUNT, mounting the system disk
%SYSINIT-I-TIME, setting the system time
%SYSINIT-I-FILCACHE, deallocating the primitive file cache
%SYSINIT-I-DEFINE, defining SYS$TOPSYS
%SYSINIT-I-MEMCONNECTING, connecting to memory disk
%SYSINIT-I-MEMCONNECTED, connected to memory disk
%SYSINIT-I-MEMDISK, using device $1$LDM6502:
%SYSINIT-I-RECERL, recovering error log buffers
%SYSINIT-I-CLRERL, clearing empty error log buffers <== This line is missing !
%RMS-F-BUG, fatal RMS condition (FFFFFFE5), process deleted
%RMS-F-BUG, fatal RMS condition (FFFFFFE5), process deleted
VSI Dump Kernel SYSBOOT May 16 2023 13:21:17
%SYSTEM-W-NOPAGEFILE, no pagefile installed; system trying to continue
Last edited by thomas@ham on Mon Jul 31, 2023 12:19 pm, edited 3 times in total.
Regards,
Thomas
Since 1985, VMS 3.6 -> OpenVMS 9.2
Thomas
Since 1985, VMS 3.6 -> OpenVMS 9.2