I have several Esxi 6.0 hosts that have several servers on each.  I wanting to use a web client, not vsphere client, to access them.  Ultimately what I need to do is be able to create a Port Group with 4 vnics so I can use vlan tags.  Is this do able without having vCenter?

Hello everyone,

I would like ask you for an advise.

This is only about my home lab, so just simple one esxi host without vcenter.

I am also using Nakivo as backup solution for my lab thats running on QNAP.

So far they were both on same subnet running without issues.

This week I added a 10GB connection to both devices and have just direct cable connection between them.

From esxi and VMs on top of it I can reach the QNAP without problem (NFS, SMB, SSH).

Also from QNAP itself I can SSH to the ESXi host.

All this using the 10GB connection.

But when I add this host with a new IP to Nakivo It all behaves very weird.

I know Nakivo is using ports 902 and 443, but nothing is being blocked on esxi side.

The only message I receive in hostd logs on esxi is

Accepted password for user nakivo from 192.168.168.5

2019-04-09T20:15:32.268Z info hostd[2098603] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=6eee63d1] Event 1208 : User nakivo@192.168.168.5 logged in as Java/1.8.0_181

2019-04-09T20:15:33.068Z info hostd[2098603] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=6eee6459 user=nakivo] Event 1209 : User nakivo@192.168.168.5 logged out (login time: Tuesday, 09 April, 2019 08:12:27 PM, number of API invocations: 0, user agent: Java/1.8.0_181)

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Activation [N5Vmomi10ActivationE:0x00000098031a9820] : Invoke done [retrieveContents] on [vmodl.query.PropertyCollector:ha-property-collector]

2019-04-09T20:15:36.182Z verbose hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Arg specSet:

--> (vmodl.query.PropertyCollector.FilterSpec) [

-->    (vmodl.query.PropertyCollector.FilterSpec) {

-->       propSet = (vmodl.query.PropertyCollector.PropertySpec) [

-->          (vmodl.query.PropertyCollector.PropertySpec) {

-->             type = "vim.HostSystem",

-->             all = false,

-->             pathSet = (vmodl.PropertyPath) [

-->                "config"

-->             ]

-->          }

-->       ],

-->       objectSet = (vmodl.query.PropertyCollector.ObjectSpec) [

-->          (vmodl.query.PropertyCollector.ObjectSpec) {

-->             obj = 'vim.HostSystem:ha-host',

-->             skip = false,

-->             selectSet = <unset>

-->          }

-->       ],

-->       reportMissingObjectsInResults = <unset>

-->    }

--> ]

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Throw vmodl.fault.SystemError

2019-04-09T20:15:36.182Z info hostd[2099204] [Originator@6876 sub=Solo.Vmomi opID=6eee636e user=nakivo] Result:

--> (vmodl.fault.SystemError) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    reason = "System exception while trasmitting HTTP Response:

--> error id = 32

--> "

-->    msg = ""

--> }

2019-04-09T20:15:36.182Z error hostd[2099204] [Originator@6876 sub=Default opID=6eee636e user=nakivo] Failed to send response to the client: Data already transmitted; cannot reset.

I am sure there is no blocking, network is setup correctly.

The thing I am not sure about is how in general esxi works with 2 management interfaces.

I would be very glad if you have any suggestions.

BR,

Jan

We recently purchased 8 new HPE DL380 Gen10 servers. They came with two 10Gbe ports embedded on the motherboard and two 10Gbe ports on a PCI card. All of these use the Intel X710 controller. Before I purchased these servers I had no idea how many problems these particular nics have given people. Here is a sampling of issues:

Install ESXi 6.5 on R730 with Intel X710

https://lonesysadmin.net/2018/02/28/intel-x710-nics-are-crap/

http://www.v-strange.de/index.php/15-vmware/239-vsphere-6-5-with-intel-x710-network-adapter

VMware Knowledge Base

