Error 13: Invalid or unsupported executable format
-
@Danp ,
The crazy thing is is these are old centos 5.5 vms. They haven't had any patches for ages. Neither have the hosts been patched for quite a while...
That's what I would think too but seems unlikely in this case...
-
I would switch them to HVM if you can, PV is dead. There's PVshim at worst.
-
@olivierlambert , thank you for your reply.
I did switch to HVM, however that's when I get the grub bootloader screen with the Error 13: Invalid or unsupported executable format.
So, PVShim might work in this case? I will give it a shot.
-
So if the issue is clearly inside the guest, then it's might not be related to XCP-ng
Could it be 32 bits vs 64 bits?
-
@olivierlambert,
This is an x86_64 VM. I originally made the VM on XenServer back when it was Citrix owned. Then I actually migrated it over to KVM about 7 years ago. And then about 3 years ago, I migrated the VM back to XCP-ng using a qcow conversion routine that included running a dracut regenerate command.dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfgI wonder if I could somehow start in recovery mode and use that same command to regenerate the VM?
-
@olivierlambert,
Is there a simple way to start the VM with PVshim? After googling around I couldn't find anything that would explain how to do this for the non-specialized person. -
First, I would start a live CD and chroot into it to see if you can get all the files (in case you can spot something corrupted)
-
@olivierlambert,
Thanks for the assistance. I'm exporting the data from the VM via Live CD and will build a new VM and import applications from old VM. -
@olivierlambert,
I ended up copying the old application data from the crashed VM via a live CD and deployed a new VM (running on HVM.) Everything seems to be working fine now. -
Good news
Also, now you are in HVM, which is a LOT better than PV for a lot of reasons (security, performance etc.)
