VMware vSphere ESXi-8.0U2b E1000 Network Driver Not Exposed in 9.2-1 or 9.2-2

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

Topic author
morriskr
Visitor
Posts: 2
Joined: Thu Mar 21, 2024 6:26 pm
Reputation: 0
Status: Offline

VMware vSphere ESXi-8.0U2b E1000 Network Driver Not Exposed in 9.2-1 or 9.2-2

Post by morriskr » Tue Apr 16, 2024 8:46 am

Hardware: HPE DL360 GEN 9
Software: VMware ESXi-8.0U2b-23305546 Standard
OpenVMS 9.2-2 Community with VMS922X_PCSI-V0100 and VMS922X_UPDATE-V0100 installed
Compatibility Mode: 8.0 (not working), 6.7 and 7.0 (works)

From the console using the "DEVICE PCI" command displays the E1000 network device:
"Intel: 82545EM Intel(R) PRO/e1000 MT Network Connection"

On this same hardware/software platform, running OpenVMS Community 9.2-2 version in hardware compatible mode as ESXi 6.7 or 7.0 exposes the network device in OpenVMS as EIA0.

Attached is the boot sequence from the console.

Where should I be looking to help diagnose this issue?
Attachments
OpenVMS Community vSphere 8.0.txt
Console output at boot time
(113.48 KiB) Downloaded 21 times


debbee.west
VSI Expert
Contributor
Posts: 16
Joined: Mon Oct 07, 2019 11:10 am
Reputation: 0
Status: Offline

Re: VMware vSphere ESXi-8.0U2b E1000 Network Driver Not Exposed in 9.2-1 or 9.2-2

Post by debbee.west » Tue Apr 16, 2024 11:30 am

Could you please post a

$anal/system
SDA> clue config/adapter

Thank you


stockdale
Visitor
Posts: 1
Joined: Tue Apr 16, 2024 3:29 pm
Reputation: 0
Status: Offline

Re: VMware vSphere ESXi-8.0U2b E1000 Network Driver Not Exposed in 9.2-1 or 9.2-2

Post by stockdale » Tue Apr 16, 2024 3:37 pm

SYS$SYSTEM:SYS$CONFIG.DAT identifies the NICs supported. Sometimes, it is possible the device offered by VMware is PCIE rather than PCI. A change was made to SYS$CONFIG.DAT when this was discovered to include PCI and PCIE entries for each LAN device. This change is in an update patch kit.

You can correct on your system by editing SYS$SYSTEM:SYS$CONFIG.DAT and duplicating the entries for E1000 (82545 for VMware) and identifying one of them as PCI and the other as PCIE.

Then do MC SYSMAN IO REBUILD then MC SYSMAN IO AUTO/LOG and the LAN device should appear.

Then update the memory disk to ensure the updated SYS$CONFIG.DAT is in it on reboot, @SYS$UPDATE:SYS$MD.COM.


Topic author
morriskr
Visitor
Posts: 2
Joined: Thu Mar 21, 2024 6:26 pm
Reputation: 0
Status: Offline

Re: VMware vSphere ESXi-8.0U2b E1000 Network Driver Not Exposed in 9.2-1 or 9.2-2

Post by morriskr » Tue Apr 16, 2024 6:28 pm

debbee.west wrote:
Tue Apr 16, 2024 11:30 am
Could you please post a

$anal/system
SDA> clue config/adapter

Thank you

Code: Select all

System Adapter Configuration:
-----------------------------
TR Adapter     ADP               Hose Bus      BusArrayEntry     Node GSIN   iVec    SCB  Port Slot Device Name / HW-Id
-- ----------- ----------------- ---- -------------------------- ---- ------------------- ---- ---- ---------------------------
 1 ACPI_IA64_P FFFFFFFF.820C3F00    0 00 IA64_BUS      
 2 PCI         FFFFFFFF.820DF680    0 00 PCI           
                                               FFFFFFFF.820DFA58    0 FFFF    0000      0         0 197615AD.71908086 (...q­.v.)
                                               FFFFFFFF.820DFB68    8 FFFF    0000      0         1 00000000.71918086 (...q)
                                               FFFFFFFF.820E01C8   38 FFFF    FFFF      0         7 MFPCI
                                               FFFFFFFF.820E0A48   78 0010    00DE   15E0        15 040515AD.040515AD (­...­...)
                                               FFFFFFFF.820E0B58   80 0011    00DD   15D0 PKA:   16 LSI Logic 1030 U320
 3 PCI         FFFFFFFF.820E2180    0 01 PCI           
 4 PCI         FFFFFFFF.820E53C0    0 00 PCI           
                                               FFFFFFFF.820E5798   38 FFFF    0000      0         7 197615AD.71108086 (...q­.v.)
                                               FFFFFFFF.820E58A8   39 000F    0000      0         7 197615AD.71118086 (...q­.v.)
                                               FFFFFFFF.820E5AC8   3B FFFF    0000      0         7 197615AD.71138086 (...q­.v.)
                                               FFFFFFFF.820E5F08   3F 0010    00DC   15C0         7 074015AD.074015AD (­.@.­.@.)
 5 ISA         FFFFFFFF.820E6580    0 00 ISA           
                                               FFFFFFFF.820163D8    0 000C    00DB   15B0         0 MOUSE
                                               FFFFFFFF.820164E8    1 0001    00DA   15A0         1 KBD
 6 XBUS        FFFFFFFF.820E6B00    0 00 XBUS          
                                               FFFFFFFF.820E6ED8    0 0004    00DF   15F0 SRA:    0 Console Serial Line Driver
                                               FFFFFFFF.820E6FE8    1 0003    00D9   1590 TTA:    1 Generic Com port
                                               FFFFFFFF.820E70F8    2 0009    00D8   1580         2 00383043.30504E50 (PNP0C08)
 7 PCIE        FFFFFFFF.82112740    0 02 PCIE          
                                               FFFFFFFF.82112A18  200 0011    00DD   15D0         0 075015AD.100F8086 (....­.P.)
 8 PCIE        FFFFFFFF.82117700    0 03 PCIE          
Note that the reply post by stockdale (Tue Apr 16, 2024 3:37 pm) instructions fixed the missing PCIE network device, which appeared after the MC SYSMAN IO REBUILD and then MC SYSMAN IO AUTO/LOG command. After the @SYS$UPDATE:SYS$MD.COM command the network device appears after a reboot.

Added in 6 minutes 22 seconds:
stockdale wrote:
Tue Apr 16, 2024 3:37 pm
SYS$SYSTEM:SYS$CONFIG.DAT identifies the NICs supported. Sometimes, it is possible the device offered by VMware is PCIE rather than PCI. A change was made to SYS$CONFIG.DAT when this was discovered to include PCI and PCIE entries for each LAN device. This change is in an update patch kit.

You can correct on your system by editing SYS$SYSTEM:SYS$CONFIG.DAT and duplicating the entries for E1000 (82545 for VMware) and identifying one of them as PCI and the other as PCIE.

Then do MC SYSMAN IO REBUILD then MC SYSMAN IO AUTO/LOG and the LAN device should appear.

Then update the memory disk to ensure the updated SYS$CONFIG.DAT is in it on reboot, @SYS$UPDATE:SYS$MD.COM.
Thank you for your quick response. Your suggestion found the missing network device.

Post Reply