On Tue, Feb 20, 2018 at 08:29:19PM +1100, Mathew McBride wrote: > On 13/01/2018 5:26 PM, Jonathan Gray wrote: > > On Thu, Jan 11, 2018 at 03:40:01PM +0100, Karel Gardas wrote: > > > > > > Hello, > > > > > > I'd like to help a bit with GHC work on OpenBSD and would like to give it > > > a try > > > to port GHC to ARMv8. GHC is a beast so I assume I'll need > > > machine/emulator > > > with 4GB RAM at least. I'm curious what you guys are using for running > > > all those > > > ARMv8 packages builders and for your own porting efforts? > > > > > > so far I see following options: > > > > > > - qemu-system-aarch64 running on OpenBSD/amd64. I've verified qemu > > > distributed with 6.2-current > > > is well capable of running Ubuntu cloud image 16.04 for ARMv8. The > > > question is, has anybody > > > here tested that or get OpenBSD/arm64 running on Qemu? The advantage > > > of this solution is flexibility > > > > qemu is quite a bit slower than real hardware and more painful. > > > > Using U-Boot with a recently proposed but not committed qemu_arm64 > > target is limited in that virtio devices can't be booted off. Using an > > EDK2 OVMF image works better but only if using a QEMU_EFI.fd older than > > the prebuilt binaries linaro now provides otherwise there is no console > > output after the kernel loads. > > > > Hi all, > This thread caught my attention as I have been doing some experimenting with > ARM virtualization recently - we (Traverse) have a ARM64 board > (NXP/Freescale LS1043 / 4xA53) [1] that runs Linux and I have built a small > distro[2] to host arm64 VM's. > > I've had good success with Linux VM's and some success with FreeBSD (i.e > needed older EDK2, and issues with emulated PCIe devices) > > OpenBSD does boot under a virtual environment (using the older EDK2 like > FBSD), but the segfaults noted on both the emulated and ThunderX > environments also occur here. > > If anyone would like me to try something to debug it, let me know. > > The qemu command line used is roughly: > qemu-system-aarch64 --enable-kvm -m 512 -cpu host -M virt,gic_version=2 -smp > 1 -mem-path /tmp/hugetlbfs -bios QEMU_EFI_bsd.fd -drive > if=none,file=openbsd.qcow2,id=hd0 -device virtio-blk-device,drive=hd0 > > My notes: > https://gitlab.com/traversetech/muvirt/wikis/OpenBSD
Hi, Nice to see interesting hardware from a local Melbourne company. I would be curious how you fare running aarch32 if the hardware/kvm supports it. The cavium hardware infamously does not, and on bare metal amd hardware memory is mapped too high for it. http://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upstream/2717/QEMU-ARM/RELEASE_GCC5/QEMU_EFI.fd any of the armv7 snapshot miniroots should work. From what I've read using an aarch32 guest on aarch64 host with kvm still requires invoking qemu-system-aarch64 but with '-cpu host,aarch64=off'.
