JP Vossen on 8 Oct 2007 22:56:47 -0000


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] obvious question? Ubuntu/VMware


> From: jeff <jeffv@op.net>
> Date: Mon, 08 Oct 2007 15:02:39 -0400
>
> The major agita seems to be VMplayer.  It flatly refuses to work.
> Since the Ubuntu versions wouldn't install, I used .tar.gz's.  It had
> to build, based upon kernel, a module every time.
>
> My guess is that because it built, it will fail to work each time
> there's a kernel upgrade.  Considering I now have about 8 choices in
> my GRUB menu, it probably won't end soon.  It has failed the last 2
> upgrades.
>
> If I am correct, does this mean I have to reinstall/rebuild VMplayer
> each time there's an upgrade?  Stay where I am?  My brain hurts.

I saw the later posts but am replying to this one for reasons of flow, you'll see why. I also include some CentOS tips, just in case, though I know the OP asked about Ubuntu.


I do not use VMware Player, but I do use VMware Server on several Ubuntu machines running Dapper, Feisty, and Gutsy (and CentOS-4). I don't recall if I ever tried the repo packages, which I think were rather old. I use the tarballs from VMware (or the RPM on CentOS).


Yes, most of the time a kernel upgrade will "break" it. For me, that is a non-issue. My process is this:

One time only:
$ sudo aptitude install build-essential linux-kernel-headers xinetd autoconf2.13 automake1.9 automake vmware-server-kernel-modules


I know for a fact that build-essential and xinetd are required. I'm pretty sure build-essential will also install linux-kernel-headers, but I included them anyway. I'm not 100% sure on the others, especially vmware-server-kernel-modules, but I figured they couldn't hurt. This is how I do it, and it works. YMMV.

For CentOS (as root):
# yum install kernel-devel gcc gcc-c++
* Remove a lot (but not all) of the garbage that Red Hat still thinks is a "minimal" install on a **server** (you might not ant to do this on a workstation. Trim the list at least).
# rpm -e acpid apmd autofs bind-libs bind-utils bluez-bluefw bluez-hcidump bluez-libs bluez-utils crash cups cups-libs dhclient dhcpv6_client dmraid finger ftp gpm indexhtml irda-utils isdn4k-utils jpackage-utils jwhois kbd lftp lockdev mdadm minicom mtr mt-st netdump NetworkManager nfs-utils nss_db nss_ldap numactl parted pax pcmcia-cs portmap ppp quota rdate rdist redhat-lsb rhnlib rp-pppoe rsh samba samba-client samba-common schedutils setarch setserial statserial sysreport system-config-mouse system-config-network-tui system-config-samba system-config-securitylevel-tui talk telnet up2date vconfig wireless-tools wvdial xmlsec1 xmlsec1-openssl ypbind yp-tools
# rm -f /etc/sysconfig/rhn/up2date-uuid.rpmsave /etc/samba/smb.conf.rpmsave /etc/sysconfig/pcmcia.rpmsave /etc/ldap.conf.rpmsave




To periodically upgrade VMware Server:
* Download the tarball however
$ tar xzf VMware-server-1.0.2-39867.tar.gz
$ cd vmware-server-distrib
$ sudo ./vmware-install.pl


After every kernel upgrade and reboot: $ sudo vmware-config.pl


If needed (OK, this one is a bit of a pain, I admit). Symptoms are compiler errors like:
/tmp/vmware-config0/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’
/tmp/vmware-config0/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to ‘int’ in declaration of ‘_syscall1’
[...]
Unable to build the vmmon module.


# Get this or NEWER
$ wget 'http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz'
$ tar xzf vmware-any-any-update113.tar.gz
$ cd vmware-any-any-update113/
$ sudo ./runme.pl




The real key to the above is installing the "build-essential" virtual package, which also installs the "linux-kernel-headers" virtual package. you'll see lots of stuff on the 'Net about installing kernel headers using `uname -r` or whatever. Don't do that! That will work once, for that that kernel. The "linux-kernel-headers" virtual package solves this problem by depending on the latest kernel headers for you.

It's also apparent to me that VMware and/or Ubuntu folks had put in some work to make this stuff work. It's now a LOT better than it was 1+ years ago. But VMware releases simply can't keep pace with Ubuntu kernel releases. I don't know about Player though, maybe it gets less attention?


So the bottom line, for me, is that after a reboot for a new kernel I run "$ sudo vmware-config.pl" and 95% of the time it Just Works and that's it. The only times it doesn't work is when I'm running a really new Ubuntu and VMware hasn't done a release in a bit, then I need vmware-any-any-update*.tar.gz.


HTH,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP            |:::======|        jp{at}jpsdomain{dot}org
My Account, My Opinions     |=========|      http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
Microsoft has single-handedly nullified Moore's Law.
Innate design flaws of Windows make a personal firewall, anti-virus
and anti-malware software mandatory. The resulting software arms race
has effectively flattened Moore's Law on hardware running Windows.
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug