Re: debugging non-working microkernel

[William Le Ferrand <warnegia@xxxxxxxxx>]

Just in case, here is what the ec2.sh script says: 

buntu@ip-172-31-29-20:~/dev/mirage/mirage-www/src$ ./../../mirari/scripts/ec2.sh _build/main.xen 

+ NAME=sumomirage2

+ BUCKET=sumomirage-b1

+ REGION=us-west-2

+ KERNEL=aki-fc37bacc

+ IMG=sumomirage2.img

+ MNT=/mnt/mirage

+ SUDO=sudo

+ '[' '!' -e _build/main.xen ']'

+ sudo mkdir -p /mnt/mirage

+ rm -f sumomirage2.img

+ dd if=/dev/zero of=sumomirage2.img bs=1M count=5

5+0 records in

5+0 records out

5242880 bytes (5.2 MB) copied, 0.00719671 s, 729 MB/s

+ sudo mke2fs -F -j sumomirage2.img

mke2fs 1.42.5 (29-Jul-2012)

Discarding device blocks: done                            

Filesystem label=

OS type: Linux

Block size=1024 (log=0)

Fragment size=1024 (log=0)

Stride=0 blocks, Stripe width=0 blocks

1280 inodes, 5120 blocks

256 blocks (5.00%) reserved for the super user

First data block=1

Maximum filesystem blocks=5242880

1 block group

8192 blocks per group, 8192 fragments per group

1280 inodes per group

Allocating group tables: done                            

Writing inode tables: done                            

Creating journal (1024 blocks): done

Writing superblocks and filesystem accounting information: done

+ sudo mount -o loop sumomirage2.img /mnt/mirage

+ sudo mkdir -p /mnt/mirage/boot/grub

+ echo default 0

+ echo timeout 1

+ echo title Mirage

+ echo ' root (hd0)'

+ echo ' kernel /boot/mirage-os.gz'

+ sudo mv menu.lst /mnt/mirage/boot/grub/menu.lst

+ sudo sh -c 'gzip -c _build/main.xen > /mnt/mirage/boot/mirage-os.gz'

+ sudo umount -d /mnt/mirage

loop: can't delete device /dev/loop0: No such device or address

+ rm -rf ec2_tmp

+ mkdir ec2_tmp

+ ec2-bundle-image -i sumomirage2.img -k /home/ubuntu/keys/pk-2XQRC5CZMJFO6AP4WE5MLIWYXGRG4KC7.pem -c /home/ubuntu/keys/cert-2XQRC5CZMJFO6AP4WE5MLIWYXGRG4KC7.pem -u 655652860901 -d ec2_tmp -r x86_64 --kernel aki-fc37bacc

Bundling image file...

Splitting ec2_tmp/sumomirage2.img.tar.gz.enc...

Created sumomirage2.img.part.0

Generating digests for each part...

Digests generated.

Creating bundle manifest...

ec2-bundle-image complete.

+ ec2-upload-bundle -b sumomirage-b1 -m ec2_tmp/sumomirage2.img.manifest.xml -a <---> -s <--->

Uploading bundled image parts to the S3 bucket sumomirage-b1 ...

Uploaded sumomirage2.img.part.0

Uploading manifest ...

Uploaded manifest.

Bundle upload completed.

+ rm -rf ec2_tmp

+ ec2-register sumomirage-b1/sumomirage2.img.manifest.xml -n sumomirage2 --region us-west-2

On Tue, Sep 17, 2013 at 4:50 PM, William Le Ferrand <warnegia@xxxxxxxxx> wrote:

hello

I followed the mirage-www tutorial and managed to get the website working on a local linux box. 

I also compiled it to a microkernel and launched it on a S3-backed EC2 instance (m1.large), but nothing happens : nothing in the instance logs ("get system logs" in the AWS dashboard) and no website on port 80. 

What would you suggest to do next :) ? 

Thanks

William

--
William Le Ferrand

Mobile : (+1) (415) 683-1484

Web : http://williamleferrand.github.com/

--
William Le Ferrand

Mobile : (+1) (415) 683-1484

Web : http://williamleferrand.github.com/