Noel's Posts

attached is the patch that works for me with Fedora 14 and (http://kojipkgs.fedoraproject.org/packages/kernel/2.6.37/1.fc15/src/kernel-2.6.37-1.fc15.src.rpm) Comparing the current patch (top of thread) with this one, they appear to be essentially identical (except for an embedded date and order of files), as makes sense.  So it seems that we've got 2.5.37 covered on the various distros.

TheBigRed wrote: i tried to use the 2 following patches from here for my kernel-2.6.37 with Workstation 7.1.3 on Fedora 14, but this fails with errors. The patch to which you refer doesn't appear sufficient.  Try the one I posted at the top of the thread, which works with the latest 2.6.37 as released by Ubuntu (and, reportedly, by others). Personally, I haven't tried 2.6.37 on Fedora.  I'm using the stock Fedora kernel as well as the CCRMA real-time kernel for Fedora 14, for which I have a separate patch.

UnderXP wrote: Is this patch compatible with kernel 2.6.37-12.26 ? (I think that is 2.6.37 final) The patch that I had updated at the top of the thread works fine for me with Ubuntu Natty 2.6.37-12.26.

rgadsdon wrote: The Workstation 7.1.3 2.6.37 patch fails with kernel.org version 2.6.37 (final): make[1]: Entering directory `/usr/src/linux-2.6.37'   CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘LinuxDriver_Open’: /tmp/vmware-root/modules/vmci-only/linux/driver.c:375:4: error: implicit declaration of function ‘init_MUTEX’ make[2]: *** [/tmp/vmware-root/modules/vmci-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.37' make: *** [vmci.ko] Error 2 make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Unable to install vmci You've got something wrong.  The patch should have modified compat_semaphore.h in vmci-only to include: #if (defined CONFIG_PREEMPT_RT && LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 31)) || LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 37)    /*     * The -rt patch series changes the name of semaphore/mutex initialization     * routines (across the entire kernel).  Probably to identify locations that     * need to be audited for spinlock vs. true semaphore.  We always assumed     * true semaphore, so just apply the rename.     *     * The -rt patchset added the rename between 2.6.29-rt and 2.6.31-rt.     */    #ifndef DECLARE_MUTEX       #define DECLARE_MUTEX(_m)  DEFINE_SEMAPHORE(_m)    #endif    #ifndef init_MUTEX       #define init_MUTEX(_m) sema_init(_m,1)    #endif #endif

The other comments are good as to choice of VMDK type. Back in the days when I was enough to run on an MS-Windows host, I found that DiskKeeper did a pretty decent job with defraging VMDK files. For linux, I have found that XFS can work well, and I periodically run xfs_fsr. Probably skipping EXT4 and looking forward to trying btrfs.

VMware is on a negative trend for USB compatibility with the linux kernel. Noel - no need to restrict that to Linux - same on Windows. Nowadays I ask users "do you need reliable USB ? - if yes - stick to 6.5.4" I don't do MS-Windows, so I didn't know that USB support is broken there, too. For the moment, I can work around this bug by blacklisting the host's (Fedora 13) snd-usb-audio module. Even worse - I see no improvement at all with the newer 7.1.* versions I agree. None of the new versions have done anything to resolve the problem, and VMware is silent. I'm not sure which is less acceptable. At the least, they should be here communicating with us, and giving the impression that they are working on the problems. VMware has a lot to learn from Open Source communities about communication and collaboration.

I tried testing my headset with Fedora 13, Lucid, Maverick, and Natty with all available kernels for each, and in ALL CASES VMware Workstation 7.1.3 is crashing the kernel during the process of taking over the USB device. Here is another report: http://www.uluga.ubuntuforums.org/showthread.php?t=1389308 The ability to use USB audio is a work requirement, so I am now forced to reinstall Fedora 11, as it is the last version that VMware is compatible with. This is not acceptable, and really requires a resolution from VMware. C'mon, guys, silence is not golden, and I am willing to help you guys debug the problem.

Just FYI, you do realize that you could ditch bootcamp, install VMware Fusion on Mac OS X, and use VMware to create a new VM containing your old PC, right? Do you have a need for bootcamp, or just thought that was the easiest way for running MS-Windows on your Mac?

I've seen it as well with different kernels and distros. Would love to see it resolved, and will likely do some testing soon, since I have some on-line classes coming up, and I need to find another working setup that's newer than the last one I had working well.

I tried using "vmrun list" and then parse the output to detect the running VMX paths. But I was unable to parse the command output with a Windows batch file... Any suggestions? Installing Python would be a start.

Thank you Noel and jlward4th! I didn't want to hound anyone, but was wondering ... You're welcome. As does James, I have Natty running here, as well. So hopefully we can continue to keep ahead of others in terms of kernel adoption. With luck VMware will pick up the patches for the next release, and start a beta soon so that I don't have to keep maintaining them. LOL

As Woody said, RTFM. NAT and Host are working exactly as expected. Bridged networking would give you both intra-host (VM-to-VM) and Internet connectivity, but at the cost of requiring host connectivity at run-time. An alternative is to configure networking for the VMs, and have one of the VMs configured to bridge between a local net and the Internet (with a second virtual NIC), as described here.

There's a patch that does it all for you. It's been mentioned here and there on these forums (just search for 2.6.35) There is a patch for 2.6.35, an updated one for 2.6.36, and a newly posted (as of tonight) revision that includes those and 2.6.37-rc1. There is also a patch in the beta forum for 2.6.31-rt.