install debian on vmware workstation 7 comments 8, win7 64 bit host

Similar Questions

• VMware Workstation 7 - comments cannot connect to the host computer

  My problem is compounded by the fact that I've upgraded to VMware 7 and added several virtual Win7 64 virtual machines at the same time so I don't know what (or who) is causing the problem.

  I have 2 host computers running Windows XP 64 and VMware 7.  Firewall is turned off on all real and virtual computers and antivirus software disabled to facilitate debugging.

  I can 'see' host an extra to my network of machines, but I can't connect any virtual machine (Win XP 64 or Windows 7 64) to the drives or folders in a. host Virtual Machines of all the flavors to host B (as can host B himself) can connect to drives and folders in host A or B computers.

  I'm really confused, because it is a new problem in a network that worked without problem for a long time.

  Thank you

  k

  kriemer wrote:

  Scissor

  I was using AVG Anti-virus v8.5.  I uninstalled since then to try to resolve the problem.

  AVG should be ok.  Other AV problems even if 'disabled '.

  I'll try to disable settings NIC "unloading" next Monday (it's my wifes computer and I'm sure you can guess the rest).

  Not to be pedantic, but you mention that it would be temporary disabling.  What happens if this does not resolve the problem, what I won't give in now the settings?

  Give you up to a tiny fraction of one percent of time processor, because your host CPU would be checksums compensable package instead of the card NETWORK adapter.  Any difference would be unnoticable on a modern desktop computer.

  If a new NETWORK adapter driver becomes available, you can always try which allows once again to see if the new driver fixes it.  Even if a newer version of the workstation out.

• Problem installing Windows on VMWare Workstation 11 10

  Good evening

  I'm a french user on VMWare.

  I have a problem when I try to install Windows on VMWare Workstation 11 10, I'm stuck here:

  

  I tried several times to reinstall.

  I use this iso standard: Windows10_TechnicalPreview_x64_FR - FR_9926.iso

  Can you help me?

  See you soon.

  Set up 2 x 2 cores CPU and memory: 3 GB

• Poor performance in VMWare Workstation 10 comments VM, score on memory Windows experience index is low

  Specification of the host is A10-5800 AMD CPU & 8 GB DDR3 - 1600 RAM(dual-channel), running VMware workstation 10 on Windows 7 Ultimate 64-bit SP1. WEI (Windows experience index) score on memory is 7.3.

  Comments is running Windows 7 Professional 32-bit SP1. VMware tool has been installed. The WEI score on memory is only 4.5. I can feel the difference when you work in the guest, because of the bad performance RAM problem.

  Some way to optimize the performance of comments?

  Can I assume that the customer has more than 960 MB and less than 1.5 GB of memory?  The more possible memory under-score with less than 1.5 GB memory is 4.5.

• Install vCMA in VMware Workstation?

  I would like to install the vCMA thin iPad client vSphere demo on my laptop.  Two questions:

  • Is vCMA 64-bit?
  • Can I run the vCMA as a VMware Workstation VM (and not as a device of ESXi)?

  When I try to import the FVO in my computer is giving me an error of bad descriptor.

  -MattG

  Hi Matt,

  Apparently, the current vCMA is based on CentOS 5.2 32 bit. Check with 'cat/etc/issue' and 'uname - a '.

  It should work well on a workstation or player as long as it can access your vCenter or ESX via the network.

  Simply, I downloaded the Zip file, compressed and open without any problems.

  Good luck.

  Concerning

  Franck

• VMplayer running in VMware workstation OS comments

  Hello

  I am a newbie in this community, so sorry if I ask something already asked, but I couldn't find the answer.

  I just want to run VMplayer in windows 2003 virtual machine under VMware workstation 7.1.

  I managed to install vmplayer, but when I run a virtual machine I get the following messages:

  "Running on a virtual machine VMware Player requires the external virtual machine is configured to run a VMware ESX guest operating system." You can not power on a Windows virtual machine until the external machine is reconfigured. »

  Does anyone know how to reconfigure the external virtual machine? If it's possible/supported...

  Welcome to the forums!

  Read this: http://xtravirt.com/how-to-install-vmware-esx-4.0-on-workstation-6.5.2-vm

  AWo

  VCP 3 & 4

  \[:o]===\[o:]

  = You want to have this ad as a ringtone on your mobile phone? =

  = Send 'Assignment' to 911 for only $999999,99! =

• VMware Workstation control comments CPU clock can accelerate?

  Hi users of VMware Workstation.

  I have a unique case to solve which requires to control the CPU clock speed in the comments. Specifically, I need to slow down a 1.5 MHz less than 500 MHz processor. Is this possible?

  Thanks in advance,

  t

  Slow down a 1.5 MHz processor? Wow Yeh yeh ok typo I understand it's 1.5 GHz.

  Can you tell us what you are trying to reach? Maybe there is another solution to your problem.

  --

  Wil

  _____________________________________________________

  Visit VMware developers at http://www.vi-toolkit.com wiki

• Application of VMWare Workstation and comments using the multicast

  Hello

  I am currently evaluating VMware Workstation (version 10.0.0 build-1295980)

  Host operating system version is Windows Server 2008 R2 Enterprise Edition 64 bit 6.1.7601, SP1

  Guest operating system is Windows 7 PRO

  In the guest OS, I try to run an application that uses multicast (group address 224.64.16.1) communication

  This translates into a fall VM, with the following log (excerpt)

  2014 02-04 T 17: 20:17.253 + 01:00 | vCPU-5 | I120: CoreDump: ei-> size 69033984: len = 69033984

  2014 02-04 T 17: 20:17.253 + 01:00 | vCPU-5 | I120: Backtrace:

  2014 02-04 T 17: 20:17.253 + 01:00 | vCPU-5 | I120: backtrace [00] frame IP params 0 0x4285b01 0 0xfaa4546 opus_repacketizer_destroy 0x13f80ef2e 0x0faaed18 + 0x4b9ce [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x0004df2e]

  2014 02-04 T 17: 20:17.253 + 01:00 | vCPU-5 | I120: backtrace [01] framework 0x0faaf640 IP 0x13f7e91a0 0x13fe6cae0 0x13ff88708 params 0 x 725 0x253cf47 opus_repacketizer_destroy + 0x25c40 [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x000281a0]

  2014 02-04 T 17: 20:17.253 + 01:00 | vCPU-5 | I120: backtrace [02] framework 0x0faaf900 IP 0x13fb83934 params 0x2a 0 x 100000000 0 0x2e opus_repacketizer_destroy + 0x3c03d4 [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x003c2934]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [03] framework 0x0faaf960 IP 0x13f9f134e 0x14023c3b0 0x13f97aa71 params 0 x 416100 0x3f6bc70 opus_repacketizer_destroy + 0x22ddee [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x0023034e]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [04] framework 0x0faaf9a0 IP 0x13f9f310c params 0x14023c3b0 0 x 100000000 0xfaaf9e0 0 opus_repacketizer_destroy + 0x22fbac [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x0023210c]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [05] framework 0x0faaf9d0 IP 0x13fd62742 params 0x3c0 0x37b0000 0 x 5 0xa34303132 opus_repacketizer_destroy + 0x59f1e2 [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x005a1742]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [06] framework 0x0faafa20 IP 0x13fd9db2e params 0 x 38000000 0x3c0 0 opus_repacketizer_destroy 0 + 0x5da5ce [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x005dcb2e]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [07] framework 0x0faafb90 IP 0x13fd62a0c 0x13fee9910 0x13feb619c params 0 x 8 0x14041b908 opus_repacketizer_destroy + 0x59f4ac [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x005a1a0c]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [08] frame IP 0x13f97b056 params 0 0x0faafbf0 0 0 0 opus_repacketizer_destroy + 0x1b7af6 [C:\Program Files (x 86) \VMware\VMware Player\x64\vmware-vmx.exe base 0x13f7c0000 0x0001: 0x001ba056]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [09] frame IP 0x76be652d params 0 0x0faafbf8 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\kernel32.dll base 0x76bd0000 0x0001: 0x0001552d]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: backtrace [10] frame IP 0x76d1c541 params 0 0x0faafc28 0 0 0 RtlUserThreadStart + 0 x 0021 [C:\Windows\SYSTEM32\ntdll.dll base 0x76cf0000 0x0001: 0x0002b541]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: Msg_Post: error

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: fatal error [msg.log.error.unrecoverable] VMware Workstation: (vcpu-5)

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120 + NOT_IMPLEMENTED d:/build/ob/bora-1295980/bora/devices/e1000/e1000Hosted.c:1829

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: [msg.panic.haveLog], a log file is available in "D:\VM\HGH2\vmware.log".

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120 + to collect data to be submitted to VMware support, choose "Collect load data" in the Help menu.

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120 + you can also run the script 'vm-support' in the folder my computer directly.

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

  2014 02-04 T 17: 20:17.269 + 01:00 | vCPU-5 | I120: ----------------------------------------

  2014 02-04 T 17: 21:52.008 + 01:00 | vCPU-5 | I120: output

  Seems to have access to a resource NOT_IMPLEMENTED?

  Someone observe similar problems?

  Tips are welcome.

  Best regards

  -Pascal

  After a further review of the pb crash was due to the configuration of jumbo packets. Should be disabled with the current use of VMWare Workstation.

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

• VMware Workstation 6.5.3 IntelCore2Quad Q8200 + XPx64 host cannot create x 64 guests

  I checked the BIOS: VT enabled. I checked the operating system: XP pro x 64 sp2 (5.2.3790). I checked VMware: version 6.5.3 - 185404, license to use OK.  I use a processor Intel Core2Quad Q8200 with 4 GB of Ram.

  Whenever I try to create a virtual machine based on a x 64 OS iso file, I get the message "64-bit operating systems are not supported by this host and will not work."

  Any idea?

  VT - x is needed to support 64-bit client on systems Intel (see 1901 KB).   The Q8200 does not support VT - x (see http://processorfinder.intel.com/details.aspx?sSpec=SLB5M).

• ESXi on VMWare Workstation with widows 2008 comments

  Hello

  I am about to begin a new deployment and I tested some things before that I have shell out money for new equipment and software.

  I tested Windows Server 2008 R2 64-bit on VMWare Workstation and everything is good.  My VMWare Workstation is on Win 7 64 bit

  Ultimately, this equipment will run on ESX, vSphere Essentials through.   To test this, I installed ESXi 4 Update 1 inside VMWare Workstation.

  Because the vSphere client is not supported on Windows 7, I installed the Client vSphere on Win XP 32 bit inside another guest of VMWare Workstation.

  During the installation of Windows 2008 R2 64-bit on ESXi, via vSphere on XP, I get the following error

  Trying to load a 64-bit application, however this CPU in is not compatible with the 64-bit mode.

  Well, I know that my cpu is 64-bit capable, because I'm already under 64-bit so much already.

  It worries me a bit, because I wasn't expecting this obstacle - my test was to validate a number of other things, not this and now I think I might switch to Hyper-V.

  I already searched the forums, and from what I found, nothing has solved the problem yet

  However, there could be a saving grace - could the fact that I'm under esxi in vmware workstation cause this problem?

  Paul

  You're out of luck.

  You cannot run 64-bit inside a virtual ESX clients.

  Nested VMs have no VT support, you need to run a 64-bit client

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

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

• How to move the Virtual Machine VMWare Workstation 10 to a completely different computer

  I have a laptop that is going to become my 'old' laptop, I bought and am always set up a new computer.

  I have a VM THAT evolution created on the 'old' portable using VMWare Workstation 10.  I installed the software VMWare Workstation 10 on the new laptop computer and am ready to move to the existing VM development since the old laptop again to continue the development of software on the virtual machine to the new machine.

  I never moved a computer virtual from one computer to another, and I guess that all I have to do is to copy and move the folder and all its content from the old laptop to the new, and then I'll be back in business?

  Just make sure it is this simple before doing so.

  Thanks for any input.

  It's as simple as that. When you start in the new machine, it should ask if you copied or moved. Answer that you moved it will keep the same MAC address and you will not be able to connect the two copies at the same time. You copied it saying assigns a new MAC and they both can connect, but a Windows machine can ask to reactivate. Seems to me he asked also to reactivate when I copied it for an Intel system AMD system, but it was a long time ago

  Lou

• VMware Workstation 9: could not open/dev/vmmon: no such file or directory

  I'll have a plethora of problems installing and get VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0 - 26-generic).

  I experienced exactly the same process on my laptop and it works perfectly, while on the desktop, it seems that everything breaks. Could someone give me some kind of help / advice on how I can do to get this working. I tried full uninstall / reinstall of the software, headers of the kernel, kernel images, different kernels, patches here on fresh installs of everything I can think of. Here are the issues I encounter in the order of importance (or so I think):

  (1) whenever I try to open my new (and virtual) machine, I get the error sequence of:

  "Could not open/dev/vmmon: no such file or directory. " Please make sure that the "vmmon" kernel module is loaded. '--> 'Failed to initialize the device monitor. "->" cannot change the power state of VM: could not find a valid peer to connect to '

  
  

  (2) every time I try to run the following command to configure the modules on a completely fresh setting (reinstalled kernel, vmware) I get the following output:

  sudo modconfig vmware - console - install-all

  Stopping VMware services:

  Demon of authentication makes VMware

  VM communication interface socket family is

  Virtual machine communication interface is

  Virtual machine monitor makes

  File system is blocking

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmmon-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driverLog.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/hostif.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/apic.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/comport.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/cpuid.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/hashFunc.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/memtrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/phystrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/task.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/vmx86.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/vmcore/moduleloop.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmmon-only/vmmon.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  CP f vmmon.ko. /... vmmon.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  Using 2.6.x kernel build system.

  make: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only»

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/hub.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/userif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/netif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/bridge.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/filter.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/procfs.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac_compat.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetUserListener.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmnet-only/vmnet.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  CP f vmnet.ko. /... vmnet.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmblock-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:285: warning: assignment of incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:296: warning: passing argument 1 of the "putname" incompatible pointer type

  include/Linux/FS.h:2052: Note: expected ' struct filename *' but argument is of type ' char *'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/inode.c:49: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:38: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a cast

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  Warning: "putname" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  CP f vmblock.ko. /... vmblock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmci-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmci-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  CP f vmci.ko. /... VMCI.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vsock-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/util.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  CP f vsock.ko. /... vsock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  Starting VMware services:

  Virtual machine monitor failed

  Virtual machine communication interface failed

  Family of VM communication interface socket failed

  File system is blocking

  Virtual Ethernet failed

  Demon of authentication makes VMware

  Cannot start the services

  (3) I often get the Ubuntu "this program has planted" messages on "/ usr/lib/vmware-installer/2.1.0/vmis-launcher" "' (this message of crash always occurs when you run the"vmware-modconfig"above command on a new installation.

  (4) at different times during Assembly and have VMware workstation on my system I get Ubuntu hangs on "/ usr/lib/vmware/bin/appLoader" and even "/ bin/su" (especially when you are trying to install - su NEVER blocks anywhere else).

  Thoughts / ideas on what is happening on earth / what could have caused this all go so downhill / how to go about fixing?

  Thank you

  Solved.

  The problem is that for another program I used gcc - 4. 4 instead of later. Restore the (by update-alternatives - config ) for gcc, g ++ and CPC - bin.

  Not a very graceful exit to have a version not valid I would say, maybe some sort of basic check could be added to ensure that the correct versions are present?

• How to uninstall VMware workstation 7.1?

  Hi all

  How can I remove VMware workstation 7.1 SLES 10 64-bit?

  I installed it via the provided script, not thtorugh RPM.

  First, search for installed versions:
  $ vmware-Installer - l

  Product product name version
  ====================== ====================
  VMware-workstation 7.1.2.301548

  Then, remove it:
  $ sudo Installer vmware-vmware-workstation 7.1.2.301548 u

  Kind regards

  Ian