Hello,

We are trying to get PXE boot working in VMware.

I am seeing very inconsistency when i do PXE boot installation. Sometime it does get DHCP address and works and sometimes it does not and time out. Our DHCP server is running on a VM on the same subnet i am trying to PXE boot. I do see in logs on DHCP server that it is offering IPs when requested. However, sometime its just time out in VMware without sending a request to DHCP server. Any idea where to start from ?

This is my dhcp server config :-

[root@pscfpl86 log]# cat /etc/dhcp/dhcpd.conf

ddns-update-style interim;

allow booting;

allow bootp;

option domain-name "xxxx.xxxx";

option domain-name-servers ns1.xxx.xxx, ns2.xxxx.xxxx;

default-lease-time 21600;

max-lease-time 43200;

authoritative;

ignore client-updates;

set vendorclass = option vendor-class-identifier;

subnet 10.11.12.0 netmask 255.255.255.0 {

        option routers                  10.11.12.1;

        max-lease-time                  1800;

        min-lease-time                  1800;

        default-lease-time              1800;

        option domain-name-servers      10.11.12.1;

        option subnet-mask              255.255.255.0;

        option domain-name              "xxxx.xxxx";

        range dynamic-bootp             10.11.12.5 10.11.12.100;

        filename                        "pxelinux.0";

        next-server                      10.11.12.2;

}

And when i get DHCP request from a VM, i can see it in logs :-

[root@pscfpl86 log]# tail -f messages

Dec 27 08:45:50 pscfpl86 dhcpd: DHCPOFFER on 10.11.12.10 to 00:50:56:90:20:ab via ens224

Dec 27 08:45:50 pscfpl86 dhcpd: DHCPREQUEST for 10.11.12.10 (10.11.12.1) from 00:50:56:90:20:ab via ens224

Dec 27 08:45:50 pscfpl86 dhcpd: DHCPACK on 10.11.12.10 to 00:50:56:90:20:ab via ens224

Dec 27 08:46:04 pscfpl86 dhcpd: DHCPREQUEST for 10.11.12.10 from 00:50:56:90:20:ab via ens224

I downloaded the Windows 10 1809 and Server 2019 ISOs the day they became available so I can start working on my templates.

I built the templates with EFI, paravirtual for the C drive and vmxnet3 adapter. I've been using this combo for other versions of windows 10/8/7and windows server 2008r2/2012r2/1016 without issue.

So far Windows 2019 (with desktop experience) seems to be ok at least for a basic vm and guest customization. Haven't tried anything else yet.

Windows 10 1809 on the other hand is very, very slow to reboot after the initial install or even just rebooting after making some changes post install. After installing the OS it took 10-15 minutes for the initial windows setup stuff (user, security settings, etc) to appear . I tried a VM set to BIOS and it seemed faster but was still quite slow. Server 2019 and other versions of windows 10 have no issue.

The hosts are esxi 6.5 and 6.7.

I haven't had a chance to try every combo of BIOS/EFI/vmxnet3/e1000e/paravirtual/lsi sas to see if one is the cause of the issue but was wondering if anyone else had noticed any issues or if it was just me?

Thanks

I'm currently on ESXi 6.5u1 (without vCenter) and have MegaRAID discovery working and can see the status and get alerts but I would like to update to ESXi 6.7.

Has anyone come up with a decent way to monitor and send email alerts about RAID, drive, battery, etc. issues concerning a ESXi 6.7 machine that has a LSI 9260-8i controller card? It seems VMWare and Broadcom will never add support for ESXi 6.7.

Motherboard I'm using with esxi came preloaded with default strings for Manufacturer and Model information. Both show up as "To Be Filled By O.E.M." within esxi. Alas these strings are not customization via the bios, and the bios image would need to be manually edited to specify them at the source.

Is there a setting to override these strings on the esxi level? Something that would use a specificed value instead of a string acquired from BIOS? Alternative would be to hide the two entries, as this would be preferred to showing an incomplete setup process.

Perhaps these values are read in one time during the setup? Is there a file I can edit via SSH to override these values?

Thank you,

Gene

Hi,

did anyone come across the problem that two identically configured ESXi talking to a linux server over ipv6, one with version 6.0 will work but v6.7 won't. Further debugging the problem lies in the ESP Auth section of the frames. The v6.7 stack generates a 4 byte longer ESP Auth with the same settings (transport mode, 3des-cbc, hmac-sha2-256 on both).

