VMWare Workstation 6.5 - configure a host as a bridge?

Similar Questions

• VMware Workstation 9 - processor Configuration

  Hello. I am new to this forum so Hello to everyone. Currently, I'm trying to re - create my virtual home for Windows Server 2008 R2 environment and other bones. I have CPU Quad-Core i7. So far, when I created virtual machines, I put config processor 1 processo and 4 cores. I realized, I could use 8 logical processors. Now, how do I configure each virtual machine for maximum performance?

  Let's say I have 4 operating systems virtual... what should be my processor configuration?

  Thanks in advance

  In fact the rule is to use a single cpu\core, unless you start to find that the single CPU is at the origin of issues and slowdowns, it's at that point you should begin to add carrots.

  In my lab at home practically everything runs on a single processor as I am more likely to face problems of ram before the cpu constraints.

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

  I created a new virtual machine using VMWare Workstation 12.1.1 build-3770994 with a guest OS from Linux Mint 18 (which is built on top of Ubuntu 16.04). I have two monitors on my system, the two 2560 x 1440. I am unable to get this virtual machine Linux Mint 18 to cover all of my two monitors when I disable "Accelerate 3D graphics" in my vm settings, I get an error. I have another Linux Mint 17 VM running on the same VMWare Workstation 12 on the same host machine from Windows 10 and it is able to expand on my two monitors very well with "Accelerate 3D graphics" disabled, but he does not open-vmware-tools.

  I have read instructions telling me to install open-vm-Tools-Office in this guest operating system of Linux Mint 18. I did it. Then I restart the guest operating system. When starting, I can click on 'Enter full screen mode' in my menu of VMWare Workstation, and the guest OS has a monitor as expected. When I then click on "Cycle multiple monitors", I get the following error. "The virtual machine could not be changed to the selected screen layout. If you add a monitor to the host computer, you must turn off and turn on the virtual machine to use this monitor. »

  

  I can optimize my VM to automatic adjustment, only one of my two screens, but not both. I tried to uninstall and reinstall open-vm-tools, open-vm-tools-desktop and restart. I tried to use /vmware-tools-distrib/vmware-install.pl's original vmware tools and who does not work either.

  In my vmware.log, I get these two lines that occur when I get the above error.

  2016 07-12 T 15: 43:19.068 - 06:00 | MKS | I125: ToolsSetDisplayTopology: send rpcMsg = 1 DisplayTopology_Set, 0 0 2560 1440

  2016 07-12 T 15: 43:24.768 - 06:00 | MKS | I125: ToolsSetDisplayTopology: rpcMsg sending = DisplayTopology_Set 2, 0 0 2560 1440, 2560 0 2560 1440

  2016 07-12 T 15: 43:24.853 - 06:00 | vCPU-1 | I125: TOOLS of the call to DisplayTopology_Set failed.

  When I activate "Accelerate 3D graphics" with the configuration described above, I am able to use both of my monitors. Why is this the case?

  I think remember having to disable "Accelerate 3D graphics" in my Linux Mint 17 comments vm because it would crash randomly. I try to run this VM Linux Mint 18 with 3D acceleration and see if it crashes, but why is there a difference with spanning multiple monitors?

  Thank you.

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

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

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

• VMWARE Workstation or ESXi

  I currently run VMWARE Workstation on my Windows XP host computer. I have a laboratory facility 5 machine Windows active directory in an environment "TEAM."

  It is soon time to expand my lab at 7 machines and want some advice on what I should do next. I was going to one of the 2 courses.

  1. update my PC by replacing the host OS 32-bit to a 64 bit OS. Get a more powerful CPU and go to 6 GB of RAM. I'm still worried about the disk i/o, however many machines with what I have all my guests running on a single hard drive. If anyone cares to elaborate on the performance by running that this many machines off 1 disc it would be greatly appreciated.

  2. get the material needed to create an ESXi whitebox. I really don't know much about the capacity or features of ESXi. I guess the main thing I want to know is that you can configure a function of 'The TEAM' as in VMWARE Workstation. I find this very handy feature.

  If I decide to build an ESXi server, is installed in a VM guest in workstation for practice? Is this desirable?

  From what you say in this thread, I think I agree with NWhiley. Stick to the workstation and add to your current HW configuration. I would definitely add additional hard disks, maybe even an external storage array. The outer table has a great performance insofar as, if you decide to go the route of ESXi to a later date, it will be easy to take your storage with you space. This will be your least expensive option (in terms of money & learning curve) and does not get to ESXi in the future. It's one of the beauties of virtualization, you can grow in stages

  Ken Cline

  VMware vExpert 2009

  VMware communities user moderator

  Blogs about: http://KensVirtualReality.wordpress.com/

• Fatal error of VMware Workstation

  Hello

  I have serious problems with VMware Workstation (version 9.02) and unique virtual machine to Windows 8. VMware Workstation is installed x 64 host Windows 8. This unique virtual machine crashes randomly with the following error message:

  

  I have other virtual machines also but I have no problems with them. First of all, I thought it was a physical disk error and I moved this virtual machine to another drive, but it did not help. I reinstalled VMware Tools and even created a new virtual machine and cloned this issue with Acronis Backup & Restore machine for this. This due to the machine crashes with the same error, but every time you start so things went even worse.

  Any ideas what to do with it?

  I attach a log file.

  Post edited by: Demuz

  I updated to VMware Workstation 10 and reinstalled the whole problematic virtual machine from scratch, but it still crashed at random several times a day with the same error.

  But now things look well so far.

  Yesterday, I changed a setting. I unchecked "Accelerate 3D Graphics" settings of the virtual machine (under the display settings). After that, the virtual machine crashed 0 times and I've been using a whole day! I have Nvidia display with the latest adapter drivers Win 8.1 x 64 installed on the host machine. I think drivers Nvidia has something to do with this virtual machine crashing, maybe...

  I started to suspect the display driver Nvidia after seeing this nvd3dumpx.dll appears more than once in the log file (this is VMware Workstation logfile ater the crash):

  2013-10 - 07T 18: 14:03.625 + 03:00 | vthread-14 | I120: backtrace [00] framework 0x1004ee48 IP 0x7ff8c64db9af params 0 x 1 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006da9af]

  2013-10 - 07T 18: 14:03.626 + 03:00 | vthread-14 | I120: backtrace [01] framework 0x1004eea0 IP 0x7ff8c655ee5c params 0xf2c680 0 0x116d5ee0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0075de5c]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [02] frame IP 0x7ff8c649c5f8 params 0 x 1 0x1004f6c0 0 0x7ff800000000 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069b5f8]

  2013-10 - 07T 18: 14:03.627 + 03:00 | vthread-14 | I120: backtrace [03] framework 0x1004f6f0 IP 0x7ff8c649860d params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0069760d]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [04] framework 0x1004f720 IP 0x7ff8c64b7f43 params 0xf2f280 0 0 0? [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x006b6f43]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [05] framework 0x1004f750 IP 0x7ff8c673c2cf params 0x7ff800000000 0 0 0 QueryOglResource + 0x1d5c2f [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b2cf]

  2013-10 - 07T 18: 14:03.628 + 03:00 | vthread-14 | I120: backtrace [06] frame IP 0x7ff8c673c51a params 0 0x1004f780 0 0 0 QueryOglResource + 0x1d5e7a [C:\Windows\SYSTEM32\nvd3dumx.dll base 0x7ff8c5e00000 0x0001: 0x0093b51a]

  2013-10 - 07T 18: 14:03.630 + 03:00 | vthread-14 | I120: backtrace [07] frame IP 0x7ff8df941611 params 0 0x1004f788 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\KERNEL32. [DLL base 0x7ff8df940000 0x0001: 0 x 00000611]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: backtrace [08] frame IP 0x7ff8e08664ad params 0 0x1004f7b8 0 0 0 RtlUserThreadStart + 0x001d [C:\Windows\SYSTEM32\ntdll.dll base 0x7ff8e07f0000 0x0001: 0x000754ad]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: Msg_Post: error

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: fatal error [msg.log.error.unrecoverable] VMware Workstation: (vthread-14)

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + Exception 0xc0000005 (access violation) occurred.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.haveLog], a log file is available in "F:\VMware\Virtual Machines\vmware.log".

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + to collect data to be submitted to VMware support, choose "Collect load data" in the Help menu.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120 + you can also run the script 'vm-support' in the folder my computer directly.

  2013-10 - 07T 18: 14:03.633 + 03:00 | vthread-14 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

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

• How to configure the network adapter when you run ESXi on VmWare workstation?

  How to configure the network card installing ESXi on VmWare workstation 6.0.0?

  These are the options: I tried bridged, host-only NAP.  None of them works

  

  What Miss me? driver or adapater?

  I'm running on vmware workstation on Windows 7 with Lenovo laptop.

  in the configuration of your virtual machine, the main issue is memory. you gave the 2 GB of RAM, whereas ESXi 6 cannot go forward without minimum 4 GB of RAM.

  If please have 4 GB of RAM and re-run Setup. you will get through.

  message about the network card should also not appear after that. What kind of network you choose depends on your need.

• Host Windows system restore back up virtual machines the VMWare Workstation?

  Is it save to perform a restore of the system on a Windows host running VMWare Workstation 9.0.2 with the premises of virtual machines? I just need confirmation that the VMs will be still functional after restoring the system.

  Welcome to the community,

  System Restore should not touch all personal documents, what configuration file and virtual disk are in reality. However, a restoration of the system can change the parameters of the application Windows for for example VMware Workstation. Anyway most that should happen is that you have to reinstall VMware Workstation in such a case.

  see "what files changed during a system restore?" at http://windows.microsoft.com/en-us/windows/system-restore-faq

  In any case, it is always useful to have a current backup!

  André

• Networking question in VMware Workstation / nested ESXi network configuration problem

  Hi guys,.

  I am trying to set up a virtual lab, I setup a domain, a vcenter server and up to 1 ESXi host controller.

  I am really struggling with the network aspect in establishing a vmnic for storing shared, please see the attached screenshots and a few questions:

  1. Is a vmnic a real network map? or vmnic correspond to "network adapters" that you put in place since the setting of your virtual machine?

  I followed a tutorial and implement 3 NICs on the ESXi host, in Bridge mode, I tried this in my configuration of vmworkstation and I lose the connection to my server vcenter to the ESXi host.

  See screenshot attached to how I configured my ESXi host, screenshot is called 'screenshot2esxihost network', I run got each of the maps defined on NAT network.

  

  See also the screenshot of how I have my configuration of network settings in my VMWare Workstation, screenshot is called "screenshot1. the tutorial does not show how it has its editor of the virtual network configuration, but it puts its ESXi host NICs in BRIDGED mode, and I'm guessing that you can set this time within the virtual network adapter. If someone could tell me what changes should I make in there and on the network cards in my ESXi host, which would be really useful.

  

  My domain controller, server ESXi hosts and vcenter are currently on the 192.168.86 range, which currently stood at NAT

  See also a screenshot from the vsphere client - I don't see a vmnic "vmnic0", my goal is to be able to add a "vmnic2" for a separate storage network.

  

  any help would be received with gratitude, I VCP510 review at the end of the month and really hope to be able to get my lab setup as soon as possible.

  The vmnic is the rising 'physical' of an ESXi host. So with the 3 network cards that you configured for the host in VMware Workstation you will see under "Network adapters" and you can use them to vSwitches in the section "network".

  André

• VMware workstation - PCI switch to OS to solve the lack of host riders invited

  Hi all

  I'm quite new to VMware applications.

  To implement PCI passthrough / directly access hardware PCI by the host OS

  is it possible to just use VMware Workstation? or VMware ESXi OS is necessary?

  In this case:

  -The machine physics processor and card motherboard BIOS supports virtualization.

  -The host OS is Windows 7 64 bit.

  -A PCI card is interrupted and got only Windows XP / Vista drivers (the two 32-bit).

  -VMware Worstation 8.0 running in the host operating system.

  -VM guest OS is Windows XP (32 bit).

  Can I somehow configure direct access to the virtual machine PCI card / guest OS?

  I think that would solve a lot of pilot uncompatibility between 32/64 bit OS versions;

  It would be useful to have work directly in the VMware workstation.

  Or is it now possible only with OS ESXi and is rather simple to use here?

  Thank you very much for the support.

  LD

  VMware Workstation isn't compatible PCI Passthrough, you must run ESX or another product to make it work.

  Linjo

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

• How to configure vmware workstation and server Suse 10 as operating system prompted

  Hi, I installed vmware workstation 6.5 on vista and Suse 10 as guest operating system.  I keep Suse as default (without any network configuration).  I modified the default vmware gateway 192.168.2.1 keep even as window by default gateway settings. I also changed to the subnet to 192.168.2.0.  The IP address is replaced by 192.168.2.128. IP address of my Vista is 192.168.2.4 and DNS Server 4.4.4.1 and 4.4.4.2.

  I tried to ping between host and guest, and comments to the host, but still received the error of "destination host unreachable". It does not matter using host only or NAT mode.

  All Documents available? All advice? What do I have to configure Suse network. ?

  Thank you

  Ming

  Mike10 wrote:

  Host:

  Wireless network connection Wireless LAN adapter:

  IPv4 address: 192.168.2.2 (Preferred)

  ... Subnet mask: 255.255.255.0.

  Ethernet VMware Network adapter adapt VMnet1:

  IPv4 address...: 192.168.17.1 (Preferred)

  ... Subnet mask: 255.255.255.0.

  Ethernet VMware Network adapter adapt VMnet8:

  IPv4 address: 192.168.30.1 (Preferred)

  ... Subnet mask: 255.255.255.0.

  For infor comments:

  eth0 Link encap HWaddr 00: 0C: 29:8E:1F:01

  INET addr:192.168.30.128 Bcast:192.168.30.255 mask: 255.255.255.0

  If the IP address of comments has the correct value you use VMnet8, not VMnet1. It should work, but this isn't the network "host-only '. That's what I need the .vmx file for. If this indicates that the virtual NETWORK adapter is configured as 'host-only' the IP of comments is wrong. It must be 192.168.17.x in this case.

  However... try to get a ping of the IP address, not name. Depending on the configuration you have posted, you should try to ping the 192.168.30.1 customer and 192.168.30.128 host. Don't forget that cannot work if your client is configured to use instead of VMnet1 VMnet8. If it is really configured to use VMnet1 you must change the IP of comments that I wrote above.

  If the host and the guest have active firewall disable them for testing purposes.

  Furthermore, by default, VMware installs a DHCP for VMnet1 and VMnet8 service. So if this service is still running on your host computer, you can assign the DHCP client and he gets the appropriate automatically for the network IP address.

  I don't no how to open the *.vmx in text format.  I noticed that vmnet1 IP address on the side of the BACK is 192.168.17.1 but side comments, it is established as 192.168.20.0.

  It is a text file. Just open in an editor and copy and paste it or attach the file to your next post.

  If you found this information useful, please consider awarding points to 'Correct' or 'Useful' answers and answers. Thank you!!

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

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

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

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

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

  He was vmnet.ko, at least for me.

  Here's how to solve,

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

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

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

  If so, you can run vmwre!

  I hope this will help you.

  Good day.

• I have a problem starting up a Windows XP Pro Machine virtual Windows 8 host system (which has VMware Workstation 10.1).

  I am new to the virtual machines.  For several months I've been running a Windows XP Virtual Machine in an old machine of Windows 7 with VMware Workstation 7.0.  The hard drive is having some problems at times, so I thought that I could move the virtual machine on a new computer that has an OS 8.1 Windows and VMware Workstation 10.  For example, on the Windows 7 machine, I copied the directory with all the * .vm files and pasted into the machine to Windows 8. But when I tried to start VMware Workstation 10 in Windows 8 machine, I got the message "this virtual machine policies are too old to be run by this version of VMware."  I went to the knowledge base and used the solution described here: I've deleted the lines of three 'policy' of the .vmx file and added the suffix .ancien to the .vmpl file, which actually disabled.  Now, when I try to start the virtual machine, the black screen appears with the VMware logo in the Center and everything seems fine, but Windows XP starts.  And logo VMware guard churning away as in a continuous loop.  It is not easy to stop.  The only way to stop VMware is via the Task Manager or restart the machine.

  What must I do to get the Windows XP Pro VM to run in the new machine?

  VMWare technical support suggested that I have disable 3D acceleration (VM > settings > view and uncheck the box 3D graphics acceleration).  The virtual machine starts now with some minor problems, but it is usable.  But by closing accel 3D turns, in the words of the Technical Support Engineer, David, that there is "a problem with the graphics card not imitate or through its capacity to the virtual machine.  In other words do not support to the VM guest 3D acceleration. "My next step is to make sure that I have the updated driver for the Intel HD Graphics 4600 display adapter.

  Minor problems are:

  (1) the virtual machine works best in screen mode reduced.  There are a few problems speed mode full-screen.

  (2) the VM will still work after switching on of the host.  But after execution of the virtual machine, if power you the virtual machine and the release of VMware workstation, then later, start the workstation, the virtual machine will power not.

  To turn it on again you must out of VMware Workstation, disconnect the host machine and then reopen it in one.

• Windows 7 64 bit host works very slowly after discontinuation of VMWare Workstation

  I am running 64 bit Windows 7 on a Dell laptop with an i7, 6 GB ram and VMWare Workstation 9 processor. Everything works well on the host and the VM, while the virtual machine is powered on but after the suspension of the virtual machine and station work out of the system host becomes very slow and applications become desensitized. This lasts for several minutes after the stoppage of work. In general, I have executed only a VM at a time, but even when I got a couple of them run both the host system and they are very sensitive. I started the task with great difficulty Manager when this occurs to see if I can see problems with the free time of processors and memory use, and everything seems fine. So far all my research turned discussions about this kind of problem during execution of the virtual machine so I am at a loss to know even where to go next to make this diagnosis.

  Kind regards

  Bruce Brandt

  This is because windows is the collection of memory the vmware used in the system and marking of these blocks of memory piece by piece as 'free '. If you shutted down of the virtual machine (not paused) then the memory can be returned to the system immediately. I guess if it was caused by the Intel RST driver because I noticed about there is also no question AMD computer used by my colleague.

  You can wait until the stops of HDD-light, keeping the stats of light, constant in the meantime try avoid to activate any application of consumption-e/s disk / operations.