fozter
Contributor
Contributor

[SOLVED] stuck after reboot: "vmkapei loaded successfully"

Jump to solution

Hello,

After a fresh install of esxi 5.5 my system doesn't seem to work properly after rebooting the host.

When all setup was done with datastores and other settings I wanted to passthrough my graphics card and therefore rebooting the host before adding the card to the host

was necessary.

The problem is now that when esxi is loading/starting all the systemfiles it just stucks on "vmkapei loaded successfully" and manually rebooting doesn't seem to help either.

Same problem occurs on both usb stick and SSD

I also used "formatwithmbr" to even be able to install esxi.

Server specifications;

Mobo: Asus P9D WS

CPU: Intel Xeon 1220v3

RAM: Crucial DDR3 ECC 2x8GB (CT2KIT102472BD160B)

GFX: Gigabyte Radeon R7 250 1GB

SSD: Samsung SSD EVO Basic 840-Series 250GB

PSU: be quiet! Straight Power E9 500W 80+ Gold

1 Solution

Accepted Solutions
Linjo
Leadership
Leadership

If you only have one GPU and are doing passthrough you will loose the console after boot, that is completely nornal and expected.

If you want to keep the console you have two options:

1. Install another GPU.

2. Do not passthrough the only GPU.

The ESX will work without a console, you just need to use SSH to do the admin tasks you normally would do on the console.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

14 Replies
zXi_Gamer
Virtuoso
Virtuoso

For your issue with passthroughing the graphics card:

Upgrade from ESXi 5.1 to 5.5 (free) and stuck at "iodm loaded successfully"

0 Kudos
Jayden56
Enthusiast
Enthusiast

Hi

Welcome to the communities.

Please share the log file from below mentioned path

/var/log/sysboot.log: Early VMkernel startup and module loading.

0 Kudos
fozter
Contributor
Contributor

Do you know how i can recover the sysboot.log without getting it in vSphere Client?

0 Kudos
fozter
Contributor
Contributor

I was able to get the sysboot.log from https://hostip/host

EDIT: The gfx is a Gigabyte r7 250 1 GB

VMKernel Initialization Time: 6000000

[01:53:25.287469] sysboot: restore-configuration 0

[01:53:25.447962] sysboot: vxlan-base 1

[01:53:25.447977] sysboot: register-vmw-satp 2

[01:53:25.483012] sysboot: register-vmw-psp 3

[01:53:25.483244] sysboot: register-vmw-vaai 4

[01:53:25.483720] sysboot: register-vmw-mpp 5

[01:53:25.483840] sysboot: PSA-boot-config 6

[01:53:25.483928] sysboot: advanced-user-configuration-options 7

[01:53:25.524984] sysboot: vmkapi-mgmt 8

[01:53:25.883722] sysboot: iodm 9

[01:53:25.893590] sysboot: aslr 10

[01:53:25.896132] sysboot: storage-early-configuration 11

[01:53:25.932489] sysboot: iommu 12

[01:53:25.932595] sysboot: dma-engine 13

[01:53:25.932648] sysboot: apei 14

[01:53:25.945877] sysboot: restore-security-policies 15

[01:53:25.949855] sysboot: hardware-config 16

[01:53:26.070462] sysboot: restore-pxe-marker 17

[01:53:26.070544] sysboot: restore-advanced-configuration 18

[01:53:28.231747] sysboot: cbrc 19

[01:53:28.233430] sysboot: restore-resource-groups 20

[01:53:28.235183] sysboot: tpm 21

[01:53:28.235250] sysboot: oem-modules 22

[01:53:28.235309] sysboot: vmkapi-socket 23

[01:53:28.244793] sysboot: vmkernel-vmkapi-compatibility 24

[01:53:28.270483] sysboot: microcode-update 25

[01:53:28.281588] sysboot: vprobe 26

[01:53:28.300319] sysboot: procfs 27

[01:53:28.309873] sysboot: procMisc 28

