Error 13 Invalid Unsupported Executable Format Xen
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 posting ads with us error 13 invalid or unsupported executable format windows 7 Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is error 13 invalid or unsupported executable format redhat 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 error 13 invalid or unsupported executable format centos 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 vote favorite I used VMWare vConverter and everything
Error 13 Invalid Or Unsupported Executable Format Windows 7 Ultimate
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 370k686731122 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 how to fix error 13 invalid or unsupported executable format 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 370k686731122 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: vmlinuz vmlinuz-2.6.18-194.17.4.el5, vmlinuz-2.6.18-194.17.4.el5xen Let's say for this segment that the kernel is called (again use the grub output from the prevous line to guide you): /vmlinuz-2
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 13 invalid or unsupported executable format GRUB error 13: Invalid executable format Quote Postby nilie » 2009/05/05 04:36:10 Hello everybody,I'm trying
Error 13 Invalid Or Unsupported Executable Format Grub4dos
to install a dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. I installed OpenSUSE first and allowed it to
Error 13 Invalid Or Unsupported Executable Format Rhel
install and configure grub 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 http://unix.stackexchange.com/questions/27001/unable-to-boot-vm-error-13-invalid-or-unsupported-executable-format solutions: either install it 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 http://www.centos.org/forums/viewtopic.php?t=13361 the options for software components installation, I've 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 ke
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social https://ubuntuforums.org/showthread.php?t=1517773 Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Error 13: Invalid or Unsupported Executable Format Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results error 13 1 to 7 of 7 Thread: Error 13: Invalid or Unsupported Executable Format Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode June 25th, 2010 #1 vmsean View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Jun 2010 Beans 4 Error 13: Invalid or Unsupported Executable Format Hello all, I've searched all over the internet and have found numerous threads error 13 invalid on this topic, none of which have helped me fix the problem. I'll post as much info I can about my setup. I have 3 hard drives... one is for ubuntu (9.10), one is for my data, and one is for Windows7. It looks like this: 1st drive (hda) = ubuntu 2nd drive (hdb) = data 3rd drive (hdc) = windows I used to be able to dual boot no problem (via grub menu) until I updated to Ubuntu 9.10 awhile ago. Now I get the ever so popular "Error 13" message anytime I try to boot into Windows. I've tried everything with regards to tweaking my menu.lst file. The odd thing is, if I physically remove drives 1 & 2, my computer will boot into windows with no problem, which sort of tells me that I don't need to run any recovery on the windows drive. Anyhow, here's an output of relevant info. Any help would truly be appreciated. sudo fdisk -l Code: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x76a6af7e Device Boot Start End Blocks Id System /dev/sda1 * 1 58336 468583888+ 83 Linux /dev/sda2 58337 60801 19800112+ 5 Extended /dev/sda5 58337 60801 19800081 82 Linux swap / Solaris WARNING: GPT