Announcement

Collapse
No announcement yet.

[solved] No net in VMWare Player 3

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [solved] No net in VMWare Player 3

    Hello,

    I am running a virtual XP on my Kubuntu 9.10 using VMPlayer 3. Unfortunately, I don't have any net access in the virtual machine, a problem that first occurred a while ago in VMPlayer 2 - if I remember it when updating to 9.04. I googled a lot but cannot find any help - maybe someone can give me a hint where to look for problems? Here's some output:

    Code:
    $ sudo vmware-modconfig --console --install-all      
    Stopping VMware services:                         
      VMware USB Arbitrator                        done
      VM communication interface socket family              done
      Virtual machine communication interface               done
      Virtual machine monitor                       done
      Blocking file system                        done
    Using 2.6.x kernel build system.                      
    make: Gehe in Verzeichnis '/tmp/vmware-root/modules/vmmon-only'      
    make -C /lib/modules/2.6.31-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
         MODULEBUILDDIR= modules                          
    make[1]: Betrete Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'       
     CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o             
     CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o           
     CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o             
    /tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
    /tmp/vmware-root/modules/vmmon-only/linux/hostif.c:1944: warning: ‘newUpBase’ may be used uninitialized in this function
     CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o                               
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o                             
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o                              
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o                             
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o                             
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o                            
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o                               
     CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o                              
     CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o                            
     LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o                                  
     Building modules, stage 2.                                              
     MODPOST 1 modules                                                   
     CC   /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o                                
     LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko                                 
    make[1]: Verlasse Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                        
    make -C $PWD SRCROOT=$PWD/. \                                              
         MODULEBUILDDIR= postbuild                                           
    make[1]: Betrete Verzeichnis '/tmp/vmware-root/modules/vmmon-only'                           
    make[1]: »postbuild« ist bereits aktualisiert.                                     
    make[1]: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmmon-only'                           
    cp -f vmmon.ko ./../vmmon.o                                               
    make: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmmon-only'                            
    Built vmmon module                                                   
    Using 2.6.x kernel build system.                                            
    make: Gehe in Verzeichnis '/tmp/vmware-root/modules/vmnet-only'                             
    make -C /lib/modules/2.6.31-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                  
         MODULEBUILDDIR= modules                                            
    make[1]: Betrete Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                         
     CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o                                 
     CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o                                   
     CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o                                 
     CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o                                  
     CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o                                 
     CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o                                 
     CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o                                 
     CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o                               
     CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o                                  
     CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o                                
     CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o                            
     LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o                                  
     Building modules, stage 2.                                              
     MODPOST 1 modules                                                   
     CC   /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o                                
     LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko                                 
    make[1]: Verlasse Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                        
    make -C $PWD SRCROOT=$PWD/. \                                              
         MODULEBUILDDIR= postbuild                                           
    make[1]: Betrete Verzeichnis '/tmp/vmware-root/modules/vmnet-only'                           
    make[1]: »postbuild« ist bereits aktualisiert.                                     
    make[1]: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmnet-only'                           
    cp -f vmnet.ko ./../vmnet.o                                               
    make: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmnet-only'                            
    Built vmnet module                                                   
    Using 2.6.x kernel build system.                                            
    make: Gehe in Verzeichnis '/tmp/vmware-root/modules/vmblock-only'                            
    make -C /lib/modules/2.6.31-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                  
         MODULEBUILDDIR= modules                                            
    make[1]: Betrete Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                         
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o                              
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o                             
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o                            
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o                             
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o                              
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o                           
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o                              
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o                             
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o                              
     CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o                              
     LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o                                
     Building modules, stage 2.                                              
     MODPOST 1 modules                                                   
     CC   /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o                              
     LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko                               
    make[1]: Verlasse Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                        
    make -C $PWD SRCROOT=$PWD/. \                                              
         MODULEBUILDDIR= postbuild                                           
    make[1]: Betrete Verzeichnis '/tmp/vmware-root/modules/vmblock-only'                          
    make[1]: »postbuild« ist bereits aktualisiert.                                     
    make[1]: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmblock-only'                          
    cp -f vmblock.ko ./../vmblock.o                                             
    make: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmblock-only'                           
    Built vmblock module                                                  
    Using 2.6.x kernel build system.                                            
    make: Gehe in Verzeichnis '/tmp/vmware-root/modules/vmci-only'                             
    make -C /lib/modules/2.6.31-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                  
         MODULEBUILDDIR= modules                                            
    make[1]: Betrete Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'                         
     CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o                               
     CC [M] /tmp/vmware-root/modules/vmci-only/linux/driverLog.o                             
     CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o                            
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o                            
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o                           
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o                            
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDs.o                              
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o                             
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciGroup.o                             
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciProcess.o
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
     CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
     LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
     Building modules, stage 2.
     MODPOST 1 modules
     CC   /tmp/vmware-root/modules/vmci-only/vmci.mod.o
     LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
    make[1]: Verlasse Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'
    make -C $PWD SRCROOT=$PWD/. \
         MODULEBUILDDIR= postbuild
    make[1]: Betrete Verzeichnis '/tmp/vmware-root/modules/vmci-only'
    make[1]: »postbuild« ist bereits aktualisiert.
    make[1]: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Verlasse Verzeichnis '/tmp/vmware-root/modules/vmci-only'
    Built vmci module
    Using 2.6.x kernel build system.
    make: Gehe in Verzeichnis '/tmp/vmware-root/modules/vsock-only'
    make -C /lib/modules/2.6.31-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
         MODULEBUILDDIR= modules
    make[1]: Betrete Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'
     CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
     CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
     CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
     CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
     CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
     CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
     LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
     Building modules, stage 2.
     MODPOST 1 modules
     CC   /tmp/vmware-root/modules/vsock-only/vsock.mod.o
     LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
    make[1]: Verlasse Verzeichnis '/usr/src/linux-headers-2.6.31-19-generic'
    make -C $PWD SRCROOT=$PWD/. \
         MODULEBUILDDIR= postbuild
    make[1]: Betrete Verzeichnis '/tmp/vmware-root/modules/vsock-only'
    make[1]: »postbuild« ist bereits aktualisiert.
    make[1]: Verlasse Verzeichnis '/tmp/vmware-root/modules/vsock-only'
    cp -f vsock.ko ./../vsock.o
    make: Verlasse Verzeichnis '/tmp/vmware-root/modules/vsock-only'
    Built vsock module
    Starting VMware services:
      VMware USB Arbitrator                        done
      Virtual machine monitor                       done
      Virtual machine communication interface               done
      VM communication interface socket family              done
      Blocking file system                        done
      Virtual ethernet                          failed
    Any help is highly appreciated!

    #2
    Re: No net in VMWare Player 3

    Hi man, I remember back some time ago when I tried VMware over Kubuntu had aany kind of problems with network connection NEVER making it work.
    Suddenly after I installed Ubuntu and then installed VMware everything worked right, so I presume there's a conflict in VMware with evertthing else that isn't GNOME.

    I'm now running Kubuntu 9.10 KDE SC 4.4, a week-fresh installation and I need to install VMware to use my virtual machines, mainly for testing things so I wil try tomorroy or Thursday to run it and if anything goes wrong I'll let you know.

    I know, I know, it's all lovely what I wrote above but I haven't give you any clue on how to solve your problem... well, actually I think there's no such and if you -and me and everyone else running Linux with something that's no GNOME- want a full network support for your virtual machine your should start going the way of Virtualbox.

    In any case, I'll let you know...

    Comment


      #3
      Re: No net in VMWare Player 3

      Thanks for your reply, looking forward to hear from you. Here's some more output from the log file:

      Code:
      Feb 17 08:52:08.355: vcpu-0| VNET: MACVNetPortOpenDevice: Ethernet0: can't open vmnet device (No such file or directory)
      Feb 17 08:52:08.355: vcpu-0| VNET: MACVNetPort_Connect: Ethernet0: can't open data fd
      Feb 17 08:52:08.355: vcpu-0| Msg_Post: Warning
      Feb 17 08:52:08.355: vcpu-0| [msg.License.cantOpenDirectory] Unable to open the /usr/lib/vmware/licenses/site license directory: No such file or directory
      Feb 17 08:52:08.355: vcpu-0| [msg.vnet.connectvnet] Could not connect Ethernet0 to virtual network "/dev/vmnet1". More information can be found in the vmware.log file.
      Feb 17 08:52:08.355: vcpu-0| [msg.device.startdisconnected] Virtual device Ethernet0 will start disconnected.

      Comment


        #4
        Re: No net in VMWare Player 3

        I (and many others here ) have been running xp in vmplayer on Kubuntu's since 8.04 and never had a problem with networking.

        Maybe you could give us some of your machines specs. You know:
        - eth card, etc. Also how are you connecting to which kind of network (internet, office network, etc)
        HP Pavilion dv6 core i7 (Main)
        4 GB Ram
        Kubuntu 18.10

        Comment


          #5
          Re: No net in VMWare Player 3

          Thanks for your reply. It did work for a while ... but that's a while ago.

          My pc is connected to the internet via a router (cable connection). The eth card is the onboard card (ASUS P5QL PRO motherboard). I did not change any of the net configuration in VMware manually and I do not have problems accessing the net from Kubuntu.

          Btw, I also noticed that the above mentioned "/usr/lib/vmware/licenses/site" does not exist. However, I do have a folder called "/usr/lib/vmware/licenses/user".

          Comment


            #6
            Re: No net in VMWare Player 3

            Okay,
            in vmware palyer 3 you can edit your guest win xp settings. Have you tried different network settings from there?

            PS. Mine is set to NAT and I use a cable / router / switch.
            HP Pavilion dv6 core i7 (Main)
            4 GB Ram
            Kubuntu 18.10

            Comment


              #7
              Re: No net in VMWare Player 3

              Yes, I tried all of them - makes no difference. Trying NAT, I get:

              Code:
              Feb 17 10:27:07.640: vmx| VNET: MACVNetPortOpenDevice: Ethernet0: can't open vmnet device (No such file or directory)
              Feb 17 10:27:07.640: vmx| VNET: MACVNetPort_Connect: Ethernet0: can't open data fd
              Feb 17 10:27:07.640: vmx| Msg_Post: Error
              Feb 17 10:27:07.640: vmx| [msg.vnet.connectvnet] Could not connect Ethernet0 to virtual network "/dev/vmnet8". More information can be found in the vmware.log file.
              Feb 17 10:27:07.640: vmx| [msg.device.badconnect] Failed to connect virtual device Ethernet0.

              Comment


                #8
                Re: No net in VMWare Player 3

                Oh, boy I remember something like that from way back when.

                Have you tried deleting your internet connection from within xp and reinstalling it again?

                Or even more drastically, deactivating your eth card, rebooting and then reactivating it and then deleting your internet connection, rebooting, reinstalling your internet connection?

                Apart from that and testing either bridged or NAT I fear I cannot help further. You may have to dive into the vmware froums:
                http://communities.vmware.com/commun...ew=discussions

                Or wait for someone else to answer (Like dible)

                I hope that works and keep us posted
                HP Pavilion dv6 core i7 (Main)
                4 GB Ram
                Kubuntu 18.10

                Comment


                  #9
                  Re: No net in VMWare Player 3

                  I just reviewed my installation log at /var/log/vmware-installer. I don't see anything that looks different from the posted one. However, I note that OP used
                  Code:
                  $ sudo vmware-modconfig --console --install-all
                  . I did not -- I simply ran the downloaded .bundle file.

                  There's a log file named vnetlib. Here's the tail of it:

                  Configured subnet: 192.168.71.0
                  Setting vmnet-dhcp IP address: 192.168.71.254
                  Opened: /dev/vmnet8
                  Recving on VNet/vmnet8/192.168.71.0
                  Sending on VNet/vmnet8/192.168.71.0
                  Feb 16 18:29:31 VNL_Load - LOG_ERR logged
                  Feb 16 18:29:31 VNL_Load - LOG_WRN logged
                  Feb 16 18:29:31 VNL_Load - LOG_OK logged
                  Feb 16 18:29:31 VNL_Load - Successfully initialized Vnetlib
                  Feb 16 18:29:31 VNL_StartService - Started "Bridge" service for vnet: vmnet0
                  Feb 16 18:29:31 VNL_CheckSubnetAvailability - Subnet: 172.16.102.0 on vnet: vmnet1 is available
                  Feb 16 18:29:31 VNL_CheckSubnetAvailability - Subnet: 192.168.71.0 on vnet: vmnet8 is available
                  Feb 16 18:29:32 VNL_StartService - Started "DHCP" service for vnet: vmnet1
                  Feb 16 18:29:32 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet1
                  Feb 16 18:29:32 VNL_StartService - Started "DHCP" service for vnet: vmnet8
                  Feb 16 18:29:32 VNL_StartService - Started "NAT" service for vnet: vmnet8
                  Feb 16 18:29:32 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet8
                  Feb 16 18:29:32 VNL_StartService - Started "Netdetect" service for vnet: vmnet0
                  Feb 16 18:29:32 VNL_Unload - Vnetlib unloaded.
                  Started Bridge networking on vmnet0
                  Started DHCP service on vmnet1
                  Enabled hostonly virtual adapter on vmnet1
                  Started DHCP service on vmnet8
                  Started NAT service on vmnet8
                  Enabled hostonly virtual adapter on vmnet8
                  Started Network detection service
                  Started all configured services on all networks
                  Internet Software Consortium DHCP Server 2.0
                  Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
                  All rights reserved.

                  Please contribute if you find this software useful.
                  For info, please visit http://www.isc.org/dhcp-contrib.html

                  Configured subnet: 172.16.102.0
                  Setting vmnet-dhcp IP address: 172.16.102.254
                  Opened: /dev/vmnet1
                  Recving on VNet/vmnet1/172.16.102.0
                  Sending on VNet/vmnet1/172.16.102.0
                  Internet Software Consortium DHCP Server 2.0
                  Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
                  All rights reserved.

                  Please contribute if you find this software useful.
                  For info, please visit http://www.isc.org/dhcp-contrib.html

                  Configured subnet: 192.168.71.0
                  Setting vmnet-dhcp IP address: 192.168.71.254
                  Opened: /dev/vmnet8
                  Recving on VNet/vmnet8/192.168.71.0
                  Sending on VNet/vmnet8/192.168.71.0
                  Feb 16 19:40:00 VNL_Load - LOG_ERR logged
                  Feb 16 19:40:00 VNL_Load - LOG_WRN logged
                  Feb 16 19:40:00 VNL_Load - LOG_OK logged
                  Feb 16 19:40:00 VNL_Load - Successfully initialized Vnetlib
                  Feb 16 19:40:00 VNL_StartService - Started "Bridge" service for vnet: vmnet0
                  Feb 16 19:40:00 VNL_CheckSubnetAvailability - Subnet: 172.16.102.0 on vnet: vmnet1 is available
                  Feb 16 19:40:01 VNL_CheckSubnetAvailability - Subnet: 192.168.71.0 on vnet: vmnet8 is available
                  Feb 16 19:40:01 VNL_StartService - Started "DHCP" service for vnet: vmnet1
                  Feb 16 19:40:01 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet1
                  Feb 16 19:40:01 VNL_StartService - Started "DHCP" service for vnet: vmnet8
                  Feb 16 19:40:01 VNL_StartService - Started "NAT" service for vnet: vmnet8
                  Feb 16 19:40:01 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet8
                  Feb 16 19:40:01 VNL_StartService - Started "Netdetect" service for vnet: vmnet0
                  Feb 16 19:40:01 VNL_Unload - Vnetlib unloaded.
                  Started Bridge networking on vmnet0
                  Started DHCP service on vmnet1
                  Enabled hostonly virtual adapter on vmnet1
                  Started DHCP service on vmnet8
                  Started NAT service on vmnet8
                  Enabled hostonly virtual adapter on vmnet8
                  Started Network detection service
                  Started all configured services on all networks
                  There was a time when I experienced problems with networking my VM -- I think it was about a year ago, perhaps. But it has been running just fine for many months. Sorry, I can't think of anything more useful than what Fintan has already suggested.

                  Comment


                    #10
                    Re: No net in VMWare Player 3

                    Hmmm... my log file gives me messages such as:

                    Code:
                    Failed to initialize
                    Feb 17 07:52:50 VNLFileExists - Cannot check for file or directory: /etc/vmware/networking , error: No such file or directory
                    Feb 17 07:52:50 VNLNetCfgLoad - Import file does not exist
                    Feb 17 07:52:50 VNL_Load - Error loading the vnet configuration, file used: /etc/vmware/networking
                    Feb 17 07:52:50 VNLNetCfgUnload - Requested cache is not loaded
                    ... which is correct, there is no such directory.

                    Comment


                      #11
                      Re: No net in VMWare Player 3

                      Clearly something is not right with the installed configuration -- that makes 2 different errors about missing directories.

                      Do you still have your downloaded .bundle file? If so, I would seriously consider giving installation another try. I always install from the /tmp directory, and I wonder if you have taken a different approach that caused some problem. Try this:

                      - copy the .bundle file to the /tmp directory
                      - run it as follows:

                      Code:
                      sudo sh VM{tab to complete}
                      Watch for any errors during the process. For me it will proceed slowly, and then put up the license agreement, and I have to "Agree", and then it continues until the VMware GUI comes up, and I point it to my VM. It will ask whether I copied it, and at some point it will invite me to download the new tools, which I agree to do.

                      Comment


                        #12
                        Re: No net in VMWare Player 3

                        Thanks for your reply. This is what I did now:

                        Code:
                        /tmp$ sudo sh VMware-Player-3.0.0-203739.i386.bundle --console -u vmware-player
                        Extracting VMware Installer...done.
                        All configuration information is about to be removed. Do you wish to
                        keep your configuration files? [no]: no
                        
                        Uninstalling VMware Installer 1.1
                          Deconfiguring...
                        [######################################################################] 100%
                        Uninstallation was successful.
                        
                        /tmp$ sudo sh VMware-Player-3.0.0-203739.i386.bundle --console
                        Extracting VMware Installer...done.
                        The product is ready to be installed. Press Enter to begin
                        installation or Ctrl-C to cancel.
                        
                        Installing VMware Player Application 3.0.0
                          Configuring...Traceback (most recent call last):
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
                          if self.shouldRollover(record):
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
                          msg = "%s\n" % self.format(record)
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
                          return fmt.format(record)
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
                          s = self._fmt % record.__dict__
                        UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 1662: ordinal not in range(128)
                        Traceback (most recent call last):
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/handlers.py", line 73, in emit
                          if self.shouldRollover(record):
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/handlers.py", line 146, in shouldRollover
                          msg = "%s\n" % self.format(record)
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/__init__.py", line 630, in format
                          return fmt.format(record)
                         File "/tmp/vmis.TxLFj3/install/vmware-installer/python/lib/logging/__init__.py", line 421, in format
                          s = self._fmt % record.__dict__
                        Installing VMware Player 3.0.0
                          Configuring...
                        [######################################################################] 100%
                        Installation was successful.
                        And guess what - after enabling the network connection in XP - it now works! YES! Fellows, you made my day!

                        Comment


                          #13
                          Re: [solved] No net in VMWare Player 3

                          Aha! Good for you!

                          Comment


                            #14
                            Re: [solved] No net in VMWare Player 3

                            And guess what - after enabling the network connection in XP - it now works! YES! Fellows, you made my day!
                            Glad to be of help
                            HP Pavilion dv6 core i7 (Main)
                            4 GB Ram
                            Kubuntu 18.10

                            Comment

                            Working...
                            X