EFI can dhcp configure KVM network device, yet OpenVMS pre-boot & OS can't see.

[viptux]

New install with latest CLP release download [9.2.2] for X86_64.

The OS does boot fine from the disk; LANCP also does not see an interface.
Should I give the Aug2024 pre-release a try?

Running on Debian Stable.

Output attached.


Kind Regards.

[roberbrooks]

How is the ethernet device configured within KVM?

I'm an ESXi, not KVM, user so I cannot give any specific advice other than you've likely configured an ethernet device that VMS does not recognize.

[viptux]

I thought so too after seeing your response.. much appreciated.

Added a SATA CDROM to the same openvms guest and booted a fresh debian-testing-amd64-netinst.iso just to inspect the pci tree from shell.

Here's the details on the ethernet interface:

---

Is there a place to download a VSI install iso versus the zipfile image downloaded from the registration portal email?


Kind Regards

[sms]

Code: Select all

> [...] KVM network device, [...]

   I've never touched KVM, so I know nothing about its network
adapter option(s).  But, ...

   Around here, on VMware (Fusion), the default network adapter appears
in the ".vmx" file as:
      ethernet0.virtualDev = "e1000"
which seems to be compatible with the SYS$EI1000X driver.  The VMS
device appears so:

V89 $ show devi /full eia0

Device EIA0:, device type i8254x, is online, network device, error logging is
    enabled, device is a template only.

    Error count                    0    Operations completed                  0
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot              S:RWPL,O:RWPL,G,W
    Reference count                0    Default buffer size                 512
    Current preferred CPU Id       1    Fastpath                              1
    Current Interrupt CPU Id       1

Operating characteristics: Link up, Full duplex, Autonegotiation.

    Speed (Mbits/sec)           1000    Adapter  Intel i82545 VBOX/VMware (Eth)
    Def. MAC addr  00-0C-29-78-21-FE    Current MAC addr      AA-00-04-00-D3-04

   If KVM offers something like that, then it might work better (with
VMS) than whatever you have now.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

> Here's the details on the ethernet interface:

> [...] Intel Corporation 82574L Gigabit Network Connection [8086:10d3]

   Hmmm.  Looking at my (V9.2-2) SYS$SYSTEM:SYS$CONFIG.DAT, I don't see
"82574" or "10d3".  It might be possible to get VMS to try the
SYS$EI1000X driver with your current interface if you add the right
stuff to SYS$SYSTEM:SYS$USER_CONFIG.DAT.  (If I knew anything, I might
have a more detailed suggestion.)


> Is there a place to download a VSI install iso versus the zipfile
> image downloaded from the registration portal email?

   If you have a Community/peon license, I believe not.  Ambassador or
paying-customer status includes that as a benefit.

[joukj]

Here's the details on the ethernet interface:

You list here how Debian is seeing it. More interesting would be how you configured your internet device within Qemu/KVM.
The most "common" way is to configure it as an e1000 bridged to the real interface.

Please post the Qemu/KVM configuration files/details.

[viptux]

surely.. please see attached.

Added in 22 minutes 58 seconds:
Some additional environment details the guest is running on:


~$ sudo /usr/bin/qemu-system-x86_64 --version

QEMU emulator version 9.0.2 (Debian 1:9.0.2+ds-2+b1)
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

$ sudo apt info libvirt-daemon
Package: libvirt-daemon
Version: 10.7.0-3
Source: libvirt
Maintainer: Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>
Description: Virtualization daemon
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The library aims at providing
a long term stable C API for different virtualization mechanisms. It currently
supports QEMU, KVM, XEN, OpenVZ, LXC, and VirtualBox.
.
This package contains the daemon libvirtd to manage the hypervisors.

[joukj]

You configured a e1000e. I think that is only supported in 9.2-3. Use a e1000.
See the installation document for 9.2-2
https://docs.vmssoftware.com/vsi-openvm ... ion-guide/
section 2.2.1 (step3)

[viptux]

Not sure if it's the newer qemu-kvm-v9 emulator or newer libvirt-v10 that only provides the virtual e1000e ethernet as an option to the virtio nic. I'll have to research into it, but for now my other guest VMs [OpenBSD, OpenIndiana, Win11] all work fine and without issues using the e1000e device, just not OpenVMS as of today.

Appreciate everyone for responding.

Have very fond memories working on DEC VAX/VMS servers from many moons ago.
The nostalgia rush just seeing an OpenVMS OS sysboot again AND on x86_64 was .. well .. delightful ! ; )


Gratitude and Best Regards !!