I have two DAC cables hooked from this server to my Juniper switch. In the ESXi console I select both of these nics for my management network, give it an IP address, mask, gateway, and dns server. I reboot the host and during the boot process pings to the management interface start working. Once the host is up and running for about 30 seconds, the pings stop. If I remove one of the nics from the management network, pings start again. In other words, when two nics are connected for the management network, it will not work. I have upgraded the driver and firmware on the HPE Ethernet 10Gb 2-port 562SFP+ Adapter (it uses the Intel X710 controller) thinking it might help. We are now sitting at driver version 1.5.8 and firmware 10.2.5. The server is running HPE customized ESXi 6.5 Update 1

Do you think the problem I am experiencing (two nics for the management network will not work) is caused by this controller?

Are there other things I can check that might be causing this behavior?

Im trying to install a certificate into ESXi using the web browser but the key I'm pasting isn't working.  I'm not sure if it's an issue with the ESXi host or with the key.  The error message I'm receiving is:

Key 

haTask--vim.host.CertificateManager.installServerCertificate-138780645

Description 

Installs a server certificate for the host

State 

  Failed  - Cannot change the host configuration. 

Errors

--------------------------

And that's it

*The purpose of me installing this cert is so that I can use SSH auth via PowerCLI. 

Please help!

is there a limit or recommendation on how many simulataneous unmap commands I can run per datastore simultaneously on a single host?

I got over 100 luns attached to a cluster and I want to run unmap on all the luns simultaneously

Hi,

I am aware Intel NUC isn't supported by VMware as a hardware to run on, but it does appear to be used a lot on home labs. I've come across an issue that appears to relate to e1000 network driver (according to Intel), and it involves the inability to wake the NUC machine via WOL (Wake-on-LAN) packet after it has been shutdown (via ESXi console or GUI). It works fine if you wake the machine up just after you switch the power on at the socket. But the minute you use a manual shutdown in ESXi, it will no longer wake up via WOL packet.

It has been raised here with Intel NUC:
https://forums.intel.com/s/question/0D70P000006GX2K/cannot-wol-with-intel-nuc8i7bek-after-shutting-down-esxi-67u1?langua…

But the conclusion by Intel is that it is caused by NE1000 driver VIB used in VMWare.

Anyone else have this issue, or have any ideas how I could potentially solve this?

Hi all

we have an strange problem,

in VCSA 6 , many of our esxi 6 hosts which have valid IP addresses become "not responding" and after disconnect and reconnect, we get the error say: "request time out"

I tried most of solutions like, restaring esxi host or restaring vcsa,  regenerating ssl certificare on host, checking 902 and 443 ports on both sides (either host or vcenter) they are open and can also both sides can ping each other. (even disabling firewall totally on host). but didn't resolved. there are only 2 points, when we change IP address of the esxi host with another ip in same subnet, it will add successfully to vcenter but after a few days it became like the previous IP and not responding, same problem... and the second point is when we try to add the problematic host to a secondary vcsa, it will add without problem. my doubt is that main problem should exist on our main VCSA and if some logs are causing problem which ones are safe to delete on vcsa? or anyone can kindly help us with this issue? thanks in advandce

Has anyone had any success figuring out how to get ESXi to run on a ZBook 15 G5? Installation succeeded after setting ignoreHeadless=TRUE, but ESXI startup stops with:

Shutting down firmware services...

Using 'simple offset' UEFI RTS mapping policy

Relocating modules and starting up the kernel...

I did set the ignoreHeadless=TRUE as a boot option for ESXi.

Hello,

I have one ESXi 6.0U3 (5050593) and my vCenter is 6.0U3h (9313458)

If I connect my ESXi to my vCenter using the IP everything it´s ok... But if I connect my ESXi to my vCenter using the hostname (not FQDN) apparently connects but after more or less 60 second disconnects from the vCenter.

What´s the issue?

Thanks

Is VMware supporting the HPE Dual microSD flash USB stick?

This is a software RAID controller variant, and VMware does not support Software Raid. is that so?

I would like to know if I can install Esxi on it?

Hello,

I have 2 ESXi hosts (6.5 10719125) that are hosted on HP ProLiant BL 460c Gen9. And I have for both of them this configuration issues message: "Host profile apply failed with error: Unexpected error updating task config spec: Unknown..". There is no host profile attached. I checked logs and founded nothing pointing to this issue . Any idea? Thank  you

