what is it, what does it do? Could not find any description in documentation

Hi all,

I've just installed UnityVSA from EMC (Version 4.0.1) in my lab with vSphere 6u2.

I've created an old fashioned VMFS-Datastore on a LUN and an NFS-Datastore on a share. Everything is working fine.

Then I created using Unisphere a Datastore for blockbased VVOLs (via iSCIS) and for filebased VVOLs (via NFS). Everything went fine in the UnityVSA.

Then I added the StorageProvider in vCenter - also this workes without error.

BUT: There are no PEs created on the vSphere.

The PEs are present on the UnityVSA (output from uemcli executed directly on the UnityVSA):

18:25:40 service@VIRT1636W2LHJW-spa spa:~> uemcli -d localhost -u admin -securePassword /stor/prov/vmware/pe show

Password:

Storage system address: localhost

Storage system port: 443

HTTPS connection

1:    ID                   = rfc4122.b835c8dd-5cc2-48d8-9bb6-4e1483c35ecf

      Name                 = nas_pe_3

      Type                 = NAS

      VMware UUID          = rfc4122.b835c8dd-5cc2-48d8-9bb6-4e1483c35ecf

      Export path          = 192.168.4.33:/rfc4122.3c70af02-00ad-4d9e-be70-16fe20fe07e7

      IP address           = 192.168.4.33

      WWN                  =

      Default SP           =

      Current SP           =

      NAS Server           = nas_1

      VMware NAS PE server = PES_1

      VVol datastore       = res_9

      Host                 =

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

2:    ID                   = rfc4122.60060160-b2ed-2021-a932-d2f0067c0253

      Name                 = scsi_pe_13

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-a932-d2f0067c0253

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:A9:32:D2:F0:06:7C:02:53

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_1

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

3:    ID                   = rfc4122.60060160-b2ed-2021-a2df-e66d9f94b2d1

      Name                 = scsi_pe_14

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-a2df-e66d9f94b2d1

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:A2:DF:E6:6D:9F:94:B2:D1

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_2

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

4:    ID                   = rfc4122.60060160-b2ed-2021-b146-73a102b508cf

      Name                 = scsi_pe_15

      Type                 = SCSI

      VMware UUID          = rfc4122.60060160-b2ed-2021-b146-73a102b508cf

      Export path          =

      IP address           =

      WWN                  = 60:06:01:60:B2:ED:20:21:B1:46:73:A1:02:B5:08:CF

      Default SP           = SPA

      Current SP           = SPA

      NAS Server           =

      VMware NAS PE server =

      VVol datastore       =

      Host                 = Host_3

      Health state         = OK (5)

      Health details       = "The protocol endpoint is operating normally. No action is required."

19:02:21 service@VIRT1636W2LHJW-spa spa:~>

Also the appropriate LUNs for the blockbased VVOLs are created and provisioned (snipplet form vmkernel.log from one of the ESXi; the iSCSI-LUNs are available via two paths):

2016-09-09T18:38:00.810Z cpu3:32925)ScsiPath: 604: Path vmhba33:C0:T3:L1023 is a VVol PE (ver:6)

2016-09-09T18:38:00.811Z cpu1:32924)ScsiPath: 604: Path vmhba33:C0:T2:L1023 is a VVol PE (ver:6)

I can create the VVOL-Datastore from vSphere Web Client, the appropriate Storage Containers (i.e. "Datastores" from UnityVSA) are presented. But as there are no PEs, the Datastores are unaccessible and show a size of 0 bytes (output from PowerCLI):

PowerCLI C:\> get-datastore vvol*

Name                               FreeSpaceGB      CapacityGB

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

vvol-nfs-vsa-1                           0,000           0,000

vvol-iscsi-vsa-1                         0,000           0,000

PowerCLI C:\>

By the way, the vvold on the ESXi ist not running, it says, that there is no VVOL-configuration.

[/etc/init.d/vvold: /etc/init.d/vvold start, called by pid 43665]

[/etc/init.d/vvold: vvold max reserve memory set to 200]

2016-09-09T20:20:15.054Z Section for VMware ESX, pid=43696, version=6.0.0, build=4192238, option=Release

------ Early init logs start --------

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGHUP handler

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGPIPE handler

2016-09-09T20:20:15.052Z info -[FFD82350] [Originator@6876 sub=Default] Successfully registered SIGTERM handler

------ Early init logs end   --------

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] Logging uses fast path: true

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] The bora/lib logs WILL be handled by VmaCore

2016-09-09T20:20:15.054Z info vvold[FFD82350] [Originator@6876 sub=Default] Initialized channel manager

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=Default] Current working directory: /var/log/vmware

2016-09-09T20:20:15.055Z info vvold[FFDC3B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE04B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE45B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=ThreadPool] Thread pool on asio: Min Io, Max Io, Min Task,

Max Task, Max Concurency: 2, 22, 2, 52, 2147483647

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFE86B70] [Originator@6876 sub=ThreadPool] Thread enlisted

2016-09-09T20:20:15.055Z info vvold[FFD82350] [Originator@6876 sub=Default] Syscommand enabled: true

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] ReaperManager Initialized

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Initalized App with config file:/etc/vmware/vvold/config.xml

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Listening on port 8090 (NOT using SSL) using version 'vvol.version.version1'.

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] Initializing SOAP tcp adapter

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Using default for nonChunkingAgents: 'VMware VI Client|VMware-client|VMware-client/3.*'

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Using default for agentsNeedingContentLength: 'VMware-client'

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default.HTTPService] Max buffered response size is 104857600 bytes

2016-09-09T20:20:15.056Z info vvold[FFD82350] [Originator@6876 sub=Default] enableChunkedResponses: true

2016-09-09T20:20:15.057Z info vvold[FFD82350] [Originator@6876 sub=Libs] UUID: Running in UW, but cannot verify vmk syscall version, giving up.

2016-09-09T20:20:15.057Z info vvold[FFD82350] [Originator@6876 sub=Libs] UUID: Valid gethostid routine. Value = A8C01704.

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=Default] Creating SOAP body handler for version 'vvol.version.version1'

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=SOAP-1] Created SOAP body handler for vvol.version.version1 (vvol/1.0)

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=Default] Creating SOAP body handler for internal version 'vvol.version.version1'

2016-09-09T20:20:15.058Z info vvold[FFD82350] [Originator@6876 sub=SOAP-2] Created SOAP body handler for vvol.version.version1 (internalvvol/1.0)

2016-09-09T20:20:15.066Z error vvold[FFD82350] [Originator@6876 sub=Default] VVold SI:main, no VVol config available, exiting

[/etc/init.d/vvold: /etc/init.d/vvold stopnomemclear, called by pid 43701]

[/etc/init.d/vvold: vvold stopped.]

[/etc/init.d/vvold: WaitVvoldToComeUp /var/run/vmware/.vmware-vvol.started created]

[/etc/init.d/vvold: vvold stopped after start!]

[/etc/init.d/vvold: /var/run/vmware/.vmware-vvol.started is not created]

[/etc/init.d/vvold: Successfully cleared vvold memory reservation]

With "esxcli storage vvol vasaprovider list" I don't get a Storage Provider listed - although it's registered in vCenter (and listed as online vie the Web Client).

Anything I should be missing, but at the moment, I don't have any idea to go further. Any help very appreciated.

Best regards,

Christian

Hello. I have a little problem. I plugged an ssd drive to my Gen8 and moved some vms to the new datastore with vcenter web client and option : move, only datastore.

Everything worked fine, perfect performance, etc.

Then I liked to move the vcente appliance (testversion) as well to the new drive. I was not sure, if I can do this also via vcenter and move options. So i connected to my esx client and went to configuration, datastore and search. There I marked the vcentre folder on the old datastore ans said moved to the other. When completed, I started the vcenter vom new datastore.

