[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] mirage, mirage-www, xen and ec2
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |