Automate testing image with qemu #165
Labels
No labels
CI enhacement
CS10 (chromestick)
HIGH PRIOROITY
Low Priority
Solved
TODO
arm64
armhf
bug
c100 (veyron minnie)
duplicate
enhancement
good first issue
help wanted
invalid
minor bug
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ev4/PrawnOS#165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that https://github.com/SolidHal/PrawnOS/pull/161 is merged, builds are automated with github actions. This is a followup to #150
However, the image itself isn't actually tested (other than building). Ideally, we'd use qemu (maybe in conjunction with
expecthttps://linux.die.net/man/1/expect) to attempt to boot/install the image.I'm familiar with qemu, but never used it for arm stuff, so will take some research. Anyway, opening the bug to keep track of it.
Feel free to assign this to me if you'd like, I don't have permission for that.
Thanks for taking this on @austin987!
Some notes for myself or anyone interested:
https://stackoverflow.com/questions/37079990/is-any-arm-platform-emulation-in-qemu-functional-enough-to-run-arm-v7-code-in-mu
https://gist.github.com/luk6xff/9f8d2520530a823944355e59343eadc1
https://blog.3mdeb.com/2014/2014-08-07-coreboot-for-qemu-armv7-vexpress-a9-emulated-mainboard/
https://github.com/lukechilds/dockerpi has a dockerfile that runs a armv6 image inside of qemu.
It supports armv7 as well, but apparently networking doesn't work yet :( https://github.com/lukechilds/dockerpi/pull/4. Though in a quick test, networking doesn't work for me in armv6 mode either.
Anyway, still useful.