On the linux end I configured tcpdump with the keys, and v6.0's ping can be decoded, also the v6.7 payload seems correct, but the latter never gets a response, I am thinking it gets thrown out. Also when the linux end initiates the ping it generates frames with the same length as v6.0.

esxcli network ip ipsec sa list's output is identical.

so is the linux side's setkey -D

And since tcpdump can decode at least the data, suggest that the ESP should be correct, but even tcpdump is weirding out on unpacking it.

On the working one:

ESP(spi=0x00000200,seq=0x26804), length 100: [bad icmp6 cksum 0x2508 -> 0x4394!] ICMP6, echo request, seq 0

gets a reply:

ESP(spi=0x00000300,seq=0x1f2a0), length 100: [bad icmp6 cksum 0x2408 -> 0x9506!] ICMP6, echo reply, seq 0

But on the broken one:

sometimes: ESP(spi=0x00000201,seq=0x364), length 104

sometimes: ESP(spi=0x00000201,seq=0x365), length 104: ip-proto-77 54

no replies.

Any ideas? I am down to try to decode the captured frames manually and see what hmac the esxi used in reality, but that's kinda tedious.

Thank you

Levi

[root@localhost:~]  esxcli software vib update -d /vmfs/volumes/paul\/ESXi650-201712001.zip

[StatelessError]

The transaction is not supported: VIB VMW_bootbank_nmlx4-core_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_nmlx4-rdma_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMware_bootbank_esx-tboot_6.5.0-1.36.7388607 cannot be live installed. VIB VMW_bootbank_nmlx4-en_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.3.0-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_misc-drivers_6.5.0-1.36.7388607 cannot be live installed. VIB VMW_bootbank_nvme_1.2.0.32-5vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_vmkusb_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMware_bootbank_esx-base_6.5.0-1.36.7388607 cannot be live installed. VIB VMware_bootbank_vsan_6.5.0-1.36.7388608 cannot be live installed. VIB VMW_bootbank_nvmxnet3_2.0.0.23-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_igbn_0.1.0.0-15vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_vmkata_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.2.0-1vmw.650.1.26.5969303 cannot be removed live. VIB MEL_bootbank_nmlx4-en_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMware_bootbank_vsan_6.5.0-1.26.5912915 cannot be removed live. VIB VMware_bootbank_esx-base_6.5.0-1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-tboot_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_igbn_0.1.0.0-14vmw.650.1.26.5969303 cannot be removed live. VIB MEL_bootbank_nmlx4-core_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMW_bootbank_misc-drivers_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvmxnet3_2.0.0.22-1vmw.650.1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvme_1.2.0.32-4vmw.650.1.26.5969303 cannot be removed live. VIB Avago_bootbank_scsi-mpt2sas_15.10.07.00-1OEM.550.0.0.1331820 cannot be removed live. VIB MEL_bootbank_nmlx4-rdma_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live.

Please refer to the log file for more details.

I have a ESXi host sat in a vCenter Cluster, from a virtualisation layer everything is working fine, VMs are sat on host, can migrate to and from host. All the hosts in the cluster are running the same version of hypervisor, same firmware. Using standard switches, active standby... able to ping the host fine

the problem with the host is the monitoring via OpsView isnt working. Just for this one host. again, the Ops view setup is identical to the other hosts in the cluster...

started with a simple reboot followed by an update of the firmware. changed the VMNICs around, from vmnic1 being the active to 2 being the active...

i can ping the gateway from the host, also able to ping out to the jump box

Any suggestions?

I've upgraded a HP Proliant Gen9 to VMware ESXi, 6.7.0, 15160138 using the latest custom image.

After that I checked compliance for baseline Critical Host Patches (Predefined) - and get the status "Incompatible".

In task log I get the message:

Host patch ESXi670-201912001 conflicts with the package EMU_bootbank_scsi-be2iscsi_10.5.101.0-1OEM.600.0.0.2159203 installed on the host and cannot be staged.

Stays the same after resetting the VUM database.

Any suggestions?

VMware ESXI 6.7 on a VM created with virtualbox 6.1 is failing with GP exception 13. Where as the same version of ESXI is installable on a VM created with VirtualBox 6.0.

I was initially using VirtualBox 6.0 with ESXI version 6.7.  I got an error while powering on a vm from the vsphere. Please find the attach screenshot.

Even though, VT-x is enabled, esxi was complaining about virtualization not configured. There seems to be a possible fix in VirtualBox 6.1 version, which allows us to use the enable vt-x option explicitly(Which was greyed out in 6.0 version of Virtual box).

But when I tried using the new version of virutal box(6.1), esxi is failing to install with GP 13 error.

Hello,

I'm trying to install updates from a zip file but always gives the same error. "No Space Left On Device"

But there is a plenty of space on Device.

When i try to run

esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201703001.zip

it gives that error:

[InstallationError]

[Errno 28] No space left on device

       vibs = VMware_bootbank_misc-drivers_6.0.0-3.57.5050593

Please refer to the log file for more details.

And in the log file:

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:50Z esxupdate: BootBankInstaller.pyc: WARNING: Cannot remove staging directory: [Errno 16] Device or resource busy: '/tmp/stagebootbank'

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:51Z esxupdate: root: ERROR: Traceback (most recent call last):

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 462, in <module>

2017-04-02T00:13:51Z esxupdate: root: ERROR:     main()

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 453, in main

2017-04-02T00:13:51Z esxupdate: root: ERROR:     ret = CMDTABLE[command](options)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 362, in VibInstallCmd

2017-04-02T00:13:51Z esxupdate: root: ERROR:     checkacceptance=checkacceptance)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 250, in InstallVibsFromSources

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 356, in _installVibs

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 399, in _validateAndInstallProfile

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 710, in Stage

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 483, in _download_and_stage

2017-04-02T00:13:51Z esxupdate: root: ERROR: InstallationError: ('VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.3.58.5224738', '[Errno 28] No space left on device')

"vdf -h" Output

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M      244K       31M   0% --

etc                        28M      204K       27M   0% --

opt                        32M        0B       32M   0% --

var                        48M      428K       47M   0% --

tmp                       256M       20K      255M   0% --

iofilters                  32M        0B       32M   0% --

hostdstats                303M        2M      300M   0% --

As you can see %0 is used on /tmp i dont know why gives that error.

How can i fix this problem ? I cant update my esxi 3620759 to 5224934.

ESXi 6.7 fully patched

Was trying to update an LSI driver and got the following message :

esxcli software vib install -v /tmp/lsi-mr3-7.707.11.00-1OEM.

670.0.0.8169922.x86_64.vib --no-sig-check

[DependencyError]

VIB Avago_bootbank_lsi-mr3_7.707.11.00-1OEM.670.0.0.8169922 requires vmkapi_2_5_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_locker_tools-light_10.2.0.7253323-8169922 requires esx-version >= 6.6.0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

Where do I find the updated vmkapi ?

Thanks,

Steve

Hello everyone,

I am trying to share disk between tow VMs hosted in serveur with ESXI 6.5 the two vm are down and I added the shared disk in the first VM of course with all configuration to make it shareable than I successfully added the disk to the second VM wich is down when I tryed to start the first it works fine but the scond VM show error message :

Power On VM 
Key  
haTask-2-vim.VirtualMachine.
powerOn-192 596 234 
Description  
Activate this virtual machine Virtual machine  oradb-shrt1 state  
Failed - LookupAndOpen [file] specific file system implementation failed errors      
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed     
File system-specific implementation of LookupAndOpen [file] failed


I have instaaled on two VM Oracle linux 7

Can you help me please ?

Best Regards,

Hello,

I have a server that I installed the latest version of ESXi 6.7 on. I have been using the hypervisor on other servers for quite a while. I have always wanted to know how to allow VMs to connect to two different internal networks. For instance, I have one switch that is set up for the 192.168.10.0/24 network, and I have another switch that is set up for the 192.168.50.0/24 network. The server I have has four Ethernet ports. I would like to set up a VM so that it can connect to both internal networks. I have looked through a variety of guides, most of which are fairly complex, and hard to understand. It is very easy to do on a real server or workstation, you just plug in a second ethernet cable to the desired switch and modify its IP accordingly.

Does someone know how to do this, or have used a guide that is easy to follow.

Thanks in advance for your help,

Darren

hi dear friends

i have 4 dl380g10 and 4  or 3 port group on each of them.PG 1 and 2 are similar but other are diffrent.one PG for vm and mgmt with 2 VMNIC .one PG with 1 vmnic for VMotion .other PG for other use.

1- is it correct that i must create every PG of my VSS in VDS?

2- how should i plan it? others told first migrate some physical NICs then vmkernels if it is right should i first mmigrate one of my mgmt VMNICS?

3-what should i do to avoid losing VDS mgmt when i lose my VC?

thank you

I installed ESXi 6.7 on a system whose only storage is a 2TB SSD. I see that the datastore occupies all available space left over after the installation. I want the space occupied by the datastore to be much smaller and I want the leftover space simply to be unallocated instead of being dedicated to ESXi. How can I accomplish that? Here's the current partition information:

Thanks,

David Habermehl

Hi All,

I am new vmware and trying to set up a test lab enviroment. I have installed and set up the sphere server. I cannot add the esxi host as I am using a free licence. it comes up with   License not available to perform the operation.The VMware vSphere 6 Hypervisor license for "Host" xxx.xxx.xxx.xxx does not include "vCenter agent for VMware host". Upgrade the license.

I have looked up to Kb Article and it says If an ESXi host is licensed with the free version of the license key, you cannot add it to vCenter Server. This license does not contain the VirtualCenter Agent, which is necessary to manage a host with vCenter Server. This feature remains locked as long as the host is licensed with the free version of the license key.

Is there a way to get around this? How can I test all the new features of vsphere and esxi 6 in a lab environment?

Thanks

Apologies if this is in the wrong section.

I have a Dell PowerEdge T130 I bought specifically to run multiple VMs on ESXi. Specifically, pfSense and FreeNAS, plus any other OS that I need to install in the future. The purpose of this is to have one machine act as a router (pfSense), NAS (FreeNAS), etc. This was connected to a Netgear Nighthawk R7000 flashed to DD-WRT and was essentially a subnet for all my devices. I enabled Promiscuous Mode to allow the manual installation/configuration of FreeNAS jails (manually assigning local IPs). This setup worked fine for several months when suddenly, I started having internet connection issues. I discovered the culprit is utopia.net starting up as a process in ESXi. I'm not sure how it became a startup process, but I reinstalled a fresh copy of ESXi on a new flash drive and reinstalled the VMs from scratch. The only stuff that persisted from the previous installation was my ESXi activation code and the FreeNAS dataset. After completing the new setup, the utopia.net malware was present immediately. At this point, I have the following theories as to how utopia.net survived a new installation:

- it's embedded in BIOS

- it's in the FreeNAS dataset

- Netgear Nighthawk router

- activation code??

The PowerEdge T130 has the following specifications:

Intel Xeon processor E3-1200

4x4tb WD Red

StarTech 4 Port PCI Express 2.0 SATA III 6Gbps RAID Controller Card with HyperDuo SSD Tiering (PPEXSAT34RH)

16x2 DDR4 ECC (Crucial CT16G4WFD824A 16Gb Ddr4 2400 Mt/S Pc4-2400 Dimm 288Pin Dr X8 Ecc Unbuff Cl17)

pfSense VM

FreeNAS VM

Linux Mint VM

Windows 7 VM

OpenVPN OVA

I can't think of anything else that would cause the malware to persist like this, so I am seeking out the knowledge/advice of others.

Hello,

We have VMware ESXi, 6.5.0, 13932383.

We are trying to set a static MAC on a VMXNET3 adapter. (we have tried E1000, same issue.)

When using C1:73:xx:xx:xx:xx the adapter in Windows comes up with Error 10, Device can't start. The same issue appears in Linux when the adapter can't start.

If we use 00:73:xx:xx:xx:xx it's fine. Other random MAC's work fine as well, it's just a MAC starting with C1 that it doesn't like.

This is being setup so we can test an application issue where by the software is MAC licensed.

Reading VMware Doco, custom MAC's outside the VMware prefix are allowed, but there is no mention of blacklisted ranges.

Any ideas.

Update command:

# esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[OSError]

[Errno 28] No space left on device

Please refer to the log file for more details.

Swap config:

All swap is on, datastore use datastore1 and more than 100G space.

Please see the /var/log/esxupdata.log below:

2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/esxupdt-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/weaselin-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: Traceback (most recent call last):^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 470, in <module>^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     main()^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 461, in main^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     ret = CMDTABLE[command](options)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 213, in ProfileUpdateCmd^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     nohwwarning=opts.nohwwarning)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esx
image/Transaction.py", line 375, in UpdateProfileFromDepot^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 2161, in cliUpgradeAction^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 997, in _parseVmwareVersion^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 514,
 in getoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 495,
 in getstatusoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 316,
 in check_output^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 383,
 in run^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 676,
 in __init__^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 1228
, in _execute_child^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: OSError: [Errno 28] No space left on device

Hi,

I have a weird problem.

Virtual machines running on the ESXi machine I can reach from outside (normal machine, on the same network). All the time.

But the virtual machines running on the ESXi host can't reach each other.

When I boot the machines, I can ping them at least for a short time. But then not anymore.

ESXI 6.7 U3 machine