The problem is, that is seems not to be in sync with the esx. It shows me VMs running, which are not running at all. I also cannot kill the process via ssh, as there is not process runnning, only in the GUI. I also cannot move these machines.

Is there a possibility to fix this, or do I need to do a reinstall :-( Thx for help !

Just finished a fresh install of 8.10 and it is asking for the ip and login for vShield Manager?

It was my understanding from the release notes, it requires NSX now...not vShield.

From the release notes:

No Support for vShield Manager

This release of vCloud Director does not support integration with VMware vShield Manager. Existing installations that are using vShield Manager must migrate their vShield Manager installations to VMware NSX Manager before upgrading to vCloud Director 8.10. Legacy vShield Manager Edge appliances are still supported in this release, but we recommend upgrading those Edges to NSX Edges as soon as possible. For information about upgrading NSX Edges, see the vCloud Director Installation and Upgrade Guide.

It won't let me past this.

When can we expect the VMware Horizon Client for Windows 10 Mobile....waiting for the ultimate end-user-experience > VMware Horizon with Lumia 950XL and Continuum

Hi! I have VCSA 6.0 with PSC domain for example sso.vl.local. How to add custom UPN (<DNS org name>.com) to PSC domain. I do not have any active directory domain.

WBR, Valery Tyurin

Hello,

trying to configure our first Linux VDI, everything works OK except the desktop displayed in 800x600 and keymap is setup to default 'us101'.

Note that both Horizon client and the VM are localized.

Looking in the /tmp/vmware/vmware-mks-xxxx.log file, I found that those default settings are set with the vmwareblastserver process.

And it seems that the blast server launch a vnc server

It gives something like :

MKS-RemoteMgr: Loading VNC Configuration from VM config file

...

MKS-RemoteMgr: VNC Configuration: port 5900, ip "", usekey 0, keymap "/usr/lib/vmware/us"

...

DictionnaryLoad: Cannot open file "/usr/lib/vmware/vnckeymap/us": No such file or directory

...

MKS-RemoteMgr: VNC Keymap table : "/usr/lib/vmware/vnckeymap/us" is invalid or incmplete. us101 is use instead

...

Startup screen size: 800x600

Clipped screen size: 800x600

I edited vmx config file tu use and copy the keymap file from esxi host to the vm

RemoteDisplay.vnc.Keymap="fr"

RemoteDisplay.vnc.KeymapFile="/usr/lib/vmware/vnckeymap/fr"

RemoteDisplay.MaxHeight=1200

RemoteDisplay.MaxWidth=1920

and nothing changed.

Did I miss something ?

Our config :

Horizon View 6.2.2

Horizon View Agent for Linux 6.2.1

vSphere and vCenter 6.0U2

VM : Linux Xubuntu 14.04.4

How can I free up space on a particular data-store with out breaks the VM? What is unnecessary and can be deleted? I do not have any snapshots.

Hello:

We are on AppVol 2.10 and Horizon 6.1.1.  Ever since we've tried to deploy Chrome with AppVol, users that have Writable Volumes get the error "Your preferences can not be read." when opening Chrome.  If they make any changes to their Chrome profile the changes are not saved (for example, creating new Bookmarks, etc.).  There's also a popup when opening Chrome that says "Warning: Your Google Chrome settings are stored on a network drive.  This may result in slowdowns, crashes, or even loss of data.".  I'm assuming this is mainly from the Writable Volume, somehow Chrome must be seeing it as a "network location".

Is there a way to permanently resolve this?  I've looked around and so far I do not see a solution or mention of this error in relation to AppVol specifically.

Thanks.

Hi all,

Today we had a SQL that went bananas on our storage. Basically affected all VM's, when we killed the server the problem went away.

While the problem is now solved (some dev messed up), I would like to understand why SIOC or modify of disk shares had no effect.

Environment:

• ESXi 6.0 hosts running on HP BL460c Gen9 blade servers
• NetApp MetroCluster running in Active/Active over Fibre Channel (with some aggregates/datastores not being replicated)
• Datastores via NFS
• SIOC enabled with 25 ms latency setting

To begin with:

Metro storage does not support SIOC, we know. Also mixing workloads on same disks (for example CIFS shares mixed with VMware workload) or internal jobs like deduplication may affect SIOC. The point is here, the problematic VM resides on a non-replicated datastore. No dedup jobs, backup jobs, snapshots etc. were taken during problems. Still the only SIOC events we can see on datastore were: "An unmanaged I/O workload is detected on a SIOC-enabled datastore".

Problem:

When problem was on going we could see VM write latency between 10-1000 ms. Also read latency jumped. NetApp showed lower values, but had 100% drive util and back to backs.

Since we found the bully VM, we let it run and start modifying disk shares on the DB disk but nothing happened. We also capped the IOPS to 500 without any affect.

Looking at performance on the NetApp:

300-350 MB/s in write throughput

3000 IOPS

10-100 ms i write latency

15-70 ms i read latency

There are 24 physical disks backing this datastore.

Can someone with better experience please help me understand this better? I know that some questions should be directed to NetApp, but SIOC and shares are relevant I think.

Thank you.

/BL

Is anyone able to get the client integration plugin from the vcenter6 U2 iso to work in Microsoft Edge on Win 10? The plugin will install but does not seem to really be active in the Edge browser. Everytime I try to upload files to a datastore the plugin keeps downloading again. Maybe Edge is just not supported yet?

Добрый день, коллеги!

Есть статья базы знаний KB 2120539 https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2120539

В ней говорится, что при определенных описанных в статье обстоятельствах на серверах HP Proliant Gen 9 с установленным ESXi 6.0 "host fails to detect the local disk".

В пояснении говорится, что проблема связана с заменой драйвера scsi-hpsa.

Вопрос: относится ли эта проблема к локальной USB-флэшке, с которой осуществляется загрузка ESXi?

По сути HPSA драйвер - это Hewlett Packard Smart Array driver и флэшка к нему отношения не имеет, т.к. она не подключена к контроллеру Smart Array.

Но в статье написано "host fails to detect the local disk", а USB-флэшка - это локальный диск.

Задал вопрос в поддержку, но пока ответа нет.

Коллеги, может быть кто-то уже проходил эту ситуацию на практике?

Has anyone seen this error when trying to remove a replication agreement?

I have 6 PSCs in my domain and was removing some excess agreements. It seems like I am only getting this error when trying to remove agreements from a particular PSC

So I have tried every possible solution on the web, nothing works...

Kali version: 4.6.0-kali1-amd64

VMware version: VMware-Player-12.1.1-3770994.x86_64

My log file:

2016-09-12T15:57:55.525-05:00| vthread-4| I125: Log for VMware Workstation pid=6745 version=12.1.1 build=build-3770994 option=Release

2016-09-12T15:57:55.525-05:00| vthread-4| I125: The process is 64-bit.

2016-09-12T15:57:55.525-05:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2016-09-12T15:57:55.525-05:00| vthread-4| I125: Host is Linux 4.6.0-kali1-amd64 Kali GNU/Linux Rolling

2016-09-12T15:57:55.524-05:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2016-09-12T15:57:55.524-05:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2016-09-12T15:57:55.525-05:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2016-09-12T15:57:55.525-05:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2016-09-12T15:57:55.556-05:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-6745.log

2016-09-12T15:57:55.560-05:00| vthread-4| I125: Obtaining info using the running kernel.

2016-09-12T15:57:55.560-05:00| vthread-4| I125: Created new pathsHash.

2016-09-12T15:57:55.560-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

2016-09-12T15:57:55.560-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.560-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.564-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.564-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.650-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

2016-09-12T15:57:55.650-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Read 18158 symbol versions

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmmon module.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmnet module.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmblock module.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmci module.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vsock module.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Setting vsock to depend on vmci.

2016-09-12T15:57:55.662-05:00| vthread-4| I125: Invoking modinfo on "vmmon".

2016-09-12T15:57:55.664-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2016-09-12T15:57:55.664-05:00| vthread-4| I125: Invoking modinfo on "vmnet".

2016-09-12T15:57:55.665-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2016-09-12T15:57:55.665-05:00| vthread-4| I125: Invoking modinfo on "vmblock".

2016-09-12T15:57:55.665-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2016-09-12T15:57:55.665-05:00| vthread-4| I125: Invoking modinfo on "vmci".

2016-09-12T15:57:55.666-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2016-09-12T15:57:55.666-05:00| vthread-4| I125: Invoking modinfo on "vsock".

2016-09-12T15:57:55.667-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2016-09-12T15:57:55.675-05:00| vthread-4| I125: to be installed: vmnet status: 0

2016-09-12T15:57:55.680-05:00| vthread-4| I125: Obtaining info using the running kernel.

2016-09-12T15:57:55.680-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

2016-09-12T15:57:55.680-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.681-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.684-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.684-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.768-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

2016-09-12T15:57:55.768-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

2016-09-12T15:57:55.780-05:00| vthread-4| I125: Read 18158 symbol versions

2016-09-12T15:57:55.780-05:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.6.0-kali1-amd64/build/include

2016-09-12T15:57:55.780-05:00| vthread-4| I125: Update kernel header path to /lib/modules/4.6.0-kali1-amd64/build/include

2016-09-12T15:57:55.780-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.780-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.784-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.784-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.785-05:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"

2016-09-12T15:57:55.786-05:00| vthread-4| I125: Got gcc version "5.4.1".

2016-09-12T15:57:55.786-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2016-09-12T15:57:55.786-05:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".

2016-09-12T15:57:55.787-05:00| vthread-4| I125: Got gcc version "5.4.1".

2016-09-12T15:57:55.788-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2016-09-12T15:57:55.788-05:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.6.0-kali1-amd64".

2016-09-12T15:57:55.788-05:00| vthread-4| I125: No matching PBM set was found for kernel "4.6.0-kali1-amd64".

2016-09-12T15:57:55.788-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2016-09-12T15:57:55.788-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.788-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.792-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.792-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.793-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2016-09-12T15:57:55.793-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.793-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.796-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.796-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.796-05:00| vthread-4| I125: Using temp dir "/tmp".

2016-09-12T15:57:55.797-05:00| vthread-4| I125: Obtaining info using the running kernel.

2016-09-12T15:57:55.797-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

2016-09-12T15:57:55.797-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

2016-09-12T15:57:55.797-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2016-09-12T15:57:55.800-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

2016-09-12T15:57:55.800-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

2016-09-12T15:57:55.883-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

2016-09-12T15:57:55.883-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

2016-09-12T15:57:55.896-05:00| vthread-4| I125: Read 18158 symbol versions

2016-09-12T15:57:55.896-05:00| vthread-4| I125: Invoking modinfo on "vmnet".

2016-09-12T15:57:55.897-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2016-09-12T15:57:56.189-05:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.6.0-kali1-amd64/misc/vmnet.ko".

2016-09-12T15:57:56.189-05:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2016-09-12T15:57:56.191-05:00| vthread-4| I125: Successfully extracted the vmnet source.

2016-09-12T15:57:56.191-05:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-lb6BCQ/vmnet-only auto-build HEADER_DIR=/lib/modules/4.6.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2016-09-12T15:57:57.093-05:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

My Kernel headers are fine and my GCC is on version 5.4.1 also working, my only problem is "Unable to start services."

PLEASE HELP!

We are currently using App Volumes 2.11 in a DoD secure environment.  This environment requires that the McAfee HIPS (Host Intrusion Prevention System) be installed on and monitor all desktops on the network.  Recently, some DoD policies came out requiring all applications be only allowed to run from C:\Program Files or C:\Program Files (x86) locations.  This is a problem currently because pdf files will not open from an Outlook attachment using our Acrobat Pro app stack.  Is it possible to change app stacks to run from another location besides C:\SVROOT?  Also, at this time we are not using writable volumes.

Thanks!

Bryan

Hi guys,

I am looking power cli script which can find Below information for 100 esxi host

1:- Network driver details ( Name , Model)

2:- HBA driver details

3:- Netwrok driver firmware version ( Name, Model)

4:- HBA driver Firnware version

5:- multipathing policy

6:- multipathing driver detials

7:-   VID

8:-   DID

9:-  SVID

10  SDID

Regards,

Triyambak

I'm getting this error message on my laptop with vSphere Client 6.0.

On other computers it works! There are no connection errors. Please find lelow the logfile.

[        :startup :W: 1] 2016-09-12 16:21:30.042  Log for vSphere Client Launcher, pid=5636, version=6.0.0, build=build-2502222, option=release

[        :Error   :W: 1] 2016-09-12 16:21:30.073  System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

   at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)

   at Microsoft.Win32.RegistryKey.SetValue(String name, Object value, RegistryValueKind valueKind)

   at Microsoft.Win32.RegistryKey.SetValue(String name, Object value)

   at VpxClient.Program.RegisterClientMimeExtension()

