Sommergibili www kernel modules

Similar Questions

• Smart TPM D30 Linux kernel module?

  Seems that Linux does not recognize the TPM chip. There no module for it in the Linux kernel? I thought D30 supports RHEL6?

  Manufacturer: LENOVO
  Product name: 422916G
  Version: ThinkStation D30
  BIOS version: 0.37

  Sorry for the noise. The problem is resolved. You need to install the kernel-modules-extras package for the tpm_tis kernel module

• How to compile and install the kernel modules after nation and nipalk for installation of Gentoo 64 bit?

  We are trying to install a PCIe 6251 DAQ card in a box of Gentoo 64 bit running Linux kernel 2.6.28 - gentoo-r5 4.3.2 - gcc and glibc - 2.8.  We have installed RPM utilities to manage the installation.  The current problem is that we are not able to compile and install the kernel modules: nidmxfk, nimsdrk, nimstsk and nipxirmk.  Here's a summary of what we have done so far, and to what extent we got.

  First of all, we have changed the configuration of the kernel that we could export the init_mm unused symbol by changing the configuration option of the CONFIG_UNUSED_SYMBOLS = o kernel and recompile the kernel.  Then we installed LabView 8.6.1.  Then we ran the nation 1.9 installer who has installed the source code in vain on the compilation.  To resolve this problem, we have changed the function of pte_offset to pte_offset_kernel by editing the file/usr/local/natinst/nation/configures following the instructions here:

  http://decibel.NI.com/content/docs/doc-4511

  We were then able to compile and install the kernel nation module thanks to:

  . / configure
  do
  make install

  lsmod said that nation has been properly installed.  Then we ran the installer for DAQmx 8.0.1 by:

  . / INSTALL - nodeps

  To do this, we have received errors indicating that LabView support could not be installed because check addictive (incorrectly we think) stated that labviewbase86 has not been installed; This caused the installer to have an abortion.  Therefore, we refused to install support for LabView 8.6 and revived the installation program which produces the output:

  Installation of the driver NOR-DAQmx Distribution of Linux Installer version 8.0.1f0...

  Already to jump Edward - 1.9.0 - f0.noarch.rpm installation, same or newer
  installed.

  Pre Installation...

  Preparing... ########################################### [100%]
  1:nitimingi ########################################### [ 4%]
  2:nipalki ########################################### [ 7%]
  3:nipali ########################################### [ 11%]
  RC0.d directory not found, startup script is not accredited with init levels.
  4:labview80 - rte # [14%]
  5:ni653x ########################################### [ 18%]
  6:nicdigi ########################################### [ 21%]
  7:nidaqmxcapiexmp # [25%]
  8:nidaqmxcapihelp # [29%]
  9:nidaqmxcapii # [32%]
  LN: create the symbolic link ' / usr/local/include/NIDAQmx.h': no such file or directory
  10:nidaqmxcfgi # [36%]
  11:nidaqmxef # [39%]
  12:nidaqmxhelp # [43%]
  13:nidaqmxinfi # [46%]
  14:nidaqmxswitch # [50%]
  15:nidimi ########################################### [ 54%]
  16:nidsai ########################################### [ 57%]
  17:nimdbgi ########################################### [ 61%]
  18:nimioi ########################################### [ 64%]
  19:nimru2i ########################################### [ 68%]
  20:nimxdfi ########################################### [ 71%]
  21:nimxpi ########################################### [ 75%]
  22:nimxs ########################################### [ 79%]
  RC0.d directory not found, startup script is not accredited with init levels.
  23:niorbi ########################################### [ 82%]
  24:nipxirmi ########################################### [ 86%]
  25:nirpci ########################################### [ 89%]
  26:niscarabmm # [93%]
  27:niscxi ########################################### [ 96%]
  28:nistci ########################################### [100%]

  After Installation...

  At this point, after reading this report, we used the Gentoo rc update utility to add several scripts for the boot runlevel initialisation:

  update of RC - a boot nipple
  update of RC - a bunch of nipxirmu
  update of RC - a bunch of mxssvr
  update of RC - a bunch of nisvcloc
  update of RC - a bunch of nidevldu

  When the computer reboots, you get an error message indicating that the following kernel modules are not: nidmxfk, nimsdrk, nimstsk and nipxirmk.  lsmod shows that the nation and nipalk are installed, but no other kernel modules NOR are present.  modprobe-l shows that only nation and nipalk are available.

  So we have several questions:

  1. we install drivers in the correct order?  Should use us NI-VISA 4.5 or NOR-488. 2 rather than DAQmx 8.0.1?

  2. What kernel modules should be loaded for this equipment run?  How to compile and install the ones that we have yet, specifically nidmxfk, nimsdrk, nimstsk and nipxirmk?  Are there others?

  3. How can we get the installer to properly recognize that we have installed LabView Core and install support for LabView?  Are there additional kernel modules related to the support of LabView?

  4. What is the symbolic link that was not created in the DAQmx installation report? (ln: create the symbolic link ' / usr/local/include/NIDAQmx.h': no such file or directory)?

  I apologize for so many questions, but these seem to be the last obstacles to obtaining OR runs correctly on this system.  Is there other information that we can provide that would be useful?  Thanks for any help or suggestions you can offer.

  Craig

  Hey Craig,.

  Given that you use 64-bit Linux all kernel modules must be compiled for 64 - bit.  User mode binaries can be 32-bit, assuming that you have installed the 32-bit support libraries.

  NOR-DAQmx is a complex architecture and requires several kernel modules to support your PCIe card.  Most of these kernel modules have not been brought to support 64-bit Linux.  Some kernel modules are components infrustructure that are shared with other pilots OR as NI-VISA and NOR-488. 2 and have been brought to support 64-bit Linux.  Unfortunately, you need all the modules to use your hardware.

  I hope that answers your question.

  Shawn Bohrer

  National Instruments

• [DEV] Kernel module for Open on Thinkpad Tablet TUN VPN support

  Since your rooting TPT is not a big problem now, it's time to enrich the tablet with powerful features - one of them is the support for OpenVPN. As with all other tablets based Tegra2 we have to flash a TUN/TAP on TPT kernel module. We have two choices:

  1. someone confirms that we can reuse just modules written for other tablets: like this thread for example: [Acer A500]

  2. or we need someone to write them for our tablet.

  Unfortunately, I'm not that experienced with Linux systems.

  phinpan is right. All you have to do is install tun.ko market Installer, run it, add additional details (I didin't) press on install. If she tells you, do not take into account that this module is not compatible. After using the tun.ko Installer, just download installer OpenVPN and OpenVPN market parameters. First run the OpenVPN Setup, follow the instructions and then start OpenVPN settings. It took less than 5 minutes and now I'm protected by my VPN provider.

• 12.0.0 Workstation install fails on Ubuntu Linux 16.04 (4.4.0 - 28 generic) [service failing vmmon; updated vmware kernel module]

  Hi guys,.

  I'm really excited to go with VMware Workstation on a new install of Ubuntu (16.04).  Planning watch GNS3 VMs and vagabond for Docker VMs integration among other things.  Since the two vmware workstation and linux/ubuntu are mature, I really expected that I would have any problem with the installation.

  I was a bit dismayed when the 12 workstation installation failed on a new installation of 16.04.  It seems that the VMware Kernel Module Updater step and specifically the Virtual Machine Monitor is the problem.

  Can someone help with the steps required for a successful installation of 12 Workstation on Ubuntu 16.04 please?

  Details of my attempt and a quick fix to follow.

  Please help, thanks!

  Greg

  Hi there =)

  Just for brevity, the "Monitor" is in fact what we call the hypervisor itself. We call the LCD screens "poster".

  So it's probably an incompatibility of which is just to be around the GPU kernel module, but it could have been any kernel module.

  Thanks for sharing your success!

• Failure to update the kernel Module

  I've upgraded to Ubuntu 12.04 and now I can't use VMWare Workstation anymore.  I have the version 8.0.3, but when I run I am prompted with "Before you can run VMWare, several modules must be compiled and loaded in the kernel currently running." and the possibility of 'Cancel' or 'install '.

  

  Then, I click on install and invites me my password to sudo.  When performing updates, the compilation of the "Virtual Network Device' seems to fail.

  

  Then I get an error "Unable to start services" which tells me to check a log file for more details.

  

  I enclose the log file.  Also, if that makes a difference, I had this problem on the version 8.0.2, but when I saw 8.0.3 was out I have downloaded and updated but still had the same problem.

  the patch worked for me:

  http://Weltall.HelioHost.org/wordpress/wp-content/uploads/2012/01/vmware802fixlinux320.tar.gz

  I have vm workstation 8.0.3 and Ubuntu 12.04 precise, kernel 3.2.0.24 and hit the same problem as op.

  my not

  1. unzip the tar.gz, open and modila the version check file patch: patch - modules_3.2.0.sh

  vmreqver = 8.0.3

  plreqver = 4.0.3

  2. go in/usr/lib/vmware/modules/source

  3 extract the vmnet.tar

  tar xvf vmnet.tar

  4. apply the patch

  patch - p1<>

  5 nescot source

  tar cvf vmnet.tar vmnet-only.

  6 restart the vmware kernel module update...

  Good luck..

