search for: virt_kend

...s as domU kernel, but the problem occurs even for linux-2.6.18.1 pv kernel as domu kernel. xend.log shows [2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it.... after doing some preliminary investigation i found out the problem is due to the change in virt_kend value, being derived from elf->pend value. Due to this domU is throwing seg_faults When things were fine the value of virt_kend used to be 0x1e1a4, but now virt_kend is having value 0x1dfa4. I have no clue why this is happening suddenly. Any clue or hints would be very helpful. here is a sa...

Hi! If there is a string table for section headers, it also gets loaded. Therefore take it into account in size calculation for kernel symtab. Also there is no need to call elf_set_verbose() a second time after elf_init() (First call happens within elf_init()). Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Keir: Can you also apply changeset 15672 and this patch to Xen

...de_kernel" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff806e2f04 (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff806e2f04 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007a000000->000000007c000000 (4...

..._LOW = 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff82197000 (XEN) virt_entry = 0xffffffff81ac41e0 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2197000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000...

...map|pae_pgdir_above_4gb|supervisor_mode_kernel" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff807014e4 (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff807014e4 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003c000000->000000003d000000 (234203 pages to be alloca...

...LOADER = "generic" (XEN) elf_xen_addr_calc_check: ELF_PADDR_OFFSET unset, using 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xc0000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xc0000000 (XEN) virt_kstart = 0xc0400000 (XEN) virt_kend = 0xc0865000 (XEN) virt_entry = 0xc075e000 (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0x865000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (477028 pages to be allocated) (XEN) V...

...e_k ernel" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff8075fe8c (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff8075fe8c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000222000000->0000000224000000 (12...

..._parse_note: PAE_MODE = "yes" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xc0000000 (XEN) elf_paddr_offset = 0xc0000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xc0400000 (XEN) virt_kend = 0xc07ec000 (XEN) virt_entry = 0xc0400000 (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0400000 -> 0xc07ec000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (253952 pages to be allocated) (XEN...

...n_parse_note: unknown xen elf note (0xd) elf_xen_parse_note: LOADER = "generic" elf_xen_parse_note: SUSPEND_CANCEL = 0x1 elf_xen_addr_calc_check: addresses: virt_base = 0xc0000000 elf_paddr_offset = 0x0 virt_offset = 0xc0000000 virt_kstart = 0xc1000000 virt_kend = 0xc1439000 virt_entry = 0xc1000000 xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc1000000 -> 0xc1439000 xc_dom_mem_init: mem 128 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_m...

...+ + /* parse binary and get xen meta info */ + elf_parse_binary(elf); + if ( (rc = elf_xen_parse(elf, &dom->parms)) != 0 ) + return rc; + + /* find kernel segment */ + dom->kernel_seg.vstart = dom->parms.virt_kstart; + dom->kernel_seg.vend = dom->parms.virt_kend; + + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 0); + + dom->guest_type = xc_dom_guest_type(dom, elf); + xc_dom_printf("%s: %s: 0x%" PRIx64 " -> 0x%" PRIx64 "\n", + __FUNCTION__, dom->guest_type, +...

...+ + /* parse binary and get xen meta info */ + elf_parse_binary(elf); + if ( (rc = elf_xen_parse(elf, &dom->parms)) != 0 ) + return rc; + + /* find kernel segment */ + dom->kernel_seg.vstart = dom->parms.virt_kstart; + dom->kernel_seg.vend = dom->parms.virt_kend; + + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 0); + + dom->guest_type = xc_dom_guest_type(dom, elf); + xc_dom_printf("%s: %s: 0x%" PRIx64 " -> 0x%" PRIx64 "\n", + __FUNCTION__, dom->guest_type, +...

...+ + /* parse binary and get xen meta info */ + elf_parse_binary(elf); + if ( (rc = elf_xen_parse(elf, &dom->parms)) != 0 ) + return rc; + + /* find kernel segment */ + dom->kernel_seg.vstart = dom->parms.virt_kstart; + dom->kernel_seg.vend = dom->parms.virt_kend; + + if ( dom->parms.bsd_symtab ) + xc_dom_load_elf_symtab(dom, elf, 0); + + dom->guest_type = xc_dom_guest_type(dom, elf); + xc_dom_printf("%s: %s: 0x%" PRIx64 " -> 0x%" PRIx64 "\n", + __FUNCTION__, dom->guest_type, +...

..._LOW = 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff81fd2000 (XEN) virt_entry = 0xffffffff81a89210 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1fd2000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000...

...xen_parse_note: PADDR_OFFSET = 0x0 xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0xffffffff80000000 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0xffffffff80000000 xc: detail: virt_kstart = 0xffffffff81000000 xc: detail: virt_kend = 0xffffffff81b08000 xc: detail: virt_entry = 0xffffffff815d5210 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff81000000 -> 0xffffffff81b08000 domainbuilder: detail: xc_dom_mem_init: mem 5000 MB, pa...

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,

...s: (XEN) [2012-06-17 00:22:20] virt_base = 0xffffffff80000000 (XEN) [2012-06-17 00:22:20] elf_paddr_offset = 0x0 (XEN) [2012-06-17 00:22:20] virt_offset = 0xffffffff80000000 (XEN) [2012-06-17 00:22:20] virt_kstart = 0xffffffff81000000 (XEN) [2012-06-17 00:22:20] virt_kend = 0xffffffff8205f000 (XEN) [2012-06-17 00:22:20] virt_entry = 0xffffffff81cfb200 (XEN) [2012-06-17 00:22:20] p2m_base = 0xffffffffffffffff (XEN) [2012-06-17 00:22:20] Xen kernel: 64-bit, lsb, compat32 (XEN) [2012-06-17 00:22:20] Dom0 kernel: 64-bit, PAE, lsb, paddr 0...

Hi, I want to try Xen on ARMv8 Simulator. Can you please provide guidance?. I am looking for information about sources, build and procedure to launch Xen on ARMv8 Thanks & Regards Vijay

...e_k ernel" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff8075fe8c (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff8075fe8c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000222000000->0000000224000000 (12...

...xen_parse_note: PADDR_OFFSET = 0x0 xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0xffffffff80000000 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0xffffffff80000000 xc: detail: virt_kstart = 0xffffffff81000000 xc: detail: virt_kend = 0xffffffff816fa000 xc: detail: virt_entry = 0xffffffff8151c200 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff81000000 -> 0xffffffff816fa000 domainbuilder: detail: xc_dom_mem_init: mem 256 MB, pag...

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not