[        :QuickInf:W: 8] 2016-09-12 16:22:07.856  Set the dll search path to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0

[        :QuickInf:W: 8] 2016-09-12 16:22:08.293  Load Shared DLLs: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0

[        :startup :W: 8] 2016-09-12 16:22:08.683  Log for vSphere Client, pid=5636, version=6.0.0, build=build-2502222, option=release, user=admin, url = https://192.168.188.10/sdk

[viclient:SoapTran:W: 8] 2016-09-12 16:22:09.447  Invoke 1 Start RetrieveContent on ServiceInstance:ServiceInstance [192.168.188.10]. [operationID:40A62C41-00000001][Caller: VmomiSupport.VcServiceImpl.InitializeTransport]

[viclient:SrvMsg  :W: 8] 2016-09-12 16:22:10.742  RMI Request Vmomi.ServiceInstance.RetrieveContent - 1

[viclient:Critical:P:13] 2016-09-12 16:22:51.879  Connection State[192.168.188.10]: Connected

[viclient:SoapTran:W: 8] 2016-09-12 16:22:51.879  Invoke 1 Finish RetrieveContent on ServiceInstance:ServiceInstance [192.168.188.10] - Serial:1.277, Server:041.129 [ERROR]

VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)

System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

   --- End of inner exception stack trace ---

   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])

   at Vmomi.ServiceInstance.RetrieveContent()

   at VmomiSupport.VcServiceImpl.InitializeTransport(ConnectionSpec)

   at VpxClient.UI.InitializeVimClient(Dictionary`2, String[])

   at VpxClient.UI.StartUpIfNotMultiVcSecure(Dictionary`2, SecureString, String[], LoginEventHandler, String, List`1)

...

   at System.Reflection.RuntimeMethodInfo.Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)

   at VpxClient.Login.VIClientObj.LateCall(String, Object[])

   at VpxClient.Login.VIClientObj.StartUpOrGetMultiVcInfo(Dictionary`2, SecureString, String[], List`1)

   at VpxClient.Login.ClientAppObject.Startup(Dictionary`2, PasswordString, RunMode)

