Here is a quick update on the Nested ESXi enviornment I am trying to build on my production cluster.

I have a vDS port group created and Set all security on that port group promiscuous mode : accept , MAC Address Changes : accept and Forged Transmits: Accept and disable the windows firewall on the source VM. I followed this link to install the nested ESXI : http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html and the hardware version selected is 9 and ESxi5.1 later and I am using ESXi 5.5 build 3116895. I confirmed with my networking team there are unable to see the MAC of the nested ESXi in the physical switch whereas the windows VM is ruining fine it is visible in the switch .Nested ESXi VM is using E1000 adapter and VMWARE tools not updated. With the same configuration mean subnet gateway and DNS set to 8.8.8.8 traceroute to 8.8.8.8 works for the windows VM but fails for the nested ESXi VM. Also I have both the VM's on the same host and have tried disabling the ecurity on that port group promiscuous mode : accept , MAC Address Changes : accept and Forged Transmits: Accept and disable the windows firewall on the source VM. But still there is no connectivity between the 2 VM's i.e windows VM and the nested ESXi .

Please advise

Hey Guys,

Got a really odd one here, for the last week I noticed all VM backups (Veeam 9.5) blew out by 35-45mins each. The problem is with 70+ VMs this pushed us outside the backup Window. In terms of troubleshooting so far we haven't got far, I've reviewed the vCenter logs and rebooted EVERYTHING. What we found from this is that when we reboot vCenter we have no issues for about 15 snapshots. The second thing we tried was snapshots from vCenter (rather than Veeam) but we have the same issue and it's only in creation, not removal. No matter how large or small the VM they all take the same time (even a 5GB CentOS Server) roughly 35-45mins. All tha past tasks looking at the vCeneter logs were between 10-130seconds for the

From what i can see in the vCenter logs there is a timeout peroid that is hit causing the task to be canceled/stopped but this is not causing a failure or any issues, everything still works fine. Its just takes 40mins longer per VM for any snapshots.

Here are the the vCenter logs:

2017-04-14T23:07:39.287+10:00 error vpxd[05084] [Originator@6876 sub=MoEvent opID=4569d102] [EventManagerMoImpl::EventBatchAppender::EventAppenderJob::PostJob] VirtualCenter did not respond to the request to append events after 2400 seconds

2017-04-14T23:07:39.291+10:00 error vpxd[05084] [Originator@6876 sub=Vmomi opID=4569d102] [VpxVmomi] IO exception while sending fault

2017-04-14T23:07:39.291+10:00 info vpxd[05084] [Originator@6876 sub=vpxLro opID=4569d102] [VpxLRO] -- FINISH task-internal-27952

2017-04-14T23:07:39.291+10:00 info vpxd[05084] [Originator@6876 sub=Default opID=4569d102] [VpxLRO] -- ERROR task-internal-27952 -- EventManager -- vim.event.EventManager.logUserEvent: vmodl.fault.UnexpectedFault:

--> Result:

--> (vmodl.fault.UnexpectedFault) {

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

-->    faultName = "vim.fault.Timedout",

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

-->    msg = ""

--> }

--> Args:

-->

--> Arg entity:

--> 'vim.VirtualMachine:vm-2741'

--> Arg msg:

--> "Source: Veeam Backup

--> Action: Job "Backup"

--> Operation: Stopped

--> Status: Success

--> ID: 9444fd99-6cb7-45c0-90b7-cead7533a244

--> Description: "

2017-04-14T23:07:39.297+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxdInvtVm::ProcessVmInfo [ProcessVmInfoTime] took 1477703 ms

2017-04-14T23:07:39.297+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxdInvtVm::ProcessVmChanges [ProcessVmChangesTime] took 1477703 ms

2017-04-14T23:07:39.300+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] [VpxdHostSync] ProcessChanges host:syd-sy1-ex02.cloud.local [ProcessChanges] took 1477706 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] [VpxdHostSync] DoHostSync:0000000004A81420 [DoHostSyncTime] took 1478249 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] InvtHostSyncLRO::StartWork [HostSyncTime] took 1478249 ms

2017-04-14T23:07:39.301+10:00 warning vpxd[05316] [Originator@6876 sub=VpxProfiler opID=HB-host-19@28497-1d592c26] VpxLro::LroMain [TotalTime] took 1478249 ms

Going bonkers here guys, not idea whats going on. Thanks in advance for any help

I've created a project on Freelancer also:vmware vcenter | VMware

Cheer.

Hi!

Have a little problem.

Server gets 2 static IP from datacenter`s network. 1st IP "connected" to ESXi, 2nd - to virtual router (VM on ESXi), that routes traffic to other 2 VM (Win Server 2008, Win Server 2012).

Sometimes ESXi drops connections (so no ping) and nobody cant connect to ESXi Web GUI, but the connection to virtual router doesn`t drop. If i connect via RDP to any WinServer VM and stop it, the connection to ESXi restores after 1-2 minutes.

In vmkernel.log no info about ESXi connection drop. Free RAM - 20 Gb - too a lot for ESXi .

The server connected to network by 1 twisted pair cable, so there is no problem with physical NIC`s interface.

So how to solve this problem?

P.S.

ESXi 6.5 (5310538) is installed on IBM x3550 m3. NIC - QLogic NetXtreme II BCM5709 1000Base-T.

I made a mistake and enabled passthrough on the wrong device. Now I want to disable it. It seems that ESXi is stuck thinking that these devices should be in passthrough mode. I followed the instructions here (Changing from passthrough to non-passthrough devices fails to take effect after a reboot (1022011) | VMware KB), but they didn't work. After editing the /etc/vmware/esx.conf using vi and then rebooting, all the devices go back to passthrough mode. So I'm stuck unable to boot up my VMs.

Here's the devices section in my /etc/vmware/esx.conf file:

/device/000:000:31.2/owner = "passthru" 

/device/000:000:31.2/device = "1e02" 

/device/000:000:31.2/vmkname = "vmhba0" 

/device/000:000:31.2/vendor = "8086" 

/device/000:000:29.0/owner = "passthru" 

/device/000:000:29.0/device = "1e26" 

/device/000:000:29.0/vendor = "8086" 

/device/000:001:00.0/owner = "passthru" 

/device/000:001:00.0/device = "1142" 

/device/000:001:00.0/vendor = "1b21" 

/device/000:000:26.0/owner = "passthru" 

/device/000:000:26.0/device = "1e2d" 

/device/000:000:26.0/vendor = "8086" 

/device/000:000:25.0/vmkname = "vmnic0"

After editing, this is what it looks like.

/device/000:000:31.2/owner = "vmkernel" 

/device/000:000:31.2/device = "1e02" 

/device/000:000:31.2/vmkname = "vmhba0" 

/device/000:000:31.2/vendor = "8086" 

/device/000:000:29.0/owner = "vmkernel" 

/device/000:000:29.0/device = "1e26" 

/device/000:000:29.0/vendor = "8086" 

/device/000:001:00.0/owner = "vmkernel" 

/device/000:001:00.0/device = "1142" 

/device/000:001:00.0/vendor = "1b21" 

/device/000:000:26.0/owner = "vmkernel" 

/device/000:000:26.0/device = "1e2d" 

/device/000:000:26.0/vendor = "8086" 

/device/000:000:25.0/vmkname = "vmnic0"

I press :wq! to save and exit from vi editor. I then load the file again to verify it saved the changes and indeed, you can see "vmkernel" in the lines as shown above and none say "passthrough". Then, after rebooting ESXi, everything reverts back to "passthrough"..... Frustrating.

I had an ESXi5.5 host fail the other day and HA did it's job and spun the up VMs on other host.  What I'm trying to figure out is what VMs were on that host prior to the failure, I'm assuming I can find that in a log file?

I'm trying to configure a datastore on an ISCSI LUN from a QNAP .

I've created the LUN on the QNAP and I can see it as available in the new datastore wizard , however when I try to create it , it fails with the " host configuration error "

Thanks

can i update security patches if my license has expired its service and subscription ?

vsphere esxi/vcenter enterprise plus license.

Hey guys,

There is a problem I haven't found a solution yet. On one of my ESXi the datastore the folder /store is symlinking at is not available anymore. I was not aware that this ESXi was configured to use a seperate datastore to host the VMware tools etc. So the whole /store folder is blown away.

Now to my question: Is it possible to recreate the whole /store folder locally or on another datastore without having the old data?

This is the output of "ls -la" in the root folder of the ESXi

lrwxrwxrwx    1 root     root            22 May 23 13:07 productLocker -> /locker/packages/6.0.0
lrwxrwxrwx    1 root     root            49 May 23 13:05 store -> /vmfs/volumes/5909d59f-2844b51d-9f88-2343554653
lrwxrwxrwx    1 root     root            17 Feb 10 07:11 vmupgrade -> /locker/vmupgrade

Another command line output:

[root@ESXi:~] cd locker
[root@ESXi:/locker] ls -la
total 12
drwxr-xr-x    1 root     root           512 Jul 10 10:47 .
drwxr-xr-x    1 root     root           512 Jul 10 08:13 ..
drwxr-xr-x    1 root     root           512 Jul 10 10:47 packages
-rw-r--r--    1 root     root             0 Jul 10 10:47 vmupgrade

Just as a short overview:

My environment consists of 17 ESXi between 5.5 and 6.0 at the moment. All ESXi OS data are normally stored on the corresponding SD cards. I have a 3PAR storage behind all the ESXi and the vCenter is version 6.0.

In advance thanks for your help!

This has been happening since at least Saturday, and others have reported this as well (in the regular Hypervisor forums).

https://my.vmware.com/group/vmware/evalcenter?p=free-esxi6

Neither the "manually download" nor the "Download Manager" links do anything.

I've tried 6 different computers (Windows XP and Windows 7 Home and Windows 7 Enterprise), 4 different web browsers (IE10, IE11, Firefox, chrome), and 3 different ISP (Verizon FIOS, Road Runner, and whoever supplies our Corporate LAN--AT&T or something).

I'm not sure VMware is even aware that there's an issue.

Hello guys,

Please share your ideas for disks best performance using SAS2208 based RAID 0 (4x DC SSD).

Guest VM has thick eager zeroed disks.

What suppose to be a strip size on RAID? Should I do it same as VMFS 1MB ?

Guest OS FS would be ext4/btrfs. Same question, what best block size for FS ? Disks will be used for heavy MYSQL load (of course with COW disabled in btrfs).

Hello, I want to virtualize a test Microsoft Cluster with a SQL-Server instance using Cluster in a Box (CIB) <-- two cluster nodes on the same ESXi.

I have some SAN disks (quorum and SQL-Server data disks) and I don't want to use RDM disks.

Have you tried any virtualization of this type?

Thank you

Good day everyone,

I am totally new here and need help! I installed ESX 6.5i on my HP Microserver about a year ago and gave it to a friend of mine to put a VM of 2012 Server on it which he did and recently returned it to me.

I have a 250gb internal SSD and two 2TB mirrored external drives in two of the bays on seperate HBA controllers.

PLEASE forgive my problem description which may seem primitive by your understanding (as I am still very new to VMWare and ESX etc.)

The 2012 Server VM WAS working and then in the last week it would not start and would not show the SSD as mounted under the Configuration Tab in the VSphere Client.

The VM is italic and greyed out and I cannot start it.

The file and path name under the IP of the Vm Client is as I am sure you people are familiar with :

/vmfs/volumes/58b0c13e-7ae8ea6e-dcdf-d0bf9c45b55c/Windows_SVR_VM.vmx (inaccessible)

When I click on the VM file/pathname itself in the left hand pane and click on the Summary Tab and click the VM Hostname.

When I click the Resource Allocation Tab I get this Error :

An internal error occurred in the vSphere Client.

Details: Object reference not set to an instance of an object.

On the Events Tab I get the description (as shown in scrnsht3.jpg) "Configuration file cannot be found" as an informational message

with the Description "Configuration file for /vmfs/volumes/58b0c13e-7ae8ea6e-dcdf-d0bf9c45b55c/Windows_SVR_VM.vmx on lucky1(host) in ha-datacenter cannot be found.

I am not 100% but I thought VM's themselves were .vmdk files and this .vmx file was on the SSD which I presume is needed to start the VM but I've copied it over to the datastore with the 2xraided disks as well last night.

I will attach screen shots, I hope somebody can help me get this working as I need 2012 to study for my exams...

Thanks and blessings in advance!

LuckyFabian

We've an ESXi 6 server ( Build 2039750 ) that was running fine for months. It uses an LSI Megaraid RAID card with 8 SSDs + Battery in RAID 10. The RAID controller reports no issue and we didn't had any power failures.

Some of the VMs stopped responding today and, after trying several things to stop/restart them, nothing worked. in SSH i'm getting some input/output errors in specific folders:

[root@localhost:/vmfs/volumes] ls

ls: ./c024ed7a-8e112696-2ae9-b4a955c7694f: Input/output error

But as i already mentioned, our RAID setup is fine.

Is there anything that we do to fix this issue? Maybe some kind of fsck in ESXi?

Would upgrading to a newer version help?

hi,

ESXi 6.5 and VCenter appliance 6.5.

i have a cluster with 3 hosts with one of them as dedicated failover host, when enabling the Admission control i am receiving the below warning :

insufficient configured resources to satisfy the desired vsphere HA failover level on the cluster

the warning is cleared when i use percentage admission control

please help

I'm looking to enable the vMotion TCP/IP Stack prior to migrating the VMK to use the Stack. Setting DNS Values, Domain Name and default gateway to allow for L3 capabilities

I ma hoping to compete this using using ESXCLI commands on the newly provisioned host that will read the command via a KS script as there are no CMDlets in PowerCli available as of yet.

It seems pretty straight forward to create the fresh new stack and then add the VMK using this method.

esxcli network ip netstack add --netstack new-vmotion

esxcli network ip dns search  add  --netstack new-vmotion --domain test.domain

esxcli network ip dns server  add  --netstack new-vmotion --server 192.168.5.5

esxcli network ip dns server  add  --netstack new-vmotion --server 192.168.5.6

esxcli network vswitch standard portgroup add --portgroup-name Vmotion_ESX --vswitch-name vSwitch0

esxcli network vswitch standard portgroup set --portgroup-name Vmotion_ESX --vlan-id 202

esxcli network ip interface add --interface-name vmk10 --portgroup-name Vmotion_ESX --netstack new-vmotion

esxcli network ip interface ipv4 set --interface-name vmk10 --ipv4 192.168.111.100 --netmask 255.255.255.0 --type static

esxcli network ip route ipv4 add --network 192.168.111.0/24 --netstack new-vmotion --gateway 192.168.111.1

But if i want to use the existing stacks (vMotion, Provisioning ) that are automatically created during install they don't seem to listed. With the exception of the defaultTcpipStack as per below.

esxcli network ip netstack list

defaultTcpipStack

Key: defaultTcpipStack

Name: defaultTcpipStack

State: 4660

I manually created the VMK and Migrated to the system stack using the web client. Once i Did i re-ran the  esxcli network ip netstack list command  and both default and the vmotion netstack were listed

defaultTcpipStack

  Key: defaultTcpipStack

  Name: defaultTcpipStack

  State: 4660

vmotion

  Key: vmotion

  Name: vmotion

  State: 4660

I tried using the "vmotion" Key/Name list from the above command to edit the dns setting etc but to no luck there either.

One last thing i did try was to enable the Netstack as i noticed you could create them in disabled mode

esxcli network ip netstack set --netstack vmotion --enable true

Unable to find a Netstack instance vmotion

Any ideas if it is possible to edit the system TCP/IP NetStacks via the esxcli prior to adding the Vmks ? Once the VMk has been migrated it is possible to edit the DNS setting etc via esxcli

Any help or pointers appreciated

I have a fresh install of ESXi 6.5 on a very vanilla Dell server, default Broadcom networking, etc.  In VMware Network config, I have a very ordinary networking setup - one management network, one data network for VMs, both on working network connections.

When trying to edit an ESXi 6.5 VM, and choosing the option to "Add network adapter", the console crashes with the following error:

Unfortunately, we hit an error that we weren't expecting.

The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.

Press the Esc key to hide this dialog and continue without refreshing.

When trying to look at the details of crash, I see:

Cause: <div ng-show="wizardOptions.data.networks[_index].AdapterType === 'VirtualSriovEthernetCard'" vui-stack-block="" data-tree-depth="1">

Version: 1.18.0

Build: 5270848

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; Touch; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; InfoPath.3; rv:11.0) like Gecko

Exception stack:

TypeError: Unable to get property 'enabled' of undefined or null reference

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:460:9439)

   at e (https://xxcorpvmw1/ui/scripts/main.js:319:3850)

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:319:23876)

   at Anonymous function (https://xxcorpvmw1/ui/scripts/main.js:319:15273)

   at r (https://xxcorpvmw1/ui/scripts/main.js:318:21124)

   at I (https://xxcorpvmw1/ui/scripts/main.js:319:15257)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11540)

   at I (https://xxcorpvmw1/ui/scripts/main.js:319:15454)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11540)

   at g (https://xxcorpvmw1/ui/scripts/main.js:319:11557)

There doesn't seem to be anything obvious I can edit in the VMX.  What other options can I try, short of having to re-install ESXi 6.5?

I SSH into my esxi 6.5 box and type dcui ... nothing happens

Over in vCenter it says it is running ....

any ideas?

Hi there,

I've been troubleshooting a bunch of servers that have a single 10GB connection each, as when moving VMs around using cold migration, the transfer speeds are between 400-500mbit. I've got SSDs in RAID-0 for testing on all these hosts that can easily do 12GB/sec (1000MB+) reads/writes so I don't have storage as a bottleneck. Using vMotion I can get the VMs moved at around 6-7Gbit, but when using cold migration, it doesn't go further than 400-500mbit, even though it is going to the same storage, same network and same physical wire/switch/NIC. I've tested across 5 different hosts, ranging from Dell R515, to R710 and R720XD, all of them with decent RAID controllers. For some reason it seems ESXi artificiality limits the network speed for cold migration (as for testing I've got one NIC on each server and they are for both management and vMotion), as the graphs never spike up or down, it is very much flat.

I checked alreayd the virtual switches and nothing is using limits. I don't know where else to look at. Also I tested SMB traffic in between VMs hosted in different hosts, connected physically by the 10GB network and I can get 6-7Gbit on file transfers, so it mean it works for everything, but cold migration. I had this problem in the past where out of nowwhere a 1GB connection would not go faster then 300mbit for example, no matter what you do. Then out of now where it would reach 1GB speeds. No reason why!

I'm using an Intel x540-t1 PCI-e card on each server.

Server have 128GB of RAM, all fully updates firmware wise, running ESXi 5.5 build 2068190.

I've also tested Veeam using the quick migration force mode, which I suppose is similar to the fastscp client in the past. Pretty much same result, around 500mbit.

Any suggestions how to speed up cold migration?

Thanks!

Is there a command that will get this done? Or if the VMDK file doesnt exist but the ESX host still think it's there even after rebooting how would I clear the VMDK or the lock of the device resource out?

Hello everybody.

I am following the step by step guide of the official VMWare ICM 6.0.

I am completely stuck on "Lab 7: Using Standard Switches", task 3 "Assigning VM a new port group".

It has to be said that I am following the guide with the desktop client (not the web).

Task 2 tells me to create a new standard vswitch with a new Port group named "Produccion" (See "Screenshot_1.jpg" attached). Ok so far.

Task 3 tells me to assign that port group to the XP client on the first ESX. (See "Screenshot_2.jpg" attached).

Then I have to turn on the VM and do a ipconfig /release followed by an ipconfig /renew command. The IP that I get can be seen on "Screenshot_3.jpg" attached.

Then I have to ping my vCenter, with no success.

¿Why that IP configuration? ¿Why is there no gateway? ¿How can I configure the "Produccion" network so I can see my vCenter (192.168.1.50)?

¿why the IP ranges of vmnic0 and vmnic1 are such (See "Screenshot_4.jpg" and "Screenshot_5.jpg" attached)?

Thanks in advance!