firecracker: Virtual block device containing UEFI partitions not mounted

I’m running the following command:

sudo ./firectl --firecracker-binary=$HOME/firecracker --kernel=$HOME/vmlinux --root-drive=$HOME/flatcar_production_image.bin --root-partition="cf6a426f-c175-42b9-a165-fd3bab6a652c" --kernel-opts="rootflags=rw mount.usrflags=ro BOOT_IMAGE=/flatcar/vmlinuz-a mount.usr=/dev/mapper/usr verity.usr=PARTUUID=7130c94a-213a-4e5a-8e26-6cce9662f132 consoleblank=0 flatcar.first_boot=detected flatcar.randomize_disk_guid=00000000-0000-0000-0000-000000000001 verity.usrhash=2ba8709773c62cf8a4feb3651ca220ce633340ec9de142f80c412d43a7f78253 console=ttyS0 reboot=k panic=1 pci=off" --cpu-template=T2 --memory=1024

Despite I get this:

INFO[0000] Attaching drive /home/salvo/flatcar_production_image.bin, slot 1, root true.
INFO[0000] Attached drive /home/salvo/flatcar_production_image.bin: [PUT /drives/{drive_id}][204] putGuestDriveByIdNoContent

I do not see any device mounted in my host machine in fact it does not boot up correctly returning

Warning: /dev/disk/by-partuuid/cf6a426f-c175-42b9-a165-fd3bab6a652c does not exist

I would not mind improving the mounting of the device wiring a PR in case there is an issue. However, at the moment, I’m stuck to debug further the following issue.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (3 by maintainers)

Most upvoted comments

@tnotw your hint is gold. It must be that the reason. From the doc

Allow virtio-mmio devices instantiation via the kernel command line or module parameters. Be aware that using incorrect parameters (base address in particular) can crash your system - you have been warned. See Documentation/admin-guide/kernel-parameters.rst for details.

and CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set in the Flatcar kernel