[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mirage, mirage-www, xen and ec2



I added an ICMP rule for 0.0.0.0/0 and applied those changes but I still can't ping my ec2 public IP (I didn't restart the instance but judging from what I read I don't think I have to):

PING ec2-54-242-80-16.compute-1.amazonaws.com (54.242.80.16) 56(84) bytes of data.
^C
177 packets transmitted, 0 received, 100% packet loss, time 176700ms

Also, this may be obvious, but I wanted to confirm that the DHCP address mirage sees is my ec2 private IP in case that sheds any light on where things may be breaking down:
Private DNS:ip-10-116-221-145.ec2.internal
Product Codes:
Private IPs:10.116.221.145

--Mark

Mark Thurman
mthurman@xxxxxxxxx


On Thu, Oct 18, 2012 at 12:18 AM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
Can you ping it?

For xen.openmirage.org, I have:
PING xen.openmirage.org (204.236.217.197): 56 data bytes
64 bytes from 204.236.217.197: icmp_seq=0 ttl=13 time=92.253 ms
64 bytes from 204.236.217.197: icmp_seq=1 ttl=13 time=90.902 ms

With firewall rules:

22 tcp0.0.0.0/0
53tcp 0.0.0.0/0
80tcp 0.0.0.0/0
53udp 0.0.0.0/0
-1icmp 0.0.0.0/0

I'll try it all myself tomorrow on a Xen box, and then on EC2....

-anil

On 18 Oct 2012, at 00:11, Mark Thurman <mthurman@xxxxxxxxx> wrote:

To the best of my knowledge, I've got port 80 open with Amazon (sorry for the screenshot, I couldn't figure out which ec2 command line tool gave me the same info). I opened those ports in the default security group before this instance was created.

I could be doing something really dumb though--like I said, I'm pretty new to all these moving pieces.

--Mark

Mark Thurman
mthurman@xxxxxxxxx


On Thu, Oct 18, 2012 at 12:01 AM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
It looks like you have received a DHCP offer:
> DHCP: offer received: 10.116.221.145

Have you opened up the firewall on EC2 correctly? This bit can be
a bit confusing, as you need to specifically open up port 80 when you
create the VM. ÂIt doesn't always work me if I reconfigure this after
the VM starts...

-anil


On 17 Oct 2012, at 23:56, Mark Thurman <mthurman@xxxxxxxxx> wrote:

> I just tried DHCP and booting up a new instance and I still can't connect (http://ec2-54-242-80-16.compute-1.amazonaws.com/):
>
> MAC: 12:31:3D:02:D2:67
> Âsg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false
> Manager: plug 0
> Manager: plug done, to listener
> Manager: VIF 0 to DHCP
> DHCP: waiting for first offer
> DHCP: start discovery
> Sending DHCP broadcast
> DHCP: input ciaddr 0.0.0.0 yiaddr 10.116.221.145 siaddr 0.0.0.0 giaddr 0.0.0.0 chaddr 1=ïg sname ip-10-116-220-170.auto.iad.ec2.substrate file
> DHCP: offer received: 10.116.221.145
> Sending DHCP broadcast
> DHCP: input ciaddr 0.0.0.0 yiaddr 0.0.0.0 siaddr 169.254.1.0 giaddr 0.0.0.0 chaddr 1=ïg sname Âfile
> DHCP: ack not for us
> Devices: [Xen.Blkif:2051] provider plug
> Xen.Blkif: create 2051
> Blkfront.create; vdev=2051
> Devices: [Xen.Blkif:2050] provider plug
> Xen.Blkif: create 2050
> Blkfront.create; vdev=2050
> Devices: [Xen.Blkif:2049] provider plug
> Xen.Blkif: create 2049
> Blkfront.create; vdev=2049
> Blkback can only use a single-page ring
> Negotiated a singe-page ring
> Blkback can only use a single-page ring
> Negotiated a singe-page ring
> Blkback can only use a single-page ring
> Negotiated a singe-page ring
> state=InitWait
> Blkfront features: barrier=false removable=true sector_size=512 sectors=1835008
> Xen.Blkif: success
> Devices: [Xen.Blkif:2051] no waiters
> state=InitWait
> Blkfront features: barrier=false removable=true sector_size=512 sectors=312705024
> Xen.Blkif: success
> Devices: [Xen.Blkif:2050] no waiters
> state=InitWait
> Blkfront features: barrier=false removable=true sector_size=512 sectors=10240
> Xen.Blkif: success
> Devices: [Xen.Blkif:2049] no waiters
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
> ARP: who-has 10.116.221.145?
>
> Thanks for your quick response!
>
> --Mark
>
>
> On Wed, Oct 17, 2012 at 11:39 PM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> Hi Mark,
>
> The default mirage-www is configured to a static IP. ÂTry modifying
> mirage-www/src/server.ml and changing the:
>
> Â Â Net.Manager.configure interface (`IPv4 ip) >>
>
> line to
>
> Â Â Net.Manager.configure interface `DHCP >>
>
> ...and this will pick up an IP address on EC2.
>
> If you've run it locally, did you already make this change? ÂDoing an
> auto-update of mirage-www to EC2 is on my todo list, so I'll check
> manually tomorrow if it works with the latest trees or not. Dave, have
> you tried this recently?
>
> -anil
>
>
> On 17 Oct 2012, at 22:50, Mark Thurman <mthurman@xxxxxxxxx> wrote:
>
> > I've played some with mirage locally this week and decided I'd try to put the sample mirage-www on ec2 using Xen. I can run it locally just fine and other computers on my network can connect to it. I roughly followed the instructions on the wiki (http://www.openmirage.org/wiki/xen-boot) and after tweaking the script slightly, I'm able to bundle, unload, and boot up and ec2 instance with a mirage kernel. The instance launches just fine and I can see output from various mirage systems in the ec2 system log output. However, when I try to connect to my ec2 host (after opening port 80 in the ec2 console), my web browser just hangs.
> >
> > Any ideas? I'm pretty new to every piece of this puzzle so I'm not really sure where to begin debugging the mnirage on xen networking stack. I'm attaching the output from the ec2 log in case that's helpful to start.
> >
> > I know that this isn't much to go on, so any pointers or help to turn on more debugging output would be appreciated.
> >
> > -----BEGIN LOG
> > xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> > close blk: backend at /local/domain/0/backend/vbd/659/2049
> > close blk: backend at /local/domain/0/backend/vbd/659/2050
> > close blk: backend at /local/domain/0/backend/vbd/659/2051
> > kernel.c: Mirage OS!
> > kernel.c: Â start_info: 0x1586000(VA)
> > kernel.c: Â Â nr_pages: 0x6a400
> > kernel.c: Â shared_inf: 0xbee14000(MA)
> > kernel.c: Â Â Âpt_base: 0x1589000(VA)
> > kernel.c: nr_pt_frames: 0xf
> > kernel.c: Â Â mfn_list: 0x1234000(VA)
> > kernel.c: Â Âmod_start: 0x0(VA)
> > kernel.c: Â Â Âmod_len: 0
> > kernel.c: Â Â Â Âflags: 0x0
> > kernel.c: Â Â cmd_line:
> > x86_setup.c: Â stack: Â Â Â0x233920-0xa33920
> > mm.c: MM: Init
> > x86_mm.c: Â Â Â _text: 0x0(VA)
> > x86_mm.c: Â Â Â_etext: 0xf3367(VA)
> > x86_mm.c: Â Â_erodata: 0x101000(VA)
> > x86_mm.c: Â Â Â_edata: 0x216940(VA)
> > x86_mm.c: stack start: 0x233920(VA)
> > x86_mm.c: Â Â Â Â_end: 0x1234000(VA)
> > x86_mm.c: Â start_pfn: 159b
> > x86_mm.c: Â Â max_pfn: 6a400
> > x86_mm.c: Mapping memory range 0x1800000 - 0x6a400000
> > x86_mm.c: setting 0x0-0x101000 readonly
> > x86_mm.c: skipped 0x1000
> > mm.c: MM: Initialise page allocator for 0x18e2000 -> 0x6a400000
> > mm.c: MM: done
> > x86_mm.c: Demand map pfns at 6a401000-206a401000.
> > gnttab_init: 2047
> > gnttab_stubs.c: gnttab_table mapped at 0x6a401000
> > ENT: Breaking up is easy to do (with OPAM)
> > ENT: Building a "xenstore stub domain" with Mirage
> > ENT: Connected Cloud Control: OpenFlow in Mirage
> > ENT: An Outing to CUFP 2011
> > ENT: A Spring Wiki Cleaning
> > ENT: Self-hosting Mirage website
> > ENT: Installation
> > ENT: OCaml Installation
> > ENT: Getting Started with Lwt threads
> > ENT: Portable Regular Expressions
> > ENT: Delimited Continuations vs Lwt for Threads
> > ENT: Running Mirage Xen kernels
> > ENT: Tech Talks
> > ENT: Papers and Related Work
> > ENT: DNS Performance Tests
> > ENT: Hello Mirage World
> > ENT: Source code layout
> > ENT: Developing the Mirage networking stack on UNIX
> > ENT: COW: OCaml on the Web
> > ENT: Introduction to HTCaML
> > Devices: [templates] sleeping
> > ..omitted 72 lines...
> > Devices: [templates] sleeping
> > Devices: [static] sleeping
> > Devices: [templates] provider start
> > Devices: [templates:templates] provider plug
> > Devices: [templates:templates] waking waiters
> > Devices: [templates] waking
> > ...omitted 72 lines...
> > Devices: [templates] waking
> > Devices: [static] provider start
> > Devices: [static:static] provider plug
> > Devices: [static:static] waking waiters
> > Devices: [static] waking
> > Manager: create
> > Manager: init done
> > Devices: [Xen.Blkif] provider start
> > found: num=0 backend-id=0
> > Netfront.create: id=0 domid=0
> >
> > MAC: 12:31:39:1C:34:A6
> > Âsg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false
> > Manager: plug 0
> > Manager: plug done, to listener
> > Manager: VIF 0 to 10.0.0.2 nm 255.255.255.0 gw [10.0.0.1]
> > ARP: sending gratuitous from 10.0.0.2
> > Devices: [Xen.Blkif:2051] provider plug
> > Xen.Blkif: create 2051
> > Blkfront.create; vdev=2051
> > Devices: [Xen.Blkif:2050] provider plug
> > Xen.Blkif: create 2050
> > Blkfront.create; vdev=2050
> > Devices: [Xen.Blkif:2049] provider plug
> > Xen.Blkif: create 2049
> > Blkfront.create; vdev=2049
> > Blkback can only use a single-page ring
> > Negotiated a singe-page ring
> > Blkback can only use a single-page ring
> > Negotiated a singe-page ring
> > Blkback can only use a single-page ring
> > Negotiated a singe-page ring
> > state=InitWait
> > Blkfront features: barrier=false removable=false sector_size=512 sectors=1835008
> > Xen.Blkif: success
> > Devices: [Xen.Blkif:2051] no waiters
> > state=InitWait
> > Blkfront features: barrier=false removable=false sector_size=512 sectors=312705024
> > Xen.Blkif: success
> > Devices: [Xen.Blkif:2050] no waiters
> > state=InitWait
> > Blkfront features: barrier=false removable=false sector_size=512 sectors=10240
> > Xen.Blkif: success
> > Devices: [Xen.Blkif:2049] no waiters
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > ARP: who-has 10.110.50.84?
> > -----END LOG
> >
> > Thanks,
> > Mark
> >
>
>


<Screen shot 2012-10-18 at 10-18-12 Â 12.08.10 AM.png>



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.