Re: [Testbed-admins] Can not bring up the first node for a new Emulab site

[Mike Hibler <mike@flux.utah.edu>]

Any chance you are getting a DHCP reply over de0?

There should be some logfiles from the DHCP process in /var/tmp.
What is in /var/tmp/netif-emulab.log?

On Wed, Aug 05, 2009 at 07:52:21PM -0400, chunhui Zhang(Evan) wrote:
> I got to the point that,
> ----------------------------------------
> Attempting boot of: /tftpboot/frisbee
> Loading /boot/defaults/loader.conf
> /boot/kernel text= ............................................etc
> /boot/acpi.ko text= ..........................................etc
> 
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel]...
> ...
> ...
> ...
> Setting hostname: .
> Emulab looking for control net among: de0 xl0 ...
> xl0: link state changed to UP
> Emulab control net is de0
> ...
> ...
> ...
> Starting local daemons: Playing Frisbee ...
> Authenticated IPOD enabled from 192.168.56.3/255.255.255.255
> Unable to get address for loading image
> Failed to load disk, dropping to login prompt at Wed Aug  5 17:36:44 MDT
> 2009
> ...
> ...
> ...
> FreeBSD/i386 (pc1) (console)
> 
> login:
> -------------------------------------------------------------------------------------
> 
> Above message tells me the control net is de0 which is not true. xl0 is the
> one I used as control NIC and the DB also have the knowledge that. My node
> was booted from xl0 and de0 do not have pxe boot ability at all.  Then I
> logged in through the dropped prompt and did 'cat /etc/testbed/controlif',
> it showed 'xl0'. I traced through the source code and find out 'tmcc
> loadinfo' gave me nothing. I am not sure how to debug this issue further. So
> I am wondering do you see the similar issue before? And any suggestions?
> 
> Thanks a lot,
> Evan Zhang
> 
> 
> On Tue, Aug 4, 2009 at 10:42 PM, chunhui Zhang(Evan) <chyz198@gmail.com>wrote:
> 
> >
> >
> > On Tue, Aug 4, 2009 at 10:26 PM, Mike Hibler <mike@flux.utah.edu> wrote:
> >
> >> On Tue, Aug 04, 2009 at 09:40:45PM -0400, chunhui Zhang(Evan) wrote:
> >> > On Mon, Aug 3, 2009 at 6:05 PM, Mike Hibler <mike@flux.utah.edu> wrote:
> >> >
> >> > > I will jump in the middle here, please excuse me if you have already
> >> > > answered
> >> > > any of my questions!
> >> > >
> >> > > In one of your earlier messages you had some text that "came out", was
> >> >
> >> >
> >> > > that on the VGA or serial line?  It doesn't matter, as long as we have
> >> a
> >> > > console that works.
> >> > >
> >> >
> >> > >
> >> > > Do I understand correctly that the 47 MFS boots on the PIII node but
> >> the
> >> > > 62 version does not?  Strange...
> >> > >
> >> > > No matter, let's go back to the 62 MFS, the 47 is a loser long term.
> >> > >  Verify
> >> > > that you have the right console selected in
> >> > > /tftpboot/freebsd.newnode/boot/loader.conf.orig
> >> >
> >> >
> >> > By changing the option 'console="comconsole"' to 'console="vidconsole"'
> >> in
> >> > loader.conf.orig solved my problem!
> >> > Thank you so much!  BTW, where can I find the document talking about
> >> this
> >> > configuration?
> >> >
> >> >
> >> > Evan Zhang
> >> >
> >>
> >> How much of your problem did it solve?  Will the MFS boot on the newer
> >> node?
> >>
> >
> >  Yes, all three MFSs can boot now.
> >
> >>
> >> Re: documentation, I thought that console config was in the README for the
> >> MFS
> >> but it isn't!  We need to fix that.
> >
> >
> > Evan
> >
> >
> >

> _______________________________________________
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins