QEMU ARM (qemu-vexpress): Difference between revisions
Appearance
m --no-fde removed (deprecated) |
vexpress does not boot anymore and was removed :( |
||
Line 23: | Line 23: | ||
| status_sms = - | | status_sms = - | ||
| status_calls = - | | status_calls = - | ||
| booting = | | booting = no | ||
}} | }} | ||
Revision as of 19:16, 14 March 2020
WARNING: This device is not recommended for future use with postmarketOS due to its armhf architecture. Alpine Linux (the distribution that postmarketOS extends) pmaports#599 has been considering dropping it. The processor of the device may support the armv7 architecture. If so, you can modify the device package and change the architecture accordingly. |
This device is marked as not booting.
Manufacturer | QEMU |
---|---|
Name | vexpress |
Codename | qemu-vexpress |
Hardware | |
Architecture | armhf |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | yes |
CPU emulation is slow! Consider using qemu-amd64 instead if x86_64 is your native architecture. |
Contributors
- MartijnBraam
- mmaret
- ollieparanoid
Usage
$ pmbootstrap init # Choose device "qemu-vexpress"
$ pmbootstrap install
$ pmbootstrap qemu --image-size=2G --display=gtk --arch=arm
Using the --display=gtk
parameter is recommended. The default display, SDL, will show two windows (of which one is unused) and you won't be able to look at the serial output. In the GTK interface, click on View / Show Tabs to display all available outputs as tabs next to each other. Check the serial0
output for what it is actually doing as the boot will probably take a few minutes, unless you have a very fast PC.
What works
- Serial output
- Storage
- Network
What does not work
- Keyboard and mouse
- QEMU 2.0.0 is too old (but it's known to be working with 2.6.50)[1]
Notes
- It boots only if you specify a separate
-dtb
flag, it doesn't use the dtb attached to the kernel (but pmbootstrap calls it right).
Links
Screenshot
- QEMU unlock screen
- QEMU running weston