I had a disk fail yesterday, and after the rebuild I noticed one of my datastores was missing.  I see the device but not the associated datastore.

I am running vSphere 6.5

When I run VOMA I get the following output:

[root@ESX-1:/var/log] voma -m vmfs -f check -d /vmfs/devices/disks/eui.30f9584100d00000

Checking if device is actively used by other hosts

Running VMFS Checker version 2.1 in check mode

Initializing LVM metadata, Basic Checks will be done

Phase 1: Checking VMFS header and resource files

   Detected VMFS file system (labeled:'raid') with UUID:59cd3f06-381b631f-8b26-002590707790, Version 5:81

ON-DISK ERROR: corrupted SFD address <FB c14268 r687> for resource file PB2

         ERROR: Failed to check pb2.sf.

   VOMA failed to check device : Severe corruption detected

Total Errors Found:           1

   Kindly Consult VMware Support for further assistance

Is there anyway to do a repair on the device in question?

Thanks for any help

Hi,

I have upgraded from 12.x to 14 and despite not changing anything in my configuration, the write caching is not working anymore.

I'm running 14.1.1. on a Windows 10 x64 host.

I have tried any and all the following options in my config.ini:

hard-disk.hostBuffer = "enabled"

hard-disk.useUnbuffered = "FALSE"

hard-disk.synchronous = "FALSE"

aiomgr.buffered = "TRUE"

aiomgr.unbuf = "FALSE"

Still, despite my entire VMDK being cached in RAM, the vmware-vmx process waits for I/O to complete before acknowledging it inside the VM. How can I fix this and get the old behaviour?

I depend on the I/O performance inside the VM and many of my workloads are broken without it. My system is using ECC RAM, and the entire workstation is powered by a 3KVA UPS and running a 12 disk RAID6 so I'm not at all worried about data loss. I just desperately need to disable the caching so I can upgrade to 14.x again. In the meantime, I have been forced back to Workstation 12.

i understand from tables 8.3 & 8.4 from the attached pdf snip that those ports are required for remote collection but how do they relate to table 8.5?

Analytics cluster can have data, Master & replica nodes (all 3 aka analytics nodes)

tables 8.3 & 8.4 would be for a firewall separating 2 domains with remote collector in domain #2 separated by the firewall & analytics node(s) in domain #1

so then table 8.5 applies only within the analytics domain #1 or is table 8.5 also required to open those ports between the 2 domains?

the use of data nodes in 8.3/8.4 seems clear but i do not understand how analytics nodes was used instead for 8.5 unless it refers to a VIP?

a VIP is not mentioned there so can anyone provide insight (excuse the vPun) on these tables

Hi,

I've been using USB devices on Workstation for a while and everything worked fine until recently.

I recently updated to the latest, 12.5.4 and now the USB devices don't show up in the menu anymore for any of my virtual machines. I tried to reboot the host and guest systems, check and change settings (USB 3.0 to USB 2.0 and vice-versa, check/uncheck the different checkboxes in the USB setting for each VM) as well as plugging the cards/flash drives (that used to work) on the different ports on the system (some are USB3.0, some are USB 2.0). I cannot seem to have the USB devices display in the VM->Removable devices anymore.

Before anybody point out the obvious, I checked, yes they are recognized by my host, Windows, and I can see them plugged in the system tray. Yes, the virtual machines have USB in them and the kernel is recent enough to use USB (Kali 2016.2, Ubuntu 16.04, 16.10, 17.04 alpha/beta, CentOS 7, etc). This issue is present on all my VM (that used to work just fine).

Last I remember using USB device is for sure 12.5.2. I may have used it in 12.5.3 but I'm not 100% certain.

Is there something I missed or is it a bug in the release?

System info: Windows 7 SP1 64 bit (up to date), Core i7 2630QM, 12Gb RAM

Hello - I need some help on winsql appstack creation. Can someone help ?

