[5932] in Release_7.7_team
Re: Why would Athena networking die when its virtual image is
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Mar 14 00:24:07 2008
From: Greg Hudson <ghudson@MIT.EDU>
To: Steve Landry <sml@mit.edu>
Cc: William Cattey <wdc@mit.edu>, release-team@mit.edu, vmware-release@mit.edu,
"Michael R. Gettes" <gettes@mit.edu>
In-Reply-To: <47D9D876.5000702@mit.edu>
Content-Type: text/plain
Date: Fri, 14 Mar 2008 00:23:31 -0400
Message-Id: <1205468611.5889.5.camel@error-messages.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Flag: NO
X-Spam-Score: 0.00
Oh, it works okay; the impractically is putting it out there as an easy
way of running Athena software on a Windows PC or Mac, because we can't
automatically provision an IP address for the VM. (There might also be
issues related to distributing an image of that size and keeping it up
to date.)
Unfortunately I do not have any insight into Bill's question about
networking and resumed VM images.
On Thu, 2008-03-13 at 21:44 -0400, Steve Landry wrote:
> I thought I saw a previous email from someone on my team (Greg?) noting
> the impracticalities of running the cluster OS on a VM image.
>
> ~ Steve
>
>
> William Cattey wrote:
> > I'm gonna start off asking this question to Release Team, and then over
> > time converge on the best place to ask such questions.
> >
> > Alex Prengel and I are experimenting with Athena in a VMware image.
> > Yesterday he brought a problem to me that I have reproduced myself:
> >
> > Repeat by:
> >
> > Start Athena VMware image.
> > Log in.
> > Suspend image.
> > Let sit over night.
> > Resume image.
> >
> > Actual behavior:
> >
> > The network is down.
> > AFS is dead.
> > A little while later the panel disappears with the helpful message,
> > "Killed"
> > in the console window.
> >
> > Expected behavior:
> >
> > Suspend and resume a few minutes later gives a fully functioning Athena
> > machine,
> > picking up where I left off.
> >
> > I was able to recover by:
> >
> > su
> > /etc/sysconfig/network-scripts/ifdown eth0
> > /etc/sysconfig/network-scripts/ifup eth0
> > /etc/init.d/openafs stop
> > /etc/init.d/openafs start
> >
> > But since panel had died I also had to log out and log back in.
> >
> > ----
> >
> > Might this be an interaction with if-plugd?
> >
> > I'm going to test to see if this is an RHEL 4 issue by doing an RHEL 4
> > install and repeating the test (first without AFS, then with AFS.)
> >
> > I'd be grateful for conjectures as to what might be happening.
> >
> > -Bill
> >
> > ----
> >
> > William Cattey
> > Linux Platform Coordinator
> > MIT Information Services & Technology
> >
> > N42-040M, 617-253-0140, wdc@mit.edu
> > http://web.mit.edu/wdc/www/
> >
> >
