search for: xc_dom_parse_elf_kernel

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,

...disk image: /rpool/vms/centosx disk size: 9120 MB network: shared physical device e1000g0 Unable to complete install ''libvirt.libvirtError virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, ''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image has no shstrtab\\n'')") Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 699, in do_install dom = guest.start_install(False, meter = meter) File "/export/builds/xvm_111a///proto/install/usr/lib/python2.4/sit...

...f hard disk. It was a pain to install xen in it but when i finally did it, i get this 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_b...

If i will use a virtualbox image with xen Must ionly convert it to raw and copy the hole image to a lvm or harddisk Or are it more advanced? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...lf_xen_parse_guest_info: PAE="yes" elf_xen_parse_guest_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...

...ymap=en-us" ] disk = [ "phy:/dev/xenvg/rhel51x64f,xvda,w" ] vif = [ "mac=00:12:3e:13:12:c0,bridge=xenbr0" ] when I boot the guest with the error: [root@CDL-XEN xen]#  xm create -c test Using config file "./test". Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n') and the error log file: [2008-03-19 05:51:29 xend 4506] DEBUG (balloon:127) Balloon: 2125808 KiB free; need 2097152; done. [2008-03-19 05:51:29 xend 4506] INFO (image:136) buildDomain os=linux dom=27 vcpus=2 [2008-03-19 05:51:29 xend 4506] DEBUG (image:201) domid...

...tion on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources? blkif-drivers-explained.txt? For a start, Grub has a Coreboot port, which is ELF, but the Xen 3.2 domain builder refuses to load it saying: xc_dom_parse_elf_kernel: ELF image has no shstrtab -- Thanks, Feri. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...tion on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources? blkif-drivers-explained.txt? For a start, Grub has a Coreboot port, which is ELF, but the Xen 3.2 domain builder refuses to load it saying: xc_dom_parse_elf_kernel: ELF image has no shstrtab -- Thanks, Feri. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...tion found.\n") -------------------------------------------------------------------------------------------------- Booting entry 2 shows -------------------------------------------------------------------------------------------------- Error: (2, ''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image has no shstrtab\n'') -------------------------------------------------------------------------------------------------- And entry 3 shows -------------------------------------------------------------------------------------------------- rtc: IRQ 8 is not free.i8042.c: No contro...

...DER = "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_malloc : 128 kB xc_dom_build_image: called xc_dom_alloc_segment: k...

...a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a while I struggled with the "Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n')" error but thanks to Nick Couchman from http://lists.xensource.com/archives/html/xen-users/2008-03/msg00603.html, I've passed that. Now I'm stuck with a kernel panic situation. Unfortunately the kernel panic error doesn't appear using "xm co...

...= 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, 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....

...= 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, 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-x8...

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

...virt_base = 0x0 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_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 dom...

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See