• "Could not open/dev/vmmon: no such file or directory." Please make sure that the "vmmon" kernel module is loaded. »

  I installed vmware Player on a linux Open Suse (32-bit), the supplied file .bundle machine. It worked very well, and I could load my file of virtual machine very well. Then, my machine had a random failure. When it restarts, I could no longer use my virtual machine, always get the error:

  "Could not open/dev/vmmon: no such file or directory."

  Please make sure that the "vmmon" kernel module is loaded. »

  I look in / dev, and of course, there is no vmmon. I see a lot of archived messages stating that you must run the script ' vmware - config.pl '... (more specifically the following link: ) http://blog.solutionperspectivemedia.co.UK/?p=6 )

  but I do not have it. It seems that maybe it was a part of the installation (no-bundle) more old?

  What should I do? Is this a known problem, as indicated in this Web site? Or random failure caused something? I'm quite confused.

  Have you tried to uninstall as root? Otherwise I think it won't work.

  With respect to your original problem, I got it, too, and that's what I did:

  sudo mv/usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

  vmware-modconfig--console--install-all--appname sudo = 'VMware Player' - icon = 'vmware-player '.

• updated VMware kernel module cannot compile after kernel upgrade - 3.7.2 (Fedora 18)

  Environments:

  OS: Fedora x86_64 18

  Kernel and kernel headers: 3.7.2 - 201.fc18

  VMware Player: VMware-Player - 5.0.1 - 894247.x86_64.bundle

  VMware-modconfig journal:

  2013-01-18T14:13:00.229+08:00| vthread-3| I120: Validating path "/lib/modules/3.7.2-201.fc18.x86_64/build/include" for kernel release "3.7.2-201.fc18.x86_64".
  2013-01-18T14:13:00.229+08:00| vthread-3| I120: Failed to find /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/version.h
  2013-01-18T14:13:00.229+08:00| vthread-3| I120: Failed version test: /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/version.h not found.
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Kernel header path retrieved from FileEntry: 
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Update kernel header path to 
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Validating path "" for kernel release "3.7.2-201.fc18.x86_64".
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Failed to find /linux/version.h
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Failed version test: /linux/version.h not found.
  2013-01-18T14:13:00.329+08:00| vthread-3| I120: Kernel header path  is invalid.
  2013-01-18T14:13:00.330+08:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"
  2013-01-18T14:13:00.335+08:00| vthread-3| I120: Got gcc version "4.7.2".
  2013-01-18T14:13:00.335+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
  2013-01-18T14:13:00.335+08:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".
  2013-01-18T14:13:00.340+08:00| vthread-3| I120: Got gcc version "4.7.2".
  2013-01-18T14:13:00.340+08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
  2013-01-18T14:13:00.345+08:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.7.2-201.fc18.x86_64".
  2013-01-18T14:13:00.345+08:00| vthread-3| I120: No matching PBM set was found for kernel "3.7.2-201.fc18.x86_64".
  2013-01-18T14:13:00.345+08:00| vthread-3| I120: Validating path "" for kernel release "3.7.2-201.fc18.x86_64".
  2013-01-18T14:13:00.345+08:00| vthread-3| I120: Failed to find /linux/version.h
  2013-01-18T14:13:00.345+08:00| vthread-3| I120: Failed version test: /linux/version.h not found.
  

  I found this in another forum and solved the problem:

  The version.h file is missing in /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/ therefore, the manuscript is not able to get the right path to fetch the other header files.

  The following will fix the problem by copying the version.h in the folder:

  CP /usr/include/linux/version.h /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/

• ESXi 5 - How to disable the unsigned kernel modules

  Hello. The Guide of strengthening "briefly" 5.0 mentions "Disabling Unsigned modules and remove the offending host VIBs»

  What is the best way to do both, that is to say: same/separate CLI commands?

  Looking for a general form of the command to do both of the above.

  Thank you.

  Community VIBs must be signed CommunitySupported would be the filter to use to get rid of any VIBs that could be signed (potentially with those signed as well).  However, the guide lists only the VMwareCertified and the VMwareAccepted as the recommended levels, so using supported that the filter will achieve what the guide is recommended.

  STEP 1: Connect to each ESX/ESXi host using the vCLI or ESXi Shell and run the command "esxcli software acceptance get ' to check the acceptance level is set to 'VMwareCertified' or 'VMwareAccepted '.  STEP 2: Connect to each ESX/ESXi host using the vCLI and run the command "esxcli software vib list" and check that the level of acceptance for each VIB is set to 'VMwareCertified' or 'VMwareAccepted '.

