While looking for a fix for the inability of VMware player 4.0.2 to get updated vmware tools (I was getting the error message “Could not find component on update server. Contact VMware Support or your system administrator.”), I found a workaround on the vmware community threads.
They say the issue will be fixed in a few days (this is the fifth day since I found the message, and 23 days since the “we’ll fix it” message was posted). Our fingers are crossed.
For those of you using VMware Player 4 on linux hosts, if you’re not happy with the autobridging for the vmnet0 network, you can choose a specific network adapter to bridge to using vmware-netcfg.
I was messing around with Vmware converter (in windows XP, running from a dual-boot partition), and then I kept getting the following message: “FAILED: Unable to find the system volume, reconfiguration is not possible” at 95% in the reconfiguration step. Apparently the windows ‘System’ drive was not marked as active. This was indeed true, because my linux ext3 boot partition was indicated as the active one in Windows Disk Management console. I didn’t want to use the ‘reconfigure machine’ option to change these properties as explained here, because I would then have to change the SID, Computer Name, etc. (more…)
I’ve been trying to get a backported kernel to work on my installation of Debian Squeeze, but it seems some include files are not included in recent kernel versions. There are also some issues with Kernel version checks in the Nvidia Makefiles.
I finally got it to work by combining information from the Debian Wiki and Paul Goins’ blog at vultaire.net