How do I configure esxi 6.7 to send HTTP   "Strict-Transport-Security" header?  I'm looking online and in the KB but I seem to be finding more definitions than configuration solutions.  One thing I'm using ESXI 6.7 the free version so where do i go to get nut and bolts info

TNX

Hi Everyone,

We have just noticed that our datastore is missing and we cannot see it under the ESXi webpage.

Not sure when did this happen, but maybe after we have updated the Esxi to 6.7.

The VMs are running fine.

We can see the Adapter under Storage -> Adapters.

We can see the hard drive under Storage -> Devices.

But the Datastore is empty and we cannot change any settings of the VMs as it throws an error

When I try to browse: "There are no browsable datastores. Currently, only vSAN and local VMFS datastores can be browsed."

I have tried to figure it out and run a few commands under SSH, but I cannot see what could be the issue or how to fix it.

Could you please let me know how to get back the datastore?

esxcli storage vmfs extent list

    Volume Name  VMFS UUID                            Extent Number  Device Name                           Partition

    -----------  -----------------------------------  -------------  ------------------------------------  ---------

    datastore1   5c8a7789-1a4c3a5c-0a47-b083fec42bdd              0  naa.6b083fe0cfb8ba002400ee74143fdef7          3

esxcfg-mpath -l

    sas.5b083fe0cfb8ba00-sas.6000ee74143fdef7-naa.6b083fe0cfb8ba002400ee74143fdef7

       Runtime Name: vmhba0:C2:T0:L0

       Device: naa.6b083fe0cfb8ba002400ee74143fdef7

       Device Display Name: Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)

       Adapter: vmhba0 Channel: 2 Target: 0 LUN: 0

       Adapter Identifier: sas.5b083fe0cfb8ba00

       Target Identifier: sas.6000ee74143fdef7

       Plugin: NMP

       State: active

       Transport: sas

       Adapter Transport Details: 5b083fe0cfb8ba00

       Target Transport Details: 6000ee74143fdef7

esxcfg-scsidevs -c

    Device UID                            Device Type      Console Device                                            Size      Multipath PluginDisplay Name

    naa.6b083fe0cfb8ba002400ee74143fdef7  Direct-Access    /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7  3814400MB NMP     Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)

esxcli storage vmfs snapshot list

     This returns nothing...

esxcli system coredump partition list

    Name                                    Path                                                        Active  Configured

    --------------------------------------  ----------------------------------------------------------  ------  ----------

    naa.6b083fe0cfb8ba002400ee74143fdef7:7  /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:7   false       false

    naa.6b083fe0cfb8ba002400ee74143fdef7:9  /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:9    true        true

partedUtil getptbl /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7

    gpt

    486267 255 63 7811891200

    1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

    5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

    2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

    3 15472640 7811891166 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

If I run a rescan on the device the kernel log shows this:

2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)World: 11943: VC opID 24fae6e5 maps to vmkernel opID b3571b7d

2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)NVDManagement: 1461: No nvdimms found on the system

2019-04-11T16:47:25.437Z cpu2:2097756)ScsiDeviceIO: 3068: Cmd(0x459a41156c40) 0x1a, CmdSN 0x11be from world 0 to dev "naa.6b083fe0cfb8ba002400ee74143fdef7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)World: 11943: VC opID 24fae6ee maps to vmkernel opID bf5b1e18

2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4616: Device rescan time 16 msec (total number of devices 5)

2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4619: Filesystem probe time 30 msec (devices probed 3 of 5)

2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4621: Refresh open volume time 1 msec

I'm relatively new to ESXi. I ordered a new workstation PC and tried to install ESXi 6.7 in UEFI mode on it. The installation won't start in UEFI with the following message.

using simple offset uefi rts mapping policy 

It gets stuck after this message.

Right afterwards I tried to install in legacy. The installation finishes successfully however it won't boot afterwards stating that it can't find a disc to boot from.

The PC is on the latest BIOS version.

