> On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
>> I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung
>> Chromebook featuring ARM Exynos dual core A15 processor.
> Sorry to slightly hijack this thread. I will try your remix later.
> Reading the comments on https://lwn.net/Articles/557132/#Comments
> it seems as if the news on KVM on the Chromebook is not good. It
> doesn't boot into HYP mode, and there's no way to make it boot into
> HYP mode, so KVM won't be supported. Is that right?
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine. Supports Linux and Windows.
This is correct as of right now. On my todo list is to try to figure out a way to make
Xen, however, does work, and I have done it with the 3.10 kernel.
I've not had as much time as I wanted to play with the Mirabox. I'm
taking this one over to the UK to give to Peter in a few hours, and I've
ordered myself another one so that I can help get it working. It's not a
high priority, but I agree that this is a nice device for F20.
In the absence of dtb support in the U-Boot, and given the ugly way the
storage is setup via USB, I'm just hacking together a test environment
that isn't using a-b-c. I use the Minimal VFAT image with a microSD card
inside an SD Card adapter (for my laptop), delete the first two
partitions, then re-create them of even size (about 256M each). Then I
format the first partition using ext2 as the filesystem.
I prep a suitable mvebu kernel by appending the dtb (using the non-lpae
kernel as that is still in prep upstream):
sudo sh -c "cat vmlinuz-$version.fc19.armv7hl
sudo mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e
0x00008000 -n $version.fc19.armv7hl.mirabox -d
Then I copy this (renamed to uImage), and the uInitrd onto the first
ext2 partition. Inserting into the Mirabox, I set the following U-Boot
environmental parameters to boot the result:
setenv bootcmd 'usb start; ext2load usb 1:1 0x02000000 uImage; ext2load
usb 1:1 0x02800000 uInitrd; bootm 0x02000000 0x02800000'
setenv bootargs 'ro rootwait root=/dev/sdb3 console=ttyS0,115200'
These are just rough notes. Ultimately, we'd want dtb support in the
U-Boot, and we'd want to have a-b-c learn about this particular
armada-370 variant. I've poked at a-b-c a couple of times but honestly
didn't go too far down that path as it's not going to be supportable
yet. You'd certainly want to change the 370 load addresses at least.