If User did not mentioned reason behind putting host into maintenance than it is not possible to get the reason until you do not ask him.
If there is no HW issue than Check ESXi networking that networking Config is matching with other Hosts in the cluster and put it in production.
Hello all,
So, wanting to create a new VM on a machine, I went and tried to login to ESXI Web UI, only to get the message that I am using an incorrect username or password... Those I'm using, the root and pwd have been working perfectly fine for the past months following the installation of ESXi (v6).
From what I've gathered on the forums, the account could be on lockdown. My first question then is: will the lockdown lift itself up after some times?
If not, I've also read that, since I'm not linked to an AD server, the only way to reset the password would be through an unsupported method, that I will keep for last resort only of course.
Now, I cannot login to the UI and I cannot also login via SSH either. For now, the only logical possible solution would be to at least try to reboot the machine, but I'll have to hard reset the server. But before doing this, I want to know if I'm missing something obvious here?
The only thing that changed lately was, around 10 days ago, my 60 days evaluation ended, and I had to login to enter my free licence informations. To be honest, I'm a bit afraid of having to do a hard reboot since at that time, I remember the VM needing a manual power on (although it might be because I did not enter the licence yet). I just don't want to be stuck in the possibility of being locked out ESXi while my VM won't auto start !
Thank you for you answers and inputs!
Can you also not login to the console via the DCUI? Lockdown mode is only applicable when connected to a vCenter, and it does not lift after a timer expires.
je voudrais une solution svp esxi 5.5
~ # ls /dev/disks/
mpx.vmhba34:C0:T0:L0
mpx.vmhba34:C0:T0:L0:1
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:1
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:2
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:3
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:5
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:6
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:7
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:8
t10.ATA_____WDC_WD3200AAJS2D60Z0A0________________________WD2DWCAV2Z366443:9
vml.0000000000766d68626133343a303a30
vml.0000000000766d68626133343a303a30:1
vml.0100000000202020202057442d57434156325a333636343433574443205744
vml.0100000000202020202057442d57434156325a333636343433574443205744:1
vml.0100000000202020202057442d57434156325a333636343433574443205744:2
vml.0100000000202020202057442d57434156325a333636343433574443205744:3
vml.0100000000202020202057442d57434156325a333636343433574443205744:5
vml.0100000000202020202057442d57434156325a333636343433574443205744:6
vml.0100000000202020202057442d57434156325a333636343433574443205744:7
vml.0100000000202020202057442d57434156325a333636343433574443205744:8
vml.0100000000202020202057442d57434156325a333636343433574443205744:9
~ # vmkfstools -C vmfs5 -S USB_Datastore /dev/disks/mpx.vmhba34\:C0\:T0\:L0:1
create fs deviceName:'/dev/disks/mpx.vmhba34:C0:T0:L0:1', fsShortName:'vmfs5', fsName:'USB_Datastore'
deviceFullPath:/dev/disks/mpx.vmhba34:C0:T0:L0:1 deviceFile:mpx.vmhba34:C0:T0:L0:1
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Creating vmfs5 file system on "mpx.vmhba34:C0:T0:L0:1" with blockSize 1048576 and volume label "USB_Datastore".
Usage: vmkfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: vmkfstools failed: vmkernel is not loaded or call not implemented.
You are posting in the ESXi community, but to me it seems that you are using another product like VMware Workstation, or Player!?
Please let us know which product you are using, and post a complete list of files (including file sizes, time stamps, ...) in the VM's folder.
André
Does anyone know how to get the remote console to run in Firefox? When I click the console button it brings up new frame with a poorly responsive console. Not functional.
IE will bring up the Remote Console but IE won't run Flash mode without crashing. So you have to use the partially functional (whatever that means) HTML 5 interface.
Firefox runs the Flash version but the remote console sucks.
What possessed VMWare to make such an important piece of software dependent on the foibles of 3rd party applications (web browsers)?
Is anyone else fighting with browsers?
Not sure about Firefox... I'm using Chrome and whitelisted vcenter for flash.
Did you install VMRC ? I think its much better than the web based consoles.
Hello,
I have a fresh install of ESXi and I went to pass through some devices but all devices are "not capable" for passthrough. I would really appreciate some ideas on how to fix this.
System:
ASUS MB M5A78LM with an AMD FX8320. ESXi is installed on an SSD connected to the MB SATA. I also have an LSI 9211-8i which has drives connected to it.The card was flashed to IT mode using latest firmware available P20. In the MB Bios, virtualization is enabled under CPU options. The device list does list everything, including the LSI card. I do also see all drives.
The fact that NO device is "capable" to pass through, it seems like something is wrong but I have no idea what. I've been searching and have seen a couple others having the same problem but no solution as of yet. I tried one suggestion and that was to disable VMkernel.Boot.disableACSCheck which had no effect.
In the logs tab, I see a few lines that seem to say something about it but searching has yet to lead me anywhere... still searching.
vmkwarning.log
0:00:00:04.666 cpu0:65536)WARNING: AMDIOMMU: 1475: failed to find IVRS in ACPI table!
0:00:00:04.666 cpu0:65536)WARNING: AMDIOMMU: 836: failed to detect any AMD IOMMU device!
0:00:00:04.666 cpu0:65536)WARNING: IOV: 88: IOV initialization failed
0:00:00:04.759 cpu0:65536)WARNING: Serial: 274: logPort initialization failed
0:00:00:04.759 cpu0:65536)WARNING: Serial: 283: gdbPort initialization failed
0:00:00:04.759 cpu0:65536)WARNING: Serial: 300: shellPort initialization failed
0:00:00:04.759 cpu0:65536)WARNING: Serial: 317: consolePort initialization failed
0:00:00:04.795 cpu0:65536)WARNING: Power: 1989: Not all CPUs have the same number of T-states detected; limiting to 0 T-states
2017-12-22T18:38:19.056Z cpu0:65950)WARNING: Keyboard: 956: Ignoring registration attempt: External USB driver already registered.
2017-12-22T18:38:19.056Z cpu0:65950)WARNING: VMKAPICore: 2423: Failed to register external keyboard driver, type: 1
2017-12-22T18:38:19.056Z cpu0:65950)WARNING: Ignoring vmk_RegisterKeyboardDriver failure: usb keyboard driver is already registered
2017-12-22T18:38:19.057Z cpu1:65930)WARNING: xhci_pci_attach:208: xhci devid 0x11421b21: Success
2017-12-22T18:38:31.512Z cpu1:65930)WARNING: xhci_pci_attach:208: xhci devid 0x11421b21: Success
2017-12-22T18:38:42.594Z cpu2:65930)WARNING: VMK_PCI: 722: device 0000:00:11.0 failed to allocate MSI interrupt
2017-12-22T18:38:42.594Z cpu2:65930)WARNING: VMK_PCI: 740: device 0000:00:11.0 failed to allocate 1 MSIX interrupts
2017-12-22T18:38:42.594Z cpu2:65930)WARNING: vmw_ahci[00000011]: driverAttachDevice:ERROR: cannot allocate MSI/MSI-X interrupt, trying INTx
2017-12-22T18:38:43.102Z cpu2:65930)WARNING: vmw_ahci[00000011]: ProbeDevice:No device
2017-12-22T18:38:43.208Z cpu2:65930)WARNING: vmw_ahci[00000011]: ProbeDevice:No device
2017-12-22T18:38:43.313Z cpu2:65930)WARNING: vmw_ahci[00000011]: ProbeDevice:No device
2017-12-22T18:38:43.417Z cpu2:65930)WARNING: vmw_ahci[00000011]: ProbeDevice:No device
2017-12-22T18:38:49.079Z cpu2:65877)WARNING: NetDVS: 681: portAlias is NULL
2017-12-22T18:38:49.331Z cpu0:66126)WARNING: Tcpip: 1282: failed to unset gateway (error = 0x31)
2017-12-22T18:39:01Z mark: storage-path-claim-completed
2017-12-22T18:38:59.903Z cpu1:66413)WARNING: FTCpt: 875: Using IPv6 address to start server listener
2017-12-22T18:39:08.699Z cpu0:66769)WARNING: PCI: 179: 0000:02:00.0: Bypassing non-ACS capable device in hierarchy
2017-12-22T18:39:08.699Z cpu2:66769)WARNING: PCI: 179: 0000:03:00.0: Bypassing non-ACS capable device in hierarchy
2017-12-22T18:39:08.699Z cpu2:66769)WARNING: PCI: 179: 0000:03:00.1: Bypassing non-ACS capable device in hierarchy
vmkeventd.log
2017-12-22T17:48:10Z vmkeventd[66361]: message handler 1 failed: Busy
2017-12-22T18:38:18Z vmkeventd[65905]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2017-12-22T18:38:18Z vmkeventd[65905]: DICT --- GLOBAL SETTINGS /usr/lib/vmware/settings
2017-12-22T18:38:18Z vmkeventd[65905]: DICT --- NON PERSISTENT (null)
2017-12-22T18:38:18Z vmkeventd[65905]: DICT --- HOST DEFAULTS /etc/vmware/config
2017-12-22T18:38:18Z vmkeventd[65905]: DICT libdir = "/usr/lib/vmware"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT authd.proxy.nfc = "vmware-hostd:ha-nfc"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT authd.fullpath = "/sbin/authd"
2017-12-22T18:38:18Z vmkeventd[65905]: DICT --- SITE DEFAULTS /usr/lib/vmware/config
2017-12-22T18:38:18Z vmkeventd[65905]: vmkmod: /vmfs is a not a regular file
2017-12-22T18:38:18Z vmkeventd[65905]: VMKMod_ComputeModPath failed for module vmfs: "Bad parameter" (bad0007)
2017-12-22T18:38:18Z vmkeventd[65926]: message handler 1 failed: Busy
2017-12-22T18:39:01Z mark: storage-path-claim-completed
2017-12-22T18:38:59Z vmkeventd[66362]: message handler 1 failed: Busy
These lines:
0:00:00:04.666 cpu0:65536)WARNING: AMDIOMMU: 1475: failed to find IVRS in ACPI table!
0:00:00:04.666 cpu0:65536)WARNING: AMDIOMMU: 836: failed to detect any AMD IOMMU device!
0:00:00:04.666 cpu0:65536)WARNING: IOV: 88: IOV initialization failed
would lead me to guess that IOMMU is not enabled in your BIOS/UEFI. Have you checked your BIOS settings to make sure all virtualization/IOMMU options are enabled?
https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371P.H.O.N.E# I_866_2o2_l499NEXT Amazon prime support number @$ Amazon prime Support Phone numberhttps://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371https://communities.vmware.com/message/2731371#2731371P.H.O.N.E# I_866_2o2_l499NEXT Amazon prime support number @$ Amazon prime Support Phone numberP.H.O.N.E# I_866_2o2_l499NEXT Amazon prime support number @$ Amazon prime Support Phone number
Hello All. I installed ESXi 6.0 on my DL380 g7 and it keeps crashing randomly when I am using the 2 VMs I have. I attached a picture of the error I am getting. I am starting to think its hardware related but I am hoping someone can provide more input. Thanks in advance.
I think you meant you installed ESXi 5.5, maybe? In any case, this is a known issue with HP and a buggy SmartArray driver. They published an advisory on it here.
Hi,
Thank you so much for the reply. I understand your reply but I have been able to install macOS on VMware on a system not using official apple hardware. Now, I wanna do the same job on ESXi, I would appreciate any help.
Thanks in advance
Have you tried install it in Fusion under Mac OS the upload to ESXi?
Hi,
Thank you so much for the reply.
No, I have tried it. How to do that?
Thanks in advance
Ah yes, you're right! I could also order an IP for KVM at my datacenter and work on it.
(Why I fail to se easiest answers at first always baffles me !)
Thanks!
Although, if the root password currently does not work via the web UI and SSH, will it still work on DCUI? (I would guess so, but asking just in case...)
Thanks for the reply. I already updated the smart array driver and I am still getting the PSOD.
Is the firmware also updated?
Only way to know is try.