...
Once you have the user space tooling installed you can now boot the hypervisor directly and manually load the dom0 kernel. Please note you’ll want to skip the UEFI bios for this:, also we downgrade the CPU as Xen doesn’t support SVE+ out of the box.
Code Block |
---|
./qemu-system-aarch64 \ -machine type=virt,virtualization=on \ -cpu max,pauth-impdef=oncortex-a57 \ -smp 8 \ -accel tcg \ -device virtio-net-pci,netdev=unet \ -device virtio-scsi-pci \ -device scsi-hd,drive=hd \ -netdev user,id=unet,hostfwd=tcp::2222-:22 \ -blockdev driver=raw,node-name=hd,file.driver=host_device,file.filename=/dev/zen-ssd2/bookworm-arm64,discard=unmap \ -serial mon:stdio \ -m 8192 \ -object memory-backend-memfd,id=mem,size=8G,share=on \ -display none \ -kernel $HOME/lsrc/xen/xen.git/xen/xen.efi \ -append "dom0_mem=4G,max:4G loglvl=all guest_loglvl=all" \ -device guest-loader,addr=0x49000000,kernel=$HOME/lsrc/linux.git/builds/arm64/arch/arm64/boot/Image,bootargs="console=hvc0 earlyprintk=xen root=/dev/sda2" |
...