• Workstation 10.0.4 or fail compilation on Debian Jessie using 3.17 kernel kernel modules

  Is the patch for 10.0.3 10.0.4-compatible?

  I just tested and it works.

• Vmmon module kernel does not not on Fedora 21 w / 11 workstation

  Don't know if anyone else has questions nightmare on Fedora with VMware and other...

  After getting through the questions with the headers of the kernel, GCC, etc... for the installation is successful, I set up a machine and try to start it but get:

  Error: Unable to open/dev/vmmon: no such file or directory. Please ensure that the "vmmon" kernel module is loaded.

  I did a lot of research and VMwares Ko, communities, as seems to be a coherent question. I have also crossed a lot of 3rd party sites too, but nothing of the resolution.

  I used the following corrections but no luck:

  • "Could not open/dev/vmmon: no such file or directory." Please make sure that the "vmmon" kernel module is loaded. " -which States:

    • MV/usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

      ... See the section below for the reconstitution of the modules

  • vmware-modconfig - console - install-all - to (re) construction of the modules for later
  • Checking service in /etc/init.d/ and attempted to launch and get:

  Starting VMware services: Virtual machine monitor [FAILURE] Virtual machine communication interface [OK] VM communication interface socket family [OK] Block the system files [OK] Virtual Ethernet [FAILURE] [OK] VMware authentication daemon

  • Tried to add vmmon kernel usage: modprobe vmmon, but get the error: modprobe: ERROR: could not insert 'vmmon': the button is not available

  
  

  I don't know there is something simple that I'm missing, right?  It seems that before the service can run just, I must get vmmon working properly?

  
  

  Journalctl newspapers attached as well.

  
  

  Thanks for your help!
  

  
  

  
  

  I encountered exactly the same problem and finally solved by disabling "Secure Boot" from the BIOS.

  When "Secure Boot" is enabled, the unsigned kernel extensions will be not allowed to load. vmmon. Ko and vmnet.ko are of course not signed with cert of Fedora, so they will not work.

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

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

• Verification for the loading of unauthorized kernel (ESXi only) modules.

  Can someone tell me how to put this:

  4.2.16.1 VMware provides digital signatures for 3 party kernel modules that meet certain requirements. By default the ESXi host does not load the kernel modules which do not have a valid digital signature. This behavior can be overridden; However, a warning is sent to the alert system administrator logs any time that an unauthorized module is loaded.

  4.2.16.1.1 the core of 'messages' log file will show an entry of any time that an unsigned module is loaded into memory. This log file should be monitored and analyzed for this text. The message will be of the form
  4.2.16.1.2 ALERT: Elf: NNNN: XXXXX kernel module has been loaded, but has no attached signature. Where "NNNN" is a number and "XXXXX" is the name

  It refers to 15 HMT in hardening paper.

  Thank you

  Hello

  I think that this is serious. If you have a kernel module that is not signed, while the kernel module is NOT blessed by VMware. However, you may have blessed it yourself, and you must have it because it is from a third-party trust provider. In this case, you have two options, check checksums and communicate to the supplier you need all your kernel modules to be blessed by Vmware.

  This is very similar to the alteration of the Linux kernels and some cannot be contaminated (by security policy), and others allow it. You need to know what the module is and why he has been charged in the first place and if use you it again.

  In this case, the knowledge is your friend, starting with the list of those signed and functional not from there. You can use the logfile approach as well, but in both cases, you can find unsigned modules.

  To define levels of more top/more detailed log look at Article #1004795

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009, 2010, 2011,2012

  Author of the books ' VMWare ESX and ESXi in the business: Planning Server Virtualization Deployment, Copyright 2011 Pearson Education. ' Of VMware VSphere and Virtual Infrastructure Security: securing the virtual environment ', Copyright 2009 Pearson Education.
  vSphere Upgrade Saga - virtualization security Table round Podcast

• Compilation of modules for an installed, but not running in the kernel?

  With

  LANG = C vmware-modconfig - console - install-all

  I can compile the kernel running modules. But how can I compile the kernel modules does not?

  Think about it.  You can't unlees you start with the kernel that is not running.