We are trial running App Volumes / Instant clones.  Is it possible to setup multiple pools with different memory / # of cores per pool based off the same image / snapshot, or do we need to have a new image per pool?

Thanks in Advanced

Dear all

hi

has anyone install veealize oracle enterprise managment pack for vrops????

(this is for bluemedora)

BR

babak

Hi All,

I have VRA 7.2 and want to enable custom email from VRO. Can someone please let me know the payload definition that i can get the VM owner email address. I am able to get the IP,VM name and resources but not able to get the email address.

Thanks

Parag 

Version 0.9.8 is available on our Fling site: download the file plugin-seed-0.9.8.zip. The 3 main changes are:

• Includes the new Javascript API bootstrap introduced with HTML SDK 6.5.u1
• Large refactoring of services and components to use Observables as a better pattern
• End-to-end tests for the plugin running in vSphere Client

See the attached change-log for the full list of changes. 

You can also compare all source changes since 0.9.7 with the file version-0.9.8.diff included with the new version.

VMworld 2017 attendees:  don't miss our workshop ELW181107U  Sunday 27th from 1:30 to 3 pm (*), where we will go through a new hands-on-lab using plugin-seed. You'll be able to ask any question to Vladimir and myself!   For others the same hands-on-lab using plugin-seed should be available soon after VMworld.

(*) FYI, it was initially scheduled Monday 2 to 3:30 pm but was moved to Sunday recently. 

Im trying to install a certificate into ESXi using the web browser but the key I'm pasting isn't working.  I'm not sure if it's an issue with the ESXi host or with the key.  The error message I'm receiving is:

Key 

haTask--vim.host.CertificateManager.installServerCertificate-138780645

Description 

Installs a server certificate for the host

State 

  Failed  - Cannot change the host configuration. 

Errors

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

And that's it

*The purpose of me installing this cert is so that I can use SSH auth via PowerCLI. 

Please help!

Dear all

Hi

i user vrops 6.6 i download this Vsx

and want monitor weblogic services add this apk and just can not do Configuring Server Object Credentials can any one help me fo solve this?

BR

Hi, I am not able to start any of my VMs today but everything was working just fine yesterday. This morning I tried to open up one of my VM's and got "Unable to retrieve kernel symbols" and it won't start up at all.

I've tried all of the other solutions offered in the past but none seem to work for me this time. Has anyone else ran into this issue on Sierra and Fusion 8?

Thanks

Hi All,

(ESXi 6.0. standlone)

I have a Windows Server 2012 VM that Im trying to setup via script.

This VM has 4 Network Adapters: VM Network, Something0, Something1, Application.

The OVA is deployed and then the VM is sysprepped before initial login.

Once logged in, I look at the network adapters in Windows and see 4 adapters, each with a name "Ethernet #". The placement of the Virtual NIC -> Windows NIC seems to be different each time, presumably because of sysprep.

Via script, Im can rename and enable the VMware Virtual Adapters to their specific portgroup and StartConnected,

but Im not sure how to map the corresponding VMware Adapters that I rename with the default "Ethernet #" Windows adapters

Any help would be greatly appreciated

Thank you

Can VMWare coexist simultaneously with HYPER-V on the same host machine and at the same time?

Regards,

Hello All-

I am doing some research for my eventual migration from my current Windows based vCenter 5.5 to the 6.5 VCSA.  My question is in regards to the networking once the migration has occurred.

I am planning to migrate the Windows vCenter 5.5 server to an ESX host that has a "Management Network" VMKernel Port on the same network as the 5.5 vCenter server (for example 10.6.2.x, same network that my ESX hosts reside on).  Currently I have 3 vSwitches.  The management network is on it's own vSwitch, then a vSwitch for Vmotion and another vSwitch for VM's.  When I migrate and create that 6.5 VCSA on the ESX host, I'm confused on how I will be able to set it up on the 10.6.2.x network because as a VM, I will only have the option of choosing one of my VM networks during the migration correct?  My management network won't show up for me to add the new 6.5 VCSA to during the migration, right?

Can I simply create another virtual machine port group on the vSwitch with the management network assigned to it?  Bascially, I'm trying to figure out how to get my new 6.5 VCSA into the correct subnet (10.6.2.x) when all my VM's are on a different, production VM network - not the management network.

Hope this makes sense.  Thank you.

Hi,

