Kickstart: linux + vmware workstation 8?

Hello!

Im getting a kickstart for Linux guests with vmware workstation 8.

is there a howto or whoever did this?

concerning

Lars

I'm not immeaditally aware of anyone doing this. I guess you are using a Red Hat based for this distribution? If so, you will want to install the development tools (the kernel headers and gcc and friends). Installation of WS should be done some time in the section cusomization of scripts of the kickstart file. If RIP you in the installer of WS, you will find the flags that will reduce the amount of questions asked (and if you dig enough deep to eliminate questions). Start the installer of linux WS help section to find the minimum set of afroementioned of the flag of questions. I would like to know how it goes... looks like fun

Tags: VMware

Similar Questions

VMWare Workstation - clone an image but not the OS license?

I have Windows 7 and 2008 and images Linux VMWare Workstation fully licensed, with additional products installed and configured with data for a demonstration complex. I can't give a partner (that is outside my company) because I don't have a license for redistribution of OS, so I was wondering if it is possible to make a sort of clone of my image into an image VMWare the BP prepared as fully licensed, without crushing for example the Windows license info , so not a clone of bit for bit full. For Linux, I think I could make rsync between two images, but how can I do this on Windows with its registry etc. ?

first to clone then boot from a cloned image & changes made again a clone

_________________________________

Good luck!

It is the answer to your query. Be sure to mark the response, which helps others.

VMWare Workstation 12 and 18 of Linux Mint (Ubuntu 16.04) and vmware tools or open-vmware-tools

I created a new virtual machine using VMWare Workstation 12.1.1 build-3770994 with a guest OS from Linux Mint 18 (which is built on top of Ubuntu 16.04). I have two monitors on my system, the two 2560 x 1440. I am unable to get this virtual machine Linux Mint 18 to cover all of my two monitors when I disable "Accelerate 3D graphics" in my vm settings, I get an error. I have another Linux Mint 17 VM running on the same VMWare Workstation 12 on the same host machine from Windows 10 and it is able to expand on my two monitors very well with "Accelerate 3D graphics" disabled, but he does not open-vmware-tools.
I have read instructions telling me to install open-vm-Tools-Office in this guest operating system of Linux Mint 18. I did it. Then I restart the guest operating system. When starting, I can click on 'Enter full screen mode' in my menu of VMWare Workstation, and the guest OS has a monitor as expected. When I then click on "Cycle multiple monitors", I get the following error. "The virtual machine could not be changed to the selected screen layout. If you add a monitor to the host computer, you must turn off and turn on the virtual machine to use this monitor. »
I can optimize my VM to automatic adjustment, only one of my two screens, but not both. I tried to uninstall and reinstall open-vm-tools, open-vm-tools-desktop and restart. I tried to use /vmware-tools-distrib/vmware-install.pl's original vmware tools and who does not work either.
In my vmware.log, I get these two lines that occur when I get the above error.
2016 07-12 T 15: 43:19.068 - 06:00 | MKS | I125: ToolsSetDisplayTopology: send rpcMsg = 1 DisplayTopology_Set, 0 0 2560 1440
2016 07-12 T 15: 43:24.768 - 06:00 | MKS | I125: ToolsSetDisplayTopology: rpcMsg sending = DisplayTopology_Set 2, 0 0 2560 1440, 2560 0 2560 1440
2016 07-12 T 15: 43:24.853 - 06:00 | vCPU-1 | I125: TOOLS of the call to DisplayTopology_Set failed.
When I activate "Accelerate 3D graphics" with the configuration described above, I am able to use both of my monitors. Why is this the case?
I think remember having to disable "Accelerate 3D graphics" in my Linux Mint 17 comments vm because it would crash randomly. I try to run this VM Linux Mint 18 with 3D acceleration and see if it crashes, but why is there a difference with spanning multiple monitors?
Thank you.

I didn't experience this problem for a few weeks. I don't have a definitive answer to my original problem.

I installed Mate instead of cinnamon 3 to my MINT 18. Then, I created a new VM with Ubuntu Gnome 3 16.04 running as the OF. I did have problems with both approaches. I also tried using Firefox as my main browser instead of Chrome, as I read that Chrome can have problems of memory. It could be a combination of several of these changes that have allowed me to work without problems.

Knowing what I know now, I think the move away from cinnamon 3 is what seems to have fixed my problems. I can certainly say that you use Firefox consumes less memory, as I can monitor the monitor system under Ubuntu. Chrome would eventually eat all my system memory, that I could see. The extent of the why? I'm not sure at this point.

6u2 ESXi host nested on VMware Workstation for Linux referee v12

Hello all, I have
I have a lab environment virtual running in VMware Workstation for Linux v12, and my ESXi hosts do not work correctly on one of the virtual networks. All my troubleshooting suggests a problem with nested ESXi hosts that may be a bug, but I want to assure you that I did everything properly first. That's why I post here with the hope that if I made a mistake that maybe someone else can point out he me.
Physical system
8 core Intel Xeon 2.1 GHz CPU
128 GB of RAM
OS - kernel Linux 64 - bit w/3.19.0-32-generic Linux Mint 17.3 (fully updated from this announcement)
VMware Workstation 12 Pro - 12.1.1. Build-3770994 (fully updated from this announcement)
Nested ESXi host VM
ESXi v6.0.0 (Build 3825889, completely updated from this announcement)
4 cards 'physical' (only 3 used for now)
-all use the e1000 NIC hardware virtual, but also tried vmxnet3 NIC with no difference
-vSwitch0 use vmnic0 & 1 vmnet16 of virtual network in a pair of active / standby
-vSwitch1 uses vmnic2 on network virtual vmnet18
-vmk0 used for management on vSwitch0 and vmk1 for iSCSI on vSwitch1
-"Promiscuous" mode and forged passes enabled on all Port vSwitch groups (activating or turning off these features makes no difference)
Test performed until now
I checked that all the IP addresses and network masks used are correct.
With the help of vmkping I ping other nodes on the network vmnet16 with success.
With the help of vmkping I tried to ping the other nodes in the network vmnet18, but that has failed.
I have depolyed other non - ESXi VMs on the vmnet18 network, and they are able to ping each other, but are unable to ping or ping by the ESXI host.
I tried various material virtual NIC as mentioned before, but without changes in the results.
I tried to use only local network instead of the vmnet18 guest network segments with no change in results.
When I find out the status of the network adapters on the ESXi host through vCenter or host incorporated client vmnic0 & 1 time display network information, but vmnic2 shows no networks. Yet, I know that there is a network with different VM communicate on it. Moreover, I was able to get all of this work on a Windows system running 10 Workstation (this is the laptop that my employer gives me with).
Having built nested ESXi labs on different platforms as well as physical environments in the past, I'm very confused as to why I can't get this special configuration to work. At this point my gut tells me that this is probably a bug any with the nested themselves ESXi hosts. Since I can get all this work on vmnet16 including the management of ESXi hosts and the VCSA that I use, I am sure that my vSwitch configuration is correct (other than the IP address space and vmnic configurations is bascially the same). Because I can get other virtual machines to communicate over the network vmnet18 I don't see how can be a VMware Workstation for the issue physical Linux host. Is there something obvious I'm missing here? I read on the ESXi hosts nested under VMware Workstation after having known problems and bugs with networking. If anyone else has experienced this?
Thanks for any help others can provide!
Kind regards
Patrick

Well, the problem is now resolved. The problem was what covelli was trying to explain, but I couldn't because the physical host network adapters being mentioned.

The problem on the Linux host, but it was a problem of permissions with the virtual Ethernet adapters. The following article has the fix:
With the help of Ethernet virtual cards in Promiscuous Mode on a Linux host (287) | VMware KB

Even if I launched the workstation under the root user I have yet met this problem and which still makes no sense to me, but change the permissions solve the problem. I was not getting an error message on my Linux Mint and Ubuntu system, but when I tried on a second box of Linux Mint that I just got the error has been generated, and the error message was the above link it contains.

So, here's what I learned:

(1) the question has nothing to with a VMware Workstation definition that you can configure.

(2) the question has nothing to do with a physical network card.
(3) the question has nothing to do with any vmnic on the nested ESXi host.

(4) apparently virtual Ethernet adapters are not the correct permissions when created.

All you have to do to fix this is:

(1) open a terminal.

(2) run the command ' sudo chmod a + rw/dev/vmnet * "(don't forget to run this each time that you create a new virtual network).

You can also create a group, as shown in the link above and simply give this group the correct permissions. Personally, I think it's easier to just give everyone the rw permission.

I appreciate the help that others have offered. I did not understand what was asked for in previous answers because of the terms that have been used.

Patch version-1379776 VMware Workstation 10.0.1 for kernel Linux 3.14.0

Warning, inline and vmnet/filter.c corrects [Diff] 24.03.2014 - Pastebin.com
Enjoy!

Full patch: [Diff] Vmware Workstation 10.0.1 patch for Linux 3.14.0 - Pastebin.com

VMware workstation 10 has no Chinese support for linux?

I installed vmware workstation on my windows and then I got a Chinese version
then installed on my Linux box, but it was always English version
How to change the language of the vmware in linux .thx

Hi ic3sk9,

VMware Workstation for Windows supports English or Japanese and Linux only English.

Are you sure you got the Chinese

Linux - compilation of the modules in the kernel (bundle of VMware Workstation 9.0.2) against core 3.10 fails

Hey,.
I try to get VMware Workstation running on an Ubuntu 13,10 pre 9.0.2 bundle, but the kernel modules won't get compiled with the kernel 3.10.0 - 6.
Here is the log of the build scripts:

Using 2.6.x kernel build system.

do: go in Verzeichnis "/ tmp/modconfig-DQkPL0/vmnet-only.

/ usr/bin/make /lib/modules/3.10.0-6-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

MODULEBUILDDIR = modules

make [1]: Betrete Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

CC [M] /tmp/modconfig-DQkPL0/vmnet-only/driver.o

CC [M] /tmp/modconfig-DQkPL0/vmnet-only/hub.o

CC [M] /tmp/modconfig-DQkPL0/vmnet-only/userif.o

CC [M] /tmp/modconfig-DQkPL0/vmnet-only/netif.o

In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/netif.c:42:

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/netif.c:42:

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

^

/tmp/modconfig-DQkPL0/vmnet-only/Netif.c: in function 'VNetNetIf_Create ':

/tmp/modconfig-DQkPL0/vmnet-only/Netif.c:191:33: error: dereferencing pointer to incomplete type

netIf-> port.jack.procEntry-> read_proc = VNetNetIfProcRead;

^

/tmp/modconfig-DQkPL0/vmnet-only/Netif.c:192:33: error: dereferencing pointer to incomplete type

netIf-> port.jack.procEntry-> data is netIf;.

^

make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/netif.o] Fehler 1

make [2]: * Warte auf noch nicht processes going...

In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/hub.c:43:

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/driver.c:51:

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/hub.c:43:

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/driver.c:51:

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

^

/tmp/modconfig-DQkPL0/vmnet-only/hub.c: in function 'VNetHubFindHubByID ':

/tmp/modconfig-DQkPL0/vmnet-only/hub.c:132:49: warning: 'sizeof' into 'memcmp' appeal argument is the expression even as the first source. Did you provide an explicit length? [- Wsizeof - pointer-memaccess]

memcmp (idNum, currHub-> id.pvnID, sizeof idNum))) {}

^

/tmp/modconfig-DQkPL0/vmnet-only/hub.c: in function 'VNetHubAlloc ':

/tmp/modconfig-DQkPL0/vmnet-only/hub.c:315:36: warning: the argument of 'sizeof' into 'memcpy' appeal is the same type of pointer ' uint8 *' as the destination. EXPECTED "uint8" or explicit length [- Wsizeof - pointer-memaccess]

memcpy (hub-> id.pvnID, id, id sizeof);

^

/tmp/modconfig-DQkPL0/vmnet-only/hub.c:366:28: error: dereferencing pointer to incomplete type

Jack-> procEntry-> read_proc = VNetHubProcRead;

^

/tmp/modconfig-DQkPL0/vmnet-only/hub.c:367:28: error: dereferencing pointer to incomplete type

-->--> Data procEntry Jack is jack.;

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/userif.c:46:

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

^

In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

from /tmp/modconfig-DQkPL0/vmnet-only/userif.c:46:

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

^

make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/hub.o] Fehler 1

/tmp/modconfig-DQkPL0/vmnet-only/userif.c: in function 'VNetUserIfIoctl ':

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/userif.c:810:7: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE(VNET_NOTIFY_VERSION == 5);

^

/tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

^

/tmp/modconfig-DQkPL0/vmnet-only/userif.c:811:7: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

ASSERT_ON_COMPILE(ACTION_EXPORTED_VERSION == 2);

^

/tmp/modconfig-DQkPL0/vmnet-only/userif.c: in function 'VNetUserIf_Create ':

/tmp/modconfig-DQkPL0/vmnet-only/userif.c:1049:34: error: dereferencing pointer to incomplete type

userIf-> port.jack.procEntry-> read_proc = VNetUserIfProcRead;

^

/tmp/modconfig-DQkPL0/vmnet-only/userif.c:1050:34: error: dereferencing pointer to incomplete type

userIf-> port.jack.procEntry-> data = userIf.

^

make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/userif.o] Fehler 1

make [1]: * [_module_/tmp/modconfig-DQkPL0/vmnet-only] error 2

make [1]: Verlasse Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

make: * [vmnet.ko] Fehler 2

make: Verlasse Verzeichnis "/ tmp/modconfig-DQkPL0/vmnet-only.

Vmnet failed. Cannot run the command build.

Using 2.6.x kernel build system.

do: go in Verzeichnis "/ tmp/modconfig-DQkPL0/vmblock-only.

/ usr/bin/make /lib/modules/3.10.0-6-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

MODULEBUILDDIR = modules

make [1]: Betrete Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/block.o

CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/control.o

CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/dentry.o

CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/file.o

/tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:38:4: warning: initialization of the [default] incompatible pointer type

.d_revalidate = DentryOpRevalidate,

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:38:4: WARNING: (near initialization for 'LinkDentryOps.d_revalidate') [default]

/tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':

/tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:104:7: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a [default] casting

return actualDentry - > d_op-> d_revalidate (actualDentry, nd);

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:104:7: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c: in function 'SetupProcDevice ':

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:211:4: error: implicit declaration of function 'create_proc_entry' [-Werror-implicit-function-declaration =]

