In my vCenter 6.7, the ESXi host Heap memory and Heap Free memory is always "0", in vCenter 6.5 is OK,   is it a issue of vCenter 6.7?

...or at least, that's what's *happening*. The error message claims that the host volume in question is almost full and asks for a specific amount of space to be freed, but it's asking for ~/50MB on a disk that has 12GB of free space. What's going on here? Is it actually asking for *contiguous* free space (in which case it should say so)?

Hello

For Player 14 vmrun is available via VIX installer. After upgrade to 15 this VIX version stopped working.

From what I checked VIX is now part of Workstation Pro install, I thought it should be also in Player installer but looks like is missing in this Workstation version.

In compare datasheet of Pro and Player vmrun is listed for both versions.

How I can install this feature for Workstation Player ?

Best Regards

Hi,

after changes in my ubuntu 14.04 computer (mainly related to the gcc compiler - if I understand it correctly), starting VMWare fails.

In the first step after starting, I am asked to perform a Kernel Module Update:

Before you can runVMware, several modules must be compiled and loaded into the running kernel.

I click on "install", are asked for my (sudo) password and get afterwards

Unable to start services.

See log file /tmp/vmware-root/vmware-12819.log for details.

This file contains the following information.

How can I resolve this issue?

Thanks in advance!

2018-10-27T14:43:13.412+02:00| vthread-4| I125: Log for VMware Workstation pid=12819 version=12.5.7 build=build-5813279 option=Release

2018-10-27T14:43:13.412+02:00| vthread-4| I125: The process is 64-bit.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2018-10-27T14:43:13.412+02:00| vthread-4| I125: Host is Linux 4.4.0-138-generic Ubuntu 14.04.5 LTS

2018-10-27T14:43:13.412+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: PREF Unable to check permissions for preferences file.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2018-10-27T14:43:13.412+02:00| vthread-4| I125: PREF Failed to load user preferences.

2018-10-27T14:43:13.446+02:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-12819.log

2018-10-27T14:43:13.451+02:00| vthread-4| I125: Obtaining info using the running kernel.

2018-10-27T14:43:13.451+02:00| vthread-4| I125: Created new pathsHash.

2018-10-27T14:43:13.451+02:00| vthread-4| I125: Setting header path for 4.4.0-138-generic to "/lib/modules/4.4.0-138-generic/build/include".

2018-10-27T14:43:13.451+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.451+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.451+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.451+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.455+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.456+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:13.595+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-138-generic/build/Module.symvers

2018-10-27T14:43:13.595+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-138-generic/build/Module.symvers.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Read 18956 symbol versions

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Reading in info for the vmmon module.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Reading in info for the vmnet module.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Reading in info for the vmblock module.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Reading in info for the vmci module.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Reading in info for the vsock module.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Setting vsock to depend on vmci.

2018-10-27T14:43:13.611+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2018-10-27T14:43:13.613+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:13.613+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2018-10-27T14:43:13.614+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:13.614+02:00| vthread-4| I125: Invoking modinfo on "vmblock".

2018-10-27T14:43:13.615+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:13.615+02:00| vthread-4| I125: Invoking modinfo on "vmci".

2018-10-27T14:43:13.616+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:13.616+02:00| vthread-4| I125: Invoking modinfo on "vsock".

2018-10-27T14:43:13.617+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2018-10-27T14:43:13.627+02:00| vthread-4| I125: to be installed: vmmon status: 0

2018-10-27T14:43:13.627+02:00| vthread-4| I125: to be installed: vmnet status: 0

2018-10-27T14:43:13.637+02:00| vthread-4| I125: Obtaining info using the running kernel.

2018-10-27T14:43:13.637+02:00| vthread-4| I125: Setting header path for 4.4.0-138-generic to "/lib/modules/4.4.0-138-generic/build/include".

2018-10-27T14:43:13.637+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.637+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.637+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.637+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.641+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.641+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:13.782+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-138-generic/build/Module.symvers

2018-10-27T14:43:13.782+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-138-generic/build/Module.symvers.

2018-10-27T14:43:13.798+02:00| vthread-4| I125: Read 18956 symbol versions

2018-10-27T14:43:13.798+02:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.4.0-138-generic/build/include

2018-10-27T14:43:13.798+02:00| vthread-4| I125: Update kernel header path to /lib/modules/4.4.0-138-generic/build/include

2018-10-27T14:43:13.798+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.798+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.798+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.798+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.803+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.803+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:13.804+02:00| vthread-4| I125: Unable to find a GCC compiler in the system path.  Attempting to use a compiler at location "/usr/bin/gcc-4.8".

2018-10-27T14:43:13.806+02:00| vthread-4| I125: Got gcc version "4.8".

2018-10-27T14:43:13.806+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-10-27T14:43:13.806+02:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc-4.8".

2018-10-27T14:43:13.808+02:00| vthread-4| I125: Got gcc version "4.8".

2018-10-27T14:43:13.808+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-10-27T14:43:13.809+02:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.4.0-138-generic".

2018-10-27T14:43:13.809+02:00| vthread-4| I125: No matching PBM set was found for kernel "4.4.0-138-generic".

2018-10-27T14:43:13.809+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-10-27T14:43:13.809+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.809+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.809+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.809+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.814+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.814+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:13.880+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-10-27T14:43:13.880+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.880+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.880+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.880+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.885+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.885+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:13.885+02:00| vthread-4| I125: Using temp dir "/tmp".

2018-10-27T14:43:13.886+02:00| vthread-4| I125: Obtaining info using the running kernel.

2018-10-27T14:43:13.886+02:00| vthread-4| I125: Setting header path for 4.4.0-138-generic to "/lib/modules/4.4.0-138-generic/build/include".

2018-10-27T14:43:13.886+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-138-generic/build/include" for kernel release "4.4.0-138-generic".

2018-10-27T14:43:13.886+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-138-generic/build/include/linux/version.h

2018-10-27T14:43:13.886+02:00| vthread-4| I125: /lib/modules/4.4.0-138-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-10-27T14:43:13.886+02:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check

2018-10-27T14:43:13.890+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-138-generic".

2018-10-27T14:43:13.890+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-138-generic/build/include" for the kernel "4.4.0-138-generic" is valid.  Whoohoo!

2018-10-27T14:43:14.029+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-138-generic/build/Module.symvers

2018-10-27T14:43:14.029+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-138-generic/build/Module.symvers.

2018-10-27T14:43:14.046+02:00| vthread-4| I125: Read 18956 symbol versions

2018-10-27T14:43:14.046+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2018-10-27T14:43:14.048+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:14.048+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2018-10-27T14:43:14.050+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2018-10-27T14:43:14.463+02:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.0-138-generic/misc/vmmon.ko".

2018-10-27T14:43:14.463+02:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-10-27T14:43:14.472+02:00| vthread-4| I125: Successfully extracted the vmmon source.

2018-10-27T14:43:14.472+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-kjIYtt/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.0-138-generic/build/include CC=/usr/bin/gcc-4.8 IS_GCC_3=no"

2018-10-27T14:43:14.714+02:00| vthread-4| W115: Failed to build vmmon.  Failed to execute the build command.

2018-10-27T14:43:14.716+02:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.4.0-138-generic/misc/vmnet.ko".

2018-10-27T14:43:14.716+02:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2018-10-27T14:43:14.724+02:00| vthread-4| I125: Successfully extracted the vmnet source.

2018-10-27T14:43:14.724+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-kjIYtt/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.0-138-generic/build/include CC=/usr/bin/gcc-4.8 IS_GCC_3=no"

2018-10-27T14:43:14.924+02:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

Hi,

Does HTML client SDK(6.5U2 and above) support <privilege> and <propertyConditions> for <metadata> of extensions?

I'm not able to find any info on the SDK Online Documentation - vSphere Client SDK Developer Guide - VMware {code}

Thanks,

Kumar

突如、仮想ＯＳに対してリモートデスクトップ接続ができなくなりました。
vCenterでの表示は[VMware tools:実行されておらず　]となっています。　
UCNで共有フォルダに対してアクセスは可能です。
CPU使用状況：2.ooGHzと高いです。
直前にAercServeのバックアップを行いました。（正常終了しています）

復旧させるためには何を調べたらよいでしょうか？

また、vCenterからゲストＯＳのVMware toolsを実行させる方法を教えてください。

Currently, I am working on a project to upload a file to VCSA  with root account using this api “makeDirectoryInGuest”， but it is fail to connect. The root cause is my root account is expired. So I want to find a API to check if the account is expired or get root expire information( such as expire date). I find ValidateCredentialsInGuest api can be used to do authority, but it will return the same exception if the password is expired or incorrect password, and I can not distinguish them. Does anyone help to guide which api should I use to get root expired information.

