[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.

Tags: VMware

Similar Questions

  • 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 7.1.2 - Linux networking questions

    I am on Windows 7 and I have a Ubuntu 10.10 I can't accept an IP address. I don't know if my question is Ubuntu configurations or VMware. I have a NETWORK adapter that is set to Custom (VMnet7) which I configured with DHCP. My goal was to implement a custom network (VMnet7) so that they can communicate without an external connection. I added Windows clients and receive DHCP addresses without problem. When I add my Ubuntu box, he does not get the IP address. I have the set eth0

    Auto eth0

    iface eth0 inet dhcp

    When I restart the network interface, he seeks an IP address by sending a DHCP request to 255.255.255.255, but never received an answer from, and finally abandoned. This machine has been downloaded from another system and pulled upwards. Any suggestions on the place where to proceed to diagnose the problem?

    -jyxavier

    I have a NETWORK adapter that is set to Custom (VMnet7) which I configured with DHCP. My goal was to implement a custom network (VMnet7) so that they can communicate without an external connection.

    FWIW VMware Desktop products already have defined VMnet1 for host only then why the need to create a host only VMnet7?

    Make sure that the client's network card is verified connected.

    What Linux Distro do you use?

    If the suggestion of sflanders does not then archive and attach the vmware.log for this virtual machine files and join a response message.

  • How to solve the problem of VMWare Workstation 8 - unable to open/dev/vmmon

    Initially, I had this problem in March 2011 after installing VMWare Workstation 7 on a lab machine 5.7 RHEL and attempt to boot an image I know was good and should work. .  Someone else fixed the problem for me - I think they had to install a new/different libraries (vmmon.o and vmnet.o for vmware).  However, I find no information detailing what has been done to solve the problem.

    I see the same error on the same machine after upgrading to VMWare Workstation 7.0 for VMWare Workstation 8.0.

    1 here are the mistakes I see:

    a. "Could not open/dev/vmmon.

    b. "failed to initialize the surveillance apparatus.
    c. "cannot change the power state of VM: cannot find a valid peers to connect to.

    Also, when I run the stop etc/init.d/vmware, then run /etc/init.d/vmware start, I see that the State of "Virtual Machine Monitor" is DOWN.


    2 here is the information on VMWare Workstation:

    VMWare Workstation 8.0.1 build 528992

    3 here is the RHEL uname - information for the host:

    2.6.18 - 274.7.1.el5xen Linux #1 SMP xxx.xxx.xxx kills Oct 17 12:06:22 EDT 2011 x86_64 x86_64 GNU/Linux
    Release of RedHat Enterprise Linux Server 5.7 (Tikanga)

    The problem could be that the version of vmmon.o and vmnet.o that comes by default with vmware does not work with linux kernel version I have on my system.  I think I need to build a new vmmon.o and vmnet.o on my particular 5.7 RHEL.

    I found that to build a new version of vmmon.o you Executive vmware - config.pl.  I have not just on my machine, and I was not able to find on the internet.

    Here is the version of vmmon.o (for RHEL 5) that I have installed on my machine:
    /usr/lib/VMware/modules/binary/BLD-2.6.18-8.EL5-x86_64smp-RHEL5/objects/vmmon.o

    Here is the version of rhel5 I use:
    2.6.18 - 274.12.1.el5xen
    It is possible that the vmmon.o using bld - 2.6.18 - 8.el5 - x86_64smp-RHEL5 is not compatible with the kernel 2.6.18 - I 274.12.1.el5xen.

    Please help me find vmware - config.pl so I can build my own vmmon.o and vmnet.o

    do not use a kernel XEN enabled when you install Workstation

  • VMware Workstation Player does not start on Fedora 23

    I've recently updated to Fedora 22 23 Fedora and can no longer run VMware Workstation 12.0.1 Player.

    I tried to uninstall the component using sudo vmware-Installer - components uninstall = vmware-player and then put it back, nothing will do. The installation is always successful, but when I try to run the application, it runs for a little while, then give up. I tried to uninstall it remove once again the previous configuration, but it still doesn't work.

    I am running

    Workstation Fedora 23

    Linux kernel 4.2.6 - 300.fc23.x86_64

    3.18.1 GNOME release

    I got it working by following this link: http://rglinuxtech.com/?p=1624

    It's a very simple solution. Basically, you just copy the libraries that are not in the directory of vmware.

    As root, run the following commands:

    # cd /usr/lib/vmware/lib
    # cp -afv /usr/lib64/libgio-2.0.so.0.4600.2 libgio-2.0.so.0/libgio-2.0.so.0
    # cp -afv /usr/lib64/libglib-2.0.so.0.4600.2 libglib-2.0.so.0/libglib-2.0.so.0
    # cp -afv /usr/lib64/libgmodule-2.0.so.0.4600.2 libgmodule-2.0.so.0/libgmodule-2.0.so.0
    # cp -afv /usr/lib64/libgobject-2.0.so.0.4600.2 libgobject-2.0.so.0/libgobject-2.0.so.0
    # cp -afv /usr/lib64/libgthread-2.0.so.0.4600.2 libgthread-2.0.so.0/libgthread-2.0.so.0
    

    Although I have not yet tested all virtual machines, this has at least the operational programme. It should solve the problem entirely. If for some reason vmware is not installed in/usr/lib/vmware, just replace the directory there. If you are unsure, running vmware whereis should tell you.

    Edit:

    I can say that this solution was able to load my virtual machines with great success. I don't need to reinstall VMWare on one of the boxes of Fedora, however (and removing the configuration files), but after that, it worked fine.

  • ESX 4 in Workstation 7.0 on Linux - networking issues

    Hi all

    I hope someone can help me to debug / identifying a problem that I'm etting ESX 4 working in VMWare Workstation 7.0 on Linux (on Ubuntu 9.04 and 9.10, both have the same problem for me).

    ESX 4.0 installs well inside a virtual machine, with the guest operating system 'Server ESX 4.0' value, but after startup, IP & DHCP packets do not work for the ESX 4 comments system.  tcpdump inside the prompt shows arp traffic and broadcast traffic for the entire LAN segment.  ESXi 4 works successfully, with DHCP/ICMP/vSwitch communications all works well.  I tested on

    The system configuration:

    • Host machine: Intel i7 920, 6 GB memory, Ubuntu 9.04.  IP: 192.168.1.54

    • Comments: ESX4.0 build 164009. IP: 192.168.1.243

    Machine in ESX 4 comments:

    vswif0 Link encap HWaddr 00:50:56:4E:6 B: D1

    INET addr:192.168.1.243 Bcast:192.168.1.255 mask: 255.255.255.0

    RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

    Fall of RX packets: 12662 errors: 0:0 overruns: 0 frame: 0

    Dropped packets TX: 56 errors: 0:0 overruns: 0 carrier: 0

    collisions: 0 txqueuelen:1000

    Bytes RX bytes: 791139 (772,5 KiB) TX: 8052 (7.8KiB)

    # tcpdump nni - vswif0

    tcpdump: removed verbose output, use - v or - vv for complete protocol decoding

    listening on vswif0, type EN10MB (Ethernet) link, capture size 96 bytes

    22:14:22.850036 00:18:51:aa:19:22 > ff: ff: ff: ff: ff: ff, ethertype ARP (0 x 0806), length 60: arp who-has 192.168.1.160 tell 192.168.1.43

    22:14:23.951134 00: 1 c: 10:5f:25:87 > ff: ff: ff: ff: ff: ff, ethertype ARP (0 x 0806), length 60: arp who-has 192.168.1.160 tell 192.168.1.4

    Host (Ubuntu 9.04):

    You can see the ARP response on the host machine and the ICMP echo request, but

    no response.  inside the machine of ESX4 tcpdump shows that the arp request/reply but

    no ICMP unicast echo request.

    arp - a - n root@I7:~# | grep 192.168.1.243

    ? (192.168.1.243) to 00:50:56:4e:6 b: d1 on eth0

    11:49:37.376389 00:24:8 c: 56:d9:a0 > ff: ff: ff: ff: ff: ff, ethertype ARP (0 x 0806), length 42: arp who-has 192.168.1.243 tell 192.168.1.54

    11:49:37.376604 00:50:56:4e:6 b: d1 > 00:24:8 c: 56:d9:a0, ethertype ARP (0 x 0806), length 60: East of the arp 192.168.1.243 - 00:50:56:4e:6 b answer: d1

    00:24:8 c 11:49:37.376617: 56:d9:a0 > 00:50:56:4e:6 b: d1, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags |) DF |, proto ICMP (1), length 84) 192.168.1.54 > 192.168.1.243: ICMP echo request, id 8551, seq 1, length 64

    00:24:8 c 11:49:38.371782: 56:d9:a0 > 00:50:56:4e:6 b: d1, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags |) DF |, proto ICMP (1), length 84) 192.168.1.54 > 192.168.1.243: ICMP echo request, id 8551, seq 2, length 64

    I'm sitting on this during a while hoping for an update of the kernel or ESX more late build could

    fix my problem, but I had no luck.  Last night, I tried ESX4.0 on

    Workstation 7 on Windows 7 and has worked successfully for comments <>- lan

    communications.  Frustrating, ESXi done work on this platform/configuration, but I want to evaluate some software that only works on ESX4.0.

    I havn't been able find someone else with my symptoms, so

    I hope one of you skilled experts can help me debug this or provide a

    suggestion on what he could be wrong.

    Thanks in advance,

    Chris

    You have configured the virtual network devices on the Linux host to allow the "Promiscuous" mode?  See 287 KB.

  • Guest OS VMware Workstation with NAT cannot communicate with the host

    I often run VMware Workstation on an Ubuntu Linux box and the load of virtual machines inside.

    The default is to configure a network card for the NAT, but that NEVER works, I have never no connectivity to the physical network in my guest operating system until I have change the type of the virtual machine network adapter for bridged.

    However, when I install ESXi 4.1 as a VM bridged, he can see the physical network, but VMs decked inside it can not...  I think that if I am NAT to work he'd let me withdraw my guest as oses nested inside BONE that is a host... If this is meaningless to anyone at all network connectivity prompt.

    I could really use help figure this.  I was hitting my head for weeks and led to nothing.

    If you do not know which IP address to use in the case of NAT, I recommend you temporarily enable DHCP on the Windows 7 host and then run "ipconfig/all" to see what it looks like. To configure the IP settings manually, make a note of the settings and set the IP address of one outside the range NAT NETWORK.

    André

  • 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...

  • 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.

  • 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.

  • 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!

  • 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

  • VMware Workstation 6.5.3 2.6.31 kernel + patches in real time

    I'm using Arch Linux as a host with kernel 2.6.31. Workstation 6.5.3 install and compile modules very well without tasks. However if I apply the fixes in real-time modules only compile and install. VMware Workstation works with linux + realtime patches to the kernel? Y at - there a patch available to get the modules to compile?

    Please try this patch

  • Problem with configure vmware workstation 6.5 with Ubuntu 9.04 64 bit latest kernel

    for the Intel-driving problem, I installed a new kernel for Jaunty.

    Normally, if you change the kernel, need new VMWARE-Workstation, but it does not work.

    I'm getting the following answer

    vmware sudo

    Login to /tmp/vmware-root/setup-26435.log

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    ModInfo: vmmon module is not found

    ModInfo: module vmnet is not found

    ModInfo: module vmblock is not found

    ModInfo: vmci module is not found

    ModInfo: vsock module is not found

    Stopping VMware services:

    Virtual machine communication interface is

    Virtual machine monitor makes

    File system is blocking

    Using 2.6.x kernel build system.

    do: enter the directory ' / tmp/vmware-root/modules/vmmon-only '.

    do /lib/modules/2.6.31-999-generic/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of

    make [1]: Entering directory ' / usr/src/linux-headers-2.6.31-999-generic'

    CC /tmp/vmware-root/modules/vmmon-only/linux/driver.o

    In file included from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:31:

    /tmp/vmware-root/modules/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.

    include/Linux/poll.h:67: error: previous declaration of 'poll_initwait' is here

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.

    /tmp/vmware-root/modules/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.

    make [2]: * /tmp/vmware-root/modules/vmmon-only/linux/driver.o error 1

    make [1]: * error 2

    make [1]: leaving directory ' / usr/src/linux-headers-2.6.31-999-generic'

    make: * http://vmmon.ko error 2

    make: leaving directory ' / tmp/vmware-root/modules/vmmon-only '.

    and the SETUP LOG

    Juli 28 19:20:55.486: app | Journal for VMware Workstation pid = 24193 version 6.5.2 = build = build-156735 option = output

    Juli 28 19:20:55.486: app | Host codepage = UTF-8 encoding = UTF-8

    Juli 28 19:20:55.486: app | Login to /tmp/vmware-root/setup-24193.log

    Juli 28 19:20:56.550: app | Extract the sources of the vmmon module.

    Juli 28 19:20:56.600: app | Module construction with the command: / usr/bin/make

    C - / tmp/vmware-root/modules/vmmon-only self-build SUPPORT_SMP = 1

    HEADER_DIR=/lib/modules/2.6.31-999-generic/build/include

    CC = / usr/bin/gcc = GREP / usr/bin/make IS_GCC_3 = no VMCCVER = 4.3.3

    and a box with this

    Error

    Failed to build the kernel module.

    Check the log file

    Does anyone know a Solution?

    Thank you

    Greetings

    Stefan

    -


    Computer laptop D830 DELL
    V9.04 Ubuntu Jaunty 64 bit


    Latest Version of VMWare Workstation

    -


    < / div >

    If you want to use the latest kernels that you should look for patches to update - look at this forum to find the last.

    http://communities.VMware.com/thread/221724?TSTART=0

    ___________________________________

    VMX-settings- VMware-liveCD - VM-infirmary

  • 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.

Maybe you are looking for