So is the interrupt thing a real HW bug in the RPi CPU or might this be solvable with some setup magic on the VC black box side? And why does isolating one core on the host side suffice, without restricting which cores the guest can run on? He's running the guest SMP enabled in the example posted.
Last line of the article is "And that’s it, now you can extract the full potential of your Raspberry Pi 2!"<p>Can someone explain this to me? I know almost nothing about virtualization, but isn't it be definition slower than straight up OS install?
Noob questions: Can I run Windows like this? Does it enable Qemu support? Can a non ARM OS be emulated in ARM hardware? (Probably not by hardware extensions, right?)
Why not just use containerization instead? it is the best fit for a RB pi in any aspect. Almost no performance penalty and incredible use cases. Imagine having a fast bare OS on it and deploying remotely containers trough tutum web interface. IoT start to make sense now? :)