Noel's Posts

anthonyvigh wrote: Got a phone call from customer support, I have put through a technical ticket, so hopefully they will create a patch for the latest kernel shortly. For the Nth time, the Natty problem is not kernel related.  We (and by "we", I mean the VMware user community) have existing patches for all current kernels, through to the most current 2.6.38.  The problem with Natty is not kernel related, as evidenced by the fact that I am running the same 2.6.38-1 kernel for Natty with Maverick, using our current 2.6.38 patch (referenced previously).

Graham Daly wrote: Maybe you can find additional information in the following? http://communities.vmware.com/thread/304307?start=0&tstart=0 Unfortunately, Graham, the referenced thread points out that even after patching the kernel modules, VMware fails to work in Natty (see also), and not in code to which we, the supporting community, have access, else we would help to fix it.

moebiusstrip wrote: I replaced deprecated lock_kernel/unlock_kernel functions with private mutexes. Hope it helps. Thanks!  I knew that was the necessary change, but hadn't had time to make it.  I'm sure it will help, although it seems that we may still have an issue with the new X Server.  I'll test it against Natty later today.

Agendum2 wrote: The VM itself would never "automatically" sleep based on time settings in the guest, but when the host sleeps it would broadcast WM_POWERBROADCAST within the guest OS.  This would give guest apps the opportunity to respond and register sleep wake events.  Those sleep wake events end up in the guest BIOS, which the VM manager is running.  The manager can then forward those sleep wake events onto the host OS. The thing is, I can easily write an application which is smart enough to forward WM_POWERBROADCAST.  However, the VM Manager would have to have some support for the sleep wake events as they appear in the VM BIOS. If that is what you want, you can have it.  You can configure the host to use vmrun suspend <path/to/vmx> and configure VMWare Tools in the guest to run a script when there are suspend and resume events.  There are already scripts installed that get excecuted.  For example, by default, the MS-Windows guest scripts run ipconfig /release when the guest suspends, and ipconfig /renew when the guest resumes.

MichaelZhou wrote:         I fail to install vmwaretool on my fedora-14 which located on work station.          The detailed information for my envrionment are listed below.         work station: 7.0.0 build-203739         Fedora : 2.6.35.11-83.fc14.i686.PAEdebug You realize that the current product is 7.1.3 build-324285, right?

Marty Felker wrote: Whats' wrong with this plicture? As I've said, VMware needs to Open Source more of the non-proprietary code, push to get more stuff into the distros, and otherwise build community that can contribute.  VMware appears to simply be unable to keep up with changes.  VirtualBox doesn't have that problem, but also isn't as good as VMware for the most part when both work.

Marty, I've had it working with Natty until this week when the X Server was updated to 1.10, along with with things.  That is when the Workstation UI stopped (complains about AppLoader failing). VMware really needs to Open Source more of the non-essential code, keeping what they *need* proprietary proprietary.  They are losing the battle in terms of release cycle.  Ubuntu, Fedora, and other Linux distros are releasing every 6 months, and everyone else is able to keep up. Personally, I'd like to see the UI redone in Python, with supporting libraries in C. It could be IronPython for MS-Windows users (pobrecitos).  That would give us a much more flexible and customizable environment, as well as enabling community-authored bugfixes (e.g., for the long-standing defect with the wrong tabs loading) and enhancements.

I also have: -rw------- 1 noel noel 19966831 2011-02-25 12:01 _usr_lib_vmware_bin_appLoader.1000.crash but seeing as it is almost 20MB (14MB compressed), please advise if you want it, and if so, where.

Kodaxo wrote: I am trying to recompile the kernel modules under Ubuntu 10.04 (Lucid) running the 2.6.37-12 kernel for Lucid from the Ubuntu kernel dev team's PPA which already includes legacy BKL. I have not tried that particular combination (Lucid + 2.6.37-12), but I have vmlinuz-2.6.37-12-generic and vmlinuz-2.6.38-1-generic both working with Natty using the updated patch attached to the first message of this thread. Apparently, we need a more involved patch for when the BKL is removed, which some other distros have done.  It is on my list, but spare time has been in short supply lately.

claudioseri wrote: i have the same problem with VMware Workstation 7.1.3 Linux kernel 2.6.37: Linux XXX.pc 2.6.37-12-generic-pae #26~maverick1-Ubuntu SMP Wed Jan 5 21:20:21 UTC 2011 i686 GNU/Linux From where did you get that kernel?  As far as I cai see, the most recent 2.6.37 from Ubuntu for Maverick, out of the Mainline PPA, is 2.6.37-020637rc2-generic, and that kernel is working here. The build command that we post with the patch procedure would show us more details about the compile failure.      --- Noel

I assume, based on some years of experience, that we'll see a real VMware upgrade that fully addresses the kernel changes in 2.6.37.  Until then, we wait and cope. I already posted the patch to handle it.  If you can't get it working, odds are you have the wrong patch.