On Fri, Mar 3, 2017 at 10:32 PM, Abhinav Upadhyay <[email protected]> wrote: > Hi, > > I was trying to fire up a NetBSD 7 instance in the Oregon region in > AWS, which is failing to boot. The instance configuration is: > > m3.medium type instance > 30 GB SSD as the root device (tried with magnetic disks too) > AMI id: ami-9c9f8ffd > > The instance was unreachable. The system log as shown by AWS is pasted > below. Did I miss something while configuring the instance? > > > > Xen Minimal OS! > start_info: 0x1110000(VA) > nr_pages: 0xf0000 > shared_inf: 0x7dfa4000(MA) > pt_base: 0x1113000(VA) > nr_pt_frames: 0xd > mfn_list: 0x990000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: root=/dev/sda1 ro 4 > stack: 0x94f860-0x96f860 > MM: Init > _text: 0x0(VA) > _etext: 0x6000d(VA) > _erodata: 0x78000(VA) > _edata: 0x80b00(VA) > stack start: 0x94f860(VA) > _end: 0x98fe68(VA) > start_pfn: 1123 > max_pfn: f0000 > Mapping memory range 0x1400000 - 0xf0000000 > setting 0x0-0x78000 readonly > skipped 0x1000 > MM: Initialise page allocator for 189c000(189c000)-f0000000(f0000000) > MM: done > Demand map pfns at f0001000-20f0001000. > Heap resides at 20f0002000-40f0002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0xf0001000. > Initialising scheduler > Thread "Idle": pointer: 0x20f0002010, stack: 0x2050000 > Initialising xenbus > Thread "xenstore": pointer: 0x20f00027c0, stack: 0x2060000 > Dummy main: start_info=0x96f960 > Thread "main": pointer: 0x20f0002f70, stack: 0x2070000 > "main" "root=/dev/sda1" "ro" "4" > vbd 2049 is hd0 > ******************* BLKFRONT for device/vbd/2049 ********** > > > backend at /local/domain/0/backend/vbd/6425/2049 > 62914560 sectors of 512 bytes > ************************** > [H [J 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/6425/2049 > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, > 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 > 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 7.0 (XEN3_DOMU.201509250726Z) > total memory = 3840 MB > avail memory = 3709 MB > kern.module.path=/stand/amd64/7.0/modules > mainbus0 (root) > hypervisor0 at mainbus0: Xen version 4.2.amazon > vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz, id 0x306e4 > xenbus0 at hypervisor0: Xen Virtual Bus Interface > xencons0 at hypervisor0: Xen Virtual Console Driver > xbd0 at xenbus0 id 2049: Xen Virtual Block Device Interface > xennet0 at xenbus0 id 0: Xen Virtual Network Interface > xennet0: MAC address 0a:9d:75:e7:04:fb > balloon0 at xenbus0 id 0: Xen Balloon driver > balloon0: current reservation: 3932160 KiB > xennet0: using RX copy mode > balloon0: current reservation: 983040 pages => target: 983040 pages > boot device: <unknown> > root device:
Hm, looks like I faced the exact same problem few years back and figured out the solution: https://mail-index.netbsd.org/current-users/2013/11/23/msg023739.html (Essentially, don't remove the second volume when creating the instance). - Abhinav
