[Testbed-admins] Can't get interactive mode while trying to test images

[Ben Burnett <bburnett@atcorp.com>]

Leigh,
     I'm having this same problem again where my nodes don't give me
the option to go into interactive mode.  I have 2 pc's with test
images (pc1 and pc2)  pc1 was in hwdown and pc2 was in reloading
neither gave me the interactive mode option.  I moved them both to
hwdown per your commands from June and they show in hwdown but still
no interactive mode option.   What Am I missing?

Thanks,
--Ben

Ben Burnett
  R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
    network monitoring and data visualization
  ATC (Architecture Technology Corporation)   http://www.atcorp.com/
  bburnett@atcorp.com                         (952) 829-5864 x167
  --------Views expressed are mine and not those of ATC--------
  Personal:
    ben@burnett.ws                            http://www.burnett.ws/
http://ben.burnett.ws/
http://www.linkedin.com/in/benburnett



On Wed, Jun 24, 2009 at 3:30 PM, Leigh Stoller<stoller@flux.utah.edu> wrote:
>> It is in "reloading" I'm guessing it needs to be in "hwdown"...  do
>> I move the node into hwdown with nfree? or is there another way?
>
> If it is in reloading, you should be able to boot it. Take a look at
> /usr/testbed/log/bootinfo.log to see if pxeboot is getting far enough
> to query it.
>
> But probably best to move it to hwdown:
>
> boss> wap sched_reserve emulab-ops hwdown pcXXX
> boss> wap nfree emulab-ops reloading pcXXX
>
>> So what do I lose by using pxeboot.emu-null instead of pxeboot.emu-sio
>> or pxeboot.emu-vga?
>
> I think it means no console, output goes into the bit bucket. :-)
>
> Lbs
>
>
>