Question

Problems with Fedora 11 Guest on VM workstation 6.5

Asked by: Hamilton-4100

Hi All,

I have VMware workstation 6.5.2 installed on a Vista 64 system.
I created a new guest as RHEL 64-bit and installed Fedora x86_64.
The problem is the sound repeats over and over so I have to disconnect the sound from the guest.
if i reconnect the sound the guest is still repeating the same sound.

I installed the VMtools with the RPM workstation provided. i didn't see any errors but i used the GUI not the CLI.

Any Ideas?

Thanks,
H41

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-06-20 at 20:26:40ID24508982
Tags

VMware workstation

,

Fedora

Topics

VMware

,

Linux

,

Fedora Linux

Participating Experts
3
Points
500
Comments
11

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. mounting devices in vmware - fedora 8
    I have a NORCO DS1220 where each of the 12 drives is partitioned as sde1 though ssp1. These partitions are assembled with mdadm into raid devices /dev/md2 (1-5) /dev/md3 (5-10) and /dev/md4 (11-12). Upon installing Fedora 8, the DS1220 and partitions were recognized withou...
  2. Install Fedora 10 on Vmware 6.5.2
    Hi, I have VMware 6.5.2 and I just downloaded fedora 10 DVD iso. I would think installing would be easy. When I boot the VM...and install begins....it says no bootable media device found . Install works with Sun V Box. WHy not with VM ware? I am running Vista...
  3. VMWare server and Fedora 10
    I am running Fedora 10 as the host operating system and have a VM guest of Windows 2003 server running on VMWare Server. Everything was working sweet until I tried to access a USB pen drive. I lost all network connectivity between the host and guest OS's. I cannot get en IP ...
  4. Installing Fedora 12 on VMWare ESXi4.0
    I am running a VMWare ESXi 4.0 Host and I am trying to install Fedora 12. I created the Virtual Machine with the standard networking etc. I have a CD of the Fedora 12 Network Install to boot to and install the OS. When I power on the VM and select the CD drive on the server t...
  5. Problems installing VMware on Fedora
    Hello, I get the following error while I try to install VMware on fedora 12. How do I resolve this and successfully install VMware server and client? [smary@smary ~]$ sudo /usr/bin/vmware-config.pl Making sure services for VMware Server are stopped. Stopping VMware auto...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: ai_ja_naiPosted on 2009-06-21 at 00:20:31ID: 24676495

what sound?

 

by: Hamilton-4100Posted on 2009-06-21 at 00:21:41ID: 24676497

any sound.

 

by: arunrajuPosted on 2009-06-21 at 01:02:49ID: 24676572

One of the most probable reasons might have to do with the experimental support for Fedora 11 OS under VMware Workstation v6.5.2.

http://www.vmware.com/support/ws65/doc/releasenotes_ws652.html

VMware provides experimental support to the following operating systems for Workstation: Fedora 11
FreeBSD 7.1
Mandriva Linux 2009
Novell SLE11.0
Red Hat Enterprise Linux 5.3
Red Hat Enterprise Linux 4.8
Sun Solaris 10 Update 6
Ubuntu 9.04

 

by: Hamilton-4100Posted on 2009-06-21 at 01:18:56ID: 24676594

how can i make sure i installed vmtools correctly?

do i need to rebuild the initrd ram disk after installing vmtools?

 

by: arunrajuPosted on 2009-06-21 at 01:24:10ID: 24676606

You do not need to rebuild the initrd RAM Disk after completing your VMware Tools installation.

Run the command - vmware-config-tools.pl

Confirm the prompt for each query and restart the Virtual Machine once.


 

by: Hamilton-4100Posted on 2009-06-21 at 11:30:07ID: 24678092

I ran 'vmware-config-tools.pl' and everything failed to build.
Here is the output from the build process:

Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                          [  OK  ]
   Virtual Printing daemon:                                [  OK  ]
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?    
[yes] yes                                                                    

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel?                                                                        
[/lib/modules/2.6.29.4-167.fc11.x86_64/build/include]                          

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only'
make -C /lib/modules/2.6.29.4-167.fc11.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules                                                              
make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'        
  CC [M]  /tmp/vmware-config0/vmmemctl-only/backdoorGcc64.o                    
In file included from /tmp/vmware-config0/vmmemctl-only/backdoor.h:29,          
                 from /tmp/vmware-config0/vmmemctl-only/backdoorGcc64.c:38:    
/tmp/vmware-config0/vmmemctl-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined                                                                
  CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o                                
In file included from /tmp/vmware-config0/vmmemctl-only/os.c:51:                
/tmp/vmware-config0/vmmemctl-only/compat_wait.h:78: error: conflicting types for poll_initwait                                                                
include/linux/poll.h:67: note: previous declaration of poll_initwait was here
make[2]: *** [/tmp/vmware-config0/vmmemctl-only/os.o] Error 1                  
make[1]: *** [_module_/tmp/vmware-config0/vmmemctl-only] Error 2                
make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'          
make: *** [vmmemctl.ko] Error 2                                                
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only'                    
Unable to build the vmmemctl module.                                            

The memory manager driver (vmmemctl module) is used by VMware host software to
efficiently reclaim memory from a virtual machine.                            
If the driver is not available, VMware host software may instead need to swap  
guest memory to disk, which may reduce performance.                            
The rest of the software provided by VMware Tools is designed to work          
independently of this feature.                                                
If you want the memory management feature, you can install the driver by      
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.  
These packages are available on your distribution's installation CD.          

                                                                               
None of the pre-built vmhgfs modules for VMware Tools is suitable for your      
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes] yes
                                                                               
Extracting the sources of the vmhgfs module.                                    
                                                                               
Building the vmhgfs module.                                                    
                                                                               
Using 2.6.x kernel build system.                                                
make: Entering directory `/tmp/vmware-config1/vmhgfs-only'                      
make -C /lib/modules/2.6.29.4-167.fc11.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules                                                                          
make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'        
  CC [M]  /tmp/vmware-config1/vmhgfs-only/backdoor.o                            
In file included from /tmp/vmware-config1/vmhgfs-only/backdoor.h:29,            
                 from /tmp/vmware-config1/vmhgfs-only/backdoor.c:40:            
/tmp/vmware-config1/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
  CC [M]  /tmp/vmware-config1/vmhgfs-only/backdoorGcc64.o                      
In file included from /tmp/vmware-config1/vmhgfs-only/backdoor.h:29,            
                 from /tmp/vmware-config1/vmhgfs-only/backdoorGcc64.c:38:      
/tmp/vmware-config1/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
  CC [M]  /tmp/vmware-config1/vmhgfs-only/bdhandler.o                                        
In file included from /tmp/vmware-config1/vmhgfs-only/rpcout.h:30,                          
                 from /tmp/vmware-config1/vmhgfs-only/hgfsBd.h:28,                          
                 from /tmp/vmware-config1/vmhgfs-only/bdhandler.c:45:                        
/tmp/vmware-config1/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config1/vmhgfs-only/request.h:35,                          
                 from /tmp/vmware-config1/vmhgfs-only/bdhandler.c:50:                        
/tmp/vmware-config1/vmhgfs-only/compat_wait.h:78: error: conflicting types for poll_initwait                                                                                            
include/linux/poll.h:67: note: previous declaration of poll_initwait was here              
make[2]: *** [/tmp/vmware-config1/vmhgfs-only/bdhandler.o] Error 1                          
make[1]: *** [_module_/tmp/vmware-config1/vmhgfs-only] Error 2                              
make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
make: *** [vmhgfs.ko] Error 2                                                                
make: Leaving directory `/tmp/vmware-config1/vmhgfs-only'                                    
Unable to build the vmhgfs module.                                                          

The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.                                                

If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.  
These packages are available on your distribution's installation CD.          
[ Press Enter key to continue ]                                                

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes] yes

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmxnet-only'
make -C /lib/modules/2.6.29.4-167.fc11.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules                                                                                        
make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
  CC [M]  /tmp/vmware-config2/vmxnet-only/vmxnet.o                                          
In file included from /tmp/vmware-config2/vmxnet-only/vmxnet.c:48:                          
/tmp/vmware-config2/vmxnet-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_change_mtu:                  
/tmp/vmware-config2/vmxnet-only/vmxnet.c:193: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_get_drvinfo:                  
/tmp/vmware-config2/vmxnet-only/vmxnet.c:267: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_set_tso:                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c:305: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_link_check:                  
/tmp/vmware-config2/vmxnet-only/vmxnet.c:659: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_probe_device:                
/tmp/vmware-config2/vmxnet-only/vmxnet.c:841: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_remove_device:                
/tmp/vmware-config2/vmxnet-only/vmxnet.c:1142: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_init_ring:                    
/tmp/vmware-config2/vmxnet-only/vmxnet.c:1213: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_open:                        
/tmp/vmware-config2/vmxnet-only/vmxnet.c:1338: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function check_tx_queue:                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c:1594: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_tx:                          
/tmp/vmware-config2/vmxnet-only/vmxnet.c:1658: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_rx:                          
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2057: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_interrupt:                    
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2232: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_close:                        
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2314: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_load_multicast:              
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2404: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_set_multicast_list:          
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2465: error: struct net_device has no member named priv                                                                                      
/tmp/vmware-config2/vmxnet-only/vmxnet.c: In function vmxnet_get_stats:                    
/tmp/vmware-config2/vmxnet-only/vmxnet.c:2545: error: struct net_device has no member named priv                                                                                      
make[2]: *** [/tmp/vmware-config2/vmxnet-only/vmxnet.o] Error 1                              
make[1]: *** [_module_/tmp/vmware-config2/vmxnet-only] Error 2                              
make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
make: *** [vmxnet.ko] Error 2                                                                
make: Leaving directory `/tmp/vmware-config2/vmxnet-only'                                    
Unable to build the vmxnet module.                                                          

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.                            
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,  
make and the kernel sources for your running kernel are installed on your      
machine. These packages are available on your distribution's installation CD.  
[ Press Enter key to continue ]                                                

None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?    
[yes]                                                                        

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmblock-only'
make -C /lib/modules/2.6.29.4-167.fc11.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules                                                                                        
make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
  CC [M]  /tmp/vmware-config3/vmblock-only/linux/block.o                                    
In file included from /tmp/vmware-config3/vmblock-only/linux/os.h:35,                        
                 from /tmp/vmware-config3/vmblock-only/linux/block.c:26:                    
/tmp/vmware-config3/vmblock-only/./include/compat_wait.h:78: error: conflicting types for poll_initwait                                                                                
include/linux/poll.h:67: note: previous declaration of poll_initwait was here              
In file included from /tmp/vmware-config3/vmblock-only/linux/vmblockInt.h:40,                
                 from /tmp/vmware-config3/vmblock-only/linux/block.c:29:                    
/tmp/vmware-config3/vmblock-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined                                                                                  
make[2]: *** [/tmp/vmware-config3/vmblock-only/linux/block.o] Error 1                        
make[1]: *** [_module_/tmp/vmware-config3/vmblock-only] Error 2                              
make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
make: *** [vmblock.ko] Error 2                                                              
make: Leaving directory `/tmp/vmware-config3/vmblock-only'                                  
Unable to build the vmblock module.                                                          

The vmblock module enables dragging or copying files from within a host and
dropping or pasting them onto your guest (host to guest drag and drop and file
copy/paste).  The rest of the software provided by VMware Tools is designed to
work independently of this feature (including guest to host drag and drop and  
file copy/paste).                                                              

If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel  
are installed on your machine. These packages are available on your            
distribution's installation CD.                                                
[ Press Enter key to continue ]                                                

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?      
[no]                                                                          

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]  

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmci-only'
make -C /lib/modules/2.6.29.4-167.fc11.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules                                                                                        
make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
  CC [M]  /tmp/vmware-config4/vmci-only/kernelStubsLinux.o                                  
In file included from /tmp/vmware-config4/vmci-only/kernelStubs.h:35,                        
                 from /tmp/vmware-config4/vmci-only/kernelStubsLinux.c:28:                  
/tmp/vmware-config4/vmci-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined  
  CC [M]  /tmp/vmware-config4/vmci-only/vmciDatagram.o                                      
In file included from /tmp/vmware-config4/vmci-only/vmciDatagram.c:42:                      
/tmp/vmware-config4/vmci-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined  
In file included from /tmp/vmware-config4/vmci-only/vmci_kernel_if.h:41,                    
                 from /tmp/vmware-config4/vmci-only/vmciDatagram.c:45:                      
/tmp/vmware-config4/vmci-only/compat_wait.h:78: error: conflicting types for poll_initwait
include/linux/poll.h:67: note: previous declaration of poll_initwait was here              
In file included from /tmp/vmware-config4/vmci-only/vmci_queue_pair.h:36,                    
                 from /tmp/vmware-config4/vmci-only/vmciGuestKernelAPI.h:43,                
                 from /tmp/vmware-config4/vmci-only/vmciUtil.h:33,                          
                 from /tmp/vmware-config4/vmci-only/vmciDatagram.c:48:                      
/tmp/vmware-config4/vmci-only/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined          
/tmp/vmware-config4/vmci-only/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined        
/tmp/vmware-config4/vmci-only/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined        
make[2]: *** [/tmp/vmware-config4/vmci-only/vmciDatagram.o] Error 1                          
make[1]: *** [_module_/tmp/vmware-config4/vmci-only] Error 2                                
make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.x86_64'                      
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/vmware-config4/vmci-only'
Unable to build the vmci module.

The communication service is used in addition to the standard communication
between the guest and the host.  The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These
packages are available on your distribution's installation CD.
[ Press Enter key to continue ]



Detected X.org version 7.5.1.



No drivers for X.org version: 7.5.1.

Skipping X configuration because X drivers are not included.

   Checking acpi hot plug                                  [  OK  ]
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                       [  OK  ]
   Guest operating system daemon:                          [  OK  ]
   Virtual Printing daemon:                                [  OK  ]

The configuration of VMware Tools 7.8.5 build-156735 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.

 

by: arunrajuPosted on 2009-06-21 at 16:50:37ID: 24679083

Did you install gcc during the time of OS Installation ?

The final output says Config for VMware Tools completed successfuly.

 

by: Hamilton-4100Posted on 2009-06-22 at 07:22:16ID: 24682737

GCC was installed with the OS and is version 4.4.0

Yeah the script completed fine, but the modules all failed to build.

 

by: arunrajuPosted on 2009-06-23 at 21:36:20ID: 24698239

Check these 2 threads

Patch for Workstation 6.5.2 on Linux 2.6.29 kernel  
http://communities.vmware.com/thread/203231

Installing Vmware Workstation in Fedora 11
http://communities.vmware.com/thread216353;jsessionid=0BB9C5EDF722DC7047EC95CD915E431B?tstart=0

 

by: Hamilton-4100Posted on 2009-06-24 at 06:23:35ID: 24700742

Those are for installing VMW on Linux. I'm installing linux in a guest on Vista64.

 

by: gtkfreakPosted on 2009-06-29 at 03:56:11ID: 24734898

Move over to VirtualBox. http://www.virtualbox.org.

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...