I have a JellyBean guest that has been running without problem for over a year on my Debian(64-bit) box. Today I exported this guest to my Windows 8.1(64) box. Both hosts have VirtualBox 5.0.14. I made no changes to guest parameters when making the .ova. I made no changes to guest parameters when importing the .ova. After grub exits, I get a kernel panic every time. I cannot copy+paste nor take a screenshot, so I have typed the lower half of the guest screen.
Did you try to simply copy the whole guest directory instead of exporting/importing? See Moving a VM, but re-interpret it as backing up/copying. That would make it clearer whether it is a potential bug in the .ova creation process or it is something entirely different.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
I did that and got the same result. Then I tried bringing over the original .vdi rather than use the .vmdk from the exporting process. I still got the same result.
As long as I had the original .vdi on the Windows host, I thought to try creating a new guest and point to it. Doing that the guest worked. The problem may involve both importing a .ova and adding a machine from existing config files; exporting probably doesn't have a bug.
Raven wrote:I thought to try creating a new guest and point to it. Doing that the guest worked.
Well, you could compare the two .vbox files; the one that failed and the new one that you created and it worked. That could point to what's different and shed some light to this.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Unfortunately, I don't see anything that would prevent booting.
Fortunately, it works, so, I'd leave it as is. Something went bad. Not anymore
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.