Newly Cloned Linode Won't Boot

Anybody? Really banging my head against the wall. Straight clone of another Linode that boots perfectly, and it refuses to boot. Will boot if I switch to Linode's kernel.

If the filesystem is a perfect copy, what could possibly be the problem? (I shut down the source Linode for the duration of the copy operation to ensure consistency.)

BTW, this has me worried that a resize operation might have the same problem. I think a resize is essentially the same as a clone since the linode gets moved to another server…

On a hunch, I tried resizing the clone down a size to the same size as the original source Linode. (I had cloned the source to a larger linode).

Guess what? It boots.

The only difference is the Linode's size.

Does this make any sense? I'm no expert in the Linux boot process. But could there be a persistent record of the RAM size (stored somewhere on disk) that is throwing off the boot process when it is not what was expected?

Please throw in your 2 cents!

I have found through trial and error that lowering the memory limit in the configuration profile to a value <= 1017 MB allows the instance to boot fine under pv-grub. Any value > 1017Mb causes it to hang during boot.

Anyone out there successfully booting a larger linode (1024MB and up) via pv-grub?

As you already saw in a different thread - I keep kernel-2.6.32-71.29.1.el6.i686 (Centos 6.0) on my VM - nothing above it boots on Linode 1024.

Hmm, I could not even get the 6.0 kernel to boot without lowering the memory limit.