I'm looking for a little advice regarding a vCenter upgrade from 6.0 U3b to 6.5. Our architecture comprises of two VCSA servers, both with their own external PSC. They were deployed in the following order:

1) PSC1
2) VCSA1
3) PSC2 (setting PSC1 as the replication partner).

4) VCSA2

From the recommended topologies from , ours is closest to this:

although technically, it's more like this:

What I can't recall is how exactly these are setup with regard to single sign on, primarily because I've found the documentation confusing (they are configured to work against Active Directory for signing in, but I don't remember if this was done on both PSC nodes or just the primary and then it replicated that data).

They were all deployed via the command line, using JSON files for the configuration. 'vsphere.local' was specified for the 'domain-name', and 'Default-First-Site' was specified for the 'site-name' for *all* 4 servers. As I understand it, this would make them all part of the same site.

Documentation seems to suggest upgrading the PSCs first. So would that be upgrading PSC1 and then PSC2? I'd assume that upgrading PSC1 would break the replication between PSC1 and PSC2, until PSC2 was upgraded also?

After this, I would look to upgrade VCSA1 and then VCSA2.

Can anyone else confirm whether this would be the correct approach?

Thank you.

Cross posting here as I am not getting very far in the vRO community Change Owner with Request a catalog resource action fails with 400 Bad Request .  Just curious if anyone can verify for me that trying to change owner of a deployment using the Library/vRealize Automation/Requests/Request a resource action workflow is functioning for them in 7.3 .  I have two environments and I can't get it to work in either.  Works fine from the gui.  Using the embedded vRO.  Tested in both a clustered and simple install.  Both fail identically.

Hello,

I'm looking for a way to upgrade the hosts in a non-HA cluster where each host has a single VM and the VMs are dependent on the rest of the VMs in the cluster, such that only a single VM (i.e. host) can be down at a time. The VMs are part of a HA product that can't be failed over at the vmware level because each VM has persisted data that is required to maintain proper functionality (like a vSAN cluster). We need to update hosts sequentially (again, like a vSAN cluster) and after a VM comes up, we need some amount of time before the next host can be taken down. Is there an API (or a way to invoke a script that we supply) that would allow the hosts (or VUM) to query the VMs and see if they're "ready" to be taken down?

Thanks,

Kevin

I see no items in the "Requests" folder in the vRA plugin inventory for 7.3... The user I am logged in with has full visibility to pretty much everything in vRA and I have also tried configuring a vRA server connection with that same user separate from what got setup during installation.  I still see nothing.  Are these in some other portion of the inventory now?  I'm wondering if this is somehow related to my previous post today hitting issues with executing an owner change for the deployment.

Have an old iMac and got a new one.

Old one runs windows 2000, windows 7 and windows 10.

Installed VMware fusion 8.5. (Old machine has version 7+.)

Wanted to migrate the virtual machine bundles but had difficulty locating them, and when I did they were greyed out.

(The bundles didn't turn up when I tried to view them via ethernet...although other files were there.)

So I copied the bundles put them on the desktop of the new machine. Not greyed out on desktop.

Still greyed out in fusion (import...choose an existing file).

I'm sure there is a discussion on this issue. So excuse me not finding it yet.

Thanks for your attention to this matter.

Good afternoon,

I have a development workstation VM that was running when my Host machine experienced a problem (memory module went bad) and unexpectedly hard reset yesterday.  I have restarted the VM a couple of times since then.  Is there any possibility that the data is still stored somewhere?

I am using VMWare Workstation 12 Pro version 12.5.7 build=5813279

Cory

After upgrade to Windows 10 Creators Update 1703 on the host, guests can no longer access host's network shares using SMB network protocol through host-only or NAT IPs.

[TLDR - steps to try to reproduce this -> Access local host network shares using IP address of the VMNet interfaces from either host or guest OS]

This was working ok on previous Win10 version 1607.

VMware Workstation version is 12.5.7 build-5813279 (upgraded from 12.5.6 after Win10 went from 1607 to 1703 few days ago)

After some troubleshooting, it appears that host server is not listening for incoming connections on ports 137,138 UDP and TCP 139 using IP addresses of the VMNet1 (host only) and VMNet8 (NAT) networks.

It's only listening on IP address of Ethernet/LAN/Physical interface.

Assuming 192.168.1.10 is host's Ethernet connection and 192.168.5.1 and 192.168.123.1 are host's VMNet1 and VMNet8 IP addresses respectively, trying to show network shares (either from host cmd prompt, or from guest gives the same result):

> net view \\192.168.1.10

shows host shares, while:

> net view \\192.168.5.1

gives error:

System error 53 has occurred.

The network path was not found.

Listing open (LISTEN) ports on the host is only showing binding to Ethernet IP address, and not VMNet* addresses

> netstat -an |findstr ":139"

  TCP    192.168.1.10:139       0.0.0.0:0              LISTENING

Testing on another computer that still has not been upgraded to Creators Update and all is well there, host is listening for and accepting network traffic on Ethernet and on VMNet* IP addresses, and guests can access host's shares.

Things I have tried already:

- windows firewall on host appears to be configured correctly and ping host from guest is working
- checked that all 4 vmware autostart services are running

- restored defaults in Virtual Network Editor

- restarted win10 several times after installing latest workstation version

- disabled and enabled VMware Virtual Ethernet adapters several times

None of this has helped so far.

Has anyone else experienced something similar?

After upgrade to Windows 10 Creators Update 1703 on the host, guests can no longer access host's network shares using SMB network protocol through host-only or NAT IPs.

[TLDR - steps to try to reproduce this -> Access local host network shares using IP address of the VMNet interfaces from either host or guest OS]

This was working ok on previous Win10 version 1607.
VMware Workstation version is 12.5.7 build-5813279 (upgraded from 12.5.6 after Win10 went from 1607 to 1703 few days ago)

After some troubleshooting, it appears that host server is not listening for incoming connections on ports 137,138 UDP and TCP 139 using IP addresses of the VMNet1 (host only) and VMNet8 (NAT) networks.
It's only listening on IP address of Ethernet/LAN/Physical interface.

Assuming 192.168.1.10 is host's Ethernet connection and 192.168.5.1 and 192.168.123.1 are host's VMNet1 and VMNet8 IP addresses respectively, trying to show network shares (either from host cmd prompt, or from guest give same results):

> net view \\192.168.1.10
shows host shares, while:

> net view \\192.168.5.1
gives error:
System error 53 has occurred.
The network path was not found.

Listing open (LISTEN) ports on the host is only showing binding to Ethernet IP address
> netstat -an |findstr ":139"
  TCP    192.168.1.10:139       0.0.0.0:0              LISTENING

Testing on another computer that still has not been upgraded to Creators Update and all is well there, host is listening for and accepting network traffic on Ethernet and on VMNet* IP addresses, and guests can access host's shares.

Things I have tried already:
- checked that all 4 vmware services are running
- restored defaults in Virtual Network Editor
- restarted win10 several times after installing latest workstation version
- disabled and enabled VMware Virtual Ethernet adapters several times
None of this has helped so far.

Has anyone else experienced something similar?

I'm having an issue where I am not able to log into the Control Center nor am I able to log into the Appliance config page.

I know the user ID and password for both (stored in a password manager) and i've logged in many times before.  It's been 5 months since I last logged in but now I can't.  Odd right?

I've followed the steps outlined in KB2136326 with no luck.

Anyone else run into the same issue, if so, what was the solution for you?

Thanks

Greeting,
but a few times it happens that I get a blue screen on the server machine vm Server2016. Below I will show you a log and images to try to help tosolve the problem...

LOG file:

2017-01-24T07:17:28.586Z| vcpu-9| I125: E1000: e1000e-- tx queue 1 is enabled.

2017-01-24T07:17:37.758Z| vcpu-7| I125: E1000: e1000e-- tx queue 1 is enabled.

2017-01-24T07:18:19.830Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:18:19.830Z| vcpu-9| W115: GuestRpc: application toolbox-dnd, changing channel 65535 -> 1

2017-01-24T07:18:19.830Z| vcpu-9| I125: GuestRpc: Channel 1, guest application toolbox-dnd.

2017-01-24T07:18:19.833Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:18:20.676Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:18:24.025Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:18:56.854Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:11.291Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:13.751Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:17.248Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:38.090Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:43.737Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:44.470Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:49.434Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:19:58.792Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:20:01.759Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:20:02.823Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:20:06.128Z| vcpu-12| I125: Guest: vsep: AUDIT: VFileFltPostOpCreate : File (\Users\TEMP.SIMIMPEX\AppData\Local\Microsoft\Vault\4BF4C442-9B8A-41A0-B380-DD4A704DDB28\Policy.vpol) in a transaction, ignore

2017-01-24T07:20:08.227Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:20:13.373Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:20:25.588Z| vcpu-16| I125: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

2017-01-24T07:20:58.994Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:21:30.085Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:22:30.078Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:22:34.577Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:23:00.099Z| vmx| I125: GuestRpc: Got error for channel 4 connection 766517: Remote disconnected

2017-01-24T07:23:10.655Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:24:09.976Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:24:39.372Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:24:43.640Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:24:56.953Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:25:00.600Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:25:03.433Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:25:12.770Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:12.770Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:12.785Z| vcpu-14| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:12.785Z| vcpu-14| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:12.832Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:12.832Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:13.082Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:13.082Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:43.789Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:43.789Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:25:47.842Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:26:14.706Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:26:44.564Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.564Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.564Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.564Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.564Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.564Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-17| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-17| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-18| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:44.565Z| vcpu-18| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:49.580Z| vcpu-14| I125: GuestMsg: Too many channels opened.

2017-01-24T07:26:49.580Z| vcpu-14| I125: GuestMsg: Too many channels opened.

2017-01-24T07:27:00.379Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:27:44.714Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:27:44.714Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:27:49.013Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:28:19.424Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:28:43.548Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:29:02.088Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:29:16.692Z| vcpu-7| I125: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

2017-01-24T07:29:16.785Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.785Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.800Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.800Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.895Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.895Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.973Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:16.973Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.051Z| vcpu-9| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.051Z| vcpu-9| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.098Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.098Z| vcpu-23| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.129Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.129Z| vcpu-2| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.160Z| vcpu-8| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.160Z| vcpu-8| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.191Z| vcpu-15| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.191Z| vcpu-15| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.207Z| vcpu-1| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.207Z| vcpu-1| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.222Z| vcpu-13| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.222Z| vcpu-13| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.347Z| vcpu-17| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.348Z| vcpu-17| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.441Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.441Z| vcpu-3| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.488Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.488Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.676Z| vcpu-10| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.676Z| vcpu-10| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.691Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.691Z| vcpu-7| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.960Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:17.960Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:18.053Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:18.053Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:29:41.197Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:29:46.288Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:31:08.349Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:31:30.878Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:32:04.153Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:32:04.153Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:32:08.201Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:32:24.210Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:33:09.663Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:33:28.132Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:33:34.727Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:33:34.727Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:33:34.727Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:33:34.727Z| vcpu-19| I125: GuestMsg: Too many channels opened.

2017-01-24T07:33:49.147Z| vcpu-8| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:33:49.147Z| vcpu-8| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:33:58.769Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:34:04.142Z| vcpu-4| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:34:04.142Z| vcpu-4| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:35:17.636Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:35:49.154Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:35:49.154Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:36:04.154Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:36:04.154Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:37:49.147Z| vcpu-6| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:37:49.147Z| vcpu-6| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:38:09.080Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:39:49.161Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:39:49.161Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:40:32.271Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:40:35.613Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:41:35.577Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:42:21.137Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:42:21.137Z| vcpu-22| I125: GuestMsg: Too many channels opened.

2017-01-24T07:42:26.664Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:42:26.664Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:42:35.611Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:42:49.151Z| vcpu-18| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:42:49.151Z| vcpu-18| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:43:04.149Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:43:04.149Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:43:24.328Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:45:27.889Z| vcpu-9| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:27.889Z| vcpu-9| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.123Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.123Z| vcpu-4| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.263Z| vcpu-16| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.263Z| vcpu-16| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.497Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.497Z| vcpu-20| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.732Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:28.732Z| vcpu-21| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:29.030Z| vcpu-11| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:29.030Z| vcpu-11| I125: GuestMsg: Too many channels opened.

2017-01-24T07:45:49.157Z| vcpu-1| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:45:49.157Z| vcpu-1| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T07:46:29.897Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:47:02.054Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:49:54.086Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:50:52.264Z| vcpu-3| I125: GuestRpc: Channel conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 1

2017-01-24T07:50:54.042Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:51:54.053Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:52:54.062Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:53:54.064Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:54:54.108Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:55:54.111Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:56:54.084Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:57:54.088Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:58:22.326Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T07:58:41.241Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:58:54.091Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T07:59:04.154Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T07:59:04.154Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T08:03:04.152Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T08:03:04.152Z| vcpu-13| I125: GuestMsg: channel 4: wrong cookie, discarding message.

2017-01-24T08:03:49.151Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T08:03:49.151Z| vcpu-3| I125: GuestMsg: channel 2: wrong cookie, discarding message.

2017-01-24T08:05:57.889Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2017-01-24T08:08:58.722Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

2017-01-24T08:12:19.968Z| vmx| I125: Guest: toolbox-dnd: Version: build-4449150

Pictures:

HOST

VM

Hi,

VMware Workstation 12.5.7 kernel module updater fails to compile virtual network device on linux (RHEL7) host. Unable to start services. Error log:

2017-08-04T15:34:55.675-10:00| vthread-4| I125: Log for VMware Workstation pid=26404 version=12.5.7 build=build-5813279 option=Release

2017-08-04T15:34:55.675-10:00| vthread-4| I125: The process is 64-bit.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2017-08-04T15:34:55.675-10:00| vthread-4| I125: Host is Linux 3.10.0-693.el7.x86_64 Red Hat Enterprise Linux Workstation release 7.4 (Maipo)

2017-08-04T15:34:55.674-10:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-08-04T15:34:55.674-10:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/marek/.vmware/config": No such file or directory.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: PREF Optional preferences file not found at /home/marek/.vmware/config. Using default values.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: PREF Unable to check permissions for preferences file.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/marek/.vmware/preferences": No such file or directory.

2017-08-04T15:34:55.675-10:00| vthread-4| I125: PREF Failed to load user preferences.

2017-08-04T15:34:55.678-10:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-26404.log

2017-08-04T15:34:55.687-10:00| vthread-4| I125: Obtaining info using the running kernel.

2017-08-04T15:34:55.687-10:00| vthread-4| I125: Created new pathsHash.

2017-08-04T15:34:55.687-10:00| vthread-4| I125: Setting header path for 3.10.0-693.el7.x86_64 to "/lib/modules/3.10.0-693.el7.x86_64/build/include".

2017-08-04T15:34:55.687-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:55.687-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:55.687-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:55.687-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:55.693-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:55.694-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:55.897-10:00| vthread-4| I125: found symbol version file /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers

2017-08-04T15:34:55.897-10:00| vthread-4| I125: Reading symbol versions from /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Read 16054 symbol versions

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Reading in info for the vmmon module.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Reading in info for the vmnet module.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Reading in info for the vmblock module.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Reading in info for the vmci module.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Reading in info for the vsock module.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Setting vsock to depend on vmci.

2017-08-04T15:34:55.921-10:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-08-04T15:34:55.923-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-08-04T15:34:55.923-10:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-08-04T15:34:55.924-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-08-04T15:34:55.924-10:00| vthread-4| I125: Invoking modinfo on "vmblock".

2017-08-04T15:34:55.926-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-08-04T15:34:55.926-10:00| vthread-4| I125: Invoking modinfo on "vmci".

2017-08-04T15:34:55.927-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-08-04T15:34:55.927-10:00| vthread-4| I125: Invoking modinfo on "vsock".

2017-08-04T15:34:55.929-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-08-04T15:34:55.937-10:00| vthread-4| I125: to be installed: vmnet status: 0

2017-08-04T15:34:55.947-10:00| vthread-4| I125: Obtaining info using the running kernel.

2017-08-04T15:34:55.947-10:00| vthread-4| I125: Setting header path for 3.10.0-693.el7.x86_64 to "/lib/modules/3.10.0-693.el7.x86_64/build/include".

2017-08-04T15:34:55.947-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:55.947-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:55.947-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:55.947-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:55.952-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:55.952-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:56.078-10:00| vthread-4| I125: found symbol version file /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers

2017-08-04T15:34:56.078-10:00| vthread-4| I125: Reading symbol versions from /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers.

2017-08-04T15:34:56.092-10:00| vthread-4| I125: Read 16054 symbol versions

2017-08-04T15:34:56.092-10:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/3.10.0-693.el7.x86_64/build/include

2017-08-04T15:34:56.092-10:00| vthread-4| I125: Update kernel header path to /lib/modules/3.10.0-693.el7.x86_64/build/include

2017-08-04T15:34:56.092-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.092-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:56.092-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:56.092-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:56.098-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.098-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:56.099-10:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"

2017-08-04T15:34:56.102-10:00| vthread-4| I125: Got gcc version "4.8.5".

2017-08-04T15:34:56.102-10:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-08-04T15:34:56.102-10:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".

2017-08-04T15:34:56.104-10:00| vthread-4| I125: Got gcc version "4.8.5".

2017-08-04T15:34:56.104-10:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-08-04T15:34:56.105-10:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.105-10:00| vthread-4| I125: No matching PBM set was found for kernel "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.105-10:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-08-04T15:34:56.105-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.105-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:56.105-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:56.105-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:56.111-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.111-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:56.112-10:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-08-04T15:34:56.112-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.112-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:56.112-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:56.112-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:56.117-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.117-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:56.117-10:00| vthread-4| I125: Using temp dir "/tmp".

2017-08-04T15:34:56.118-10:00| vthread-4| I125: Obtaining info using the running kernel.

2017-08-04T15:34:56.118-10:00| vthread-4| I125: Setting header path for 3.10.0-693.el7.x86_64 to "/lib/modules/3.10.0-693.el7.x86_64/build/include".

2017-08-04T15:34:56.118-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.118-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:34:56.118-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:34:56.118-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:34:56.123-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:34:56.123-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:34:56.246-10:00| vthread-4| I125: found symbol version file /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers

2017-08-04T15:34:56.246-10:00| vthread-4| I125: Reading symbol versions from /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers.

2017-08-04T15:34:56.260-10:00| vthread-4| I125: Read 16054 symbol versions

2017-08-04T15:34:56.260-10:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-08-04T15:34:56.262-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-08-04T15:34:56.430-10:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/3.10.0-693.el7.x86_64/misc/vmnet.ko".

2017-08-04T15:34:56.430-10:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2017-08-04T15:34:56.436-10:00| vthread-4| I125: Successfully extracted the vmnet source.

2017-08-04T15:34:56.437-10:00| vthread-4| I125: Building module with command "/usr/bin/make -j12 -C /tmp/modconfig-KMc5lV/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.0-693.el7.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-08-04T15:34:57.627-10:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

2017-08-04T15:37:18.351-10:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-08-04T15:37:18.351-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:37:18.351-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:37:18.351-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:37:18.351-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:37:18.366-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:37:18.366-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:37:18.367-10:00| vthread-4| I125: Using temp dir "/tmp".

2017-08-04T15:37:18.368-10:00| vthread-4| I125: Obtaining info using the running kernel.

2017-08-04T15:37:18.368-10:00| vthread-4| I125: Setting header path for 3.10.0-693.el7.x86_64 to "/lib/modules/3.10.0-693.el7.x86_64/build/include".

2017-08-04T15:37:18.368-10:00| vthread-4| I125: Validating path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for kernel release "3.10.0-693.el7.x86_64".

2017-08-04T15:37:18.368-10:00| vthread-4| I125: Failed to find /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h

2017-08-04T15:37:18.368-10:00| vthread-4| I125: /lib/modules/3.10.0-693.el7.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-08-04T15:37:18.368-10:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-08-04T15:37:18.382-10:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "3.10.0-693.el7.x86_64".

2017-08-04T15:37:18.382-10:00| vthread-4| I125: The header path "/lib/modules/3.10.0-693.el7.x86_64/build/include" for the kernel "3.10.0-693.el7.x86_64" is valid.  Whoohoo!

2017-08-04T15:37:18.565-10:00| vthread-4| I125: found symbol version file /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers

2017-08-04T15:37:18.565-10:00| vthread-4| I125: Reading symbol versions from /lib/modules/3.10.0-693.el7.x86_64/build/Module.symvers.

2017-08-04T15:37:18.592-10:00| vthread-4| I125: Read 16054 symbol versions

2017-08-04T15:37:18.592-10:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-08-04T15:37:18.595-10:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-08-04T15:37:18.812-10:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/3.10.0-693.el7.x86_64/misc/vmnet.ko".

2017-08-04T15:37:18.812-10:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2017-08-04T15:37:18.822-10:00| vthread-4| I125: Successfully extracted the vmnet source.

2017-08-04T15:37:18.822-10:00| vthread-4| I125: Building module with command "/usr/bin/make -j12 -C /tmp/modconfig-6BiJQy/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.0-693.el7.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-08-04T15:37:20.063-10:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

Any advise would be very welcome,

Marek

---------

VMware workstation:

# vmware -v

VMware Workstation 12.5.7 build-5813279

(did try version 12.5.0 as well I used to have working on older kernel before new system install)

Host:

Red Hat Enterprise Linux 7 workstation

# uname -r

3.10.0-693.el7.x86_64