I am migrating a Windows 2012 Server guest from an ESXi 6.0 host to a ESXi 6.6 host.  When the Windows guest comes up the 1TB drive has moved from E: to D: (messing up drive shares) and Window's storage manager does not allow me to reassign it back to E:.   Probably windows thinks something is still on E, just disconnected.

Windows guest has 3 drives

     80GB

     10GB Swap

     1TB (E: drive, "REPO01_1.vmdk")

1) shutdown Windows Server 2012 guest on ESXi 6.0

2) delete 1TB disk from VM config

3) migrate VM to ESXi 6.6 host using VMware vCenter Converter Standalone

4) SFTP the 1TB VMDK file to ESXi 6.6 host

5) add 1TB drive to VM on ESXi 6.6 host using VMDK file

6) start Windows guest on ESXi 6.6 host

I use SFTP because it's 20x faster than VMware's converter.  Moving 1TB+ drive would take days with it.

Looks like I'm on SCSI 0:1 so I'd expect the drive to be migrated as expected.

Source VM:

[root@ESX02:/vmfs/volumes/5ab95e62-7d552784-050c-98f2b328fd94/REPO01] grep -i scsi REPO01.vmx

scsi0.virtualDev = "lsisas1068"

scsi0.present = "TRUE"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:0.fileName = "REPO01.vmdk"

scsi0:0.present = "TRUE"

sched.scsi0:0.throughputCap = "off"

sched.scsi0:0.shares = "high"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "REPO01_1.vmdk"  <-- 1TB disk

sched.scsi0:1.shares = "high"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

scsi0.pciSlotNumber = "160"

scsi0.sasWWID = "50 05 05 6e 40 53 60 f0"

scsi0:1.redo = ""

scsi0:0.redo = ""

Destination VM:

[root@ESX04:/vmfs/volumes/5dcc5389-e14224e2-7655-002590be2724/REPO01] grep scsi REPO01.vmx

scsi0.virtualDev = "lsisas1068"

scsi0.present = "TRUE"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:0.fileName = "REPO01.vmdk"

sched.scsi0:0.shares = "high"

sched.scsi0:0.throughputCap = "off"

scsi0:0.present = "TRUE"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "/vmfs/volumes/5dd30100-83438218-99b6-002590be2724/REPO01/REPO01_1.vmdk"  <-- 1TB disk

sched.scsi0:1.shares = "normal"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

scsi0.pciSlotNumber = "160"

scsi0:1.redo = ""

scsi0:0.redo = ""

scsi0.sasWWID = "50 05 05 6f 79 08 3b a0"

What can I do to fix this besides letting the VMware Converter handle all 3 drives meaning it works its magic on the 1TB partition for 48 hours?

Thanks

Hi All -

I've been recently working on a number of PXE booted installs of ESX.  I have a kickstart file that has a %post section that performs a few actions, then sends a simple GET request to a web server using wget.  The %post stuff works great in 5.5 Update 3, 6.0 Update 2, and 6.0 Update 3.  When I try it with 6.5.0a (4887370) everything works great EXCEPT the wget call.  Wget times out (can't connect to remote host (x.x.x.x): Connection timed out.

• The remote host is the exact same host that ESXi booted and installed off of without issue (via HTTP).
• The interface (vmnic0/vmk0) is up and has a valid IP address.
• The HTTP host responds normally to pings.
• The HTTP host responds normally to requests from other systems on the same network.

The HTTP server is on port 8080, is there something funky w/ 6.5 that "blocks" outgoing traffic on port 8080?  I'm stumped!!

Thanks in advance for any input!

How do i automate the process of downloading latest ESXi image from the data source. is there any documentation provided. Please help me in this.

I have multiple IP addresses on my host so I have two different firewalls running virtually to play with and as a backup, i'd like the other firewall/subnet to also be able to access the ESXI interface directly and not through a tunnel back to the primary firewall.

I created a new TCP/IP stack, added a vmkernel with a different VLAN and got that VLAN's ip address through the second firewall. I assigned management to this vmkernel but I am still unable to access its web interface. I can ping the ESXi interface on this secondary subnet of course.

Needless to say I have already played with the firewall but its default set to accept for any ip address and i've even disabled it for giggles but no go.

What am I missing?

Hello all-

just attempted to update my ESXi server from 5.1 799733 to 5.1U1 1065491.  During the upgrade the process hangs at 24% completion with the error message as above:

OSError: [Errno 39] Directory not empty: '/vmfs/volumes/3934f7e6-f070467f-afd0-f0ef312248d9/state.7173326'

I have retried a second time with the same result.  Is there any workaround?  Or can I perform a clean install and just import the VMs from the datastores without any problems?

I added my host to a domain. It joined successfully . I also added my domain account to the administrator role on the esxi host but I cannot login to the esxi host with my domain creds

any idea?

ESXi5.5  can  use.  This  is the  IPFC  driver on   ESXi5.5 .    自带的

~ # esxcli software vib list | grep -i lpfc

lpfc                           10.0.100.1-1vmw.550.0.0.1331820       VMware  VMwareCertified   2019-12-12

scsi-lpfc820                   8.2.3.1-129vmw.550.0.0.1331820        VMware  VMwareCertified   2019-12-12

How to  use the Lpe11000  on ESXi 6.7

So while in the midst of upgrading my ESXi 6.5u1 to 6.7u2, I ran into this on many of my hosts. "The system has insufficient locker space for the image profile." While I had to try different things on a case by case basis to get to ESXi 6.7u2. In the majority of the hosts I kept seeing the following in images below. In some cases I was able to delete everything in the /locker folder in some I'm not. I'm only able to remove enough stuff so that I can copy over the packages and var folders which should be the only things in here. Just wondering if anyone else has ran into this and can shed some light. I'm also getting this on some hosts when I try the following command to remove everything in folder (rm -rf *)

Hi *,

i can access the ESXi console with my root & pw, but not the WebAccess with "root" & pw. The pw is the same, there are no spell / keyboard language issues.

We have a single ESXi 6.5 (4887370), no vCenter. No Domain Account, just local.

Best regards

Max

As soon as I take a snapshot, or make a backup (with Synology Active Backup for Business), I get a pop-up "The redo log of xxx is corrupted".

This is 100% reproducible, and happens every time for every type of guest that I tried.

The VM is broken and can't be recovered after this pop-up.

I am using the free ESXi, version 6.7.0 Update 3 (Build 14320388).

Host is an Intel NUC8i5BEH with a Samsung SSD for storage. ESXi itself is installed on an USB stick.

How can this be debugged? Given that the Intel NUC is not a supported device, I can't ask VMWare for help.

I can't find much in the system log, but this is what is there:

2019-12-14T11:07:21.901Z cpu1:2101917)VSCSI: 6602: handle 8209(vscsi0:0):Destroying Device for world 2101909 (pendCom 0)

2019-12-14T11:07:21.901Z cpu1:2101917)NetPort: 1580: disabled port 0x2000009

2019-12-14T11:07:22.441Z cpu1:2101917)FDS: 617: Enabling IO coalescing on driver 'deltadisks' device '81031d-Windows-000001-sesparse.vmdk'

2019-12-14T11:07:22.441Z cpu1:2101917)VSCSI: 3810: handle 8215(vscsi0:0):Creating Virtual Device for world 2101909 (FSS handle 11207458) numBlocks=268435456 (bs=512)

2019-12-14T11:07:22.441Z cpu1:2101917)VSCSI: 273: handle 8215(vscsi0:0):Input values: res=0 limit=-2 bw=-1 Shares=1000

2019-12-14T11:07:22.442Z cpu1:2101917)NetPort: 1359: enabled port 0x2000009 with mac 00:0c:29:f7:63:a0

2019-12-14T11:07:28.847Z cpu6:2097184)ScsiDeviceIO: 3435: Cmd(0x459a40c53c00) 0x1a, CmdSN 0x19484 from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2019-12-14T11:07:48.715Z cpu1:2097584)INFO (ne1000): false RX hang detected on vmnic0

2019-12-14T11:10:14.688Z cpu7:2097699)DVFilter: 5963: Checking disconnected filters for timeouts

I'm kind of confused. People talk about "pass through", but this is not what I want. I would just need basic 3D support, rendered by the host.

As far as I can tell, I need to enable 3D in the video settings of the guest. When I do this, ESXi reports "No 3D support is available from the host".

The host uses a standard Intel processor with Iris plus 655 GPU. How can this not be supported?

Am I overlooking something here? ESXi is 6.7u3, Host is an Intel NUC8i5BEH.

Hi,

We've one ESXI 6.5 updae 1 version 650.U1.10.2.0 running with 5 VM's but none of the VM's detect the external HDD, I tried with WD & Seegate external drive also updated VM tool to the latest 10.3 but no effect.

Kindly advice what is the possibility to overcome this.

Thanks in advance

Hello,

my customer is running ESXi 6.5 on Soyoustart server with two independend disks. For VMs are available two datastores with VMFS5 filesystem.

Now I'm instaling OpenSuSE Thumbleweed linux in VM and I'd like to use Linux raid for data protection. So I have created two disks with same size, one disk is located in datastore1 with other vms files and second disk is located in datastore2 in folder, what I have created for this VM, disks size is 20 GB. Both disks are set as thin provisioned. Durring instalation I have created standard linux raid partitions on both disk and merge them into raid1 disk, where is system instalated. When I look into datastores I see, that vmdk file in datastore1 has size about 3 GB, but vmdk file in datastore2 has size 20 GB. Can enyone explain me, why second disk si provisioned with full allocated size?

Thank you
Radek Masin

I'm trying to get ESXi up and running on my NUC device.

It appears to boot but the process is fairly lengthy, like around 2 to 4 minutes.

Once I see the "running" screen, it shows me what IP address I can manage it from but it never actually installs on the hard drive of the NUC, it only runs on the USB stick I configured using Rufus from the .iso I downloaded.

I remember installing ESXi a number of months ago, but it was on different hardware.

Booting into BIOS shows an internal hard drive and the USB stick so I'm confused as to why it seems to be running as a "live" system.

Can someone point me to what is going on here?

Thanks in advance.

Hello folks, one of my hosts just locked up and the kernel panic screen isn't very informative so I'm not sure where to start troubleshooting this as the iDRAC logs are clean... Can anyone make sense of this? This is running off a Dell M630.

There is no easy way to do it, it seems.

So I wanted to say that I couldn't afford to do an upgrade on my server and my service provider wanted $30 for IPMI access. I have searched countless forums on how in the world to fix this problem. I set Passthrough on and all my datastores vanished and said I need to add a datastore. I couldn't remove Passthrough because since the file system is mounted in read only for some reason you can't ssh in to the server and edit esxi.conf to fix the problem. This is my first tutorial on how to do this, so don't bash my head that it's sloppy.

1. Boot with a debian or ubuntu live cd

List your drives / partitioned: Open a terminal window

2. type parted -l

Mine was sda5

3. mount /dev/sda5 /mnt

4. ls /mnt/

5. cp /mnt/state.tgz ~/

6. cd ~

7. tar xvf state.tgz

8. tar xvf local.tgz

So you get a etc folder now. Go to /etc/vmware

9. nano esxi.conf

10. Replace everything that says passthru with vmkernel

11. Save the file

Now lets copy the file back to the mount point, but first we have to recreate the archive.

12. tar czf local.tgz etc/

13. tar czf state.tgz local.tgz

14. cp state.tgz /mnt/

Done. Reboot and everything should work as it did originally.

This was tested in ESXi 6.0 and 5.5.

Hope this will help others that are trapped in a similar situation. Of course you can reinstall but a lot of people wanted to know how to do it. This which is basically 14 steps can probably be shortened. I hope that my first contribution on this forum is not overlooked.

Hi,

I just met an issue to use ESXi self contianed PyVim to connect itself. It works with IPv4, however when I connect it with IPv6. It will report timeout.

This behavior works in 6.7.

Could you please help check it?  If its sdk connects ipv6 on other hosts, this connection works.

Basic behavior:

1. enter esxi cli.     get IPv6 from "esxcfg-vmknic -l".

2. enter python to python shell.

inputs all to python all will be as below:

from pyVim import connect

from pyVmomi import vim

from pyVmomi import vmodl

from pyVim import connect

import ssl

ssl._create_default_https_context = ssl._create_unverified_context

DEFAULT_USER="root"

DEFAULT_PASSWORD="Pass1234"

host="fe80::250:56ff:fe63:xxxx%vmk0"

connection = connect.Connect(host=host, user=DEFAULT_USER, pwd=DEFAULT_PASSWORD)

in 7.0, the connect.Connect will report:

Traceback (most recent call last):

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVim/connect.py", line 339, in __Login

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVmomi/VmomiSupport.py", line 556, in <lambda>

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVmomi/SoapAdapter.py", line 1448, in InvokeMethod

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 1107, in request

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 1152, in _send_request

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 1103, in endheaders

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 934, in _send_output

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 877, in send

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVmomi/SoapAdapter.py", line 1085, in connect

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 1253, in connect

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 849, in connect

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/socket.py", line 712, in create_connection

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/socket.py", line 703, in create_connection

TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVim/connect.py", line 249, in Connect

  File "/build/mts/release/bora-15104183/bora/build/esx/release/vmvisor/vim/lib64/python3.5/site-packages/pyVim/connect.py", line 343, in __Login

1. pyVmomi.VmomiSupport.HostConnectFault: (vim.fault.HostConnectFault) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = '[Errno 110] Connection timed out',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) []

}

Best Regards,

Bruce

Hello wherever you are in the world.  I am new to ESXi, but not new to virtualization.  I am finding that there are quite a few features about ESXi that I like over Hyper-V.  In my lab on my Dell PowerEdge T610, ESXi is installed and I have three virtual machines running.  Lately, whenever I log into the web client and I click on a console to view it, it will say "failed to connect", please see screenshot below.  As far as I recall, I haven't made any changes to the default configuration of this ESXi installation and this problem occurs with each of the 3VM's.  What should I check for now?

When I vMotion a virtual machine, I can see the following entries in the hostd.log on the destination ESXi host.

2015-10-26T14:58:22.441Z [301D7B90 verbose 'Vcsvc.VMotionSrc (1445871396819489)'] Set source task result vm downtime to 115329

2015-10-26T14:58:22.441Z [301D7B90 verbose 'Vcsvc.VMotionSrc (1445871396819489)'] Set source task result precopyBandwidth to 576226700

2015-10-26T14:58:22.441Z [301D7B90 verbose 'Vcsvc.VMotionSrc (1445871396819489)'] Set source task result precopyStunTime to 8491272

What exactly is precopyStunTime?

I assume that "vm downtime" is the switchover time at the end of vMotion. The precopy phase where the memory is copied in the first iteration does not require a Stun, so it does not make any sense? I don't think that this has anything to do with "Stun During Page Send" beacuse I also see this with SDPS Disabled (Migrate.SdpsEnabled=0).

When the precopyStunTime is in "us" (like vm downtime) this would result in 8 seconds in the example above. This would be a pretty long stun?

The question is not specific to a ESXi version, but the version I am running here is VMware ESXi 5.1.0 build-2323236

Hi All

can you help me with some advice on how we can identify user IP connected to ESXi via SSH

Thanking you in advance.