Hello.

I am trying to install owncloud on my VMware ESXi. I click on deploy OVA, then drag it onto the area it says to, then next, I agree to the terms then it says do not vlose window whilst it deploys. The file uploads fine to the server.

In the Tasks area it says importing VApp, with the progress bar, however the progress bar sits at 0%. I gave it 45 minutes last night before giving up and tried again this morning from scratch and gave it 1,5 hours. Still nothing that progress bar does nothing.

Can anyone offer any hints as to what I could try next?

Version 6.7.0 (Build 8169922)

Hello.

I'm hopping someone has some clue why this is happening.

Using esxi 6.5u2, passthrough GPU (NVIDIA 2080 TI) works perfectly. On 6.7U1 it works until I reboot the Windows VM. After rebooting I get error code 43 and the only working fix is to reboot the host. The GPU passtrhough only works on the first VM boot. If I reboot the VM it stops working with error code 43.

Downgrading to esxi 6.5U2 fixes the issue.

Any suggestions ?

We have 3 VMWare hosts, with shared and direct attached storage.  We have been moving things around, and temporarily moved some VM's to a Windows 2012r2 Storage server.  We setup the storage as NFS 4.1 in VMWare, and setup following the many guides on the internet on the 2012r2 server.

I'm not sure what happened, but we can no longer extend or create storage.  I have tried many many things on both the VMware side and the server 2012r2 server, but am at a loss.  None of the 3 hosts can create disks on the 2012 datastore.  I can create disks on my OpenSuse NFS storage, as well as the local direct attached storage.  All 3 vmware hosts are acting the same. 

The error message I get when trying to create a disk:

A general system error occurred: Error creating disk Device or resource busy

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of Unlink[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of Ioctl[file] failed

File system specific implementation of RenameFile[file] failed

I can browse the data store, and I can create folders, edit files, etc..  I can mount existing disks and the vm works.  I just can't create new, or extend the size of existing. 

Any ideas? 

Thanks!

Hello,

I'm upgrading vcenter with external psc from 6.5 U1 to 6.5 U2.

The first step of PSC upgrade was OK but i had an issue in step 2. The issue was appeared during the pre-upgrade check.

When i looked into the log files I saw that there was an issue with ntp service.

2019-01-06T23:37:26.510Z INFO service_manager Service vmware-stsd: STARTED

2019-01-06T23:37:26.510Z INFO sdk_utils Appliance has version 6.5.0.0

2019-01-06T23:37:26.517Z ERROR transport Command ['/sbin/chkconfig', 'ntp'] exit-code=1, stdout=, stderr=ntp: unknown service

I ran the command /sbin/chkconfig ntp on the psc server. These were the results.

root@psc [ ~ ]# /sbin/chkconfig ntp

ntp: unknown service

root@psc [ ~ ]# /sbin/chkconfig ntpd

Note: Forwarding request to 'systemctl is-enabled ntpd.service'.

enabled

root@psc [ ~ ]#

You will find attached the log files.

Can someone help me solve this?

Thanks

Our ESXI6.5 worked fine for several months.

The uplink to the physical switch is done by 3 physical NICs (vmnic3, vmnic4, vmnic5) in failover configuration.

Load balancing mode: explicit failover order

Network failure detection: Beacon Probing

Notify Switches: tried both Yes or No makes no difference

Failback: Yes

With the upgrade U1 installed we get every few minutes messages like:

Lost network connectivity on virtual switch "red". Physical NIC vmnic5 is down. Affected portgroups:"red".

The funny thing is, that the affected NIC changes from time to time. Any of 3 NICs show the Errors for a few hours before it changes to the next one.

Sometime 2 of them show the Errors alternating.

I don't think there is a hardware failure because any of the NICs show this behaviour and the actual connectivity is most of the time fine.

The statistics of the connected physical switch shows no Errors or Disconnects on any of the 3 ports who are connected to the physical NICs.

Any idea ?

Hello all

I've recently upgraded from 6.5u1g to 6.7u1 using a custom Fujitsu ISO.  After ESXi hosts were upgraded, I was given an information warning:

This host is potentially vulnerable to issues descibed in CVE-2018-3636, please refer to https://kb.vmware.com/s/article/55636 for details and VMware recommendations. KB 55636.

The hardware is Fujitsu servers running Xeon E5-2620 v2.

Looking at the article, its suggests applying patch 6.7.0d.  The release date of the notice is 2018-08-14.

I'm assuming as I have 6.7u1 (release 2018-10-14) that this patch is rolled up in at and this warning can be safely ignored?  I just find this odd that I'm getting the warning after installing a later version?

Thanks for your help!

Hello,

I was doing some tests in my customer environment. We have a cluster, 6 ESXI 6.1 U3.

When I connect to the DCUI and I poweroff the ESXi all the virtual machines running in this server poweroff and move to another ESXi host, but they don´t power on. My customer complains because he says that HA is not acceptable. I think it´s the normal way but I didn´t find any evidence.

If you can help me.

Thanks in advance.

Hello,

i hope i am in the right place here.

I am trying to import a virtual machine via the vmware esxi web client.

The upload of the file works without problems, but when the host is trying to import the VAPP it's getting a timeout.

I couldn't find anything about this specifcally and i already tried every diffrent setting during the setup I could think of.

I hope you guys can help me. If any further informations are needed I am sure that i could provide them.

Best regards

Hi All,

Using an Intel i7 4770 which has the Intel onboard HD 4600 graphics. I've passed this through to the Win10 VM and as a result I now have QuickSync/Hardware acceleration working for a CCTV tool I'm using.

What is not working is the HDMI onboard of the motherboard and part of the HD4600 - if I cable this to an external display, I get no output at all.

Any thoughts as to what I can check?

Im using latest Intel drivers, Win10 updates and ESX

Thank you

I've installed an ESXi evaluation and stumbled upon a bug. Reported it to @vmwarecares on Twitter and they've told me to report it here. This isn't a question, but merely a bug report to the development department. I couldn't submit this through the support page, as evaluations aren't listed (it requires to select a product, but there are none for that reason).

Product: VMware ESXi Version: 6.5.0 (Build 5224529) - Image profile: ESXi-6.5.0-4564106-standard (VMware, Inc.)

Category: BUG

Behaviour: When an invalid SSL certificate is uploaded through the vSphere web client, it's refused but applied nevertheless, crashing any and all of the management daemons.

Expected behaviour: When an invalid SSL certificate is uploaded through the vSphere web client, vSphere web client throws an error.

Steps to reproduce:

1. Login to the vSphere web client (https://{$IP}).
2. Navigate to Host -> Manage -> Security & Users -> Certificates.
3. Click 'Import new certificate'.
4. Import any, single PEM encoded certificate.
5. vSphere will throw an error, rejecting the certificate.
6. Wait a few minutes.
7. Refresh the web client (hard refresh!), it will refuse the connection.
8. Login to the SSH daemon, most management actions will be impossible (eg, vim-cmd, esxcli, will throw an refused connection error).

Steps to diagnose:

1. The VPXA log (/var/log/vpxa.log) contains this line:
   [Originator@6876 sub=Default] Failed to initialize the SSL context: N7Vmacore3Ssl12SSLExceptionE(SSL Exception: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch) --> Panic: Failed to initialize the SSL context.

Steps to fix:

1. Execute: /sbin/generate-certificates
2. Restart the management daemons: services.sh restart

3x Fujitsu Primergy RX2510 M2

running ESXi 6.5 u1 (Fujitsu VMvisor-Installer-6.5-5969303-v411-1) with Intel I350 4port NICs

All drivers are as vmware/Fujitsu ISO standard.

HP ProCurve Switch 5406zl  with cluster uplinks connected to the same 24 port Gig-T ZL module.

all 4 uplinks on each port group are patched into the same switch, have the same switch port configs (untagged vlan xxx)

I have an intermittent issue with 4 vmnic4 showing "no networks". The vmnic in question is one port on a 4 port Intel I350 P4 card.

Once a vmnic shows this state, its stuck that way until I either down and up the vmnic, or reboot the host.

A week later a second host did exactly the same with a different port on the same make/model of 4-port card.

about 10 days later the 3rd host also did the same with a different port again.

If i vmotion the VM to another host its fine.

If i drop the problem vmnic out of the port group, the vms are fine on the remaining uplinks.

the problem NIC on each server is one port in a 4 port card, with all 3 other links functioning perfectly before and after.

I have been all over this including wiresharking the problem port from a VM.  The "no networks" uplink still shows some traffic from the LAN, however a lot of ARPs are going unanswered etc. so Im not convinced this is a flakey port.  However Ive also replaced the 4 port NIC in one server, only to have the issue reappear a week later.

esxcli network nic stats get -n VMNIC4 reveal the following:

Receive FIFO errors 57039176

Receive missed errors: 57039176

No other errors are shown.

Any pointers on this would be a huge help!

Cheers

O

As an assignment, we're supposed to create the following scenario:

We only have access to one PC for the servers. Our instructor suggested creating a virtual machine inside VMWare Workstation and loading up VMWare ESXi in the virtual machine; then we are to create 4 virtual machines inside ESXi for the servers mentioned above.

I don't quite understand why do we have to go through all this trouble. We've only been breathly introduced to Workstation so I don't know what advantage does ESXi have over just creating four virtual machines on the system. On the other hand, I don't know how to make the four virtual machines inside ESXi accessible through the switch. I thought of setting both Workstation and ESXi to bridge mode but I couldn't find anything online backing this idea. I'd appreciate it if you could help me with these two questions.

I have looked into few Python APIs and its very tough to find any host related operations which doesn't need vCenter.

Is there any API in python to reboot/shutdown the standalone ESXi host ?

Hello

ESXi version: 6.7.0 build: 8169922

In the web tool, config page there is the number of CPU setting. I have one CPU with 12 cores. License says Up to 8-way virtual SMP. If I have two guest and I put 6 CPU on each, will the only use 8 cores in total together or will alla 12 cores be used?

cheers

All, I have a Datastore that will not mount.  It is on a HP P2000 and VMware (5.5.0 u3b) on the host required a rebuild after corruption.  Note the store would not mount previously.  9 out of 10 stores mount and are visible in VMware. 

I have already tried to reset the partition table - using partedUtil.  following the guidance  here - VMware Knowledge Base

~ # partedUtil getptbl /vmfs/devices/disks/naa.600c0ff00014c353c7c00f5001000000

gpt

497976 255 63 8000000000

1 2048 7999997951 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

getUsableSectors returned -  7999999966

Current status -

~ # partedUtil getptbl /vmfs/devices/disks/naa.600c0ff00014c353c7c00f5001000000

gpt

497976 255 63 8000000000

1 2048 7999997951 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

Note - have tried both 7999997951 and 7999999966 for usable sectors

The drive does not show within /vmfs/volumes yet the device shows as mounted via the vSphere Client, under storage adapter, Operational State. 

Errors in the kernel log show - 'No FS driver claimed device 'naa.600c0ff00014c353c7c00f5001000000:1': Not supported'

Calculated value for usable sectors was - 7999984439 - and this also fails.

This volume is 4TB.

Any ideas?  Many thanks.

This is killing me. All I want to do is add an additional NIC to two VMs. I can't. This is a new installation. I have 5 running production VMs plus the vcenter appliance. Things WERE working fine and just quit working out of the blue.

I can't even "connect" an ISO image to a CDROM.

I tried powering down the VM with no change. (Actually the VM never would even show is was powered off in the client, but since the only power option was "power on" at this point, I assumed it was off.)

I can't modify ANY VMs at all. I have restarted the vCenter Appliance with no change in behavior. Why are we forced to use this horrible Web Client??????

Running 5.5 build 1750787 - Have been pushing to sell hyper-v since the support options for vmware are cost prohibitive for SMB, but vendor for this customer requested vmware.

I am new to VMWare...

I have two VMWare 6.7 hosts at different sites and I am trying to connect the same type of backup solution in the same way.

At one site it works fine and at the 2nd site the backup solution is unable to connect.

The only difference I can see is at the site the works the web clients shows VMotion Supported = Yes and at the 2nd site it says No.

Both sites are unlicensed.

I see in the event log that the backup device logs in and then immediately logs out.

Could this VMotion setting be the cause and if so how can I change the 2nd site to match the 1st?

Thanks in advance.

Hi all,

Kind of lost here.

I'm trying to upgrade a Lenovo hosts (System x3550 M5) to 6.7.

We have two identical units.

First attempt failed on VIB merge:

ValueError: Cannot merge VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03, ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 with unequal payloads attributes: ([elx-esx-libelxi: 1493.833 KB], [elx-esx-libelxi: 1602.936 KB])

We solved it on the first host, by deleting the problematic VIB and and then proceeded with the update and it worked like a charm.

We try to do the same on the second host, but the update failed.

Below is a snippet from the VUA log which i think is relevant.

Notice that the <expected> </expected> section is empty.Any help is appreciated, thanks.

<test>

<name>PACKAGE_COMPLIANCE</name>

<expected> </expected>

<found>

...

...

<value>VMware_bootbank_esx-dvfilter-generic-fastpath_6.7.0-0.0.8169922</value>

<value>VMW_bootbank_lpnic_11.4.59.0-1vmw.670.0.0.8169922</value>

<value>VMware_bootbank_esx-base_6.7.0-1.28.10302608</value>

...

...

</found>

<result>ERROR</result>

</test>

Server 2016, latest OS updates

ESXi 6.7.0 Update 1 (Build 10764712)

VMWare Tools 10.3.2 build 9925305

when i run a snapshot with the "Quiesce guest file system" option, the snapshot results in "Failed - An error occurred while quiescing the virtual machine. See the virtual machine's event log for details." (unless i reboot the server first, see below).

in the application log of the server i see nothing helpful. shadow copy is duplicating discs, the lsass service announcing that it's database moved to a new location and is recovering.

DFSRs (2180) \\.\C:\System Volume Information\DFSR\database_E0D0_742D_D074_BD2\dfsr.db: The database engine stopped the instance (0).

lsass (580) Shadow copy instance 7 freeze started.

svchost (2156) Shadow copy instance 7 freeze started.

DFSRs (2180) \\.\C:\System Volume Information\DFSR\database_E0D0_742D_D074_BD2\dfsr.db: The database engine (10.00.14393.0000) is starting a new instance (0).

lsass (580) The database engine is initiating recovery steps.

lsass (580) A database location change was detected from 'C:\Windows\NTDS\ntds.dit' to '\\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c}\Windows\NTDS\ntds.dit'.

system log shows nothing helpful either. volumes are mounted, and are healthy. what is strange is that one volume gets mounted 12 times (in this case, volume 40)

Volume \\?\Volume{0943f5aa-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume36) is healthy.  No action is needed.

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

.... 12 times in total...

Volume \\?\Volume{0943f5ad-14de-11e9-8b96-000c2998569c} (\Device\HarddiskVolume40) is healthy.  No action is needed.

then the message "disk 1 has been surprise removed" but according to a google search this is nothing to worry about. message appears on other vms too, where q-snapshots work fine, so i guess it can be ignored.

the dfsr service gets stuck and doesn't recover, meaning no more sysvol replication between this DC and it's peer. i can create files in sysvol on the partner DC and these files get synced to me, but creating files in sysvol on the affected DC don't get synced back. only a DFSR service restart fixes this.

when i restart the DC, i can do one snapshot with Quiesce option and it works fine, but trying a second time it results in failure again.

apart from searching the net for the entire day, i have tried restarting several services, like the vmware tools service, the VSS service, the DFSR service, but i can not reliably make it work/fail afterwards, and i have so far not the slightest clue why this happens. only a full server reboot can reliably make it work again once.

the only "solution" i found so far was to uninstall the vmware vss helper

this "solved" the problem for good but i am not confident i should leave it like this?

the server is quite a fresh install (5 month), with a fresh domain on it, there is no other software installed on it and it has not been "played with" configuration wise, so this is the most basic OS+AD+Vmwaretools install you can get.

any ideas, anyone?

I'm trying to connect to vSphere to remote control a machine but I'm being unable to because the application hangs.

I tried to check for logs in /var/log/vmware but there are only USB arbitrator errors. Including:

usbArb| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

How can I diagnose and solve such issue?