Open agustinhenze opened 5 years ago
Sorry about my comment here before. Was just following links and looking on the issue description and did not notice that I was no longer on my project.
I have used an xml created by virtinst and then I discovered it's trying to use boot2docker.iso. This project has hardcoded x86 everywhere :'(. One of the components is Tiny Core Linux which only supports x86_64 :/. Do I have to build my own .iso and pass it as parameter? Do you think it could work?
There is a version of Tiny Core Linux now that supports arm32
(armv6/armv7/armv7l), it is called "piCore".
So it is possible to make version that supports arm64
too, but it would require a substantial effort first...
Another approach is using another distribution (like ubuntu), and make it follow the same contract (user, etc).
Hello.
it's more of a challenge,to be able to emulate the raspberry pi 3 on my Jetson nano (aarch64) using virt-install. I'm learning how to do that by reading heavily here :
https://github.com/dhruvvyas90/qemu-rpi-kernel
I tried to do something like this :
virt-install \ --name pi \ --machine raspi3 \ --cpu arm1176 \ --memory 1024 \ --import \ --disk /root/Desktop/zi/Work/Android/Raspy/Debian/2019-09-26-raspbian-buster-lite.img,format=raw,bus=virtio \ --network user,model=virtio \ --video vga \ --graphics spice \ --rng device=/dev/urandom,model=virtio \ --boot 'uefi=RPI_EFI.fd,dtb=bcm2710-rpi-3-b-plus.dtb,kernel=kernel8.img,kernel_args=root=/dev/vda2 rootwait panic=1 dwc_otg.fiq_fsm_enable=0' \ --events on_reboot=destroy
But I get this error :
ERROR internal error: Unexpected enum value 0 for virDomainDeviceAddressType
I've got the UEFI BIOS file from here :
I'm not sure if it isn't the right efi file to use in this specific configuration or if it is,but I'm passing the parameter badly. What do you suggest me to do ?
Hello we are trying to run docker-machine-kvm on arm64 and we are getting the following error
we found something similar here https://github.com/kubevirt/kubevirt/issues/2470. It seems to be related to having hardcoded the architecture somewhere but honestly no idea :man_shrugging:, just doing my best guess.