search for: elf_load_binary

...o: ffffffff811e3000->ffffffff811e349c (XEN) Page tables: ffffffff811e4000->ffffffff811f1000 (XEN) Boot stack: ffffffff811f1000->ffffffff811f2000 (XEN) TOTAL: ffffffff80000000->ffffffff81400000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804c3c58 (XEN) elf_load_binary: phdr 1 at 0xffffffff804c3c80 -> 0xffffffff805d6ef0 (XEN) elf_load_binary: phdr 2 at 0xffffffff805d7000 -> 0xffffffff805d7c08 (XEN) elf_load_binary: phdr 3 at 0xffffffff805d8000 -> 0xffffffff80611388 (XEN) Initrd...

...36d8 (XEN) Start info: ffffffff80e94000->ffffffff80e9449c (XEN) Page tables: ffffffff80e95000->ffffffff80ea0000 (XEN) Boot stack: ffffffff80ea0000->ffffffff80ea1000 (XEN) TOTAL: ffffffff80000000->ffffffff81000000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 1 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804d5d20 (XEN) elf_load_binary: phdr 1 at 0xffffffff804d5d80 -> 0xffffffff805ebf50 (XEN) elf_load_binary: phdr 2 at 0xffffffff805ec000 -> 0xffffffff805ecc08 (XEN) elf_load_binary: phdr 3 at 0xffffffff805ee000 -> 0xffffffff80628388 (XEN) Initrd...

...o: ffffffff8fffc000->ffffffff8fffc4b4 (XEN) Page tables: ffffffff8fffd000->ffffffff90082000 (XEN) Boot stack: ffffffff90082000->ffffffff90083000 (XEN) TOTAL: ffffffff80000000->ffffffff90400000 (XEN) ENTRY ADDRESS: ffffffff81ac41e0 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0x18446744071578845184 -> 0x18446744071589261312 (XEN) elf_load_binary: phdr 1 at 0x18446744071589330944 -> 0x18446744071590043888 (XEN) elf_load_binary: phdr 2 at 0x18446744071590047744 -> 0x18446744071590133248 (XEN) elf_load_binary: phdr 3 at 0x18446744071590133760 -> 0x18...

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could not find device-model'...

...: ffffffff85e8f000->ffffffff85e8f4b4 (XEN) Page tables: ffffffff85e90000->ffffffff85ec3000 (XEN) Boot stack: ffffffff85ec3000->ffffffff85ec4000 (XEN) TOTAL: ffffffff80000000->ffffffff86000000 (XEN) ENTRY ADDRESS: ffffffff81a89210 (XEN) Dom0 has maximum 24 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81820000 (XEN) elf_load_binary: phdr 1 at 0xffffffff81a00000 -> 0xffffffff81a740e8 (XEN) elf_load_binary: phdr 2 at 0xffffffff81a75000 -> 0xffffffff81a88340 (XEN) elf_load_binary: phdr 3 at 0xffffffff81a89000 -> 0xffffffff81b11000 (XEN) Scrubbi...

...: 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: elf_load_binary: phdr 3 at 0x0x7fdeca15a000 -> 0x0x7fdeca1cd000 domainbuild...

...000000000000 xc: detail: TOTAL: 0000000000000000->000000007f000000 xc: detail: ENTRY: 0000000000100610 xc: detail: PHYSICAL MEMORY ALLOCATION: xc: detail: 4KB PAGES: 0x0000000000000200 xc: detail: 2MB PAGES: 0x00000000000003f7 xc: detail: 1GB PAGES: 0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model did n...

...[2012-06-17 00:22:20] Boot stack: ffffffff86528000->ffffffff86529000 (XEN) [2012-06-17 00:22:20] TOTAL: ffffffff80000000->ffffffff86800000 (XEN) [2012-06-17 00:22:20] ENTRY ADDRESS: ffffffff81cfb200 (XEN) [2012-06-17 00:22:20] Dom0 has maximum 4 VCPUs (XEN) [2012-06-17 00:22:20] elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81ad5000 (XEN) [2012-06-17 00:22:20] elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81ce50e0 (XEN) [2012-06-17 00:22:20] elf_load_binary: phdr 2 at 0xffffffff81ce6000 -> 0xffffffff81cfa480 (XEN) [2012-06-17 00:22:20] elf_load_binary: p...

...: 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: elf_load_binary: phdr 3 at 0x0x7f3a59724000 -> 0x0x7f3a5973a0d8 xc: detail:...

...o: ffffffff80fe2000->ffffffff80fe24b4 (XEN) Page tables: ffffffff80fe3000->ffffffff80ff0000 (XEN) Boot stack: ffffffff80ff0000->ffffffff80ff1000 (XEN) TOTAL: ffffffff80000000->ffffffff81400000 (XEN) ENTRY ADDRESS: ffffffff80758200 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff806de000 (XEN) elf_load_binary: phdr 1 at 0xffffffff806de000 -> 0xffffffff8074c438 (XEN) elf_load_binary: phdr 2 at 0xffffffff8074d000 -> 0xffffffff8074d888 (XEN) elf_load_binary: phdr 3 at 0xffffffff8074e000 -> 0xffffffff807b8200 (XEN) elf_loa...

...gt;c0e7c400 (XEN) Phys-Mach map: c0e7d000->c1056d90 (XEN) Start info: c1057000->c1057474 (XEN) Page tables: c1058000->c1067000 (XEN) Boot stack: c1067000->c1068000 (XEN) TOTAL: c0000000->c1400000 (XEN) ENTRY ADDRESS: c075e000 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc0720000 (XEN) elf_load_binary: phdr 1 at 0xc0720000 -> 0xc07a7d08 (XEN) Initrd len 0x617400, start at 0xc0865000 (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited:...

...gt;c0efec00 (XEN) Phys-Mach map: c0eff000->c0fff000 (XEN) Start info: c0fff000->c0fff46c (XEN) Page tables: c1000000->c100f000 (XEN) Boot stack: c100f000->c1010000 (XEN) TOTAL: c0000000->c1400000 (XEN) ENTRY ADDRESS: c0400000 (XEN) Dom0 has maximum 1 VCPUs (XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc068771c (XEN) elf_load_binary: phdr 1 at 0xc0688000 -> 0xc0733cc4 (XEN) Initrd len 0x712c00, start at 0xc07ec000 (XEN) Scrubbing Free RAM: ...............................................................................................done. (XEN) Xen trace buffers:...

...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 0x1439+0xa0 at 0xb32e7000 xc_dom_do_gunzip: unzip ok, 0x3b899 -&gt...

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

...o: ffffffff81cec000->ffffffff81cec49c (XEN) Page tables: ffffffff81ced000->ffffffff81d00000 (XEN) Boot stack: ffffffff81d00000->ffffffff81d01000 (XEN) TOTAL: ffffffff80000000->ffffffff82000000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 8 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804f3d70 (XEN) elf_load_binary: phdr 1 at 0xffffffff804f3d80 -> 0xffffffff80640290 (XEN) elf_load_binary: phdr 2 at 0xffffffff80641000 -> 0xffffffff80641c08 (XEN) elf_load_binary: phdr 3 at 0xffffffff80642000 -> 0xffffffff8067f0a8 (XEN) Initrd...

...AL: 0000000000000000->000000007f000000 > xc: detail: ENTRY: 0000000000100610 > xc: detail: PHYSICAL MEMORY ALLOCATION: > xc: detail: 4KB PAGES: 0x0000000000000200 > xc: detail: 2MB PAGES: 0x00000000000003f7 > xc: detail: 1GB PAGES: 0x0000000000000000 > xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151 > domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 > libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device > model: spawn failed (rc=-3) > libxl: error: libxl_create.c:1340:domcreate_devmodel_started:...

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

Hi! From other people posting to this list, I know that there has been a bug related to the issue described in Xen Security Advisory 36 that disables iommu for some AMD users like me. However, even when passing "iommu=no-amd-iommu-perdev-intremap" it still disables i/o virtualisatoin. Related Xen dmesg output: (XEN) IVHD Error: Invalid IO-APIC 0 (XEN) AMD-Vi: Error initialization

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,

Hi Everyone I have sorted out the initial issues I''ve had and decided to give Xen another go. I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1 failed, and when I gave it a second go, rc3 was already out). As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and under Xen as dom0, but I have reservations against running 2.6.32,