Skip to main content

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7

When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7:
error: ‘struct net_device’ has no member named ‘trans_start’;
did you mean ‘mem_start’?
    dev->trans_start = jiffies;

This seems to be an already encountered problem:
I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies;
+ netif_trans_update(dev);

I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 

On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.



Comments

  1. Many thanks. Applied updates and found several things messed up afterward. After taking hours to find the cause of my being unable to logon to the system, and fixing that, I found that (among other things remaining to fix such as regressions in updated code) VMWare Player also was broken again with Linux kernel 4.7. You saved me hours more of time working through that myself.

    ReplyDelete
  2. Thank you for posting that. Would have taken me hours to fix it - maybe I would have ditched vmware instead finally from my system. Great!
    BTW: Since vmware creates a temporary folder to compile that stuff, it's obvious that you have to update the tar file.
    For me "tar uvf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only/netif.c" did the trick.

    BR
    J. Gritsch

    ReplyDelete
  3. If you are using Workstation 12.5.2, you need this change instead, in file vmnet-only/compat_netdevice.h:
    - #define compat_netif_trans_update(d) do { (d)->trans_start = jiffies; } while (0)
    + #define compat_netif_trans_update(d) do { netif_trans_update(d); } while (0)

    ReplyDelete
  4. Thank you! I encountered this issue using CENTOS 7, kernel 3.10.0, VMWare Player 7.1.4.

    I applied the fix to netif.c mentioned in this article as follows, just in case there are people who aren't super familiar with the process:

    cd /usr/lib/vmware/modules/source
    tar xvf vmnet.tar

    Open the offending file in the text editor:

    gedit vmnet-only/netif.c

    In the text editor, change line 468 from:

    dev->trans_start = jiffies;

    to

    netif_trans_update(dev);

    Repackage the tar file:

    tar cvf vmnet.tar vmnet-only

    Remove the untarred directory:

    rm -fr vmnet-only

    Now restart VMware Player as usual, it should compile.

    ReplyDelete

Post a Comment

Popular posts from this blog

vmware libz libfontconfig libexpat

Archlinux - Kernel 4.11 - VMWare workstation 12.5.7 With this combination, when I launch "vmware", despite the fact I already "export VMWARE_USE_SHIPPED_LIBS=force", I get those lines:

Unable to load libfontconfig.so.1. /usr/lib/vmware/lib/libz.so.1/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/libpng16.so.16) Unable to load libfontconfig.so.1 from /usr/lib/vmware/lib/libfontconfig.so.1/libfontconfig.so.1: libexpat.so.0: cannot open shared object file: No such file or directory Unable to load dependencies for /usr/lib/vmware/lib/libvmware-modconfig.so/libvmware-modconfig.so
In order to workaround, I decided to get the things to the maximum: Add all shipped libraries in the LD_LIBRARY_PATH.

So I created my custom launcher of "vmware" and this is the content:

#!/bin/bash
export VMWARE_USE_SHIPPED_LIBS=force
LD_LIBRARY_PATH=""
LD_LIBRARY_PATH=$( find /usr/lib/vmware/lib/ -maxdepth 1 -mindepth 1 -type d | awk 'BEGIN{p=&quo…

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…