[7673] in testers
Re: vmware interfaces on linux box
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Dec 26 11:38:21 2007
Date: Wed, 26 Dec 2007 11:37:17 -0500
Message-Id: <200712261637.lBQGbHNo004268@equal-rites.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
CC: testers <testers@MIT.EDU>
In-reply-to: <1198477101.6088.24.camel@error-messages.mit.edu>
> Unfortunately, the vmware-config script does not appear to have
> command-line options to control individual network choices. That
> leaves me in a bad situation.
Well, the good news is that I figured out a moderately clean way to
run vmware-config without creating the NAT and host-only interfaces.
The bad news is that I did not find an easy way to clean up the
interfaces on alpha and beta machines. The manual procedure is easy
enough. Two options:
Option 1 is, before updating to 9.4.46:
rpm -e VMwarePlayer
Option 2 is, after updating to 9.4.46:
rpm -e VMwarePlayer
cd /afs/dev.mit.edu/system/rhlinux/rhel-4-updates/vmware.com
rpm -Uvh VMwarePlayer-2.0.2-59824.i386.rpm
# Reboot if you want VMware Player configured
Note that 9.4.46 doesn't exist yet. That should be fixed within a
day. I will probably write a fix-vmware script for the release locker
after I put it out.
To see if you have the unwanted interfaces, run "ifconfig -a". If you
see vmnet1 and vmnet8, you have them. If you don't see vmnet1 and
vmnet8, you're all set.
