search for: xc_dom_pfn_to_ptr

...8 MB, pages 0x8000 pages, 4k each xc_dom_mem_init: 0x8000 pages xc_dom_boot_mem_init: called x86_compat: guest xen-3.0-x86_32p, address size 32 xc_dom_malloc : 128 kB xc_dom_build_image: called xc_dom_alloc_segment: kernel : 0xc1000000 -> 0xc1439000 (pfn 0x1000 + 0x439 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0x439 at 0xb3387000 elf_load_binary: phdr 0 at 0x0xb3387000 -> 0x0xb3686890 elf_load_binary: phdr 1 at 0x0xb3687000 -> 0x0xb3701b64 xc_dom_alloc_segment: ramdisk : 0xc1439000 -> 0xc14d9000 (pfn 0x1439 + 0xa0 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x14...

...xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 10000 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xffffffff81000 000 -> 0xffffffff81b08000 (pfn 0x1000 + 0xb08 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0xb08 at 0x7fdec9b85000 xc: detail: elf_load_binary: phdr 0 at 0x0x7fdec9b85000 -> 0x0x7fdeca0dd000 xc: detail: elf_load_binary: phdr 1 at 0x0x7fdeca0dd000 -> 0x0x7fdeca1460e8 xc: detail: elf_load_binary: phdr 2 at 0x0x7fdeca147000 -> 0x0x7fdeca1597c0 xc: detail:...

...est xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 512 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xffffffff81000000 -> 0xffffffff816fa000 (pfn 0x1000 + 0x6fa pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0x6fa at 0x7f3a5921f000 xc: detail: elf_load_binary: phdr 0 at 0x0x7f3a5921f000 -> 0x0x7f3a5964c000 xc: detail: elf_load_binary: phdr 1 at 0x0x7f3a5964c000 -> 0x0x7f3a59722150 xc: detail: elf_load_binary: phdr 2 at 0x0x7f3a59723000 -> 0x0x7f3a59723888 xc: detail:...

Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed,

...arams = dom->kernel_blob; + + elf->dest = xc_dom_seg_to_ptr(dom, &dom->kernel_seg); + elf_load_binary(elf); + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 1); + + bootparams_pfn = xc_dom_alloc_page(dom, "bootparams"); + bootparams = xc_dom_pfn_to_ptr(dom, bootparams_pfn, 1); + memset(bootparams, 0, sizeof(*bootparams)); + + memcpy(&bootparams->hdr, &bzparams->hdr, sizeof(bootparams->hdr)); + + dom->bootparams_pfn = bootparams_pfn; + + return 0; +} + +static struct xc_dom_loader bzimage_loader = { + .name = &qu...

...arams = dom->kernel_blob; + + elf->dest = xc_dom_seg_to_ptr(dom, &dom->kernel_seg); + elf_load_binary(elf); + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 1); + + bootparams_pfn = xc_dom_alloc_page(dom, "bootparams"); + bootparams = xc_dom_pfn_to_ptr(dom, bootparams_pfn, 1); + memset(bootparams, 0, sizeof(*bootparams)); + + memcpy(&bootparams->hdr, &bzparams->hdr, sizeof(bootparams->hdr)); + + dom->bootparams_pfn = bootparams_pfn; + + return 0; +} + +static struct xc_dom_loader bzimage_loader = { + .name = &qu...

...arams = dom->kernel_blob; + + elf->dest = xc_dom_seg_to_ptr(dom, &dom->kernel_seg); + elf_load_binary(elf); + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 1); + + bootparams_pfn = xc_dom_alloc_page(dom, "bootparams"); + bootparams = xc_dom_pfn_to_ptr(dom, bootparams_pfn, 1); + memset(bootparams, 0, sizeof(*bootparams)); + + memcpy(&bootparams->hdr, &bzparams->hdr, sizeof(bootparams->hdr)); + + dom->bootparams_pfn = bootparams_pfn; + + return 0; +} + +static struct xc_dom_loader bzimage_loader = { + .name = &qu...

...der: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 1024 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x9a0000 (pfn 0x0 + 0x9a0 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x0+0x9a0 at 0x7f18be2e9000 xc: detail: elf_load_binary: phdr 0 at 0x0x7f18be2e9000 -> 0x0x7f18bec88f60 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x9a0000 -> 0xaa0000 (pfn 0x9a0 + 0x100 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn...

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

Where is the code that maps the kernel of a DomU into memory? i.e, when you do a xm create <config file> what code is called to actually map the kernel into memory? Is it a python script or is it re-directed to Dom0 to do? Thanks. -Brian --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.