I only saw one other post about this and it hasn't seen any response in years, so I'll try a new thread and see if there is any luck.  I have a need to see if a particular vCenter I'm connected to is in an Enhanced Linked Mode configuration or not, can this be done via PowerCLI or via API call from PowerCLI perhaps?  Anyone know where this information is exposed that I could get to from my PowerShell script?

Hello all,

I have a -flat.vmfs file that is locked, and unable to manually unlock it. The mac address 78:ac:c0:3d:17:d6 is the same as VMNIC1 which is vswitch0 and management network.

Please help, thanks, Joseph

vmfsfilelockinfo Version 2.0

Looking for lock owners on "Domain Controller_5-flat.vmdk"

"Domain Controller_5-flat.vmdk" is locked in Exclusive mode by host having mac address ['78:ac:c0:3d:17:d6']

Trying to use information from VMFS Heartbeat

Host owning the lock on file is 192.168.5.6, lockMode : Exclusive

Total time taken : 5.1094890889944509 seconds.

No VM hosts are running on ESXI at the moment.

Have tried to break the lock and get this error.

[root@esxi:/vmfs/volumes/5a8851d9-a91eccc3-ed02-78acc03d17d6] vmkfstools -B Domain\ Controller_5-flat.vmdk

VMware ESX Question:

LVM lock on the device Domain Controller_5-flat.vmdk will be forcibly broken. See the vmkfstools or ESX documentation for information on breaking the LVM lock.

Ensure that multiple servers are not accessing this device.

Continue to break lock?

0) _Yes

1) _No

Select a number from 0-1: 0

Error breaking LVM device lock.

Error: Specified adapter, disk, partition, or named file system

does not exist, or not all filesystem extents online.

Multipathing policy "Round Robin" is configured on my datastores with two active paths. My storage guy plans to perform SAN switch migration from one vendor to another and it will be one switch at a time activity. I need to understand what will be the impact on my luns and ESXi host when they bring down one of the SAN switch and when they bring both the switch up post the activity.

Hi!

Please teach me that the way to use writable volume,

and it can be supported vmware?

I created writable volumes  by temaplate_uia_plus_profile.

But my user ask me that we wanted to be enabled VSS to only desktop and document folder.

So, I configured  folder redirection only desktop and document folder.

Is this configuration supported?

Please help me !!

Thank you.

I can't seem to find an ADMX template that works. I'm using UEM and App Volumes. Office 365 will be deployed as an App Stack and we are using Writable Volumes UIA+Profiles.

Hi there, I'm learning programming with VDDK.,but when I run the sample given by VDDK , i got the following log

zhl@ubuntu:~/vmware-vix-disklib-distrib/doc/samples/diskLib$ LD_LIBRARY_PATH=~/vmware-vix-disklib-distrib/lib64/ ./vix-disklib-sample -info -initex ~/vddk.conf -host 192.168.31.165 -user "root" -password "#Bugsf0r$" -thumb "F0:F7:CC:5C:8F:E3:58:DE:D6:58:1C:DF:E4:14:BC:F8:3F:47:FD:DE" -libdir ../../../ "[datastore1] Ubuntu/Ubuntu.vmdk"

Log: OBJLIB-LIB: Objlib initialized.

Log: VixDiskLib: Attempting to locate advanced transport module in "../../../".

Log: VixDiskLib: Advanced transport plugin ../../..//lib64/libdiskLibPlugin.so was successfully loaded into vixDiskLib.

Log: VixDiskLib: Enabling advanced transport modes.

Log: VixDiskLib: Available transport modes from DiskLib: file:nbdssl:nbd:san.

Log: VixDiskLib: Initialize transport modes.

Log: 2018-03-15T10:16:14.632+08:00 info -[7F335FA25740] [Originator@6876 sub=vm:DictionaryLoad: Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

Log: 2018-03-15T10:16:14.632+08:00 info -[7F335FA25740] [Originator@6876 sub=vm:[msg.dictionary.load.openFailed] Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

Log: 2018-03-15T10:16:14.632+08:00 info -[7F335FA25740] [Originator@6876 sub=vm:FeatureStateLib: Error while loading feature config file: /etc/vmware/vsphereFeatures/vsphereFeatures.cfg]  using default feature state values.

Log: VixDiskLib: Available transport modes: file:san:hotadd:nbdssl:nbd.

Log: VMware VixDiskLib (6.5) Release build-7387093

Log: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

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

Log: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

Log: DictionaryLoad: Cannot open file "/home/zhl/.vmware/config": No such file or directory.

Log: [msg.dictionary.load.openFailed] Cannot open file "/home/zhl/.vmware/config": No such file or directory.

Log: PREF Optional preferences file not found at /home/zhl/.vmware/config. Using default values.

Log: DictionaryLoad: Cannot open file "/home/zhl/.vmware/preferences": No such file or directory.

Log: [msg.dictionary.load.openFailed] Cannot open file "/home/zhl/.vmware/preferences": No such file or directory.

Log: PREF Optional preferences file not found at /home/zhl/.vmware/preferences. Using default values.

Log: lib/ssl: OpenSSL using FIPS_drbg for RAND

Log: lib/ssl: protocol list tls1.2

Log: lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

Log: lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

Log: VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.

Log: VixDiskLib: VixDiskLib_Connect: Establish connection.

Log: VixDiskLib: Allocate connection.

Log: VixDiskLib: Prepare remote connect.

Log: VixDiskLib: Resolve host.

Log: VixDiskLib: Load thumbprint.

Log: VixDiskLib: VixDiskLib_OpenEx: Open a disk.

Log: VixDiskLib: Open a disk with standard transport mode.

Log: VixDiskLib: Construct full path to disk.

Log: VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [datastore1] Ubuntu/Ubuntu.vmdk.

Log: VixDiskLibVim: Resolve host.

Log: VixDiskLibVim: Initialize callback data with username/passwd credential type.

Log: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

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

Log: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

Log: DictionaryLoad: Cannot open file "/home/zhl/.vmware/config": No such file or directory.

Log: [msg.dictionary.load.openFailed] Cannot open file "/home/zhl/.vmware/config": No such file or directory.

Log: PREF Optional preferences file not found at /home/zhl/.vmware/config. Using default values.

Log: DictionaryLoad: Cannot open file "/home/zhl/.vmware/preferences": No such file or directory.

Log: [msg.dictionary.load.openFailed] Cannot open file "/home/zhl/.vmware/preferences": No such file or directory.

Log: PREF Optional preferences file not found at /home/zhl/.vmware/preferences. Using default values.

Log: lib/ssl: OpenSSL using FIPS_drbg for RAND

Log: lib/ssl: protocol list tls1.2

Log: lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

Log: lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

Log: VixDiskLibVim: Connect to server.

Log: VixDiskLibVim: Login completed

Log: 2018-03-15T10:16:14.752+08:00 info -[7F335FA25740] [Originator@6876 sub=Libs] GVmomi: Instantiating VMOMI session at https://192.168.31.165:443/sdk

Log: 2018-03-15T10:16:14.752+08:00 info -[7F335FA25740] [Originator@6876 sub=Libs] GVmomi: Verifying SSL certificate with thumbprint F0:F7:CC:5C:8F:E3:58:DE:D6:58:1C:DF:E4:14:BC:F8:3F:47:FD:DE

Log: VixDiskLibVim: Callback for verifying SSL certificate.

Log: 2018-03-15T10:16:14.753+08:00 info -[7F335FA25740] [Originator@6876 sub=Libs] GVmomi: Certificate accepted

Log: VixDiskLibVim: Callback for login.

Log: VixDiskLibVim: Call appropriate TicketFind routine for type: 3.

Log: VixDiskLibVim: Logout ticket queue.

Log: VixDiskLibVim: Logout from server.

Log: 2018-03-15T10:16:15.372+08:00 info -[7F335FA25740] [Originator@6876 sub=Libs] BasicHttpOnSent: g_object_get_data returned GVMOMI_SESSION_DATA_UNLINK_VALUE session

Log: VixDiskLibVim: Clean up after logging out from server.

Log: VixDiskLibVim: Clean up callback data.

Log: VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

Log: NBD_ClientOpen: attempting to create connection to ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902

Log: [NFC DEBUG] Using username/password authentication, user=root, useSSL=0

Log: [NFC INFO] Plain-text connection is deprecated; use SSL to connect to NFC serverLog: CnxConnectAuthd: Returning false because CnxAuthdProtoConnect failed

Log: Cnx_Connect: Returning false because CnxConnectAuthd failed

Log: Cnx_Connect: Error message: 550 User not authorized for host agent contact

Warning: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: 550 User not authorized for host agent contact

Log: [NFC DEBUG] Using username/password authentication, user=root, useSSL=0

Log: [NFC INFO] Plain-text connection is deprecated; use SSL to connect to NFC serverWarning: SSL: Unknown SSL Error

Log: SSL Error: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

Warning: SSL: connect failed (1)

Log: CnxAuthdConnect: Returning false because SSL_ConnectAndVerify failed

Log: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

Log: Cnx_Connect: Returning false because CnxConnectAuthd failed

Log: Cnx_Connect: Error message: The remote host certificate has these problems:

Log:

Log: * self signed certificate in certificate chain

Warning: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: The remote host certificate has these problems:

Warning:

Warning: * self signed certificate in certificate chain

Log: NBD_ClientOpen: Couldn't connect to 192.168.31.165:902 The remote host certificate has these problems:

Log:

Log: * self signed certificate in certificate chain

Log: DISKLIB-DSCPTR: : "ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902" : Failed to open NBD extent.

Log: DISKLIB-LINK  : "ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902" : failed to open (NBD_ERR_NETWORK_CONNECT). 

Log: DISKLIB-CHAIN : "ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902" : failed to open (NBD_ERR_NETWORK_CONNECT).

Log: DISKLIB-LIB   : Failed to open 'ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).

Log: VixDiskLib: Detected DiskLib error 2338 (NBD_ERR_NETWORK_CONNECT).

Log: VixDiskLib: Failed to open disk ha-nfc://[datastore1] Ubuntu/Ubuntu.vmdk@192.168.31.165:902?root/#Bugsf0r$. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 4799.

Log: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore1] Ubuntu/Ubuntu.vmdk. Error 14009 (The server refused connection) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 5026.

Log: VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore1] Ubuntu/Ubuntu.vmdk. Error 14009 (The server refused connection) at 5064.

