Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

[Ross Vandegrift <rvandegrift@debian.org>]

Hi Lucas,

On Wed, Jul 26, 2023 at 08:53:29PM +0200, Lucas Nussbaum wrote:
> On 24/07/23 at 22:00 -0700, Ross Vandegrift wrote:
> > I've been in touch with folks from the kdevops project [1].  They are looking
> > for more vagrant images for arm64.  Would it be possible to publish the arm64
> > boxes that debian-vagrant-images can build?
> > 
> > I started looking into this.  I'm pretty new to vagrant, but here's what I
> > learned so far:
> > 
> > - vagrant doesn't handle boxes with different architectures [2].  The advice
> >   seems to be to publish under a different name: e.g.  "debian/testing-arm64".
> > 
> > - Building the arm64 box works just fine, and I can import it sucessfully.
> > 
> > - I'm trying to get vagrant to boot it, but still not quite there yet.
> 
> If you manage to get working images for arm64, I would then be happy to
> maintain them at the same time as the amd64 images.

I've confirmed the vagrant arm64 build works with qemu on amd64.  If you have
qemu-system-arm and qemu-efi-aarch64 installed, the following Vagrantfile
should boot up:

Vagrant.configure("2") do |config|
  config.vm.box = "debian/bookworm-arm64"

  config.vm.provider :libvirt do |libvirt|
    libvirt.cpu_mode = "custom"
    libvirt.cpu_model = "max"
    libvirt.driver = "qemu"
    libvirt.emulator_path = "/usr/bin/qemu-system-aarch64"
    libvirt.graphics_type = "none"
    libvirt.input :type => "mouse", :bus => "virtio"
    libvirt.loader = "/usr/share/AAVMF/AAVMF_CODE.fd"
    libvirt.nvram = "/var/lib/libvirt/qemu/nvram/vagrant.fd"
    libvirt.machine_arch = "aarch64"
    libvirt.machine_type = "virt"
    libvirt.memory = 512
  end
end

The system tests need some easy fixes.  The end to end test tries to boot the
image on the native arch.  It probably needs a feature to check if qemu is
needed.  Time permitting, I plan to look at these in the next few days.

Ross