The following hardware is used:

• Intel Xeon E-2176G 6C CPU
• (4x16GB) DDR4 2666 DIMM ECC
• NVIDIA Quadro P400 2GB (3)mDP GFX
• 2x Intel I210-T1 Ethernet Server Adapter

Many thanks in advance!

Update: Using the HPE custom image results in the exact same behaviour

Nachricht geändert durch Christoph Muehlbacher

Hi

i have a partner who bought a server wit h VMware OEM licenses inside.

now he would like to move his server to an another country EEC ( from Germany to Poland)

Same firm, just the country changes

is it compliant ? i saw in the VMware EULA license should be bought and used in the same country...

is there any exception ?

Thanks

JP

Hi all,

I need to make more free space on bootbank.

Current size is

[root@ESXi1:~] du -d 1 /bootbank/ -m

156 /bootbank/

But I wish to delete unused modules.

I can list modules with

[root@ESXi1:~] esxcfg-module -l

Name                     Used Size (kb)

vmkernel                 147  10572 

chardevs                 142  48    

user                     1    3064  

crypto                   93   116   

vsanapi                  12   92    

vsanbase                 10   112   

vprobe                   0    392   

vmkapi_mgmt              6    28    

iodm                     3    24    

dma_mapper_iommu         0    16

procfs                   2    16    

vmkapi_v2_3_0_0_mgmt_shim0    8     

vmkapi_v2_2_0_0_mgmt_shim0    8     

vmkapi_v2_2_0_0_vmkernel_shim0    84    

vmkapi_v2_3_0_0_vmkernel_shim10   96    

vmkapi_v2_1_0_0_vmkernel_shim0    68    

vmkusb                   9    788   

vmkata                   3    416   

iscsi_trans              6    60    

iscsi_trans_compat_shim  3    12    

vmkapi_v2_3_0_0_vmklinux_shim3    12    

vmkplexer                1    24    

vmklinux_9               9    680   

qlnativefc               8    1816  

vmkapi_v2_2_0_0_iscsiInc_shim0    20    

vmkapi_v2_3_0_0_iscsiInc_shim1    20    

etherswitch              14   384   

netsched_fifo            2    12    

netsched_hclk            2    80    

netioc                   2    32    

vmklinux_9_2_3_0         7    48    

cnic_register            2    12    

bnx2                     1    216   

vmkapi_v2_3_0_0_iscsi_shim3    8     

cnic                     1    96    

dm                       6    16    

nmp                      42   212   

vmw_satp_local           23   16    

vmw_satp_default_aa      0    12    

vmw_psp_lib              6    12    

vmw_psp_fixed            22   16    

vmw_psp_rr               3    16    

vmw_psp_mru              0    12    

vmci                     10   200   

healthchk                3    176   

teamcheck                1    168   

vlanmtucheck             1    180   

heartbeat                0    168   

shaper                   2    180   

lldp                     0    28    

cdp                      8    196   

ipfix                    3    208   

tcpip4                   1    1492  

dvsdev                   6    16    

dvfilter                 13   156   

lacp                     4    60    

vmkapi_v2_1_0_0_dvfilter_shim0    8     

vmkapi_v2_2_0_0_dvfilter_shim0    8     

vmkapi_v2_3_0_0_dvfilter_shim0    8     

iscsi_linux_92           1    20    

bnx2i                    0    112   

megaraid_sas             1    100   

esxfw                    4    184   

dvfilter-generic-fastpath0    208   

vmkibft                  0    32    

vmw_satp_alua            1    32    

vmw_satp_lib_cx          2    16    

vmw_satp_alua_cx         3    20    

vaai_filter              3    28    

vmw_vaaip_emc            1    8     

vmw_vaaip_cx             3    12    

gss                      1    168   

lvmdriver                3    164   

deltadisk                0    256   

vdfm                     13   24    

sunrpc                   5    136   

vmfs3                    3    1388  

vfat                     3    56    

ufs                      0    84    

vmklink_mpi              2    36    

swapobj                  1    56    

nfsclient                0    140   

nfs41client              0    472   