Error: [vixDiskLibSample.cpp:673]  36b9 The server refused connection

Log: VixDiskLib: VixDiskLib_Disconnect: Disconnect.

Log: VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.

Log: VixDiskLib: Clean up VixDiskLib.

Log: VixDiskLibVim: VixDiskLibVim_Exit: Clean up.

Log: VixDiskLib: Release socket.

When I check vSphere hostd.log, I found this:

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-134546279. Applied change to temp map.

2018-03-15T10:32:47.306Z info hostd[B481B70] [Originator@6876 sub=Solo.Vmomi opID=dc9ddd48 user=root] Activation [N5Vmomi10ActivationE:0x0af33f28] : Invoke done [waitForUpdatesEx] on [vmodl.query.PropertyCollector:ha-property-collector]

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=Solo.Vmomi opID=dc9ddd48 user=root] Arg version:

--> "1"

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=Solo.Vmomi opID=dc9ddd48 user=root] Arg options:

--> (vmodl.query.PropertyCollector.WaitOptions) {

-->    maxWaitSeconds = 300,

-->    maxObjectUpdates = <unset>

--> }

2018-03-15T10:32:47.306Z info hostd[B481B70] [Originator@6876 sub=Solo.Vmomi opID=dc9ddd48 user=root] Throw vmodl.fault.RequestCanceled

2018-03-15T10:32:47.306Z info hostd[B481B70] [Originator@6876 sub=Solo.Vmomi opID=dc9ddd48 user=root] Result:

--> (vmodl.fault.RequestCanceled) {

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

-->    faultMessage = <unset>

-->    msg = ""

--> }

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp REMOVE: sessionList["52ea0343-6a6c-315d-40ce-3213cf82d567"], ha-sessionmgr. Applied change to temp map.

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp REMOVE: latestPage[13001], session[5264d262-ab4d-d97c-d577-7020e79fb1ee]52962b73-74ca-fe8a-a6db-afa0ba60ce9c. Applied change to temp map.

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp ADD: latestPage[13011], session[5264d262-ab4d-d97c-d577-7020e79fb1ee]52962b73-74ca-fe8a-a6db-afa0ba60ce9c. Applied change to temp map.

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.

2018-03-15T10:32:47.306Z info hostd[B481B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=dc9ddd49 user=root] Event 13011 : User root@192.168.31.63 logged out (login time: Thursday, 15 March, 2018 10:32:46, number of API invocations: 0, user agent: VixDiskLib)

2018-03-15T10:32:47.306Z verbose hostd[B481B70] [Originator@6876 sub=PropertyProvider opID=dc9ddd49 user=root] RecordOp ASSIGN: info, haTask--vim.SessionManager.logout-134546279. Applied change to temp map.

my running platform is Ubuntu server 16.04 (4.4.0-87-generic).

Can someone help me . Thank you.

Hello ..

This is my first post in the group, also almost fresh in vmware.

As pert of setting up Virtual Environment (ESXi 6.5),  wee have taken one dedicated server with following IP details:-

1.2.3.4 - Management IP

1.2.3.5 - Additional IP (purchased to configure router VM)

4.5.6.7/28 (Additional Subnet, purchased to assigns VMs)

As per server provider additional subnet (4.5.6.7/28) is statically routed via 1.2.3.5. So suggested to setup a router VM with this IP: 1.2.3.5. We have only one active NIC only connected to the network.

So I would like to get your support how can I setup a router-VM and assign the IP and do other routing. How can I assigns IPs from additional subnet to new VMs. So if need to any additional configuration to assign the subnet ?

Thanks in advance ..

Regards,

Navas

表題で質問です。

Cisco Unified Communication Managerが仮想ゲストとして存在している機器があります。

ESXのホストとして監視はできており、仮想ゲストのリストも確認できてますが

監視に至っておりません。

監視マネージャーサーバからのPingの疎通もあるのですが、監視を実行する前に以下の

エラーがあり監視ができておりません。

Router cannot be monitored as virtual server

解決策などございましたら教えてください。

During an audit for unsigned processes we discovered this VMware process running that was unsigned. We are using VMware tools 10.2.0 build-7259539 in the guest (the latest) and VMware Workstation Pro 14.1.1 build-7528167 in the host (also the latest). Also what does it do?

Sigcheck v2.53 - File version and signature viewer

Copyright (C) 2004-2016 Mark Russinovich

Sysinternals - www.sysinternals.com

c:\program files\vmware\vmware tools\vmware caf\pme\bin\ManagementAgentHost.exe:

        Verified:       Unsigned

        Link date:      5:23 AM 11/30/2017

        Publisher:      n/a

        Company:        n/a

        Description:    n/a

        Product:        n/a

        Prod version:   n/a

        File version:   n/a

        MachineType:    64-bit

Hi,

I am using VMWare Workstation Player 14.1.1.

For a VM, after I remove a Hard disk from the Hardware tab, the only item from that list is removed.

The VMDK files are still present in the folder and the hard drive entries are still there in the VMX file.

Is this normal behavior or am I missing something?

I thought that when I remove a hard disk from the hardware tab, all its entries and associated files should ideally get removed.

Thanks

Hi,

I have a Dell PowerEdge R430 running Dell customized 5.5 image. My question is does it matter if I use VMware's own 6.5 ISO or Dell customized 6.5 ISO to perform the upgrade? VMware upgrade doc seems to suggest VMware's own 6.5 ISO will preserve custom Dell drivers but I am wondering if Dell customized 6.5 ISO has new or improved drivers on it which may be more suitable for the upgrade?

Thanks,

Hello

Can any one share the steps to upgrade from vCenter 6.0 to 6.5 for vCenter Server?

Hello,

in a standalone esxi 6.5, during the import of a vm via web client I stopped it, so now I have an entry in the web client that point to a vmx file that doesn't exists: in the list of virtual machines in the web client I have, as virtual machine name, the path of the vm that doen't exists and in Status field the "invalid" value.

How I can delete the entry? Is it possible?

I attach an image with 2 vm, the one invalid and one valid:

--

Regards

Hello to all here,

Today, CentOS 7.4  has updated the kernel.

When I try to start vmware, VMware Kernel Module Updater tells me,

that several modules must be compiled and loaded into the running kernel.

After that, I get a error and a hint to the log file, which I appended to this message.

Also the patch of Darius don't work any more.

(See the logs below)

Does anyone know, whats the matter?

Greetings from North Germany,

Holger

This is the log of the try to load the modules regularly:

2018-03-09T22:49:20.997+01:00| vthread-1| I125: Log for VMware Workstation pid=21793 version=14.1.1 build=build-7528167 option=Release

2018-03-09T22:49:20.997+01:00| vthread-1| I125: The process is 64-bit.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8

2018-03-09T22:49:20.997+01:00| vthread-1| I125: Host is Linux 3.10.0-693.21.1.el7.x86_64 CentOS Linux release 7.4.1708 (Core)

2018-03-09T22:49:20.997+01:00| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: DictionaryLoad: Cannot open file "/home/kaengo/.vmware/config": No such file or directory.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/kaengo/.vmware/config": No such file or directory.

2018-03-09T22:49:20.997+01:00| vthread-1| I125: PREF Optional preferences file not found at /home/kaengo/.vmware/config. Using default values.

2018-03-09T22:49:21.044+01:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-21793.log

2018-03-09T22:49:21.093+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-03-09T22:49:21.093+01:00| vthread-1| I125: Created new pathsHash.

2018-03-09T22:49:21.093+01:00| vthread-1| I125: Setting header path for 3.10.0-693.21.1.el7.x86_64 to "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include".

2018-03-09T22:49:21.093+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.093+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.093+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.093+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.109+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.109+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:21.387+01:00| vthread-1| I125: found symbol version file /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers

2018-03-09T22:49:21.387+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers.

2018-03-09T22:49:21.404+01:00| vthread-1| I125: Read 16075 symbol versions

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Reading in info for the vmmon module.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Reading in info for the vmnet module.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Reading in info for the vmblock module.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Reading in info for the vmci module.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Reading in info for the vsock module.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Setting vsock to depend on vmci.

2018-03-09T22:49:21.405+01:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-03-09T22:49:21.412+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:21.412+01:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-03-09T22:49:21.418+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:21.418+01:00| vthread-1| I125: Invoking modinfo on "vmblock".

2018-03-09T22:49:21.425+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:21.425+01:00| vthread-1| I125: Invoking modinfo on "vmci".

2018-03-09T22:49:21.432+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:21.432+01:00| vthread-1| I125: Invoking modinfo on "vsock".

2018-03-09T22:49:21.441+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-03-09T22:49:21.450+01:00| vthread-1| I125: to be installed: vmmon status: 0

