firecracker-microvm/firecracker · error

address should be allocated

Error message

address should be allocated

What it means

Error "address should be allocated" thrown in firecracker-microvm/firecracker.

Source

Thrown at src/vmm/src/builder.rs:288

    if let Some(entropy) = vm_resources.entropy.get() {
        attach_entropy_device(
            &mut device_manager,
            &vm,
            &mut boot_cmdline,
            entropy,
            event_manager,
        )?;
    }

    // Attach virtio-mem device if configured
    if let Some(memory_hotplug) = &vm_resources.memory_hotplug {
        attach_virtio_mem_device(
            &mut device_manager,
            &vm,
            &mut boot_cmdline,
            memory_hotplug,
            event_manager,
            virtio_mem_addr.expect("address should be allocated"),
        )?;
    }

    #[cfg(target_arch = "aarch64")]
    device_manager.attach_legacy_devices_aarch64(
        &kvm_vm,
        event_manager,
        &mut boot_cmdline,
        vm_resources.serial_out_path.as_ref(),
        vm_resources.serial_rate_limiter(),
    )?;

    device_manager.attach_vmgenid_device(&kvm_vm)?;
    device_manager.attach_vmclock_device(&kvm_vm)?;

    #[cfg(target_arch = "aarch64")]
    if vcpus[0].kvm_vcpu.supports_pvtime() {
        setup_pvtime(&mut kvm_vm.resource_allocator(), &mut vcpus)?;

View on GitHub (pinned to a5a45f68b8)

Solutions

1. Ensure the MMIO address range is allocated before the device is attached.
2. Check device-manager ordering so address allocation precedes device creation.

When it happens

Trigger: Thrown at src/vmm/src/builder.rs:288 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of firecracker-microvm/firecracker@a5a45f68b8 (2026-08-19). Data as JSON: /api/errors/f228a794e6b8a769. Report an issue: GitHub.