[01:53:28.318913] sysboot: vmklinux 29

[01:53:28.414144] sysboot: vmkdevmgr 30

[01:53:28.888222] sysboot: etherswitch 31

[01:53:28.952814] sysboot: networking-drivers 32

[01:53:33.596285] sysboot: mlx4_en 33

[01:53:33.596372] sysboot: usb 34

[01:53:33.783722] sysboot: local-storage 35

[01:53:33.946107] sysboot: psa-mask-paths 36

[01:53:33.952377] sysboot: psa-filter-pre-claim-config 37

[01:53:34.007336] sysboot: psa-nmp-pre-claim-config 38

[01:53:34.214996] sysboot: nmp-vmkapi-compatibility 39

[01:53:34.230927] sysboot: restore-storage-multipathing 40

[01:53:34.232925] sysboot: psa-load-rules 41

[01:53:34.239369] sysboot: psa-nmp-post-claim-config 42

[01:53:34.239381] sysboot: psa-filter-post-claim-config 43

[01:53:34.239390] sysboot: restore-keymap 44

[01:53:34.240301] sysboot: network-uplink-init 45

[01:53:34.240369] sysboot: storage-drivers 46

[01:53:38.265914] sysboot: storage-psa-init 47

[01:53:41.268027] sysboot: bnx2fc 48

[01:53:41.268157] sysboot: iscsi-vmkapi-compatibility 49

[01:53:41.283849] sysboot: restore-system-uuid 50

[01:53:41.285687] sysboot: network-support 51

[01:53:41.691771] sysboot: firewall 52

[01:53:41.846382] sysboot: vmotion 53

[01:53:41.891563] sysboot: hbr 54

[01:53:41.908403] sysboot: record-replay 55

[01:53:41.922858] sysboot: dvfilters-vmkapi-compatibility 56

[01:53:41.938925] sysboot: dvfilter-generic-fastpath 57

[01:53:41.956927] sysboot: dvfilter-config 58

[01:53:41.956938] sysboot: vds-vmkapi-compatibility 59

[01:53:41.956946] sysboot: vds-config 60

[01:53:41.956955] sysboot: mount-filesystems 61

[01:53:41.957080] sysboot: vmci 62

[01:53:41.961824] sysboot: vfat 63

[01:53:41.972665] sysboot: lacp-daemon 64

[01:53:43.009727] sysboot: restore-networking 65

[01:53:43.047736] sysboot: dvfilters 66

[01:53:43.048003] sysboot: fcoe-config 67

[01:53:43.049882] sysboot: ipmi 68

[01:53:43.049982] sysboot: random-seed 69

[01:53:43.050094] sysboot: auto-configure-networking 70

[01:53:43.050171] sysboot: inetd 71

[01:53:43.051303] sysboot: rpc 72

[01:53:43.063463] sysboot: software-iscsi 73

[01:53:43.078926] sysboot: storage-path-claim 74

[01:53:51.178962] sysboot: system-image-cache 75

[01:53:51.179015] sysboot: filesystem-drivers 76

[01:53:51.206533] sysboot: restore-paths 77

[01:53:51.230007] sysboot: vsan-devel 78

[01:53:51.233407] sysboot: restore-bootbanks 79

[01:53:51.279425] sysboot: tag-boot-bank 80

[01:53:51.280747] sysboot: dump-partition 81

[01:53:51.285507] sysboot: plog 82

[01:53:51.349897] sysboot: vmfs 83

[01:53:51.386542] sysboot: vflash 84

[01:53:51.401963] sysboot: vfc 85

[01:53:51.420439] sysboot: vsan 86

[01:53:51.528912] sysboot: mount-disk-fs 87

[01:53:51.642626] sysboot: auto-configure-storage 88

[01:53:51.642670] sysboot: nfs 89

[01:53:51.657117] sysboot: restore-nfs-volumes 90

[01:53:51.660891] sysboot: configure-locker 91

