Kernel Error 13
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this error 13 invalid or unsupported executable format redhat site About Us Learn more about Stack Overflow the company Business Learn more how to fix error 13 invalid or unsupported executable format about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix error 13 invalid or unsupported executable format centos & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works:
Grub Error 13 Invalid Or Unsupported Executable Format
Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Unable to boot VM: Error 13: Invalid or Unsupported Executable Format up vote 5 down vote favorite I used VMWare vConverter and everything converted fine, but when I try to boot I get an error: The physical machine boots correctly, so I don't think it is a error 13 invalid or unsupported executable format windows 7 source machine issue. I am not sure why the VM won't boot; aren't VMs exact copies of source machines? linux kernel virtual-machine xen vmware share|improve this question edited Dec 30 '11 at 23:11 Gilles 372k696761127 asked Dec 16 '11 at 19:18 Bob Loblaw 36112 Was this a physical XEN-Dom0 server before? –Nils Jul 28 '12 at 19:39 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote You are trying to boot a Xen-specific kernel, intended for a Xen dom0, and also suitable for a Xen domU. I don't think that kernel works outside Xen. Install a regular kernel for a VMware guest. You'll need to boot from a rescue disk if you don't have any other kernel installed in that VM. share|improve this answer answered Dec 30 '11 at 23:10 Gilles 372k696761127 add a comment| up vote 0 down vote Grub can not find this kernel This could be for several reasions. The name of the kernel is wrong (since this is a xen kernel this would not supprise me). Try editing the line in the grub boot loader and remove the "xen" from the end of it. Gru
bits OS developers. It has the advantages of being a(n) (obviously) pre-written bootloader with more code to handle quirks of various BIOSs than it is worthwhile for any individual to do by himself or error 13 invalid or unsupported executable format rhel herself. Please see the following thread for a bit more info: http://forum.osdev.org/viewtopic.php?f=1&t=21158&start=0. However, many
Invalid Or Unsupported Executable Format Grub4dos
folks have problems getting the GrUB to recognize their kernel's executable image. The following is a solution for GrUB's infamous Error 13 pertaining to ELF files. Example Source The GNU Multiboot Specification requires the Multiboot Header to be aligned on a 4 byte boundary within the first 8KB of the kernel executable file. should your http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format kernel's image not fit this description, GrUB will promptly issue an Error 13. Your Linker Script gives the linker details on how to position the executable sections of your kernel within the kernel executable file. You are not restricted (using ELF; there are Executable formats which restrict you to certain format-specific sections) to just the ELF recommended sections. You may define as many sections as you please within your http://wiki.osdev.org/Grub_Error_13 kernel executable image, and position them as you see fit, using your linker script. We assume the use of the GNU LD linker for this article. Within the ASM source file where you have defined your Multiboot Header options, edit the Multiboot Header to look like this: (This article is not going into detail about the GNU multiboot spec. I'm just telling you minor changes to make around the header) ;; Remove the section .text you copy/pasted from the Bare Bones tutorial;) section .__mbHeader align 0x4 ;; Copy/Paste your current Multiboot Header here ;; Reposition the section .text here. What does this do? We have placed the multiboot header into a separate ELF section in the relocatable file generated by NASM. When the linker is going through the Object files, it places the section symbols in each object file in their corresponding output sections in the eventual kernel image. How do we tell the linker to place the .__mbHeader ELF section in the 1st 8KB of the kernel image? Technically, there is no way to guarantee that it will be there if the kernel file grows exorbitantly large. At that point, you may have to invent a special technique of editing your outp
Assigned to Milestone grub (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: grub (Ubuntu) Filed here by: sadicote When: 2009-04-23 Confirmed: 2010-01-09 https://bugs.launchpad.net/bugs/365331 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Confirmed Undecided Assigned https://bbs.archlinux.org/viewtopic.php?id=63565 to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I got this immediately after error 13 an update and reboot. Tried booting from live CD and using sudo grub-install /dev/sda1 but got a "device not found" message in the terminal. I am/was running Jaunty with occupies my entire 160 GB hdd. I think the Jaunty updater causes the problem when on ext4. Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 invalid or unsupported bytes Disk identifier: 0x556b556b Device Boot Start End Blocks Id System /dev/sda1 * 1 19128 153645628+ 83 Linux /dev/sda2 19129 19457 2642692+ 5 Extended /dev/sda5 19129 19457 2642661 82 Linux swap / Solaris ubuntu@ubuntu:~$ Add tags Tag help sojourner (itsmealso2) wrote on 2009-05-08: #1 this occured to me after a fresh install of jaunty ( released version) with ext4 and then changing sources .lst to karmic and updating, all went well until I installed the 2.6.30-1 kernel , with that kernel I would get grub error 13 , with 2.6.28-11 the boot was ok , reinstalling grub from within karmic allowed me to boot the 30-x kernels , there are several reports of this in the karmic dev forum and reinstalling grub does not seem to work for everyone . David Stansby (dstansby-deactivatedaccount) wrote on 2009-05-08: #2 I've had exactly the same experience of sojourner above. Vish (vish) wrote on 2009-06-29: #3 This solved the problem for me, from > http://ubuntuforums.org/showpost.php?p=6977997&postcount=5 Quote: boot from the live medium and chroot into the Linux installation: $ sudo mkdir /mnt/linux $ sudo mount -t ext4 /dev/sda1 /mnt/linux $ sudo mount -t proc proc /mnt/linux/proc $ sudo mount -t sysfs sys /mnt/linux/sys $ su