[viclient:Error   :W: 8] 2016-09-12 16:22:51.895  RMI Error Vmomi.ServiceInstance.RetrieveContent - 1

<Error type="VirtualInfrastructure.Exceptions.RequestTimedOut">

  <Message>The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)</Message>

  <InnerException type="System.Net.WebException">

    <Message>The command has timed out as the remote server is taking too long to respond.</Message>

    <Status>Timeout</Status>

  </InnerException>

  <Title>Connection Error</Title>

  <InvocationInfo type="VirtualInfrastructure.MethodInvocationInfoImpl">

    <StackTrace type="System.Diagnostics.StackTrace">

      <FrameCount>12</FrameCount>

    </StackTrace>

    <MethodName>Vmomi.ServiceInstance.RetrieveContent</MethodName>

    <Target type="ManagedObject">ServiceInstance:ServiceInstance [192.168.188.10]</Target>

  </InvocationInfo>

  <WebExceptionStatus>Timeout</WebExceptionStatus>

  <SocketError>Success</SocketError>

</Error>

[        :ShowExcp:W: 8] 2016-09-12 16:22:51.895  Connection Error: The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)

VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)

   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)

   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)

   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)

   at Vmomi.ServiceInstance.RetrieveContent()

   at VmomiSupport.VcServiceImpl.InitializeTransport(ConnectionSpec cnxSpec)

   at VpxClient.UI.InitializeVimClient(Dictionary`2 specMap, String[] arguments)

   at VpxClient.UI.StartUpIfNotMultiVcSecure(Dictionary`2 specMap, SecureString password, String[] arguments, LoginEventHandler handler, String dllPath, List`1 listOfVcUrls)

System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

   --- End of inner exception stack trace ---

[        :QuickInf:W: 8] 2016-09-12 16:23:01.770  VIC #0 End.

[        :QuickInf:W: 8] 2016-09-12 16:23:01.770  CientAppObject.CleanUp...

[        :Critical:W: 8] 2016-09-12 16:23:01.770  ShutdownClient

[viclient:Critical:W: 8] 2016-09-12 16:23:01.770  Connection State[192.168.188.10]: Disconnected

[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770  Attempting graceful shutdown of service ...

[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770  Pending Invocation Count: 0

[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770  Graceful shutdown of service: Success

[        :QuickInf:W: 8] 2016-09-12 16:23:01.785  CientAppObject.CleanUpDone...

[        :QuickInf:W: 8] 2016-09-12 16:23:01.785  Scheduling delayed unload for AppDomain VIC #0

Hello all, I've developed an "Intelligent" shutdown / startup script using PowerShell for my setup. I've come across an issue where VMs that power down after vCenter has been powered off will have a duplicate VM on two different hosts, when powering up depending on which VM is started there will be a slew of problems usually identified by the VM having an APIPA address, and the other VM NICs giving an invalid configuration error when attempting to Connect the NICs.

Overview of the setup:

ESXi 5.5

3 Nutanix blocks

12 total ESXi hosts

DRS rules in place for several VMs (the VMs that power off after vCenter has been powered off are in DRS)

High Availability enabled

70-100 VMs

The script powers the VMs off using the PowerCLI command, then enters a loop checking for a Powered Off state with PowerCLI.

Power off has to be done in this order:

Secondary VMs

vCenter

SQL

Domain Controllers

The issue only seems to happen on the VMs powered off after vCenter.

The reading I've done makes mention of HA being a possible culprit; when shutting down in the same order manually this issue does not arise.

The VMs in question will also display a question when attempting to power them on (copied / moved / cancel).

The vCenter database is housed on SQL.

Hope my thoughts aren't too unorganized, any and all help is appreciated!

Good Morning,

I have a few pools that when recomposed with new 7.0 agent, they are getting stuck in the customizing state.  The odd part is when i go look at teh desktop it shows it powered off.  Once i manually power it on it finishes the customize state and then becomes available.  Any ideas what's going on since the upgrade??  Any help is appreciated.  Thanks 

I know in the release notes of 6.1 the following defect was fixed.
243524 -

• Enable TLS 1.2 and disable TLS 1.0 for external port access

However our scans show :

port 443

TLS v1.2 is not enabled on this port.

It also looks like openssl 0.9.8 is the SSL layer and that's incompatible with tls 1.2!

So does anyone have a clue how to force this port to use TSL 1.2?