controlProcEntry = create_proc_entry (VMBLOCK_CONTROL_DEVNAME,

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:211:21: warning: assignment makes pointer from integer without a cast [default]

controlProcEntry = create_proc_entry (VMBLOCK_CONTROL_DEVNAME,

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:221:20: error: dereferencing pointer to incomplete type

controlProcEntry-> proc_fops = & ControlFileOps;

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:285:9: warning: [default] incompatible pointer type assignment

name = getname (buf);

^

/tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:296:4: warning: passing argument 1 of the [default] incompatible pointer type "putname"

putname (Name);

^

In file included from include/linux/proc_fs.h:8:0,

from /tmp/modconfig-DQkPL0/vmblock-only/linux/control.c:28:

include/Linux/FS.h:2055:13: Note: expected ' struct filename *' but argument is of type ' char *'

extern void putname (struct filename * name);

^

Cc1: some warnings are treated as errors

make [2]: * [/ tmp/modconfig-DQkPL0/vmblock-only/linux/control.o] Fehler 1

make [2]: * Warte auf noch nicht processes going...

make [1]: * [_module_/tmp/modconfig DQkPL0/vmblock-only] error 2

make [1]: Verlasse Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

make: * [vmblock.ko] Fehler 2

make: Verlasse Verzeichnis "/ tmp/modconfig-DQkPL0/vmblock-only.

Vmblock failed. Cannot run the command build.

I hope that the core 3.10 will be supported with the next version of bundle.
Greetings
Thilo

There is a patch for VMWare WS 9.0.2 to play nice with 3.10 kernel here:

https://wiki.archlinux.org/index.php/VMware#3.10_kernels

Or you can wait for VMWare WS 10.0 out...

Virtual MACHINE created on VMWare Workstation for Windows - move to VMWare Workstation for Linux?

I have a bunch of VMs that I built using VMWare Workstation for Windows running on a Win2003 Server 7.1.3. The virtual machine is running Windows XP sp3. Can I move these Ubuntu VM to run under VMWare for Linux, if I buy a license for the current version or any version?
Thank you

Yes, but with some reservations. Of course, Windows and Linux use different ways to represent the paths and devices so a few changes to the virtual machine may be necessary. All that is hard coded in the configuration file .vmx depicting the paths of type Windows and device names must be changed by the GUI settings or manually edit the .vmx config file. In addition any virtual machine containing snapshots where the parentFileNameHint in the DescriptorFile of disc, so drowned in a monolithicSparse or the first measure not binary snapshot virtual hard drive, which uses a QPF (fully qualified path name), it will have to be changed. If you are unsure how to do this then I suggest a delete all snapshots before moving on to another system.

A Windows VM that fall under the WPA will in all likelihood have to be reactivated if the host CPU are not in the same class.

If you copy a Windows VM for the delivery of a copy on the source system, that you must have and or get the appropriate number of licenses and or product keys for the copy number you keep.

64-bit Linux does not work on VMware Workstation 8

I'm running an installation entirely under license of VMware Workstation 8.0.2. This forum works on a Lenovo Thinkpad T420 with 8 GB of RAM and a 160 GB SSD, so what matters. The T420 has an Intel Core i7 2.8 GHz processor. It's running Windows 7 Enterprise SP1 for 64-bit.
When I try to create a virtual machine on this machine to run RHEL 5 in 64-bit mode, I get the following error when trying to turn on the virtual machine:
When I click on the link on VMware.com, I get a utility to check the CPU on my machine. When I run this utility, it shows that my CPU is fine for the performance of the VMS 64-bit. Go figure.
Also, I rebooted and explored the BIOS. Didn't see anything obvious here to turn on to enable this.
Bottom line: I need to create a VM Linux 64-bit on this puppy, and he won't. Any ideas anyone?

Welcome to the community,

Please check the settings of the BIOS again. I'm not familiar with Lenovo systems, but "virtualization technology (VT - x)" as well as "No. Execute Disable" settings are generally in the part of the security of the configuration of the BIOS. Two of them must be enabled. After you change the any of these settings, you will need to equip completely from the cycle of the system (a simple reboot may not be enough).

If you can't find the settings, please report (attach) the latest vmware.log file of the virtual machine file to see what VMware Workstation detects.

André

[Solved] VMware Workstation 7.1.3 Linux kernel 2.6.36 patch, anyone?

A new service/bugfix VMWare Workstation was released yesterday, unfortunately even if changelog mentions vmware modules have been made compatible with recent Linux kernels, VMWare modules still won't compile under kernel 2.6.36.

Stopping VMware services:
   VMware USB Arbitrator                                   [  OK  ]
   VM communication interface socket family                [  OK  ]
   Virtual machine communication interface                 [  OK  ]
   Virtual machine monitor                                 [  OK  ]
   Blocking file system                                    [  OK  ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/2.6.36-ic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/linux-2.6.36'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
/tmp/vmware-root/modules/vmmon-only/linux/driver.c: In function ‘init_module’:
/tmp/vmware-root/modules/vmmon-only/linux/driver.c:425:15: error: ‘struct file_operations’ has no member named ‘ioctl’
make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/linux-2.6.36'
make: *** [http://vmmon.ko|http://vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Unable to install vmmon

Try this patch.

Convert the physical Linux machine with VMware Converter Standalone 4.0.1 on VMware Workstation

Hello
I work in a virtualization project, now I test and I want to test the new version of the converter, because I need to convert some Linux machines and I know that with this version is not difficult.
I do not have the ready virtual infrastructure so I test on a workstation environment. I would like to know if someone has converted a physical Linux machine to virtual and if the destination has VMware workstation 6.5. I know that this is not supported, but this does not mean that you couldn't do.
When I have to specify the type of destination, I got the error that you could see on the photo.
Please let me know if you have tested this before and you know how to solve this problem.
Thanks in advance!
See you soon

Malulas,

Welcome to the Community Forums.

To do a physical to virtual conversion, you MUST GO to ESX. It is a requirement under the guidance of the user manual.

If the virtual machine was already in ESX, you might be able to export to a workstation image while the ESX VM is powered off.

Sorry for the bad news.

Kind regards

EvilOne

VMware vExpert 2009

NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

A model of Linux wants to install VMware-Workstation - 6.5.1 - 126130.x86_64.bundle

VMware-Workstation - 6.5.1 - 126130.x86_64.bundle, shell script (application/x-script shell), 344,9 MB (361697489 bytes), location: / home/owner/Desktop
You want to try this. New to Linux.
Dual Boot Ubuntu 8.10 - 64/Windows XP Home SP3
Downloaded and it sits on the Linux desktop. 99.999% that I downloaded the right thing, just don't know how to install it on Linux.
Goal is to start on Linux and run windows programs.
Can anyone help? Thank you

Open the Gnome Terminal or any other terminal X

$ cd Desktop

$ chmod + x VMWare - xxx.bundle

$ sudo./VMWare-xxx.bundle

Try asking on irc://irc.freenode.net/ubuntu

WIN a key problem in vmware workstation, using a linux machine and a windows XP guest.

Hello
I'm using vmware workstation 6.5 on a linux kernel 2.6.27 host and I installed a windows XP as a guest, when I press the down arrow key, think the comments is a SUPER (WIN) key, how can I solve this problem?
but when I use rdesktop to connect at this prompt, key perform normally.

Without more information, it is probably related to the known bug xkeymap.keycode in my computer at the moment.

You can find a solution: HERE

Or in the Sub-forum of the workstation, just do a search for "xkeymap.keycode" or something...

I hope this helps!

Can't build the kernel Linux in VMware Workstation 7.0 modules

Hi, I have VMware Workstation 7.0 installed on a Fedora 20 x86_64 system, and I can't get past the 'install' kernel modules I looked around, but and I tried some things but none have worked. Is there anyone here who knows how to create and load the modules in the kernel for my system. The kernel is 3.13.8 - 200.fc20.x86_64 - x86_64.
Thank you

Fedora is not a host operating system support however is not officially supported and may / will this market are separate things.

I have VMware Workstation 10 running under Fedora 20 on the stock kernel however the core of 3.13.x is not yet supported on supported OS host and modules need to be patched.

VMware Workstation 7 is probably to old for work, unless you can find patches of third parties to the versions of core and WS.

VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

Hi, I faced the same problem, and now I have corrected this issue.

He was vmnet.ko, at least for me.

Here's how to solve,

You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

And then run vmware, if you fail at the first, please run again.

If so, you can run vmwre!

I hope this will help you.

Good day.

Kickstart: linux + vmware workstation 8?

Similar Questions

Maybe you are looking for