VMware Workstation 7.1.2 - Linux networking questions

Similar Questions

• ESX 4 in Workstation 7.0 on Linux - networking issues

  Hi all

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

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

  The system configuration:

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

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

  Machine in ESX 4 comments:

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

  INET addr:192.168.1.243 Bcast:192.168.1.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

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

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

  collisions: 0 txqueuelen:1000

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

  # tcpdump nni - vswif0

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

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

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

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

  Host (Ubuntu 9.04):

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

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

  no ICMP unicast echo request.

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

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

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

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

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

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

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

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

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

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

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

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

  suggestion on what he could be wrong.

  Thanks in advance,

  Chris

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

• [Solved] VMware Workstation 7.1.3 Linux kernel 2.6.36 patch, anyone?

  A new service/bugfix VMWare Workstation was released yesterday, unfortunately even if changelog mentions vmware modules have been made compatible with recent Linux kernels, VMWare modules still won't compile under kernel 2.6.36.

  Stopping VMware services:
     VMware USB Arbitrator                                   [  OK  ]
     VM communication interface socket family                [  OK  ]
     Virtual machine communication interface                 [  OK  ]
     Virtual machine monitor                                 [  OK  ]
     Blocking file system                                    [  OK  ]
  Using 2.6.x kernel build system.
  make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
  make -C /lib/modules/2.6.36-ic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
  make[1]: Entering directory `/usr/src/kernels/linux-2.6.36'
    CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
    CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
    CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  /tmp/vmware-root/modules/vmmon-only/linux/driver.c: In function ‘init_module’:
  /tmp/vmware-root/modules/vmmon-only/linux/driver.c:425:15: error: ‘struct file_operations’ has no member named ‘ioctl’
  make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
  make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
  make[1]: Leaving directory `/usr/src/kernels/linux-2.6.36'
  make: *** [http://vmmon.ko|http://vmmon.ko] Error 2
  make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
  Unable to install vmmon

  Try this patch.

• VmWare Workstation 6.5.1 - local network configuration problem

  Hi guys!

  I have a server with 2 lan card hardware. First of all in the DMZ (10.10.10.X) and the second in LAN (192.68.100.X)

  I started 3 virtual machine with Windows 2003 server.

  SERVER (PDC): 1 Lan (in Lan) cards

  SERVER B (SQL): 2 Lan (Lan 1, 1 private SERVER C network) card

  C (WEB) SERVER: 2 lan card (1 in the DMZ, in private network with SERVER B 1)

  I create 1 BRIDGE with VMNet0, 1 lan private VMNet2

  The problem is when I put the lan card 2 in the same group lan becouse ServerB VMNet2 not ping server C (I test the ping with the installation of DHCP and the static IP... but nothing!)

  What I see, your DMZ network is connected to VMnet2:

  Regarding your screenshot of the VMWare Virtual Network editor VMnet2 is connected to the Broadcom and your first post regarding your host has a NETWORK card in the local network (192.168.100.0) and the other in the demilitarized zone (10.10.10.0). --> VMNet2is is connected to your local network or demilitarized zone (that is why I needed the ipconfig host as well, but you don't post it).

  I guess the Broadcom's DMZ for now.

  This means that if VMnet2 is considered to be the DMZ with 192.168.200.0 (look at Server C) which do not function as it relates to the Broadcom with 10.10.10.0.

  Server c:

  He must have a card in the demilitarized zone (on the name) who has an IP address of 192.168.200.2. It does not not 10.10.10.x? If this is the adapter that uses VMnet2 which does not work.

  ServerB:

  Server B seems to have the correct IP addresses, but it has no way to reach C because it has no address of 192.168.200.x.

  If you really want to have a private connection (no DMZ) between B and C, private by VMnet1 card and use the IPS that VMware provides for this network.

  I guess you want like this:

  LAN (192.168.100.0) - B - VMnet1 (private/host-only/192.168.200.0)---C---DMZ (via VMnet2 jumpered to Broadcom 10.10.10.0)

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

  AWo

  VCP / vEXPERT 2009

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

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

• Workstation 10, VM Android no network

  someone was lucky to the provision of the network for an android x 86 virtual machine on VMware Workstation?  I edited the network settings according to various online tutorials and now network setting seems to be OK and I can ping to ip addresses even after setting the dns of google dns I can ping web addresses of the terminal, but since the android interface, I can not connect, the only options of connection is via wifi or mobile network , so I can not recognize the network! everything under the hood is functional and right! why it can't recognize the network?

  Well, since no body here has given me no help, I had to fix myself, I followed this tutorial, I found via google and it worked fine, I don't know if I'm allowed to post links or not, but carried away, I'm really sorry!
  Install Android x 86 on the development of VirtualBox and Eclipse | ankulrastogi

• How to activate the Internet connection on Windows Server 2003 is installed in the virtual machine in VMware Workstation 8?

  I have Windows Server 2003 is installed on a virtual machine in VMware Workstation 8. I need it to learn and practice the use of the Active Directory. I've also set up 3 Windows XP workstations connect to it, which means that they can communicate with Server 2003. What is lacking is the Internet connection on all of them. When I run ping 8.8.8.8 in one of these virtual machines, I get, 'Destination host unreachable.'

  I'm not sure, what if the problem comes from the settings in Windows or the settings of the virtual machine.

  Can someone help me?

  Thank you, guys. I was finally able to put in place. It was quite an ordeal to deal with IP addresses and virtual networks. Here's how I did (in the screenshots) in case someone else needs it.

  (I also confess that it is perhaps one of the ways to implement. Maybe there is an easier way to do it with DHCP...)

  1. in your computer where is installed VMware Workstation 8 begin the "Virtual Network Editor." It is located in the folder of installation of VMware Workstation. And implement the network following (VMnet2 in my case):

  

  2 then in VMware Workstation itself in the virtual machine when Windows Server 2003 is installed set up two network as connections:

  This one is for external access to the Internet:

  

  And this one for intranet communications AD:

  

  3. then in the machine virtual de Windows Server 2003 set up what follows for two network adapters:

  For Internet access:

  

  Then, you need allow this connection to share:

  

  And then for the ad access to workstations (ensure that the static IP address is in the range specified in the virtual network over VMnet2 network editor). I've also set up DNS to 127.0.0.1 because I installed on this Windows 2003 DNS server:

  

  4. from the Windows 2003 VM try ping 8.8.8.8. It should work now.

  5. go to each workstation, in my case, Windows XP, each in its own virtual machine and set up the network in the VMware Workstation as follows:

  

  6. then in the virtual machine, configure the network connection for Windows XP workstation. Don't forget to assign a new static IP address for each workstation, which not coinside with IP of the domain (this IP address must come from the range specified in the virtual network over VMnet2 network editor):

  

  7. try first ping the domain, in my case ping 192.168.237.128. And then Internet, ping 8.8.8.8. The two should work!

  Continue with steps [5-7].

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

• Questions to install VMware Workstation

  Hello everyone and thank you for your interest in my post.  For the last 6 months I spent reviewing messages to build and run a secure Channel 5 on a laboratory at home and collected a lot of information.  Budget delays I am not near my goal I thought I'd be so I thought I would get something on my current equipment with VMware Workstation.

  I got a 64 bit Windows 7 with Intel I7 processor gaming computer and wanted to add Workstation 8 or 9 now that it is out.  Finally, I would like to build some virtual labs, but now want to get running in the virtual world.

  Help for the following questions would be appreciated.

  1 install Workstation 8 on a Windows 7 64 bit computer or do a clean install on the computer and run a Windows 7 as a virtual machine?

  If a clean install Workstation 8 or 9 is recommended how could I get my image of Windows 7 today converted to a virtual machine before the clean install?

  Guess the question would be, is I there a VM tool that can convert an image of current computer hardware in a virtual machine so that I can run on a new installation of VMware Workstation 9?

  2. what steps should be taken to migrate from a hardware configuration to a configuration of the VM on the same box?

  3. what risks are there to lose data?

  4. what license issued or limitations can I exect meet when I create several virtual machines, alias windows, Linux and others?  Can you build and run several different VMS at the same time?

  5. return to the VM tools, I know on the side of Vsphere there are tools to create virtual machines for ESXi, but what tools are there for Workstation 8 or 9 build and run virtual machines?

  That ye may know that my training and the ability to understand your answers I was in the field of information technology since 1990.  Currently, I am a network engineer and have experience as a non-virtuelle system administrator installs computer and server and operation.

  Thanks again to all who help out.  I hope that once I get the speed I can contribute to the community as well.

  David

  Since you are a "Network Engineer and have experience as a system administrator" then IMO shouldn't really ask!   How hard is it to type 'physical to virtual' in Google and get to VMware vCenter Converter?  Also read the documentation on it as well as VMware Workstation!   Yes I know you said "on non-virtuelle installs computer and server and operation" however do practically is fundamentally not different then do it physically, although with virtualization, there are additional methods that can be used, as using an ISO Image vs optical media to install from, etc.  Seriously with your course, you should be able to install VMware Workstation, browse and examine the different menu commands and create VM almost without having to read the documentation however takes the time to at least he skim initially and then jump in.    As a tip activate everything installs Windows without first installing VMware Tools, if you plan to install VMware Tools in the virtual machine, and wait until you are sure that you have configured as you want, and then select as appropriate.

  One thing you'll need to do if you are using the latest version of VMware vCenter Converter you will need to select the correct mass storage controller as you walk through the wizard because it is by default in the IDE and you want LSI SAS with Windows 7.

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

• Nested 5.5 ESXi in Workstation 10 Networking question

  Hi all

  I have an instance of VMware workstation 10 running on an HP z600 with guest OS in RHEL 6u3 where I am trying to accommodate a nested instance of ESXi 5.5 for a lab environment.  I have no problem with the guest OS (Windows or Linux) network using deck vmnic on workstation instance.  I have set the ESXi Server also uses a vmnic bridge.  I can connect to the end ESX Server from any workstation on my network with vSphere, but I can't connect to all nested ESX Server virtual machine hosting.  I tried Linux and Windows virtual machines with the same result.  Virtual machines do not seem to be a problem to get my (interesting) DHCP Server IPv4 configuration.  From the virtual machine, I cannot ping the default router.  Ping indicates the destination is unreachable.  I ping the IP of management on the ESX Server from any workstation on my network, but not VM.  Network mgt ESX and vmnetwork are on the same vmnic.  Very simple configuration.  Any thoughts on where to start?

  Network bridged on VM workstation:

  

  Parameters of ESX on worksation:

  

  ESX vSwitch parameters:

  

  Thanks for any help,

  -dave

  You have the vmnet devices configured to allow the "Promiscuous" mode?  See http://kb.vmware.com/kb/287.

• Kickstart: linux + vmware workstation 8?

  Hello!

  Im getting a kickstart for Linux guests with vmware workstation 8.

  is there a howto or whoever did this?

  concerning

  Lars

  I'm not immeaditally aware of anyone doing this.  I guess you are using a Red Hat based for this distribution?  If so, you will want to install the development tools (the kernel headers and gcc and friends).  Installation of WS should be done some time in the section cusomization of scripts of the kickstart file.  If RIP you in the installer of WS, you will find the flags that will reduce the amount of questions asked (and if you dig enough deep to eliminate questions).  Start the installer of linux WS help section to find the minimum set of afroementioned of the flag of questions.  I would like to know how it goes... looks like fun

• Convert the physical Linux machine with VMware Converter Standalone 4.0.1 on VMware Workstation

  Hello

  I work in a virtualization project, now I test and I want to test the new version of the converter, because I need to convert some Linux machines and I know that with this version is not difficult.

  I do not have the ready virtual infrastructure so I test on a workstation environment. I would like to know if someone has converted a physical Linux machine to virtual and if the destination has VMware workstation 6.5. I know that this is not supported, but this does not mean that you couldn't do.

  When I have to specify the type of destination, I got the error that you could see on the photo.

  Please let me know if you have tested this before and you know how to solve this problem.

  Thanks in advance!

  See you soon

  Malulas,

  Welcome to the Community Forums.

  To do a physical to virtual conversion, you MUST GO to ESX.  It is a requirement under the guidance of the user manual.

  If the virtual machine was already in ESX, you might be able to export to a workstation image while the ESX VM is powered off.

  Sorry for the bad news.

  Kind regards

  EvilOne

  VMware vExpert 2009

  NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

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