Re: NetBSD on AWS

[Abhinav Upadhyay <er.abhinav.upadhyay%gmail.com@localhost>]

On Thu, Nov 14, 2013 at 9:21 PM, Eric Haszlakiewicz 
<erh%nimenees.com@localhost> wrote:
> Abhinav Upadhyay <er.abhinav.upadhyay%gmail.com@localhost> wrote:
>>Hi,
>>
>>I am trying to run NetBSD in AWS. I have tried launching instances
>>with 3 different NetBSD AMIs (6.1.2, 6.1.1, and 6.0), all 64 bit
>>variants. However, upon starting up the instance, I am unable to
>>connect to it using ssh. Port 22 is open in the security group
>>configurations.
>>
>>I tried to probe the ports open in the instance using nmap. As per
>>nmap, only port 25 is open in the instance.
>
> Did you manage to get this working?
> I don't think the standard install has anything running on port 25.
> Are you sure you're connecting to the right IP address?  Unless you've 
> configured a dedicated one you can get allocated a new one every time you 
> start up.

Yes, I got it working. When creating the instance, I was removing the
extra EBS volume that was being attached (/dev/sda2 in the AWS
console). I thought it was a tactic by AWS to draw extra money for
extra storage. However, it turns out that the 2nd volume is being used
as the root partition?

I am pasting the System log output from the instance which was not
reachable via SSH. It might be of some use:

Xen Minimal OS!
  start_info: 0xa01000(VA)
    nr_pages: 0x26700
  shared_inf: 0x7e4c2000(MA)
     pt_base: 0xa04000(VA)
nr_pt_frames: 0x9
    mfn_list: 0x967000(VA)
   mod_start: 0x0(VA)
     mod_len: 0
       flags: 0x0
    cmd_line: root=/dev/sda1 ro 4
  stack:      0x946780-0x966780
MM: Init
      _text: 0x0(VA)
     _etext: 0x61e65(VA)
   _erodata: 0x76000(VA)
     _edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
       _end: 0x966d34(VA)
  start_pfn: a10
    max_pfn: 26700
Mapping memory range 0xc00000 - 0x26700000
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for b3e000(b3e000)-0(26700000)
MM: done
Demand map pfns at 26701000-36701000.
Heap resides at 36702000-76702000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x26701000.
Initialising scheduler
Thread "Idle": pointer: 0x36702008, stack: 0xbf0000
Initialising xenbus
Thread "xenstore": pointer: 0x36702478, stack: 0x26600000
Dummy main: start_info=0x966880
Thread "main": pointer: 0x367028e8, stack: 0x26610000
"main" "root=/dev/sda1" "ro" "4"
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********


backend at /local/domain/0/backend/vbd/3711/2049
Failed to read /local/domain/0/backend/vbd/3711/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/3711/2049/feature-flush-cache.
62914560 sectors of 0 bytes
**************************
  Booting 'NetBSD AMI'



root (hd0)

 Filesystem type is ext2fs, using whole disk

kernel /boot/netbsd root=xbd1



xc_dom_probe_bzimage_kernel: kernel is not a bzImage
close blk: backend at /local/domain/0/backend/vbd/3711/2049
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,

    2006, 2007, 2008, 2009, 2010, 2011, 2012

    The NetBSD Foundation, Inc.  All rights reserved.

Copyright (c) 1982, 1986, 1989, 1991, 1993

    The Regents of the University of California.  All rights reserved.


NetBSD 6.1.2 (XEN3PAE_DOMU)

total memory = 615 MB

avail memory = 597 MB

mainbus0 (root)

hypervisor0 at mainbus0: Xen version 3.4.3.amazon

vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz, id 0x206d7

xenbus0 at hypervisor0: Xen Virtual Bus Interface

xencons0 at hypervisor0: Xen Virtual Console Driver

npx0 at hypervisor0: using exception 16

xbd0 at xenbus0 id 2049: Xen Virtual Block Device Interface

xennet0 at xenbus0 id 0: Xen Virtual Network Interface

xennet0: MAC address 0a:8e:2f:33:6e:3f

balloon0 at xenbus0 id 0: Xen Balloon driver

balloon0: current reservation: 629760 KiB

xennet0: using RX copy mode

balloon0: current reservation: 157440 pages => target: 157440 pages

boot device: <unknown>

root device: