search for: elf_init

...t when booting as dom0 under the xen hypervisor it crashes. I just figured out how to redirect xen output to my IPMI/BMC serial port and I see this: (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Does this mean that Debian is compiling the kernel incorrectly (in which case I''ll file a bug), or is my Xen now too old to support it? Thanks James

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 3.1-stable, since these fixes an regression for Xen 3.1, please? -- AMD Saxony, Dresden, Germany Operating System Research Cen...

Hi. I'm having a problem which I am not able to solve and yet it is easily reproducible. 1. Install Debian Stable AMD64 2. Add backports repository 3. aptitude -t lenny-backports install xen-linux-system-2.6.32-bpo5-xen-amd64 After rebooting You will get the usual error: elf_init: not an ELF binary *************************** Panic on CPU 0: Could not set up DOM0 guest OS *************************** reboot in five seconds Am I doing something wrong? I cannot stay on Stable because I get "time went backwards" errors in spite of using jiffies as clocksource so I am...

...Severity: important I upgraded today from Lenny to Squeeze. I upgraded via apt-get dist-upgrade and then installed the new xen-packages (including hypervisor and kernel). But I wasn't able to boot the system after the upgrade anymore with Xen enabled: On every boot-attempt, I just get "elf_init: not an ELF binary". I googled a lot but I just found an unanswered bugreport against backports and no solution. I never built my own kernel or sth like this, I was doing all the "debian-way". I hope somebody has a solution for this, as I was upgrading a running, productive server...

Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards

<<handle_msi_irq_storm.patch>> Hi, Keir, This patch handles MSI irq storm. Unluckily, I have observed this phenomenon again. This will happen when some kind of MSI-X capable NIC is assigned to an HVM guest. The basic idea is to mask the interrupt on receiving the second interrupt and set a timer to unmask after 1ms. Can you have a look and give some comments on that? Thanks! Best

...; + struct elf_binary *elf; + unsigned offset; + + rc = check_bzimage_kernel(dom, 1); + if ( rc != 0 ) + return rc; + + params = dom->kernel_blob; + offset = elf_offset(params); + + elf = xc_dom_malloc(dom, sizeof(*elf)); + dom->private_loader = elf; + + rc = elf_init(elf, dom->kernel_blob + offset, dom->kernel_size - offset); + if ( xc_dom_logfile ) + elf_set_logfile(elf, xc_dom_logfile, 1); + if ( rc != 0 ) + { + xc_dom_panic(XC_INVALID_KERNEL, "%s: corrupted ELF image\n", + __FUNCTION__); + ret...

...; + struct elf_binary *elf; + unsigned offset; + + rc = check_bzimage_kernel(dom, 1); + if ( rc != 0 ) + return rc; + + params = dom->kernel_blob; + offset = elf_offset(params); + + elf = xc_dom_malloc(dom, sizeof(*elf)); + dom->private_loader = elf; + + rc = elf_init(elf, dom->kernel_blob + offset, dom->kernel_size - offset); + if ( xc_dom_logfile ) + elf_set_logfile(elf, xc_dom_logfile, 1); + if ( rc != 0 ) + { + xc_dom_panic(XC_INVALID_KERNEL, "%s: corrupted ELF image\n", + __FUNCTION__); + ret...

...; + struct elf_binary *elf; + unsigned offset; + + rc = check_bzimage_kernel(dom, 1); + if ( rc != 0 ) + return rc; + + params = dom->kernel_blob; + offset = elf_offset(params); + + elf = xc_dom_malloc(dom, sizeof(*elf)); + dom->private_loader = elf; + + rc = elf_init(elf, dom->kernel_blob + offset, dom->kernel_size - offset); + if ( xc_dom_logfile ) + elf_set_logfile(elf, xc_dom_logfile, 1); + if ( rc != 0 ) + { + xc_dom_panic(XC_INVALID_KERNEL, "%s: corrupted ELF image\n", + __FUNCTION__); + ret...

I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructi...

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

Hello everyone, this is the very first 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