Shared publicly  - 
I've had some people ping me about "running virtual machines on your chromebook". OK, I just went through setting up somebody's chromebook yesterday and there is one bit of news you may not like. You're going to have to crack it open, so you can enable a reflash of the BIOS. Long story, sorry, won't happen in the future, but there it is. Get in touch with me if you're still interested. The link has more info, but hey, most of you are pretty capable people, so I doubt the need to crack it open will slow you down much. running virtual machines on your chromebook | dev
Joe Nash's profile photoron minnich's profile photoJosé J. Cabezas Castillo's profile photoMarc Jones's profile photo
I'm happy to get emails. My only request is that you write up what kind of issues you run into, so we can help others. I assume first you have a chromebook ...
I didn't see the bit about the BIOS (or the reason) at that link. I vaguely remember a BIOS reflash on the old Samsung Chromebook but don't remember having to open the device (it was a command I could run once the developer switch was set, I think). I did open the chromebook, but that I think was only to add a bigger SSD (and why not).
Yeah, I have fo finish writing that part up.
In short, the issue is this: core 0 has VMX disabled in firmware. I've learned the hard way that if you start a VM on core 1, and for some reason it ends up running on core 0, the CPU will reset fast ... very fast. The fix, then, is to rewrite the firmware to not disable vmx on any core (which it does now, too late for the xe550 chromebook) or change kvm so it won't run VM's on cores on which vmx is disabled. The firmware change is the best long term but the kvm change would be good for people who don't want to crack their chroimebook open ...
This is very, very cool.  I don't own a Chromebook at the moment to benefit from your work but congrats are in order!
The first step is easy, so you might want to give it a go. Mentally sign the form releasing me from any consequences of this second step, cause if you bust your shiny new chromebook, well, it's on you. It's kind of a heartbreaker, though, as you have to remove 8 screws from the bottom, and to do that you have to remove the 4 plastic feet. Ah well. What I recommend is to remove the feet, remove all 8 screws, and put back the 4 feet right away. Never put those 4 under-the-feet screws in again. Next you have to take the bottom off the case. NEVER use a screwdriver, it scratches it. Just use a thumbnail (or a friend's thumbnail) and, starting at the right front or left front corner, split the case open. Then just GENTLY work your way around, going around the front to one side, the back, then the other side, separating the top and bottom, thinking at each step just how badly you maybe just violated the warranty, ah sad. It feels bad to pry the bottom off, but it's quite easy once you get the hang of it. And you're here to hack, right? 

Once your thumbnail comes off, it's all the better, you now have a Tool for later use (just kidding!).

Of course, if you want, help me figure out how to keep VMs off of core 0, and then none of this is necessary :-)

Hey, as long as it's open, think about adding a 64GB SSD and an 8 GB memory module to boost your RAM to 10 GB! That's a pretty nice enhancement! These chromebooks are quite extensible ...

Also I just got the Pekka's wonderful KVM tool almost working with a linux image. FAR easier to hack on than QEMU, and you can link it statically, which has not worked on QEMU for quite some time. In the future, I want to use kvmtool exclusively. 
"think about adding a 64GB SSD " is it an SSD, a slimline (7mm) SSD, or one of those mSATA things that caught me by surprise with the old one?
The 'series 5' designation has left a lot of confusion I think. For the newest samsung x-86 based laptop, there is soldered down and socketed ram. My friend got these from amazon for ram: Patriot Memory Signature DDR3 8GB 1600MHz SODIMM (PC3 12800) PSD38G16002S and this for the MSATA: OCZ Technology 120 GB Nocti Series 3.0 Gb-s Slim mSATA SATA II Solid State Drive (NOC-MSATA-120G)  and they work well. 
Hand on, I'll try to find the web page w/instructions. One question -- do you want to run SeaBIOS?
Some people prefer it because it's a more traditional BIOS interface. I kind of like the u-boot setup myself, I think it's quite slick, but tastes vary.
OK, it's time to move this discussion to the coreboot IRC
 or mailling list. Let's go there.
What? No! You're starving Google+ of its traffic-of-interest-to-bystanders?!
Sorry to renew the conversation here, Ron, but is there any chance of this for the new ARM Chromebook? Cheers
All you have to do is flip it into dev mode, get the kernel with kvm for arm, and then tell me how it's done :-)
Add a comment...