Grub Error 13 Invalid Or Unsupported Executable Format
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 site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or error 13 invalid or unsupported executable format redhat posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix error 13 invalid or unsupported executable format windows 7 & 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 error 13 invalid or unsupported executable format centos a minute: Sign up Here's how it works: 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 how to fix error 13 invalid or unsupported executable format 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 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 372k696751126 asked Dec 16 '11 at 19:18 Bob Loblaw 36112 Was this a physical XEN-Dom0
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
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 372k696751126 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. Grub is looking in the wrong place on the file system for the kernel. Again there is a good chance that this was caused by the V2V, possibly changing the partition numbers. To fix this one try running the following at the grub prompt: grub > find /vmlinuz. This should display the something like the following. (hd0,0) Note that if it is different use what grub shows, it should be in the format (hd,X,Y) Next to get the full name of the kernel type grub > null (hd0,0) /vmli and press TAB This should output something like the following: Possible files are:
fails with GRUB error 13: Invalid executable format General support questions including new installations Post Reply Print view Search Advanced search 4 posts • Page 1 of 1 nilie Posts: 3 Joined: 2009/05/05 04:02:11 Booting CentOS v5.2 fails with GRUB error
Error 13: Invalid Or Unsupported Executable Format Cisco
13: Invalid executable format Quote Postby nilie » 2009/05/05 04:36:10 Hello everybody,I'm trying to install a error 13 invalid or unsupported executable format centos 6 dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. I installed OpenSUSE first and allowed it to install and configure grub error 13 invalid or unsupported executable format rhel in the MBR and after that I wanted to proceed with CentOS v5.2. The installation went fine with two notable exceptions:- when I had to configure grub installation parameters, CentOS offered me only 2 solutions: either install it http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format on the MBR of the first hard disk or not installing it at all. Other distributions are more flexible allowing you to install it in the boot sector of the root partition for example. Because I didn't want to ruin the existent grub configuration, I reluctantly accepted not to install it for CentOS assuming that I could manually configure the entry later in grub's menu.lst file.- when I was presented with the options for software components installation, I've http://www.centos.org/forums/viewtopic.php?t=13361 clicked on virtualization category/function because I intend to use the machine as a VMware host. There was no guidance on screen at that point and I blindly assumed that by choosing the virtualization function I would get necessary tools and drivers that will help me further on. It seems that this was a wrong move as you can see it below.After completing the installation, I tried to search for a template or guiding on how the menu entry in menu.lst should look like but the grub directory was empty, not surprisingly because I've told CentOS earlier not to install it. Using the files in the /boot directory from the CentOS installation I tried to improvise a menu entry but it's not working. The boot stops with famous Error 13: Invalid or unsupported executable format. Using the file command to check what kind of files I'm trying to load as kernels I'm getting :marte:~ # file /mnt/vmlinuz-2.6.18-92.el5xen/mnt/vmlinuz-2.6.18-92.el5xen: gzip compressed data, from Unix, last modified: Tue Jun 10 19:20:51 2008, max compressionmarte:~ # file /boot/vmlinuz-2.6.27.21-0.1-pae/boot/vmlinuz-2.6.27.21-0.1-pae: Linux/x86 Kernel, Setup Version 0x209, bzImage, Version2.6.27.21, RO-rootFS, root_dev 0x809, swap_dev 0x2, Normal VGAObviously, the CentOS kernel file is not in the right format and the xen word gave me a bad feeling. Doing a little research, I found that the xen kernel contains a Linux kernel that runs on the Xen hypervisor and that the li
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 Target Distribution Baltix https://bugs.launchpad.net/bugs/365331 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 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 an update and reboot. Tried booting error 13 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 bytes Disk identifier: 0x556b556b Device Boot Start End Blocks Id invalid or unsupported 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 $ sudo mount -o bind /dev /mnt/linux/dev $ sudo chroot /mnt/linux If /boot is on a separate partition, this partition mu