[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Unable to boot xen on cubieboard2



ÂThanks. Yes, I git cloned and built as dom0, xen and u-boot as in the doc. I just looked at my log, there's a bit at the end I missed. Here's the entire log, I've highlighted the last part. Looks like some build parameter went missing, complaining that its not in NS Hyp mode....

U-Boot 2014.04-01572-gea1ac32 (Jul 12 2015 - 01:41:38) Allwinner Technology

CPU: Â Allwinner A20 (SUN7I)
Board: Cubieboard2
I2C: Â ready
DRAM: Â1 GiB
MMC: Â SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In: Â Âserial
Out: Â serial
Err: Â serial
Net: Â dwmac.1c50000
Hit any key to stop autoboot: Â0
reading uEnv.txt
** Unable to read file uEnv.txt **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
reading boot.scr
1243 bytes read in 21 ms (57.6 KiB/s)
Jumping to boot.scr
## Executing script at 44000000
reading /xen
688912 bytes read in 56 ms (11.7 MiB/s)
reading /sun7i-a20-cubieboard2.dtb
20757 bytes read in 29 ms (698.2 KiB/s)
reading /vmlinuz
5284760 bytes read in 263 ms (19.2 MiB/s)
Kernel image @ 0x7ea00000 [ 0x000000 - 0x0ef700 ]
## Flattened Device Tree blob at 7ec00000
 ÂBooting using the fdt blob at 0x7ec00000
 Âreserving fdt memory region: addr=7ec00000 size=6000
 ÂUsing Device Tree in place at 7ec00000, end 7ec08fff

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Xen must be entered in NS Hyp mode -
- Boot failed -


On Sun, Jul 19, 2015 at 5:30 PM, Luke Dunstan <lukedunstan81@xxxxxxxxx> wrote:
I was going to ask whether you downloaded a pre-built image from http://blobs.openmirage.org/ but that site doesn't seem to be available at the moment, so I guess you built an image? But regardless of that, first try writing the image to the card again with "dd", as I've occasionally had that step fail to work.

The early output of a successful boot looks like this (depending on the version of U-Boot):

U-Boot 2014.04-01540-ga74a847 (Jun 26 2015 - 14:22:47) Allwinner Technology

CPU: Â Allwinner A20 (SUN7I)
Board: Cubieboard2
I2C: Â ready
DRAM: Â1 GiB
MMC: Â SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In: Â Âserial
Out: Â serial
Err: Â serial
Net: Â dwmac.1c50000
Hit any key to stop autoboot: Â0Â
reading uEnv.txt
** Unable to read file uEnv.txt **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
reading boot.scr
1243 bytes read in 22 ms (54.7 KiB/s)
Jumping to boot.scr
## Executing script at 44000000


The warning about ext2 is not likely to be related to your problem.

Luke


On Mon, 20 Jul 2015 at 04:03 Mukund Parthasarathy <mukundanps@xxxxxxxxx> wrote:
Hello-
ÂTrying to set up my cubieboard2 perÂhttps://mirage.io/wiki/xen-on-cubieboard2.

ÂXen won't boot, looks like it is expecting ext2 filesystem, rather than ext4:

U-Boot 2014.04-01572-gea1ac32 (Jul 12 2015 - 01:41:38) Allwinner Technology

CPU: Â Allwinner A20 (SUN7I)
Board: Cubieboard2
I2C: Â ready
DRAM: Â1 GiB
MMC: Â SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In: Â Âserial
Out: Â serial
Err: Â serial
Net: Â dwmac.1c50000
Hit any key to stop autoboot: Â0
reading uEnv.txt
** Unable to read file uEnv.txt **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **


Boot fails....any ideas? Please let me know if I should be posting on a different DL, Ultimately, I'd like to run a mirageos unikernal...
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.