vflash                   1    64    

dell                     1    44    

vmkapei                  0    40    

procMisc                 0    8     

nrdma                    3    360   

nrdma_vmkapi_shim        2    12    

vmkapi_v2_3_0_0_rdma_shim0    12    

ipmi                     2    92    

vmkapi_v2_1_0_0_nmp_shim 0    8     

vmkapi_v2_3_0_0_nmp_shim 0    8     

vmkapi_v2_2_0_0_nmp_shim 0    8     

vrdma                    8    116   

vmkapi_v2_2_0_0_iscsi_shim0    8     

vmkapi_v2_1_0_0_iscsi_shim0    8     

balloonVMCI              2    8     

hbr_filter               2    204   

ftcpt                    0    316   

filtmod                  10   88    

svmmirror                1    56    

cbt                      2    16    

migrate                  2    508   

vfc                      0    164   

tracing                  10   64    

rdt                      8    260   

vsanutil                 7    292   

lsomcommon               3    360   

plog                     2    824   

virsto                   1    776   

lsom                     1    1184  

dvfg-igmp                0    32    

cmmds_net                1    96    

cmmds                    2    680   

cmmds_resolver           1    76    

vsan                     0    2028  

nsx-dvfilter-switch-security3    132   

nsx-traceflow            3    32    

nsx-bfd                  1    28    

nsx-core                 3    12    

nsx-vdl2                 6    460   

nsx-vdrb                 1    356   

nsx-vsip                 28   932   

nsx-operations           0    16    

nsx-dvfilterUser         9    24    

iscsi_vmk                2    228   

esx_splitter             5    1168  

qflge                    Not Loaded

ixgben                   Not Loaded

qfle3                    Not Loaded

Also I can list VIBs

[root@ESXi1:~] esxcli software vib list

Name                           Version                               Vendor            Acceptance Level  Install Date

-----------------------------  ------------------------------------  ----------------  ----------------  ------------

RP-Splitter                    RPESX-00.5.2.0.3.0.a.412.000          EMC_Recoverpoint  PartnerSupported  2018-12-21 

emcjiraf                       5203.a.412-1OEM.600.1.17.3657938      EMC               PartnerSupported  2018-12-21 

ata-libata-92                  3.00.9.2-16vmw.650.0.0.4564106        VMW               VMwareCertified   2018-07-30 

ata-pata-amd                   0.3.10-3vmw.650.0.0.4564106           VMW               VMwareCertified   2018-07-30 

ata-pata-atiixp                0.4.6-4vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ata-pata-cmd64x                0.2.5-3vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ata-pata-hpt3x2n               0.3.4-3vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ata-pata-pdc2027x              1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

ata-pata-serverworks           0.4.3-3vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ata-pata-sil680                0.4.8-3vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ata-pata-via                   0.3.3-2vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

block-cciss                    3.6.14-10vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

char-random                    1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

ehci-ehci-hcd                  1.0-4vmw.650.0.14.5146846             VMW               VMwareCertified   2018-07-30 

elxnet                         11.1.91.0-1vmw.650.0.0.4564106        VMW               VMwareCertified   2018-07-30 

hid-hid                        1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

i40en                          1.3.1-5vmw.650.1.26.5969303           VMW               VMwareCertified   2018-07-30 

igbn                           0.1.0.0-14vmw.650.1.26.5969303        VMW               VMwareCertified   2018-07-30 

ima-qla4xxx                    2.02.18-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

ipmi-ipmi-devintf              39.1-4vmw.650.0.0.4564106             VMW               VMwareCertified   2018-07-30 

ipmi-ipmi-msghandler           39.1-4vmw.650.0.0.4564106             VMW               VMwareCertified   2018-07-30 

ipmi-ipmi-si-drv               39.1-4vmw.650.0.0.4564106             VMW               VMwareCertified   2018-07-30 

ixgben                         1.4.1-2vmw.650.1.26.5969303           VMW               VMwareCertified   2018-07-30 

lpfc                           11.1.0.6-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

lsi-mr3                        6.910.18.00-1vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

lsi-msgpt2                     20.00.01.00-3vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

lsi-msgpt3                     12.00.02.00-11vmw.650.0.0.4564106     VMW               VMwareCertified   2018-07-30 

misc-cnic-register             1.78.75.v60.7-1vmw.650.0.0.4564106    VMW               VMwareCertified   2018-07-30 

misc-drivers                   6.5.0-1.36.7388607                    VMW               VMwareCertified   2018-07-31 

mtip32xx-native                3.9.5-1vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

ne1000                         0.8.0-16vmw.650.1.26.5969303          VMW               VMwareCertified   2018-07-30 

nenic                          1.0.0.2-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-bnx2                       2.2.4f.v60.10-2vmw.650.0.0.4564106    VMW               VMwareCertified   2018-07-30 

net-bnx2x                      1.78.80.v60.12-1vmw.650.0.0.4564106   VMW               VMwareCertified   2018-07-30 

net-cdc-ether                  1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

net-cnic                       1.78.76.v60.13-2vmw.650.0.0.4564106   VMW               VMwareCertified   2018-07-30 

net-e1000                      8.0.3.1-5vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-e1000e                     3.2.2.1-2vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-enic                       2.1.2.38-2vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

net-fcoe                       1.0.29.9.3-7vmw.650.0.0.4564106       VMW               VMwareCertified   2018-07-30 

net-forcedeth                  0.61-2vmw.650.0.0.4564106             VMW               VMwareCertified   2018-07-30 

net-igb                        5.0.5.1.1-5vmw.650.0.0.4564106        VMW               VMwareCertified   2018-07-30 

net-ixgbe                      3.7.13.7.14iov-20vmw.650.0.0.4564106  VMW               VMwareCertified   2018-07-30 

net-libfcoe-92                 1.0.24.9.4-8vmw.650.0.0.4564106       VMW               VMwareCertified   2018-07-30 

net-mlx4-core                  1.9.7.0-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-mlx4-en                    1.9.7.0-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-nx-nic                     5.0.621-5vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

net-tg3                        3.131d.v60.4-2vmw.650.0.0.4564106     VMW               VMwareCertified   2018-07-30 

net-usbnet                     1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

net-vmxnet3                    1.1.3.0-3vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

nhpsa                          2.0.6-3vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

nmlx4-core                     3.16.0.0-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

nmlx4-en                       3.16.0.0-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

nmlx4-rdma                     3.16.0.0-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

nmlx5-core                     4.16.0.0-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

ntg3                           4.1.2.0-1vmw.650.1.26.5969303         VMW               VMwareCertified   2018-07-30 

nvme                           1.2.0.32-4vmw.650.1.26.5969303        VMW               VMwareCertified   2018-07-30 

nvmxnet3                       2.0.0.22-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

ohci-usb-ohci                  1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

pvscsi                         0.1-1vmw.650.1.26.5969303             VMW               VMwareCertified   2018-07-30 

qedentv                        2.0.3.29-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

qfle3                          1.0.2.7-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

qflge                          1.1.0.3-1vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

qlnativefc                     2.1.50.0-1vmw.650.1.26.5969303        VMW               VMwareCertified   2018-07-30 

sata-ahci                      3.0-26vmw.650.1.26.5969303            VMW               VMwareCertified   2018-07-30 

sata-ata-piix                  2.12-10vmw.650.0.0.4564106            VMW               VMwareCertified   2018-07-30 

sata-sata-nv                   3.5-4vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

sata-sata-promise              2.12-3vmw.650.0.0.4564106             VMW               VMwareCertified   2018-07-30 

sata-sata-sil24                1.1-1vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

sata-sata-sil                  2.3-4vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

sata-sata-svw                  2.3-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

scsi-aacraid                   1.1.5.1-9vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

scsi-adp94xx                   1.0.8.12-6vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

scsi-aic79xx                   3.1-5vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

scsi-bnx2fc                    1.78.78.v60.8-1vmw.650.0.0.4564106    VMW               VMwareCertified   2018-07-30 

scsi-bnx2i                     2.78.76.v60.8-1vmw.650.0.0.4564106    VMW               VMwareCertified   2018-07-30 

scsi-fnic                      1.5.0.45-3vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

scsi-hpsa                      6.0.0.84-1vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

scsi-ips                       7.12.05-4vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

scsi-iscsi-linux-92            1.0.0.2-3vmw.650.0.0.4564106          VMW               VMwareCertified   2018-07-30 

scsi-libfc-92                  1.0.40.9.3-5vmw.650.0.0.4564106       VMW               VMwareCertified   2018-07-30 

scsi-megaraid-mbox             2.20.5.1-6vmw.650.0.0.4564106         VMW               VMwareCertified   2018-07-30 

scsi-megaraid-sas              6.603.55.00-2vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

scsi-megaraid2                 2.00.4-9vmw.650.0.0.4564106           VMW               VMwareCertified   2018-07-30 

scsi-mpt2sas                   19.00.00.00-1vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

scsi-mptsas                    4.23.01.00-10vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

scsi-mptspi                    4.23.01.00-10vmw.650.0.0.4564106      VMW               VMwareCertified   2018-07-30 

scsi-qla4xxx                   5.01.03.2-7vmw.650.0.0.4564106        VMW               VMwareCertified   2018-07-30 

shim-iscsi-linux-9-2-1-0       6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-iscsi-linux-9-2-2-0       6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libata-9-2-1-0            6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libata-9-2-2-0            6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libfc-9-2-1-0             6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libfc-9-2-2-0             6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libfcoe-9-2-1-0           6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-libfcoe-9-2-2-0           6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-vmklinux-9-2-1-0          6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-vmklinux-9-2-2-0          6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

shim-vmklinux-9-2-3-0          6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

uhci-usb-uhci                  1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

usb-storage-usb-storage        1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

usbcore-usb                    1.0-3vmw.650.1.26.5969303             VMW               VMwareCertified   2018-07-30 

vmkata                         0.1-1vmw.650.1.26.5969303             VMW               VMwareCertified   2018-07-30 

vmkplexer-vmkplexer            6.5.0-0.0.4564106                     VMW               VMwareCertified   2018-07-30 

vmkusb                         0.1-1vmw.650.1.26.5969303             VMW               VMwareCertified   2018-07-30 

vmw-ahci                       1.0.0-39vmw.650.1.26.5969303          VMW               VMwareCertified   2018-07-30 

xhci-xhci                      1.0-3vmw.650.0.0.4564106              VMW               VMwareCertified   2018-07-30 

cpu-microcode                  6.5.0-0.0.4564106                     VMware            VMwareCertified   2018-07-30 

emulex-esx-elxnetcli           11.1.28.0-0.0.4564106                 VMware            VMwareCertified   2018-07-30 

esx-base                       6.5.0-1.36.7388607                    VMware            VMwareCertified   2018-07-31 

esx-dvfilter-generic-fastpath  6.5.0-0.0.4564106                     VMware            VMwareCertified   2018-07-30 

esx-nsxv                       6.5.0-0.0.8590012                     VMware            VMwareCertified   2018-08-09 

esx-tboot                      6.5.0-1.36.7388607                    VMware            VMwareCertified   2018-07-31 

esx-ui                         1.21.0-5724747                        VMware            VMwareCertified   2018-07-30 

esx-xserver                    6.5.0-0.23.5969300                    VMware            VMwareCertified   2018-07-30 

lsu-hp-hpsa-plugin             2.0.0-5vmw.650.1.26.5969303           VMware            VMwareCertified   2018-07-30 

lsu-lsi-lsi-mr3-plugin         1.0.0-10vmw.650.1.26.5969303          VMware            VMwareCertified   2018-07-30 

lsu-lsi-lsi-msgpt3-plugin      1.0.0-7vmw.650.1.26.5969303           VMware            VMwareCertified   2018-07-30 

lsu-lsi-megaraid-sas-plugin    1.0.0-8vmw.650.1.26.5969303           VMware            VMwareCertified   2018-07-30 

lsu-lsi-mpt2sas-plugin         2.0.0-6vmw.650.1.26.5969303           VMware            VMwareCertified   2018-07-30 

native-misc-drivers            6.5.0-0.0.4564106                     VMware            VMwareCertified   2018-07-30 

rste                           2.0.2.0088-4vmw.650.0.0.4564106       VMware            VMwareCertified   2018-07-30 

vmware-esx-esxcli-nvme-plugin  1.2.0.10-1.26.5969303                 VMware            VMwareCertified   2018-07-30 

vmware-fdm                     6.7.0-9232925                         VMware            VMwareCertified   2018-07-31 

vsan                           6.5.0-1.36.7388608                    VMware            VMwareCertified   2018-07-31 

vsanhealth                     6.5.0-1.36.7388609                    VMware            VMwareCertified   2018-07-31 

tools-light                    6.5.0-0.23.5969300                    VMware            VMwareCertified   2018-07-30

Question 1

- Is command

esxcfg-module -l

thesame like command

lsmod

in linux? If answer is yes, "zero" in column "used" mean that I can delete that module, esxi host do not use them?

Question 2

How to make relationship between modules and VIB aka

module XXX belong YYY VIB?

TNX

A co-worker of mine is running Workstation 11, and needs to set up a VM with Windows Server 2016. When he ran through the normal process of creating the VM and installing the OS, the installer failed out with an error. The VM would then reboot, encounter the same error, reboot, ad infinitum. (I know I should have the details on the error to help diagnose, but at the moment I don't. But please continue reading, there's more...)

From there we've done the following troubleshooting and attempted workarounds, but to no avail:

1. I checked the MSDN ISO we're using and confirmed it's intact and complete (SHA1 matches).
2. I used the ISO to install Win2016 to a new VM on my Worktation instance, no problem. The install completed and the VM boots up fine. I have Workstation 14.x, while he has (as noted) version 11.x.
3. I created a second new VM, using the compatibility option for Workstation 11.x. I then installed Win2016 to this VM; no problem. The install completed and the VM boots up fine.
4. My coworker full-cloned a new VM from a snapshot I created on the VM from Step 3. He tried booting up the VM on his (11.x) Workstation instance, but the VM bluescreened while booting.
5. He then tried just copying the entire Step-3 VM folder to his local machine and booting it up on 11.x. Same problem; the VM bluescreens.

Nothing like this has ever happened before in our usage of Workstation. We've had no difficulty cloning & copying VMs which used other (earlier) versions of the Windows OS.

The obvious diagnosis is that there's some basic incompatibility such that Win2016 won't install or boot properly on Workstation 11.x, and we're pursuing an upgrade for him to work that angle.

But in the meantime, has anyone else experienced these issues with a Win2016 VM -- and if so found a workaround to get the VM to work?

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.

Hi,

I have just started to use ESXi and are having some problems with my VM.

Im going to create an AP on a Debian machine (like this for RPi). But Im not getting it to work with my wifi-dongle TP-Link WN722N.

Is this even possible? I have been trying with few different alternatives but without success.

My wifi-adapter is there when i run "lsusb" on host.

Bus 001 Device 003: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n

For my VM I have given access to the USB-device. In the VM the interface is called "wlx6470022dc209" (why not wlan0?).

Installed the firmware with: apt-get install firmware-atheros

Using ESXi 6.7

What information do you need to help me solve this?

Thanks in advance!

I have a brand new HPE ProLiant DL380 Gen10 server.  I am getting an error when trying to install ESXi (have tried both 6.5 and 6.7) on this bare metal new server.  The first method I tried was mounting the ISO via HPE's intelligent provisioning through the iLO, second method I tried was making a bootable USB with the ISO.  Both failed on the initial install, before it even gets to the pop up welcome screen, during the grey and yellow boot screen, runs through the services, then stops on "Reading Installation scripts" I get this error and the server reboots:

"Error (see log for more info):

An error has occurred while parsing the installation script

error:file:///ks.cfg:line 3: bootproto --device= specified, but "undefined" was not found on the system."

Any help or insight would be extremely helpful.  Server specs and error screenshot attached.