[01:53:51.679865] sysboot: set-acceptance-level 92

[01:53:51.951121] sysboot: scratch-storage 93

[01:53:52.105669] sysboot: restore-host-cache 94

[01:53:52.130893] sysboot: restore-system-swap 95

[01:53:52.135195] sysboot: dump-file 96

[01:53:52.147221] sysboot: coredump-configuration 97

[01:53:52.188480] sysboot: pingback 98

[01:53:52.188523] sysboot: crond 99

[01:53:52.189903] sysboot: Instrumentation

[01:53:52.189903] sysboot: Jumpstart duration: 26.902451

=== Jumpstart configuration info ===

Verbose: 0

Parallel: 0

Randomize: 0

Interactive Mode: 0

Random Seed: 1392774804

0 Kudos
Linjo
Leadership
Leadership

If you only have one GPU and are doing passthrough you will loose the console after boot, that is completely nornal and expected.

If you want to keep the console you have two options:

1. Install another GPU.

2. Do not passthrough the only GPU.

The ESX will work without a console, you just need to use SSH to do the admin tasks you normally would do on the console.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

fozter
Contributor
Contributor

But the things is that when i turn off the host for 5 min and then boots it again it will not connect via vsphere/http, same ip and user/pw.

When i reboot the host using vspehre it connects after some minutes. What do i have to do with SSH then?

When adding the gfx to windows 7 i can actually output via HDMI to my TV Smiley Happy

0 Kudos
fozter
Contributor
Contributor

It's Alive!! I left the host on "vmkapei loaded successfully" for about 30 minutes after manually rebooting with delay from shutdown to boot, then all went well and i can now connect via vsphere :smileygrin:.

Ogeccut
Contributor
Contributor

I am having the same issue. Are there any steps i can take to start troubleshooting?

Did anyone else have this issue?

Thank you.

0 Kudos
weiluo
Contributor
Contributor

I experienced same problem.  Any way to resolve this yet?  thx

0 Kudos
IlyaBakulin
Contributor
Contributor

The same problem for me:

stuck after reboot: "vmkapei loaded successfully"stuck after reboot: "vmkapei loaded successfully"

Tried to wait 1-2-3 hours - no changes, no pings (and I have no external GPU). Tried to upgrade version from 5.5 to 6.0 and again the same problem but with another tip:

vmkapi_v2_1_0_vmkernel_shim loaded successfully

and then stuck - no ping of the server...

Does anyone know how to handle this?

Thank you in advance!

0 Kudos
jcosta
Enthusiast
Enthusiast

Did anyone get this fixed?  Just started to have a server do it.

Latest build of 6.  It says the same thing on the screen:   

stuck after reboot: "vmkapei loaded successfully"stuck after reboot: "vmkapei loaded successfully"

Funny thing is I can connect to it via vsphere and all vms are functioning correctly but on the host screen it is stuck loading.

Thanks,

J

0 Kudos
jcosta
Enthusiast
Enthusiast

nevermind!  I just found out one of my techs was playing with passthrough and picked the onboard GPU.  It wasn't turning the screen black but did make it look like it was locked up.  After removing the pass through GPU it shows the normal ESXI screen.

Later!

0 Kudos
asemen
Contributor
Contributor

I have the same problem on ESXi 6.5.0 on boot.

It starts booting, stuck after the message "vmkapi_v2_1_0_0_vmkernel_shim loaded successfully"

Looks like some kernel modules did not load.

Our hardware is a Thomas -Krenn X95SRL-F.

Is there a way to disable or skip or time out the load of the kernel module failed.

Is there a tool or  a rescue way to fix that problem

The problem is also that the VMware server did not get network up, so I not ping or connect to it possible.

Dose anyone can help on this to make the server boot again?

0 Kudos
ndilimani
Contributor
Contributor

I had the mda_immon stuck and i upgraded to 6.5 and now i have your error

0 Kudos