Hello everyone, I've tried searching for an answer to this but have had no luck. I have one ESXi host that keeps crashing periodically (once or twice a week). I get a fuchsia  screen and have to reboot the host. In the logs and on the fuchsia screen I see the following error:

Alarm 'Host error' on x.x.x.x triggered by event 1732405 'Issue detected on x.x.x.x Duplicate name 'vpxa.19.gz' entry in cache

When I check the Events, I see a similar entry (actually there are 10 entries one after the other)

These Show as Warnings (10 of them in a row):

DC: 783: Duplicate name 'vpxa.19.gz' entry in cache

These Show as Errors (9 of them in a row):

0/23/2019, 7:33:21 AM Alarm 'Host error' on 10.0.0.96

triggered by event 1743276 'Issue detected on 10.0.0.96 in ###### HO: DC: 783: Duplicate name 'vpxa.19.gz' entry in cache. (2019-10-23T11:33:03.815Z cpu6:2097484)'

I was running ESXi 6.7.0 release 1 and tried updating to release 3 to see if that would fix the issue but it did not.

Anyone have any ideas what might be causing this or where to look for more information?

Hello, I am running esxi 6.7 enterprise plus and need to make some NFS related changes such as (Net.TcpipHeapSize = 32) but there is no host profile setting for this. And the change does not stick when made on the auto deployed host under advanced system settings on vCenter. Any recomendations? Thanks

Hello,

I bought a Chelsio N320E-SR and I am trying to connect it to a VMware 6.5 host.  The plan is do a back to back 10GB link for vmotion to another host.  The card is being recognized by VMware but I guess I am missing the drivers for it to work properly.  Does anyone know where I can get drivers for this card?

[root@localhost:~] lspci | grep -i Chelsio

0000:82:00.0 Ethernet controller: Chelsio Communications Inc T320 10GbE Dual Port Adapter

Hi,

I wonder if anyone can help in case I am missing something.

I have an X3650 M5 with Emulex VFA 5 10 GB MLE Adapter. The adapter is set so the IMM2 shares the 10GB port for management.

I have ESXI 6.7 U3 lenovo custom build which works fine without isues. I installed Lenovo Xclarity Administrator successfully but does not discover the IMM2 IP address. At first I thought it was just an issue with XClarity but using a Windows 2019 VM found that had the same issue. The IMM2 will ping successfully on any machine other than itself.

Any help would be appreciated.

Regards,

Simon

Hi guys,

I currently have a problem with one of my servers running ESXI 6.5 and using an ARECA 1883 Controller.

So, I already installed the latest update for my ESXI for 6.5 following the guide from How to update any VMware ESXi Hypervisor to the latest using ESXCLI for easy download and install | TinkerTry IT @ Home . Also I installed the correct ARECA VIB which I got for my controller from https://www.areca.com.tw/support/downloads.html.

The installation of the VIB looked fine:

esxcli software vib install -v /vmfs/volumes/SSD/scsi-arcmsr-1.40.00.09-1OEM.550.0.0.1331820.x86_64.vib

Installation Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

   VIBs Installed: areca_bootbank_scsi-arcmsr_1.40.00.09-1OEM.550.0.0.1331820

   VIBs Removed: areca_bootbank_scsi-arcmsr_1.30.00.03-1OEM.550.0.0.1331820

   VIBs Skipped:

However, in the webinterface I can see the adapter, but I can not create a new datastore:

I also had a look at /dev/disk on the shell, no sight of the RAID 10 I created on the ARECA Controller:

I am not using VMWare certified Hardware, however, I already have other server running slightly different hardware with ESXI 6.0 and 6.5 and also a different range of AREAC Controllers (e.g. 1224) and hadnt any big problems so far. But right now I am out of ideas.

Any suggestions? Also, if you need any more information, feel free to ask.

ARECA-Controller

Areca ARC-1883 SAS/SATA RAID 6 Adapter

ESXI-Version

Client version: 1.27.2

Client build number: 9210160

ESXi version: 6.5.0

ESXi build number: 10175896

Hi everyone!

It is my first post, I hope to do well.

I am really confused and need some guidance, I had a VM in esxi 6.7.0 (8169922).

with a single 900Gb virtual disk in a 940Gb Datastore.

After performing the clean installation of the operating system I made a snapshot, and then with the necessary software within the operating system, I made another snapshot and then I forgot about them.

As a result I got two snapshots (one of ~ 4Gb and the last one with ~ 36Gb) with all the information and I haven't been able to start the VM for a week.

Oddly, snapshots were created outside of the VM folder.

The first thing I try to do is delete the snapshots from the administrator in the web client, and then try to consolidate disks, the process does not throw any errors and ends, but I still see in the browser the vmdk of the snapshots outside the VM folder , just as they were previously to consolidate the disk.

So I try to move the first snapshot to an nfs folder on a seagate NAS, this process is halted and a flat ... file of ~ 930Gb ....... appears in the Datastore.

inside the snapshot that is still in the datastore, it refers to another obviously missing snapshot CID (see attached image)

and now is when i think ..

- how is it possible that a 940Gb datastore enters two 900Gb files + the last 36Gb snapshot? ...

- is this flat file an incomplete file and should I recover the deleted snapshot?

I will not comment on the other issues that come from ignorance.

I hope someone can help me and I hope this problem is not so serious.

Regards!! and thank you very much in advance.

As stated in the post title I am experiencing a PSOD on install ESXi 6.7.0 (U3) the error is as follows:

(turned greyscale so as not to burn out anyones eyes)

Hardware:

CPU: AMD Ryzen 9 3950X 3.5 GHz 16-Core Processor

Motherboard: Asus Pro WS X570-ACE ATX AM4 Motherboard

Memory: Corsair Dominator Platinum RGB 128 GB (4 x 32 GB) DDR4-3200 Memory

Video Card: Asus GeForce GTX 1080 8 GB ROG STRIX Video Card

I'm going to go out on a limb and guess its hardware compatibility issues considering the hardware but I'd like verification before I move on to use something like Proxmox instead. Ideally I wanted to use ESXi to get a bit more familiarization with it. But at this rate it seems my familiarization is just going to boil down to "Make sure everything is compatible beforehand.".

I am attempting to share a drive between two VMs.  When I provision a drive as Eagerly Zeroed without turning sharing on, after the drive formats, ESXi displays it as Lazily Zeroed.  It took several hours to format.

I was able to get around this by turning sharing on when creating the drive.  Now it shows correctly on the machine it was initially set up on:

However, when I try to set it up on another machine, the same disk appears as lazily zeroed:

I executed a mkfstools -D on the disk to verify the state, and this is the result:

Lock [type 10c00001 offset 112467968 v 44, hb offset 3440640

gen 85, mode 0, owner 00000000-00000000-0000-000000000000 mtime 659

num 0 gblnum 0 gblgen 0 gblbrk 0]

Addr <4, 3, 17>, gen 28, links 1, type reg, flags 0, uid 0, gid 0, mode 600

len 472, nb 0 tbz 0, cow 0, newSinceEpoch 0, zla 4305, bs 65536

tbz 0 should mean that the disk is eager thick, but it is still not registering correctly.

ESXi 6.5.0 Update 2 (Build 8294253).  Updating limited due to compatibility with the LSI raid controller's management package.

Hello

I have ran into a rather scary situation.  For some reasons my VM have become non responsive.  So I decided to restart it by issuing the "reset" command.  Unfortunately this resulted in the VM not being able to start up.  I tried rebooting the ESXi server and am still given the following message when attempting to start the VM.

Failed to start the virtual machine.
Module Disk power on failed. 
Cannot open the disk '/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58/<VM Name>/<VM Name>.vmdk' or one of the snapshot disks it depends on. 
22 (Invalid argument)

The screen shot looks like the image attached named "PowerOnError.jpg".

Even more puzzling is the ESXi shell isn't able to find the .vmx file.  Note I tried to list content of the directory it attempts to include the .vmx file but isn't able to.  In fact before the reboot it was included in the output of this command, in addition to showing something unable to stat file or something like that.  And if I tried to copy it it'd say Invalid Argument.  If I do something like 'strace cp <VM Name>.vmx <dest>' it'd show the error happened during the Linux system call 'open' operation with returned value EINVAL -1.

[root@esxi6prim:/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58/<VM Name>] ls -ltr
ls: ./<VM Name>.vmx: No such file or directory
total 52833280
-rw-r--r--    1 root     root             0 Oct  4  2015 <VM Name>.vmsd
-rw-r--r--    1 root     root        179092 Oct  9  2015 vmware-1.log
-rw-r--r--    1 root     root        177929 Oct 14  2015 vmware-2.log
-rw-r--r--    1 root     root     409599604 Nov 24 07:26 vmware-3.log
-rw-------    1 root     root           524 Nov 24 09:55 <VM Name>.vmdk
-rw-------    1 root     root     53687091200 Feb 17 12:52 <VM Name>-flat.vmdk
-rw-------    1 root     root          8684 Mar 28 04:42 <VM Name>.nvram
-rw-r--r--    1 root     root        270087 Mar 28 04:42 vmware.log

If I try to copy the directory to another location it'd say the following.  Note it says the <VM Name>-flat.vmdk can't be opened due to an Invalid argument despite it's shown as having a size of 53687091200 on the above 'ls' output? 53687091200

[root@esxi6prim:/vmfs/volumes/557dc2e2-2c11eba8-1494-00259066ac58] cp -rp '<VM Name>' '<VM Name>.orig.copi
ed.after.reboot'
cp: can't stat '<VM Name>/<VM Name>.vmx': No such file or directory
cp: can't open '<VM Name>/<VM Name>-flat.vmdk': Invalid argument

I'm seriously out of ideas here.  Any suggestions on how to fix this?

Thanks.

I've been putting together a whitebox esxi 6 host for my lab at home, and was attempting to get adaptec's maxview setup so that I can utilize the utility to grow the raid 6 array as I slot more drives into the case. I followed the provided instructions having already folded the latest drivers for the Adaptec card into the ISO as part of the install to have the array  visible during the installation

esxcli software vib list | grep aacraid  gets me the following

I disabled the watchdog server

and set the software acceptance level

esxcli software acceptance set –-level=CommunitySupported

and I successfully I install the vib's downloaded with the install package for Maxview VMWare (msm_vmware_v2_00_21811)

esxcli software vib install --no-sig-check -v /tmp/vmware-esx-provider-arcconf.vib

esxcli software vib install --no-sig-check -v /tmp/vmware-esx-provider-arc-cim-provider.vib

and reboot per the documentation, however after the reboot, the storage controllers are no longer recognized and the most of the GUI is unavailable.

Access to the shell via SSH is much slower and specific commands may or may not run.

I can reinstall ESXi and leave the datastores alone and on the post install reboot they come back.

Any Help would be appreciated. . .

Setup:

- ESXi 5.5u3 on Gigabyte 990FXA-UD3 motherboard (whitebox setup)

- 32GB unbuffered ECC

- Radeon 5450 GPU, ESXi console output

- Radeon 6450 GPU, passthrough

- Radeon 5450 GPU, passthrough

- USB 3.0 cards, passthrough

I've been using this setup for years.  I had a major issue today where the 5450 GPUs no longer are detected by ESXi as passthrough devices in Advanced Settings, so I removed one of the 5450 GPUs.

The only way I can get one of the 5450s detected as passthrough in ESXi is if I make it the first PCIe and that's the primary ESXi console output (via BIOS). If I change primary BIOS output to PCIe2 and have the 6450 there, the 6450 will output the ESXi console to a monitor, but 5450 passthrough disappears.  If I set BIOS primary output to PCIe1 which is a 5450, I'll see both the 5450 and 6450 as passthrough options.  If I put the 6450 in PCIe1 and the 5450 PCIe2, the 5450 never shows up in passthrough, so the only option I have right now is 5450 in PCIe1 as primary console output, and 6450 in PCIe2 for passthrough.

Now, I use passthrough successfully to a VM with the 6450, and it shows up in Windows 7 (x64 pro) display manager, but no matter what I do, in display settings, it only sees the SVGA as a display output.  I've tried different drivers, removing (even deleting drivers) for the 6450 and/or the SVGA, just can't get it to work.  Windows sees both, but I cannot output to the 6450.  Any ideas?

I would build a whole new system, but I haven't found a nice article on a 6.7 whitebox with new hardware. There's a lot else going on in the system, but when I was diagnosing I was running nothing but this Windows VM and testing with it.

Hello,

VMware vCenter Server Appliance 6.7.0.10000 (build 8217866)

VMware ESXi 6.5.0 (build 8294253)

Supermicro server with LSI MegaRAID 9261-8i

SMIS Provider 00.66.V0.02 installed

but i do not see storage array status under Monitor-Hardware Status-Sensors

Hi everyone, since the dimension of vswp equals the assigned ram (consider no reservation), what happens if I hot add virtual ram on a virtual machine? Does the vswp hot-increase its dimension or not? Thank you

I have installed ESXi 6.5 ISO on Hetzner machine. I had to use customizer to get working network drivers otherwise installation would not proceed.

After days of fixing this I have got ESXi 6.5 working, but I can't get the VM to share same internet connection as the host/machine. I do not have any additional IPs, I just have a basic server with 1 IP but I have seen setups where people have been able to get internet without problems on the VM with the host/machine IP.

Please don't ask me to search or say it has been solved in many other posts, I promise I tried searching but all results I have seen have such specific setups. I do not want to use pfSense or anything like that. I just want the VM to use same internet connection as the host/machine.

Thank you so much really appreciate any help!

One of my team mates ran a packet capture so as to generate only 10MB files. I believe

his intention was that it would create one 10MB file and stop. But it made another and

another until the session became stuck. We'll reboot the host and everything's still

running ok. But the question is - what would be the syntax to create packet capture

for a certain vmnic that outputs one and only one file of size 10MB?

Thank you.

Hi all,

After running for a long time without any problems. Some vms started to hang.

They're not reacting on anyting. The CPU usage is 0 Hz and if you try to take over the vmware console of the vm, the connection will be interupted.

So I started to dig in the logs of the virtual machine, and found a lot of log entries like this:

Log for VMware ESX version=6.7.0 build=build-14320388

2019-12-07T14:14:01.622Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.627Z| vcpu-0| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.630Z| vcpu-0| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.634Z| vcpu-4| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.637Z| vcpu-0| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.639Z| vcpu-0| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.643Z| vcpu-3| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.647Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.650Z| vcpu-0| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.653Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.657Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.660Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.662Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.668Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.673Z| vcpu-2| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

2019-12-07T14:14:01.679Z| vcpu-4| W115: Memory regions  (0xfc000000, 0xfcfff000) and  (0xfc810000, 0xfc81f000) overlap (0x54f0024000 0x5520026000).vcs = 0xfff, vpcuId = 0xffffffff

And after this:

2019-12-07T14:14:01.679Z| vcpu-4| E105: PANIC: PhysMem: creating too many Global lookups.

2019-12-07T14:14:08.634Z| vcpu-4| W115: A core file is available in "/vmfs/volumes/5cdd51ee-fd4310f2-58c4-24b6fd652bce/0-pg-virtgpu008/vmx-zdump.000"

2019-12-07T14:14:08.634Z| mks| W115: Panic in progress... ungrabbing

2019-12-07T14:14:08.634Z| mks| I125: MKS: Release starting (Panic)

2019-12-07T14:14:08.634Z| mks| I125: MKS: Release finished (Panic)

2019-12-07T14:14:08.643Z| vcpu-4| I125: Writing monitor file `vmmcores.gz`

2019-12-07T14:14:08.722Z| vcpu-4| W115: Dumping core for vcpu-0

2019-12-07T14:14:08.722Z| vcpu-4| I125: VMK Stack for vcpu 0 is at 0x451ae7c93000

2019-12-07T14:14:08.722Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:09.115Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:09.116Z| vcpu-4| W115: Dumping core for vcpu-1

2019-12-07T14:14:09.116Z| vcpu-4| I125: VMK Stack for vcpu 1 is at 0x451af3b13000

2019-12-07T14:14:09.116Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:09.510Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:09.510Z| vcpu-4| W115: Dumping core for vcpu-2

2019-12-07T14:14:09.510Z| vcpu-4| I125: VMK Stack for vcpu 2 is at 0x451aebb13000

2019-12-07T14:14:09.510Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:09.904Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:09.905Z| vcpu-4| W115: Dumping core for vcpu-3

2019-12-07T14:14:09.905Z| vcpu-4| I125: VMK Stack for vcpu 3 is at 0x451aeb713000

2019-12-07T14:14:09.905Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:10.300Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:10.300Z| vcpu-4| W115: Dumping core for vcpu-4

2019-12-07T14:14:10.300Z| vcpu-4| I125: VMK Stack for vcpu 4 is at 0x451affd13000

2019-12-07T14:14:10.300Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:10.692Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:10.693Z| vcpu-4| W115: Dumping core for vcpu-5

2019-12-07T14:14:10.693Z| vcpu-4| I125: VMK Stack for vcpu 5 is at 0x451af0313000

2019-12-07T14:14:10.693Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:11.085Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:11.085Z| vcpu-4| W115: Dumping core for vcpu-6

2019-12-07T14:14:11.085Z| vcpu-4| I125: VMK Stack for vcpu 6 is at 0x451afcb13000

2019-12-07T14:14:11.085Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:11.474Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:11.474Z| vcpu-4| W115: Dumping core for vcpu-7

2019-12-07T14:14:11.474Z| vcpu-4| I125: VMK Stack for vcpu 7 is at 0x451af2813000

2019-12-07T14:14:11.474Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:11.941Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:11.941Z| vcpu-4| W115: Dumping core for vcpu-8

2019-12-07T14:14:11.941Z| vcpu-4| I125: VMK Stack for vcpu 8 is at 0x451af4913000

2019-12-07T14:14:11.941Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:12.334Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:12.334Z| vcpu-4| W115: Dumping core for vcpu-9

2019-12-07T14:14:12.335Z| vcpu-4| I125: VMK Stack for vcpu 9 is at 0x451ae7293000

2019-12-07T14:14:12.335Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:12.728Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:12.728Z| vcpu-4| W115: Dumping core for vcpu-10

2019-12-07T14:14:12.728Z| vcpu-4| I125: VMK Stack for vcpu a is at 0x451af4f93000

2019-12-07T14:14:12.728Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:13.121Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:13.122Z| vcpu-4| W115: Dumping core for vcpu-11

2019-12-07T14:14:13.122Z| vcpu-4| I125: VMK Stack for vcpu b is at 0x451ae8913000

2019-12-07T14:14:13.122Z| vcpu-4| I125: Beginning monitor coredump

2019-12-07T14:14:13.514Z| vcpu-4| I125: End monitor coredump

2019-12-07T14:14:34.966Z| vcpu-4| I125: Printing loaded objects

So the vms has crached, and it sort of looks like memory related.

I have more vms like this.

Anyone any idea ??

Thanks!!

Has anyone seen these errors before when trying to take a snapshot??

An error occurred while taking a snapshot: msg.snapshot.error-NOTFOUND.

An error occurred while saving the snapshot: msg.snapshot.error-NOTFOUND.

Thanks !!!!

(Moderator edited title)

I installed ESXI 6.7u3 and after configuring all my VMs I went to configure autostart and restarted ESXI for testing.

To my surprise, when the ESXI went up, an error screen appeared.

Exception 14 in world 2097930. I searched and found nothing about this error.

Could someone guide me?

So I just downloaded the 60 day trial version of vSphere 6.7 u3b on an HP Gen10 dl380. Booted and installed from a usb, but during the install it skipped the entire section where I'm suppose to walk through the setup, create root pwd, etc...it's like it literally auto installed everything on it's own. Now I can't even login through the DCUI since I don't know the root pwd. 

First time experiencing this. Is there a way to reset the root pwd? or am I suppose to install the base 6.7 version first?

Any Suggestions?

Thanks in advance!

Hi all,

With the current climate and COVID-19 I just wanted to document an issue I had and a workaround as I presume more and more people are currently working from home.

We, as a small business, have ESXi installed on a physical machine at our business premises. I am responsible for our IT network and today I had a call regarding a issue with one of the VM's, I connected to our VPN and was able to ping the ESXi host but couldn't access it via the client or web browser. The only way I had of connecting to it was through remote desktop to an on-site computer and accessing it through a web browser.

Our network config is as follows:

I can access other servers on the business network so I knew it must be an issue with the ESXi server, rather than the network config.

It was fixed by logging into the ESXi host via SSH and running the following command:

esxcli network ip route ipv4 add -g 192.168.1.1 -n 10.0.0.0/24

and after this, I could connect via the client and web browser from my home PC. I hope this helps!