search for: xc_dom_mem_init

...s error whenever i try to create a vm. I checked /var/log/xen/.log and here is some of the stuff i get: *domain-builder-ng.log* virt_entry = 0xffffffff80200000 p2m_base = 0xffffffffffffffff xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff80200000 -> 0xffffffff8072ce88 xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 4k each xc_dom_mem_init: 0x20000 pages xc_dom_boot_mem_init: called x86_compat: guest xen-3.0-x86_64, address size 64 x86_compat: warning: failed (rc=-1) xc_dom_boot.c:143: panic: xc_dom_boot_mem_init: can''t allocate low memory for domain xc_dom_release: c...

...uest_info: LOADER="generic" elf_xen_addr_calc_check: addresses: virt_base = 0x0 elf_paddr_offset = 0x0 virt_offset = 0x0 virt_kstart = 0x0 virt_kend = 0x1dfa4 virt_entry = 0x0 xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0x0 -> 0x1dfa4 xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each xc_dom_mem_init: 0x2000 pages xc_dom_boot_mem_init: called x86_compat: guest xen-3.0-x86_32p, address size 32 here is the log when xend is intact.... xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... OK elf_parse_binary: phdr: 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,

..._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_malloc : 128 kB xc_dom_build_image: called xc_dom_alloc_segment: kernel : 0xc1000000 -> 0xc1439000 (pfn 0x1000 + 0x439...

...000000 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, pages 0x138800 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x138800 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 10000 kB domainbuilder:...

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

...000000 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, pages 0x10000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x10000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 512 kB domainbuilder: detail...

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

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

...offset = 0x0 xc: detail: virt_kstart = 0x0 xc: detail: virt_kend = 0x99ff60 xc: detail: virt_entry = 0x0 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x99ff60 domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x20000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 1024 kB domainbuilder: detai...

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -