I mounted vmdk file and now I can see this mounted hard in my linux OS

but when I want to see hard details with ls command, I get this error message

root@redhost:/data# lsblk -f | grep sd

sda                                                                                     

├─sda1 ext4                          22400b10-###-42ce-9c78-###  253.2G     3% /

├─sda2                                                                                  

└─sda5 swap                          c2370f02-###-485b-98b3-###                [SWAP]

sdb                                                                                     

└─sdb1 ufs                           5ca9951671###                       79.3G    52% /data

~:/data# df -h | grep sd

/dev/sda1       276G  8.7G  254G   4% /

/dev/sdb1       197G  102G   80G  57% /data    <<<<<<<<<<<<

~:/data# cd /data

~:/data# ls

ls: reading directory '.': Input/output error

How can I resolve this problem?

Hi

Always a topic for us.

How do you do the automated ESXI install on HPE servers?

Do you have any scripts or tools?

I do not speak of 1-2 servers. It is more in the 20-30 per year which are new

Many Thanks for hints

Hello,

When I want to upload a file to the datastore then it show me "failed to log into nfc server". My firewall configuration is:

How can I solve it?

Thanks.

Hi, I am using ESXi 6.7U3 and I have a NVIDIA V100 installed in my host.

I already installed the NVIDIA .VIB file with the driver in the ESXi host and it recognizes the graphic card (nvidia-smi successful).

The problem I have is that in my web client there should be a section "Graphics" inside the "Hardware" tab that would allow me to configure the GPU in "Shared Direct" mode, but there is nothing instead

But... when I check the capabilities that the Evaluation version of ESXi provide during the evaluation period, vGPU is among them:

Any ideas about how to solve this?

Thanks in advance!

Got this message after adding a new hosts.  Looks at all the Advances System Settings and they are all the same as the rest of the hosts in the cluster.  All host say ([] /scratch/log  for Syslog.global.logDir.  And the ScratchConfig.CurrentScratchLocation is set to /tmp/scratch.  So not sure why the error.  Anyone have a clue why I am still getting this Warning?  Any help is appreciated.  Thanks

Perry

Hello, I have an IBM ULT3580 LTO4 library that I have presented via FC to the 2 hosts that make up a cluster in production, at the OS level it shows them, but from the vcenter console I cannot add them to the VM, they can help me withThis inconvenience, or is something else that I need to configure.

Regards

GTOMALA

Hi All,

We are running 2 node ESXi 6.5. each node has 4 NICs. Two connected to Vswitch0 and other two connected to Vswitch1

Vswitch0 ->> Nic1, Nic2; Vswitch1 --> Nic3,Nic4

Nic1, Nic2 -> VLAN 102; Nic3,Nic4 -> VLAN 113

VMK0 connected to Vswitch0 and VMK1 connected to Vswitch1

VMK0 used for Management & Vmotion traffic and Physical adapter associated with it are trunked.

VMK1 used for vSAN traffic and Physical adapter associated with Access Port.

Both the VMK0 and VMk1 are in same subnet 192.168.2.x. We are trying to change the VMK1 IP to different subnet 192.0.2.x

Current IP Address [VMK0 - 192.168.2.11, VMK1-192.168.2.14]

Our NW person changing the VLAN of Physical adapter Nic3 & Nic4 in switch to match subnet of 192.0.2.x

Once I change the IP address in VMK1, i'm unable to take Putty / web console of my management Interface.

We are clueless how both are interlinked. can anyone help please

Is recommended to update ESXi on servers whitch don't have any issue ?

I have only one server (production server) HP ProLiant DL380 Gen9 and vSphere ESXi Essentials Kit 6.

It was installed in march 2008 - Custom Image ISO HPE so this is ESXi 6.5 U1 (6.5.0 build 7388607).

Is any recommended and sugested to upgrade to latest version ? In my case for today is ESXi 6.7.0 U3 ??

Is this good idea to take risk and update ESXi ?? Maybe better way is do nothing because everythink work fine without any issue.

Hi,

I have installed Windows Server 2016 on the latest version of ESXI 6.5.0b but it's almost unusable.

The VM has 2 CPU and 2GB of RAM with VMware Tools 10.1.5 (5055683) and is used for Active Directory for my lab but it's really slow.

For example for open DNS I take almost 10 secs.

On ESXI I get High VM Memory Usage alarm but if I check on task manager on the guest vm ram usage is always around 40% and CPU is around 3 4% max and even if I put 4 gb the problem is still there.

Is this a know problem or there's something that I can do to slove this problem beside downgrade to Windows Server 2012 R2?

My Host ESXI specs are:

Asus X99WS-IPMI

I7-6800K

128GB RAM DDR4

1x SSD 250GB + 4xSSD 500GB on LSI 9260-4i on RAID 0

ESXI Booted from USB Stick

Thanks

Marko

Hello.

For upgrade ESXi 6.5 to 6.7 I must put the host in the maintenance mode, in this mode, my VMS disconnected? Any method to upgrade ESXi without shutdown the VMs?

Thank you.

hi.The virtual machine version is not compatible with the version of the host  this error dont let me to migrate vm from one host to other.my vcenter license is 1 instances

This is a Dell PowerEdge M630, using ESXi downloads provided by dell for this server and the hardware is compatible with ESXi 6.7

I upgraded from ESXi 5.5 to 6.0 with no issues.   6.0 to 6.5 threw this:

which appears to be regarding the LSI SCSI driver.

While SSH'd into the host:

[root@HOST:~] esxcli software vib list | grep LSI

scsi-megaraid-perc9            6.901.57.00-1OEM.550.0.0.1331820       LSI       VMwareCertified   2019-10-14

scsi-mpt3sas                   04.00.00.00.1vmw-1OEM.500.0.0.472560   LSI       VMwareCertified   2019-10-14

Here is an attempt to see what drivers are in use:

[root@HOST:~] esxcfg-scsidevs -a

vmhba38 ahci              link-n/a  sata.vmhba38                            (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

vmhba39 ahci              link-n/a  sata.vmhba39                            (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

vmhba0  lsi_mr3           link-n/a  sas.544a842031c5c000                    (0000:02:00.0) LSI / Symbios Logic PERC H730 Mini (blade)

vmhba1  ahci              link-n/a  sata.vmhba1                             (0000:00:11.4) Intel Corporation Wellsburg AHCI Controller

vmhba2  ahci              link-n/a  sata.vmhba2                             (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

vmhba40 ahci              link-n/a  sata.vmhba40                            (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

vmhba41 ahci              link-n/a  sata.vmhba41                            (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

vmhba42 iscsi_vmk         online    iqn.1998-01.com.vmware:vm-08-187a21de   iSCSI Software Adapter

vmhba32 usb-storage       link-n/a  usb.vmhba32                             () USB

vmhba34 ahci              link-n/a  sata.vmhba34                            (0000:00:11.4) Intel Corporation Wellsburg AHCI Controller

vmhba35 ahci              link-n/a  sata.vmhba35                            (0000:00:11.4) Intel Corporation Wellsburg AHCI Controller

vmhba36 ahci              link-n/a  sata.vmhba36                            (0000:00:11.4) Intel Corporation Wellsburg AHCI Controller

vmhba37 ahci              link-n/a  sata.vmhba37                            (0000:00:1f.2) Intel Corporation Wellsburg AHCI Controller

I am not seeing any mpt3sas or scsi-mpt3sas referenced.   Does this mean it would be safe for me to run a:

[root@HOST:~]  esxcli software vib remove -f --vibname scsi-mpt3sas

Without killing my RAID array?

I'd like to think so, but I am not expert on this and don't fully know how to interpret the results of "esxcfg-scsidevs -a" to 100% know for sure if the driver/VIB is used or not.

Thanks.

If I run the command  esxcli network vswitch standard portgroup policy failover get -p "[portgroup name]"  I get exactly what I expect: 

Load Balancing: srcport

   Network Failure Detection: link

   Notify Switches: true

   Failback: true

   Active Adapters: vmnic0, vmnic1

   Standby Adapters:

   Unused Adapters:

   Override Vswitch Load Balancing: false

   Override Vswitch Network Failure Detection: false

   Override Vswitch Notify Switches: false

   Override Vswitch Failback: false

   Override Vswitch Uplinks: false

When I look for that data in a vm-support generated from that host (or any host), I cannot find it.     Is that data not collected?

Hello,

we have some Cisco servers equipped with Intel X520-DA2 card.

As you can see below the very same server running ESXi 6.5 see the 2x 10GB links active (Up) but as soon as the ESXi get updated to 6.7 the ports get marked as Down.

Interestingly the activity leds still blink and the switch side still see the connection UP/UP.

From google search I found that only selected SFP seems to be officially supported yet we had connectivity UP when running 6.5.

Does anyone faced any similiar issue already (and possibly find a workaround to it?) ?

Thx,

A.

Server model: UCSC-C220-M3L

NIC card: Intel X520-DA2 10 Gbps 2 port NIC

NIC card cable: Cisco SFP-H10GB-CU3M

--- 6.5 ---

[root@esxi165:~] vmware -v

VMware ESXi 6.5.0 build-8294253

[root@esxi165:~]

[root@esxi165:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address         MTU  Description

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

vmnic0  0000:01:00.0  igbn    Up            Up            1000  Full    88:5a:92:88:35:8e  1500  Intel Corporation I350 Gigabit Network Connection

vmnic1  0000:01:00.1  igbn    Up            Up            1000  Full    88:5a:92:88:35:8f  1500  Intel Corporation I350 Gigabit Network Connection

vmnic2  0000:82:00.0  ixgbe   Up            Up           10000  Full    90:e2:ba:6d:48:7c  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

vmnic3  0000:82:00.1  ixgbe   Up            Up           10000  Full    90:e2:ba:6d:48:7d  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

[root@esxi165:~]

[root@esxi165:~] esxcli software vib list | grep ixgbe

ixgben                         1.4.1-12vmw.650.2.50.8294253          VMW     VMwareCertified   2019-10-15

net-ixgbe                      3.7.13.7.14iov-20vmw.650.0.0.4564106  VMW     VMwareCertified   2019-10-15

[root@esxi165:~]

--- 6.7 (1) ---

[root@esxi165:~] vmware -v

VMware ESXi 6.7.0 build-13004448

[root@esxi165:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address         MTU  Description

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

vmnic0  0000:01:00.0  igbn    Up            Up            1000  Full    88:5a:92:88:35:8e  9000  Intel Corporation I350 Gigabit Network Connection

vmnic1  0000:01:00.1  igbn    Up            Up            1000  Full    88:5a:92:88:35:8f  1500  Intel Corporation I350 Gigabit Network Connection

vmnic2  0000:82:00.0  ixgben  Down          Down             0  Half    90:e2:ba:6d:48:7c  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

vmnic3  0000:82:00.1  ixgben  Down          Down             0  Half    90:e2:ba:6d:48:7d  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

[root@esxi165:~]

[root@esxi165:~] esxcli software vib list | grep ixgbe

ixgben                         1.4.1-16vmw.670.1.28.10302608         VMW     VMwareCertified   2019-10-15

net-ixgbe                      3.7.13.7.14iov-20vmw.670.0.0.8169922  VMW     VMwareCertified   2019-10-15

[root@esxi165:~]

--- 6.7 (2) ---

[root@esxi165:~] vmware -v

VMware ESXi 6.7.0 build-14320388

[root@esxi165:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address         MTU  Description

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

vmnic0  0000:01:00.0  igbn    Up            Up            1000  Full    88:5a:92:88:35:8e  9000  Intel Corporation I350 Gigabit Network Connection

vmnic1  0000:01:00.1  igbn    Up            Up            1000  Full    88:5a:92:88:35:8f  1500  Intel Corporation I350 Gigabit Network Connection

vmnic2  0000:82:00.0  ixgben  Down          Down             0  Half    90:e2:ba:6d:48:7c  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

vmnic3  0000:82:00.1  ixgben  Down          Down             0  Half    90:e2:ba:6d:48:7d  1500  Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection

[root@esxi165:~]

[root@esxi165:~] esxcli software vib list | grep ixgbe

ixgben                         1.7.1.16-1vmw.670.3.73.14320388       VMW     VMwareCertified   2019-10-15

net-ixgbe                      3.7.13.7.14iov-20vmw.670.0.0.8169922  VMW     VMwareCertified   2019-10-15

[root@esxi165:~]

Hi,

While troubleshooting snapshot consolidation issues (VM powered off, unable to start, consolidation fails due to a file lock) I discovered that MAC address of the vmnic that owns the lock belongs to the adapted that is disconnected (not assigned to any vswitches, port groups, etc.) How can I remove this lock?

The host runs esxi 6.0 and is connected to the vCenter 6.0

Thanks

Slow iscsi performance on ESXi 6.7.0.

setup 1:-

1) Created a new LUN from ISCSI storage(500 GB) and presented to ESXi hosts.Created a new ISCSI data store and provided 200 GB storage to Windows 2016 OS.

When we are testing the file copy between C to D,we are seeing the transfer rate is below 10 mbps/sec.It starts at 200mbps/sec and going down to below 10 mbps/sec.

setup 2:-

2) When we are passing the direct ISCSI LUN(as a RDM) to Win 2012 OS,we see the transfer rate is more than 1 gbps/sec.

I dont know where is the problem. I like to test the below option to see the performance.

1) First,we need to change the RAID controller in to write cache(enabled) i.e BBRC. If possible,we can insert HBA card to test this.---->Not tested yet.

2) Can be tested by enabling Jumbo frames from Network to Standalone ESXi server/storage server.---->Not tested yet.

3) Can create a new subnet for ISCSI(dedicated) and then can be checked with dedicated NICS.---->Not tested yet.

4) Can change one VM to vmxnet3 and another machine to E1000 and then can be tested.---->Tested but no luck

5) Can change one VMDK to lazy zeroed/eager zeroed and then can be tested---->Tested but no luck

6) Create a new SCSI controller with "Para Virtualization" and then test the performance---->Tested but no luck

Note:- Right now I have 2*10 G NICS for VSAN network.ISCSI also using through the same VSAN network.

Any other suggestions?

Thanks,

Manivel RR

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.

Hello -

New installation of 6.7.0 build 14320388 and have the following in %firstboot section:

vim-cmd hostsvc/enable_ssh 2>&1 >> /tmp/log

vim-cmd hostsvc/start_ssh 2>&1 >> /tmp/log

vim-cmd hostsvc/enable_esx_shell 2>&1 >> /log

vim-cmd hostsvc/start_esx_shell 2>&1 >> log

This has worked previously with no issues.  With this latest build, neither SSH nor the ESX shell are getting enabled.  The firstboot is running as I get the log file and other commands in the section are running, however this just isn't.  There's no errors spit out anywhere either.

Note also that a esxcli network interface ipv4 get command returns an error of "Connection failed".

I tried adding /etc/init.d/vpxa status and hostd status to the log, and they both show as running.

Any thoughts???  Thanks in advance.

I have been having ESXI crash when users have been connected over rdp for a period of time.

The console remains active and is fine but the web interface goes down. A restart through the console brings the system back up ok.

I am a total novice to ESXI but does it look like a drive problem?

ESXI system log [https://paste.bband.net/0fe2a9b7bd53](https://paste.bband.net/0fe2a9b7bd53) latest crash happened at around 9pm.

What do you think is causing it to go down? and what do you think could be done to rectify it?

On installation of new server the server created a new data store - this contains 2 folders  -

Can we request a remote viewer to try understand why this happened can we also delete this local data store  - see below, d

Don’t know how the installer came to add this or appeared from -  either this picked up something from raid as I didn’t partition anything on the build?

It contains 2 folders -

.ssd.sf

Vmkdump

Can we delete this data store - request a remote session.