Alpine VM Image Fails To Boot

I am very pleased to see a VM image for Alpine Linux 3.12. Unfortunately on the Raspberry Pi (Arm 64), it fails to boot.

It gets very far, but then gets stuck. Here are the last few lines from the console:-

[ 1.709052] virtio-pci 0000:01:00.5: enabling device (0000 -> 0002)
[ 1.723283] virtio-pci 0000:03:00.0: enabling device (0000 -> 0002)
[ 1.764488] input: QEMU Virtio Keyboard as /devices/pci0000:00/0000:00:01.0/0000:01:00.2/virtio2/input/input0
[ 1.772125] input: QEMU Virtio Tablet as /devices/pci0000:00/0000:00:01.0/0000:01:00.3/virtio3/input/input1
[ 1.791568] scsi host0: Virtio SCSI HBA
[ 1.797241] scsi 0:0:0:1: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
[ 1.838313] random: fast init done
[ 1.852668] sd 0:0:0:1: Power-on or device reset occurred
[ 1.856522] sd 0:0:0:1: [sda] 19531248 512-byte logical blocks: (10.00 GB/9.31 GiB)
[ 1.860617] sd 0:0:0:1: [sda] Write Protect is off
[ 1.863638] sd 0:0:0:1: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 1.875883] sda: sda1 sda2
[ 1.879001] sd 0:0:0:1: [sda] Attached SCSI disk
[ 1.946668] [drm] pci: virtio-gpu-pci detected at 0000:04:00.0
[ 1.949307] [drm] virgl 3d acceleration not supported by host
[ 1.952143] [drm] EDID support available.
[ 1.955862] [TTM] Zone kernel: Available graphics memory: 501880 KiB
[ 1.958853] [TTM] Initializing pool allocator
[ 1.960963] [TTM] Initializing DMA pool allocator
[ 1.963227] [drm] number of scanouts: 1
[ 1.964967] [drm] number of cap sets: 0
[ 1.968093] [drm] Initialized virtio_gpu 0.1.0 0 for virtio8 on minor 0
[ 1.977615] Console: switching to colour frame buffer device 128x48
[ 1.998697] virtio_gpu virtio8: fb0: virtio_gpudrmfb frame buffer device
[ 2.367389] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
[ 2.370582] EXT4-fs (sda2): write access will be enabled during recovery
[ 2.548338] EXT4-fs (sda2): recovery complete
[ 2.602865] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)

Please can you open an issue over at https://github.com/lxc/lxd/issues

Actually, this is likely an image issue, so should be https://github.com/lxc/lxc-ci/issues

1 Like

@monstermunchkin can you take a look?
Do you still have some rpi that can run LXD?

If not, you can add do:

lxc remote add rpi https://[2001:470:b0f8:1015:dea6:32ff:feb2:befb]:8443

From canonical-lxd (password is rpi) and test things on there.

New issue opened on GitHub. Thanks.