No, the firmware doesn't disable Hyp mode; it just starts the kernel in Secure-SVC, rather than in Hyp mode. It's pretty trivial to get from Secure-SVC to Hyp in the bootloader before starting the kernel -- there are u-boot patches floating about which do it.
http://www.virtualopensystems.com/media/chromebook/chromeboo... is probably a good place to start if you want to tinker.
As far as I can tell the main issue with the Chromebook is that there's no one organization who's taking responsibility for making sure fixes and changes like this get upstream, so every distro/person ends up reinventing or locally maintaining patches.
Yeah, I'm running Debian Wheezy on a Pixel and, besides building my own more current kernels, there is nothing special going on here.
However the Pixel has an Intel chip doesn't it?
It does, though most people seem to suggest the same crouton stuff for it. I tried that for a weekend and think that advice is misguided.
I wouldn't say "for longer". The original CR-48 had instructions for dual booting Ubuntu, and not Fedora or Arch (or any other distro)...
https://fedoraproject.org/wiki/Architectures/ARM/F19/Remixes... http://archlinuxarm.org/platforms/armv7/samsung/samsung-chro...
The next challenge is getting KVM working. The Chromebook has an A15 chip which has hardware assisted virtualization. Unfortunately the firmware disables HYP mode, but the Xen guys managed to workaround this in their bootloader so it should be possible for KVM too.
Another note about the Chromebook is it is not possible to boot it from an external hard drive. You have to boot it from USB flash although after boot you can of course use a real hard drive as the root filesystem.