Hi,

When creating the 2 vmkernels (which will have one active uplink and one unused uplink), should I assign a different network/subnet to each vmkernel?

We would like to delete a Datastore on our vSphere Server but it doesnt work ... We always get a "Not a known device" Error and were not sure why that is ... We had problems before with this specific Datastore, and thats why we wanted to delete it. Is it possible something is still linked to the Datastore and how do we find out if it is? What else could it be?

I am getting the "Configuration Issues" when I login to vSphere client on newly installed "VMware-VMvisor-Installer-6.0.0.update03-9313334.x86_64-DellEMC_Customized_A12.iso" on Dell server., installed on internal SD Card.

Any help. Did tried uservar to 1 but no luck.

Hello all,

we have an issue while trying to mount NFS datastores to additional hosts.

If we use the the flash client the operation fails.

The window that shows a collection of hosts from which you can choose to mount the DS stays empty and ceeps "refreshing" until you cancel the operation.

Mounting the DS using the HTML5 client or powercli works without any problems.

Does anybody had an idea where the problem can come from?

Is the vpx.log the right log to look for an hint?

thank you.

kind regards

PS: Version 6.5.0.20000 Build 9451637

Hey everyone,

We are in the process of deploying AppVolumes to certain users (for Adobe Pro). I have a weird behavior once the AppStack is deployed. If we assigned the appstack by users, the AppStack will only apply every 2 login, here's the process:

1.Initial login, AppStack available. Sign out occurs, VM reboots (due to RebootAfterDetach).

2.User logs back in and the AppStack in unavailable.

3.User sign out, reboot, user logs back in and AppStack is available.

After logging into vSphere, I was monitoring the tasks after the sign out of the VM, on step 1 the VHD will be detached from the VM and on step 2 it will not be re-attached. On step 3 it re-attaches again. So the issue is at step 2 where the VHD is actually never attached to the VM.

I've tried to replicate the isssue with computer assignment (with detach on shutdown) and it works perfectly, the VHD is always re-attached to the VM.

We are using version 2.14.

Has anyone had the same issue?

Thank you,

Hello,

I have built a new linked clone pool from a golden image which is Win 10 with .net35 (for a software) and app volumes client. Also I have used the VMWare Optimazation Tool.

I have also built a "standard application App Volume" which I have mapped to an AD User (also a group but there is another thread for this).

When I now log in on my linked clone I don't get the virtual applications. When I look in the activity log on the App Vol Server I see that he tries to attach the volume to the client but this line in the log is filled with a red background color.

After some search in the log files I found the part where he tries to attach and everything seems fine on the first look. He authenticates, he recognize the volumes to attach and then he declines the attachment. In the log there is following line:

[2018-10-30 14:05:41 UTC] P4200R1053RA ERROR   RvSphere: vSphere operation failed: Failed to add disk 'scsi0:2'.

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Async completed for Machine <Virt18-HOff002> (50386119-c629-09e1-159b-538cf3f77642) with result false, Total time taken 0.44 secs

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Incrementing unmount count for volume #32, now 1

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Incrementing incomplete mount count for volume #32, now 1

[2018-10-30 14:05:41 UTC] P4200R1053RA ERROR        Cvo: Declined all 1 attachments for "User <HM1\grossman>" on "Machine <Virt18-HOff002> (50386119-c629-09e1-159b-538cf3f77642)"

I have googled the error and someone suggest to look for other VMs which have the vmdk mapped but I couldn't find any (the system is new and so here are only few other machines). No I don't know where to search further. Can you see anything what helps me with that problem?

Regards

Hello



I installed VMware WSX and once on "http: // localhost: 8888 /" I could not log ... so I realized that I need to put the local account of my machine, but it does not work no ... on my machine there is only one admin account, with account name "Flitz" and no passwords on the session ....



So how to do this connect knowing that WSX refuses the connection by saying "Invalid username or password"

thank you

Hello, I ask for help in solving my problem, because searches so far have not led to anything.

I assembled a test bench from 3 Dell R720 hosts (integrated RAID PERC H710 Mini) in All-flash configuration. Each host has an Intel DC S4600 SSD drive, 240GB for the cache and two 480GB drives for data. Each drive in the raid is configured for RAID-0 with the following settings: Read Policy — No Read Ahead, Write Policy — Write Through, Stripe Size — 256K. Each host also has a 10GB Broadcom QLogic 57800 network card and is connected via a 10GB Ubiquiti 16XG switch. VMware ESXi, 6.5.0, 10175896 is installed.

Measurements of the read/write speed in the VM show the sad performance of 585\150 Mb/s. Measurements produce program CrystalDiskMark. Exactly the same indicators were when instead of SSD drives were regular SAS 10k drives. And also if you look at the analysis of VSANa itself, low IOPS (I attach screenshots). I tried different releases, customized images from Dell, but the result does not meet expectations. Can anyone come across a similar

I'm using ESXi version - VMware ESXi 6.7.0 build-10302608 and server  HPE ProLiant DL360 Gen10 machine.  Loaded with this 10Gig card (QLogic Inc. QLogic 57810 10 Gigabit Ethernet Adapter) which uses native driver =qfle3.

I've set the SR-IOV enable from HP BIOS and enable the host with DRSS,RSS,rxqueue/txqueue.

[root@localhost:~] esxcfg-module -g qfle3

qfle3 enabled = 1 options = 'DRSS=4,4 RSS=1,1 rxqueue_nr=8,8 txqueue_nr=8,8'

Unfortunately, I did not enable SR-IOV from vCenter/vSphere Client, hence the SR-IOV was not enabled due to the native driver qfle3.

1. Using the host client http://ip_address/ui doesn't have the ability to enable SR-IOV under physical adapter.  Is there another way of doing it?

or

2. Install a software vib with bnx2x driver to force the SR-IOV settings from ESXi host level using "max_vfs" command.  Where can i find it?

Buenos días,

Estoy teniendo a la hora de correr el asistente de migración de vCenter 6.7 U1.

En el paso de de configurar el acceso al appliance de vCenter y al host ESXi me dice "Unable to find the source appliance on the specified ESXi host or vCenter Server."

He revisado que todos los datos son los correctos como muestro en la imagen. Mi vCenter es la IP 192.168.0.102 y el servidor ESXi donde se encuenta la maquina virtual de vCenter es 192.168.0.106.

El log me indica un error que no me ayuda mucho:

2018-10-30T12:17:45.584Z - info: installerLogFile: C:\Users\Francis\AppData\Local\Temp\vcsaUiInstaller\installer-20181030-131745581.log

2018-10-30T12:17:45.620Z - info: networkLogFile: C:\Users\Francis\AppData\Local\Temp\vcsaUiInstaller\network-20181030-131745581.log

2018-10-30T12:18:08.801Z - debug: wizardTitle: Upgrade - Stage 1: Deploy appliance

2018-10-30T12:18:48.068Z - info: getDeploymentType() on source VC:192.168.0.102

2018-10-30T12:18:48.069Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:18:50.186Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:18:50.219Z - debug: session does not exist: 192.168.0.102,

2018-10-30T12:18:50.220Z - debug: Logging in to 192.168.0.102:443 as

2018-10-30T12:18:53.244Z - error: Failed to login to 192.168.0.102:443 as : ServerFaultCode: Cannot complete login due to an incorrect user name or password.

2018-10-30T12:19:24.111Z - info: THUMBPRINT(vCenterAppliance): 09:5D:E2:F8:54:DC:46:1D:9A:A6:3A:29:A3:8D:4C:13:EF:7B:B4:3A

2018-10-30T12:19:24.135Z - info: THUMBPRINT(esxiHost): 9C:3E:A7:ED:C9:07:8A:EE:DF:A4:99:CD:96:15:46:A7:D7:92:14:E2

2018-10-30T12:19:24.868Z - info: attemptHttpsConnToSourceVc

2018-10-30T12:19:24.907Z - info: login() to source VC:192.168.0.102

2018-10-30T12:19:24.907Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:19:24.974Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:19:24.998Z - debug: session does not exist: 192.168.0.102, administrator@vsphere.local

2018-10-30T12:19:24.998Z - debug: Logging in to 192.168.0.102:443 as administrator@vsphere.local

2018-10-30T12:19:25.111Z - info: Logged in to 192.168.0.102:443 as administrator@vsphere.local, session: 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:19:25.112Z - info: Login successful to source VC, IP: 192.168.0.102

2018-10-30T12:19:25.112Z - info: login() to host managing the source VC:vm01.cpsi.local

2018-10-30T12:19:25.112Z - info: initializing vsphere API connection to vm01.cpsi.local:443

2018-10-30T12:19:26.065Z - info: vimService apiType: HostAgent, version: 6.5.0

2018-10-30T12:19:26.095Z - debug: session does not exist: vm01.cpsi.local, root

2018-10-30T12:19:26.095Z - debug: Logging in to vm01.cpsi.local:443 as root

2018-10-30T12:19:26.182Z - info: Logged in to vm01.cpsi.local:443 as root, session: 52568a7c-5ab7-389c-8b6d-042e83afb791

2018-10-30T12:19:26.182Z - info: Login successful to host for source VC, IP: vm01.cpsi.local:443

2018-10-30T12:19:26.183Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

2018-10-30T12:19:26.183Z - info: Source VC, version: 6.5.0, isOSLinux: true

2018-10-30T12:19:26.184Z - debug: isIp: 192.168.0.102: true

2018-10-30T12:19:26.185Z - debug: getVmWithIPFQDN: hostName 192.168.0.102 is associated with [ '192.168.0.102' ]

2018-10-30T12:19:26.254Z - debug: token:undefined, length:3, running total:3

2018-10-30T12:19:26.255Z - error: No VM found with hostname 192.168.0.102

2018-10-30T12:19:26.255Z - error: Error in getting VM: vm01.cpsi.local ,Error: [object Object]

2018-10-30T12:19:26.255Z - error: Failed to read the nodetype, Error: No VM found with hostname 192.168.0.102

2018-10-30T12:19:26.255Z - error: The source specified does not manage source VC, source host= vm01.cpsi.local ,error:[object Object]

2018-10-30T12:19:30.023Z - info: Log file was saved at: C:\Users\Francis\Downloads\installer-20181030-131745581.log

2018-10-30T12:20:02.030Z - debug: Source Host IP address in DOM input value is: 192.168.0.106

2018-10-30T12:20:02.030Z - debug: Source Host IP Value in data model is: 192.168.0.106

2018-10-30T12:20:02.031Z - debug: Source Host IP Value in data model after correction is: 192.168.0.106

2018-10-30T12:20:02.136Z - info: THUMBPRINT(vCenterAppliance): 09:5D:E2:F8:54:DC:46:1D:9A:A6:3A:29:A3:8D:4C:13:EF:7B:B4:3A

2018-10-30T12:20:02.158Z - info: THUMBPRINT(esxiHost): 9C:3E:A7:ED:C9:07:8A:EE:DF:A4:99:CD:96:15:46:A7:D7:92:14:E2

2018-10-30T12:20:03.083Z - info: attemptHttpsConnToSourceVc

2018-10-30T12:20:03.121Z - info: login() to source VC:192.168.0.102

2018-10-30T12:20:03.122Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:20:03.942Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:20:03.963Z - debug: session exists: 192.168.0.102, administrator@vsphere.local, 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:20:03.979Z - info: successfully logged out from 192.168.0.102, administrator@vsphere.local, 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:20:03.979Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:20:04.030Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:20:04.030Z - debug: Logging in to 192.168.0.102:443 as administrator@vsphere.local

2018-10-30T12:20:04.135Z - info: Logged in to 192.168.0.102:443 as administrator@vsphere.local, session: 5288c16a-5e21-7905-26cc-f9b0424b5a11

2018-10-30T12:20:04.136Z - info: Login successful to source VC, IP: 192.168.0.102

2018-10-30T12:20:04.136Z - info: login() to host managing the source VC:192.168.0.106

2018-10-30T12:20:04.137Z - info: initializing vsphere API connection to 192.168.0.106:443

2018-10-30T12:20:05.021Z - info: vimService apiType: HostAgent, version: 6.5.0

2018-10-30T12:20:05.077Z - debug: session does not exist: 192.168.0.106, root

2018-10-30T12:20:05.077Z - debug: Logging in to 192.168.0.106:443 as root

2018-10-30T12:20:05.160Z - info: Logged in to 192.168.0.106:443 as root, session: 52a61557-5c65-44a6-fa15-99b77b4fb0b8

2018-10-30T12:20:05.161Z - info: Login successful to host for source VC, IP: 192.168.0.106:443

2018-10-30T12:20:05.161Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

2018-10-30T12:20:05.161Z - info: Source VC, version: 6.5.0, isOSLinux: true

2018-10-30T12:20:05.161Z - debug: isIp: 192.168.0.102: true

2018-10-30T12:20:05.161Z - debug: getVmWithIPFQDN: hostName 192.168.0.102 is associated with [ '192.168.0.102' ]

2018-10-30T12:20:05.208Z - debug: token:undefined, length:3, running total:3

2018-10-30T12:20:05.208Z - error: No VM found with hostname 192.168.0.102

2018-10-30T12:20:05.208Z - error: Error in getting VM: 192.168.0.106 ,Error: [object Object]

2018-10-30T12:20:05.208Z - error: Failed to read the nodetype, Error: No VM found with hostname 192.168.0.102

2018-10-30T12:20:05.208Z - error: The source specified does not manage source VC, source host= 192.168.0.106 ,error:[object Object]

2018-10-30T12:20:44.605Z - info: Log file was saved at: C:\Users\Francis\Downloads\installer-20181030-131745581.log

Muchas gracias.

Hello,

We've noticed an event that gets logged against almost every one of our VMs every day on about 25 minute intervals.  An event description example is " 10/30/2018, 7:29:32 AMGuest operation authentication failed for operation Delete Directory on Virtual machine <VM name>".  We think this started after upgrading vROPs from 6.7 to 7.0 as that was the only thing that changed in our environment but can't confirm.

The environment is vCenter 6.5 with  ESXi, 6.5.0, 7967591.  The VM hardware versions range from 9 to 13.  Hyperic is also loaded in vROPs but isn't set up to monitor all VMs.

Has anybody seen this to be caused by vROPs or a plugin installed in vROPs that tries to interact with VMs?  Are there additional logs we could look at to see the source of these operation attempts?  We would like to find out what is causing these operations and stop them.

Thanks in advance!

Hello,

I am having an issue where my vRO workflows fail if I attempt to perform two guest operations on a single machine at the same time.  An example of how I can recreate the issue is start a guest script workflow that loops and attempt to use the built-in get processes from guest workflow.  Below is the error.  I am using VMTools 10.1.15 on the guest and it is running Server 2016.

I have been trying to narrow this down for some time and finally narrowed it down to two ops running at once.  Is this a limitation?  I have been researching and I have not seen anyone with this specific case.  I have not discovered anything useful in the Logs (Windows, VMware, VMTools).

Thanks!

Cody

[2017-12-21 14:32:56.313] [E] Error in (Workflow:Get processes from guest / Scriptable task (item1)#8) The operation is not allowed in the current state.

[2017-12-21 14:32:56.320] [E] Workflow execution stack:

***

item: 'Get processes from guest/item1', state: 'failed', business state: 'null', exception: 'The operation is not allowed in the current state. (Workflow:Get processes from guest / Scriptable task (item1)#8)'

workflow: 'Get processes from guest' (C98080808080808080808080808080800180808001322751030482b80adf61e7c)

ESXi - VMware ESXi 6.7.0 build-10302608, 10Gb/25Gb BCM57414 card and SR-IOV enabled.  When assigning the virtual function to a VM it only providers 2 TX queus and 2 RX queues.   Is there any configuration settings needed so that VM will get 8 TX queues and 8 RX queues by default?

I've tried many combination from ESXi host level and also set the VM [ ethernetX.pnicFeatures = “4” ] inside .vmx file and both are not working.  Using ethtool -S. <device_name> to verify inside VM guest OS (ubuntu 18.04). 

Card settings:

esxcfg-module -g bnxtnet

bnxtnet enabled = 1 options = 'DRSS=4,4 RSS=4,4 max_vfs=8,8 force_hwq=8,8'

esxcli network  sriovnic list

Name    PCI Device    Driver   Link  Speed  Duplex  MAC Address         MTU  Description

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

vmnic4  0000:11:00.0  bnxtnet  Up    25000  Full    9c:dc:71:ba:9f:f0  9000  Broadcom Limited BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller

vmnic5  0000:11:00.1  bnxtnet  Up    25000  Full    9c:dc:71:ba:9f:f8  9000  Broadcom Limited BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller

[root@localhost:~] esxcli network  sriovnic vf list -n vmnic4

VF ID  Active  PCI Address     Owner World ID

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

    0   false  00000:017:02.0   -

    1   false  00000:017:02.1   -

    2   false  00000:017:02.2   -

    3   false  00000:017:02.3   -

    4   false  00000:017:02.4   -

    5   false  00000:017:02.5   -

    6   false  00000:017:02.6   -

    7   false  00000:017:02.7   -