2018-03-09T22:49:21.450+01:00| vthread-1| I125: to be installed: vmnet status: 0

2018-03-09T22:49:21.462+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-03-09T22:49:21.462+01:00| vthread-1| I125: Setting header path for 3.10.0-693.21.1.el7.x86_64 to "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include".

2018-03-09T22:49:21.462+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.462+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.462+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.462+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.480+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.480+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:21.743+01:00| vthread-1| I125: found symbol version file /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers

2018-03-09T22:49:21.743+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers.

2018-03-09T22:49:21.761+01:00| vthread-1| I125: Read 16075 symbol versions

2018-03-09T22:49:21.761+01:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include

2018-03-09T22:49:21.761+01:00| vthread-1| I125: Update kernel header path to /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include

2018-03-09T22:49:21.761+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.761+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.761+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.761+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.782+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.782+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:21.783+01:00| vthread-1| I125: Found compiler at "/usr/local/bin/gcc"

2018-03-09T22:49:21.793+01:00| vthread-1| I125: Got gcc version "4.9.2".

2018-03-09T22:49:21.793+01:00| vthread-1| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2018-03-09T22:49:21.805+01:00| vthread-1| I125: Got gcc version "4.9.2".

2018-03-09T22:49:21.805+01:00| vthread-1| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2018-03-09T22:49:21.808+01:00| vthread-1| I125: Trying to find a suitable PBM set for kernel "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.808+01:00| vthread-1| I125: No matching PBM set was found for kernel "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.809+01:00| vthread-1| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2018-03-09T22:49:21.809+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.809+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.809+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.809+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.826+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.826+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:21.835+01:00| vthread-1| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2018-03-09T22:49:21.835+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.835+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.835+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.835+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.853+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.853+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:21.853+01:00| vthread-1| I125: Using temp dir "/tmp".

2018-03-09T22:49:21.857+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-03-09T22:49:21.857+01:00| vthread-1| I125: Setting header path for 3.10.0-693.21.1.el7.x86_64 to "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include".

2018-03-09T22:49:21.857+01:00| vthread-1| I125: Validating path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for kernel release "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.857+01:00| vthread-1| I125: Failed to find /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h

2018-03-09T22:49:21.857+01:00| vthread-1| I125: /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-03-09T22:49:21.858+01:00| vthread-1| I125: using /usr/local/bin/gcc for preprocess check

2018-03-09T22:49:21.875+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.21.1.el7.x86_64".

2018-03-09T22:49:21.875+01:00| vthread-1| I125: The header path "/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include" for the kernel "3.10.0-693.21.1.el7.x86_64" is valid.  Whoohoo!

2018-03-09T22:49:22.211+01:00| vthread-1| I125: found symbol version file /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers

2018-03-09T22:49:22.211+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/3.10.0-693.21.1.el7.x86_64/build/Module.symvers.

2018-03-09T22:49:22.229+01:00| vthread-1| I125: Read 16075 symbol versions

2018-03-09T22:49:22.229+01:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-03-09T22:49:22.236+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:22.236+01:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-03-09T22:49:22.244+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-03-09T22:49:22.348+01:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/3.10.0-693.21.1.el7.x86_64/misc/vmmon.ko".

2018-03-09T22:49:22.348+01:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-03-09T22:49:22.390+01:00| vthread-1| I125: Successfully extracted the vmmon source.

2018-03-09T22:49:22.390+01:00| vthread-1| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-dgt1mf/vmmon-only auto-build HEADER_DIR=/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include CC=/usr/local/bin/gcc IS_GCC_3=no"

2018-03-09T22:49:22.875+01:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

2018-03-09T22:49:22.884+01:00| vthread-1| I125: Setting destination path for vmnet to "/lib/modules/3.10.0-693.21.1.el7.x86_64/misc/vmnet.ko".

