VMware Workstation 10.0.5 MSI failed

Similar Questions

• VMware Workstation 7.1.2 installs failed on Fedora 14

  I've updated to Fedora 14 earlier, but find the compiled kernel module failed on the first bet on.

  The log file contains no useful information. I installed the kernel headers and development packages and compiled the graphic driver nvidia successfully.

  I guess that the problem is related to the CCG 4.5. Are there available patches? Thank you.

  You both probably need to patch for use with kernel 2.6.35.  See my post: http://communities.vmware.com/message/1640726#1640726

• Installation of VMWare Workstation 11.1.0 on Win 8.1 is THAT MSI will fail with the error "could not write value vmware - tray.exe for \software\microsoft\windows'currentversion\run-cles.

  Hi all

  The MSI failed with the error message as "could not write value vmware - tray.exe in \SOFTWARE\Microsoft\Windows'CurrentVersion\Run key.  Make sure you have fufficient access to that key, or contact your support staff' while trying to install vmware workstation 11.1.0 in windows 8.1.
  I tried to call the installer with run as administrator but it does not help, please suggest me overcome this error.

  Hi Vincentand welcome to the VMware communities!

  This error indicates that you have some security software (antivirus or antimalware software) that protects the part of the registry.  Can you try to temporarily disable all security software on your host computer and see if the installation can move forward?

  See you soon,.

  --

  Darius

• Failed installation of VMware Workstation 9 on new install of win 7

  I looked at the discussion of installation has failed VMware Workstation 9, verified that I am administrator, cleaned folder and looked at the registry and I'm still having problems.  The name of the account used is not Admin/Admin or anything close.

  This is a new installation today of windows 7 with all updates applied.  Avast is my anti-virus software.  The behavior does not change with it running or disabled.

  I think that the problem to be that KLM/Sofware/VMware Inc. does not appear.  I checked that I can create keys.

  "In my installs I've seen: message" failure of the MSI MSI "and once"the MSI MSI failed. "  Authorization of VMware (VMAuthService) failed to start service.

  Here are the logs from my last install.

  Can someone provide me with more information about the problem and how to get this installed?

  Thank you

  Finally got this resolved after many setup logs sent to VMware.  I came across the registry problems and VMAuthdServices fail to start due to software AV.

  In short, following http://kb.vmware.com/kb/1031302 (KB1031302) is important as well as some comments from howellrj.  Here's what I did in detail and why during my various tests of installation:

  http://KB.VMware.com/kb/1031302

  1 I used the only account on the system, which did not have a name as owner, admin, administrator, which has administrator privileges

  2 wiped % TEMP % whenever I made an attempt to install

  3 MS KB 942288 not recommended for Win7 so I jumped

  4 no earlier version of VMware Workstation has been installed on the system, so I jumped

  5 ran http://support.microsoft.com/kb/2438651/en-us (MS KB2438651) whenever I made an attempt to install.  He has never found anything wrong

  6 was not running WinXP so I jumped

  7 has made run msconfig to disable all services and should follow https://support3.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1334 (Avast KB1334) to disable Avast self protection mode.  Even with Avast protection auto mode disabled and all the disabled Avast shields were always running and prevent.  The only way to clear the checkpoint was to remove Avast completely.

  8 I ran sfc/scannow before each installation to be sure.  No problems have ever been found.

  So, here is what I did to get the software installed successfully:

  An item copied to my system

  1 AV Installer on my system

  2 use FixIt of MS KB 2438651

  Disconnected the network B

  C restart the system with network not connected

  D removed Avast

  E to restart the system with network not connected

  1 erase TEMP

  2 Ran FixIt utility of MS KB 2438651

  3 ran sfc/scannow

  F install VMware Workstation

  G restart the system

  H check VMware Workstation starts

  I install Avast

  J stop the system

  K connecting to the network

  L reboot the system with connected network

  M update Avast

  N reconfigure Avast

• VMware Workstation 9 installation failed

  Signed in as an administrator and run the installation "as Administrator".

  Downloaded twice in case file has been corrupted.

  How to get:

  The MSI 'c:\users\administrator\AppData\Local\temp\\vmware_1350226415\vmwareworkstation_x86.msi' failed.

  Service "VMware Workstation Server" (VMwareHostd) could not be installed. Make sure you have sufficient privileges to install system services.

  This file has all the rights

  Is the following: "ALEX ~ 1.SYS ' really your admin account?

  Don t have a normal account with a name like "admin" or something? -I expect it works with such a name.

  The restore script failed - Please check if the permissions of the registry for HKLM\Software\VMware Inc. are always ok

• VMware Workstation failed to mount the physical disk 10TB

  VMware workstation or any other product vmware does support more than 2 TB of physical disks?

  I am trying to connect a 5 of 10 TB raid enclosure and mount it on my ubuntu vmware workstation machine. The common error that I receive is when mounting the reader on ubuntu and I think it might have something to do with the size of the file.
  I am running vmware workstation 12 in windows 10.
  The disk is taken offline in windows and I'm under WS as an administrator.

  Error	VMDK CONTENT	DiskPart Info
  Operation failed on the file "\\.\PhysicalDrive1". If the file is located on a remote file system, make sure that the network connection and the server on which resides this disk to work correctly. If the file is saved on a removable medium, link media. Select Retry to retry the operation. Click Cancel to end this session. Select continue to pass the error to the guest operating system. I/o error, dev sdb, sector 11721553632 I/o error, dev sdb, sector 11721552128 I/o error detected. File system stop Please unmount the file system and to rectify the problem (s) metadata I/O error: block 0x2baa8b100 ("xlog_bwrite") error 5 numblks 8200 can not read the superblock	# Disk DescriptorFile version = 1 Encoding = "windows-1252". CID = 6f4a8bb1 parentCID = ffffffff isNativeSnapshot = 'no '. createType = "fullDevice." # Description of the measure RW 23441768448 DISH '\\.\PhysicalDrive1' 0 partitionUUID \\?\scsi#disk & ven_h #w & prod_raid5 #5 & 19bb575e & 0 & 010000 #{53f56307-b6bf-11d0-94f2-00a0c91efb8b} # The database disk #DDB ddb.adapterType = "free". ddb.geometry.biosCylinders = "1024". ddb.geometry.biosHeads = "255".

  ddb.geometry.biosSectors = "63".

  DDB. Geometry.Cylinders = "16383.

  DDB. Geometry.Heads = "16".

  DDB. Geometry.sectors = "63".

  ddb.longContentID = "55c8f3052c372c02465d66656f4a8bb1".

  DDB. UUID = "60 00 C2 97 8 a 7 c c2 cb - 9 a 27 51 78 58 a7 e6 3f"

  ddb.virtualHWVersion = "12".

  H/W RAID5

  Disc ID: 00000000

  Type: SATA

  Status: Offline (policy)

  Path: 1

  Target: 0

  LUN ID: 0

  Path: PCIROOT (0) #PCI (1C07) #PCI (0000) #ATA (C01T00L00)

  Current read-only State: No.

  Read-only: No.

  Boot disk: No.

  Disk swap file: No.

  Disk hibernation file: No.

  Crash dump disk: No.

  Cluster disk: No.

  The official version said that WS allows only virtual up to 8 TB of disk.

  According to my own tests, it only limits the size of the VMDK for 'New - VM' Assistant.
  Once you have a greater vmdk - just tried a vmdk 10TB - WS won't complain about the size.
  I don't expect that WS will prevent the physical disks to use inside a virtual machine that is already configured.
  So in your case I think you started WS with a normal user account.
  Try to start as administrator WS - maybe even using the administrator account.
  I think that then it will work.
  Unfortunately, the error messages produced by vmware.exe are not really accurate-, so there is no way to know if you really have a bad super block.
  To test if this is really the problem and not just an error message - poor try to mount the drive directly.
  Please post the vmdk - want to know if there is something unusual about 5.5 TB in the disk.

• Any Installation of Vmware Workstation failed in my machine, why? See the details

  

  Hey guys, I'm trying to install vmware workstation 11,10 even though 9, but unfortunately it shows this kind of error every time.

  then I try to install from appdata/local/temp, but it shows the error of capture4... I tried many things to fix this... but I failed...

  So guys help me please install... sorely lacking...

  is my laptop config: core i5 - 3230M, ram - 4 GB os-win7 64 bit sp1...

  need help please...

  Welcome to the community,

  the problem is probably caused by the apostrophe in the name of the folder of the user. Try at each logon with a different user (temporary) account, or change the temp/tmp environment variable to point to a different directory (existing), for example, "C:\TEMP".

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

• VMWare Workstation fail to restart after suspend

  I'm using VMWare Workstation 7.1.1 build 282343 on a laptop Windows 7 Ultimate x 64 (8 GB). I run my VMS machines from a disk external eSata. My VMs are all Windows Server 2008 x 64. When I finished work I suspend the virtual machine, stop VMWare Workstation, then disconnect the eSata drive. It is, whenever I just restarted the VM, I get a message that is not possible to restore and I give myself the opportunity to "get rid" or retry - retry fails, so I have to throw. It's embarrassing because it then takes a boot for a long time the virtual machine from scratch.

  Any ideas how to solve this problem?

  disable USB-support for this virtual machine and start again

• VMware workstation 7.1.4 failed on Debian

  Hello

  I'm trying to install VMware-Workstation-Full - 7.1.4 - 385536.x86_64.bundle under the Debian Wheezy (test version).

  I use the linux kernel "3.0.0 - 1-amd64.

  I have patched my kernel to compile the interfaces (with this patch and tutorial)-> http://Weltall.HelioHost.org/WordPress/2011/05/14/running-VMware-Workstation-player-on-Linux-2-6-39-updated/

  Compilation failed for the 'file system blocking'

  Starting VMware services:
  USB VMware arbitrator shall
  Virtual machine monitor makes
  Virtual machine communication interface is
  VM communication interface socket family is
  Block file system failed
  Virtual Ethernet is

  I saw during the compilation of these curious message

  Description: VMware virtual network driver.
  Author: VMware, Inc..
  depends on:
  vermagic: 3.0.0 - 1-amd64 SMP, modversions mod_unload
  ERROR: modinfo: module vmblock is not found
  file name: /lib/modules/3.0.0-1-amd64/misc/vmci.ko
  support: external

  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:348:4: warning: passing of argument 3 of 'kern_path' from incompatible pointer type
  /usr/src/linux-headers-3.0.0-1-common/include/Linux/Namei.h:76:12: Note: expected ' struct path *' but argument is of type ' struct nameidata *'
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c: in function 'FsOpGetSb ':
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:622:4: error: implicit declaration of function 'get_sb_nodev '.
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:622:4: warning: return makes pointer from integer without a cast
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c: at the highest level:
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:48:23: warning: 'FsOpMount' used but never defined
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:58:12: warning: 'FsOpReadSuper' used but never defined
  /tmp/vmware-root/modules/vmblock-only/Linux/filesystem.c:617:1: warning: 'FsOpGetSb' defined but not used
  make [4]: * [/ tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] error 1
  make [3]: * [_module_/tmp/vmware-root/modules/vmblock only] error 2
  make [2]: * [branded] error 2
  make [1]: * [all] error 2
  make [1]: leaving directory '/usr/src/linux-headers-3.0.0-1-amd64 '.
  make: * [vmblock.ko] error 2
  make: leaving directory '/ tmp/vmware-root/modules/vmblock-only.
  Using 2.6.x kernel build system.

  You have a solution?

  Thank you for your help

  Try it - it works for the 3.1.4 VMware Player, so I think it will work the same for 7.1.4 workstation:

  http://communities.VMware.com/thread/324995?TSTART=180

• Workstation installation - MSI failed - Win 7 Pro 64-bit

  Hi all

  I just got a new system and I am trying to install Workstation 7.1.2 (trial) on this subject. System is running Win 7 Professional 64 bit on a processor intel I5 (couldn't find anywhere if the processor is actually supported, but I think it is).

  I get the error that says "the C:\*.* MSI failed.

  I did some research and in vain the following solutions:

  -run the file directly from c:\ (as administrator)

  -changed the name of the installer to something simple (setup.exe, buggy.exe).

  -extract the /e *.exe file and tried to start the installer directly

  -changed the location of the temporary file in c:\temp

  -Run the *.exe/z "action"="install".

  -disable UAC

  -re-downloaded and tried new

  -Downloaded the file smaller and tried everything again

  I'm quite at my limit of frustration right now, so I thought maybe something had this figured out problem. Most of the posts here point to what I tried.

  I have attached the log file in case someone noticed. I noticed a lot of messages "access denied to the LUA environment...". ». Other lines said that he could not find "eclipse.exe '...

  I appreciate any idea on getting through this.

  Thanks in advance,

  rkaram

  Have you had an older version before by chance? I think I saw a cleaning too listed in the downloads. Make sure that your antivirus and security software is disabled also. Which might be interfearing with the installation. It might be interesting to try the cleaning tool before attempting to install another.

  Joe

• MSI failed on the latest version of VMware player

  I use Vista 64 Ultimate.  When I use "run" and add the z switch, as follows

  'Action '=' install', VMware-player-3.0.0-203739.exe/z * I keep on getting error MSI failed. All of the suggestions.

  It is said 'The MSI C:\Users\Username\AppData\Local\Temp\vmware_1259165632\vmwareplayer.msi' failed.

  Thanks in advance.

  random tips that may help...

  Redirect %tmp% into C:\temp - make sure that it has at least 200 MB of free space

  Rename the file VMware-player-* .exe 'buggy.exe '.

  disable any firewall programs and Antivir

  kill a process running called webcam.exe if yopu have such a process

  don't forget to login as administrator and use "run as Administrator".

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

• Snapshot fails on VMWare Workstation 11 Pro

  Hello

  I have created a virtual machine on VMWare Workstation 11 Pro with Windows Server 2008 R2 and baptized "HYP". When I'm trying to take a snapshot, I get the following message:

  VMware Workstation cannot find the virtual disk 'G:\YP.vmdk '. Check that the path is valid and try again.

  The system cannot find the specified file

  Cannot open disk 'G:\HYP-000001.vmdk' or one of the snapshot disks it depends on.

  Necessary to the VM to suspend operation and the VM could not continue to run.

  After that I click OK in the message box that precedes, the virtual computer turns off and then I can turn it on again - I get the following message:

  File not found: YP.vmdk

  This file is required to power on this virtual machine. If this file has been moved, specify the new location.

  Note that I might be able to on and off this machine virtual without problem before I tried to take the snapshot.

  How is that possible I could have it fixed?

  Thank you very much!

  I found where it was. When I was creating this virtual machine, I indicated the location for the new virtual machine as any new drive G. After I had removed this virtual machine and created a new in 'G:\FolderName', the new virtual machine begins to create fine snapshots.

  It is important to specify the folder (not just a new drive letter) as the location for the new virtual machine.

• Failed to create virtual machine using VMWare Workstation 11 (test)

  Hello people,

  I installed VMWare Workstation on my machine Windows 10 and trying to create multiple virtual machines to test the object. I have done this before on the Windows 7 computer and did not face any problems, but this time, as soon as I gave the location of the file to deploy an operating system it comes up with some fatal errors as error BLK_CACHE IOERR if I have enough space on the HARD drive and everything is not going further. So, my question is if my computer has compatible with Windows 10 problems or there is something else that would cause this problem. Any help or comments would be appreciated on this topic.

  Thank you!.

  Thanks for your answer, Noel

  I was going through discussions in the community with similar and found subjects that VMWare had released 12 pro workstation that supports Windows 10 entirely. I personally installed it on my physical machine and it works. Here is the link for the release of Workstation 12 notes.

  VMware Workstation 12 Pro Release Notes

• VMware tools install fails - Centos 6.2 on VMware Workstation 8

  Some setting in context.

  ArcSight make an OVF vmware assessment based on Centos 6.2. I am able to install VMware tools on the ESXi 5.1 platform supported but NOT on VMware Workstation version 8.0.6 build 1035888 which is apparently not supported but works fine on my laptop.

  
  

  The big problem here is that the time on the host computer is massively adrift without VMware tools and make more from the point of the eval worthless SIEM.

  
  

  I'm sure it's a problem of script, but is not certain. When configuring VMware tools that occurs the following

  
  

  START INSTALLATION TEXT

  [root@logger bin]./vmware-config-tools.pl # ]

  Initializing...

  Ensuring services for VMware Tools are arrested.

  [EXPERIMENTAL] The synchronization of VMware filesystem (vmsync) driver is a new feature which

  creates backups of virtual machines. Please refer to the VMware Knowledge Base

  For more details on this ability. You want to enable this feature?

  [None]

  Before you can compile modules, you must have the following installed...

  do

  CCG

  headers of the kernel running kernel

  Looking for a CCG...

  The path "" is not a valid path to the GCC binary.

  You want to change it? [Yes]

  What is the location of the program CCG on your machine? CCG

  The path "/ usr/bin/gcc" is not a valid path to the GCC binary.

  You want to change it? [Yes]

  TEXT OF INSTALLATION END

  I played with the script Perl, but similar problems continue with the location of the kernel headers having precisely defined the variable PATH CCG.

  A few pieces of information of the host.

  [root@logger bin] # uname - m.

  2.6.32 - 220.EL6.x86_64 x86_64

  [root@logger bin] # gcc - v

  Using plug integrated.

  Target: x86_64-redhat-linux

  Configured with:... / configure - prefix = / usr - mandir = / usr/share/man - infodir = / usr/share/info-with-bugurl = http://Bugzilla.redhat.com/Bugzilla --enable-bootstrap--enable-shared--enable-threads = posix--enable-vérification = libération--with-système-zlib--enable-__cxa_atexit--disable-libunwind-exceptions--enable-gnu-unique-objet--enable-langues = c, c ++, objc, obj-c + +, java, fortran, ada--enable-java-awt = gtk--disable-dssi--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre--enable-libgcj-multifile--enable-java-maintainer-mode--with-ecj-jar=/usr/share/java/eclipse-ecj.jar--disable-libjava-multilib--avec-ppl--avec-cloog--avec-tune = generic--avec arch_32 = i686--build = x86_64-redhat-linux

  Thread model: posix

  GCC version 4.4.6 20110731 (Red Hat 4.4.6 - 3) (CCG)

  [root@logger bin] # / usr/bin/make - v

  GNU Make 3.81

  Copyright (C) 2006 Free Software Foundation, Inc.

  This is free software; See the source for copying conditions.

  There is NO WARRANTY; not even a MARKET value or fitness for a

  PARTICULAR PURPOSE.

  This program built for x86_64-unknown-linux-gnu

  [root@logger bin] # / usr/bin/make - v

  GNU Make 3.81

  Copyright (C) 2006 Free Software Foundation, Inc.

  This is free software; See the source for copying conditions.

  There is NO WARRANTY; not even a MARKET value or fitness for a

  PARTICULAR PURPOSE.

  This program built for x86_64-unknown-linux-gnu

  [root@logger bin] #

  
  

  Thank you in advance. Kevin
  

  I solved this problem by upgrading VM Workstation v10 v8.

  All installed now.

  As a newbie here, is there a way I can move this post a status resolved?