2018-03-09T22:49:22.884+01:00| vthread-1| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2018-03-09T22:49:22.906+01:00| vthread-1| I125: Successfully extracted the vmnet source.

2018-03-09T22:49:22.907+01:00| vthread-1| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-dgt1mf/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.0-693.21.1.el7.x86_64/build/include CC=/usr/local/bin/gcc IS_GCC_3=no"

2018-03-09T22:49:23.430+01:00| vthread-1| W115: Failed to build vmnet.  Failed to execute the build command.

That was the try to patch Workstation 14 with the workstation 12 patch from Darius:

[root@localhost vmnet-fix]# patch -p0 < ~/Downloads/VMware-Workstation-12.5.7-vmnet-RHEL74.patch

patching file vmnet-only/compat_netdevice.h

Hunk #1 FAILED at 337.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/compat_netdevice.h.rej

[root@localhost vmnet-fix]#

After that, I tried to install workstation pro 12 ,

but I also had had no success in patching it:

[root@localhost vmnet-fix]#   cp /usr/lib/vmware/modules/source/vmnet.tar ./vmnet-12.5.7.tar

[root@localhost vmnet-fix]#  tar xf vmnet-12.5.7.tar

[root@localhost vmnet-fix]# patch -p0 < ~/Downloads/VMware-Workstation-12.5.7-vmnet-RHEL74.patch

patching file vmnet-only/compat_netdevice.h

[root@localhost vmnet-fix]#  tar cf vmnet.tar vmnet-only/

[root@localhost vmnet-fix]# cp vmnet.tar /usr/lib/vmware/modules/source/vmnet.tar

cp: overwrite ‘/usr/lib/vmware/modules/source/vmnet.tar’? y

[root@localhost vmnet-fix]# vmware-modconfig --console --install-all

Stopping vmware (via systemctl):                           [  OK  ]

Using kernel build system.

make: Entering directory `/tmp/modconfig-sS7npk/vmmon-only'

/usr/bin/make -C /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/3.10.0-693.21.1.el7.x86_64'

arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Toolchain update recommended..  Stop.

make[1]: Leaving directory `/usr/src/kernels/3.10.0-693.21.1.el7.x86_64'

make: *** [vmmon.ko] Error 2

make: Leaving directory `/tmp/modconfig-sS7npk/vmmon-only'

Using kernel build system.

make: Entering directory `/tmp/modconfig-sS7npk/vmnet-only'

/usr/bin/make -C /lib/modules/3.10.0-693.21.1.el7.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/3.10.0-693.21.1.el7.x86_64'

arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Toolchain update recommended..  Stop.

make[1]: Leaving directory `/usr/src/kernels/3.10.0-693.21.1.el7.x86_64'

make: *** [vmnet.ko] Error 2

make: Leaving directory `/tmp/modconfig-sS7npk/vmnet-only'

Unable to install all modules.  See log for details.

[root@localhost vmnet-fix]#

仮想マシンの最大ディスク待ち時間合計の色が変わったメッセージが頻繁に出ているサーバがあります。

とても遅いです。

もうしばらく使わないとならないのが問題なのですが

本日以下のようなメッセージがVM上で出てきました。

イベント詳細: 
  説明: XXXX の XXXX の XXXX の警告メッセージ: Timed out while quiescing the virtual machine. 
時刻: 2018/03/15 0:15:53

エラー スタック: 
   仮想マシンの静止中にタイムアウトになりました。

追加のイベント詳細: 
  タイプ名: VmMessageWarningEvent
VC ビルド: 2442329
ターゲット オブジェクト タイプ: ClusterComputeResource
DataCenter オブジェクト タイプ: Datacenter
ホスト オブジェクト タイプ: HostSystem
ホスト ビルド: 2456374
VirtualMachine オブジェクト タイプ: VirtualMachine
ChainId: 12190461

何か対処法がありましたらお知らせください。