Skip to content

failing to start a VM produces a "cannot drop a runtime in a context where blocking is not allowed" panic #838

@gjcolombo

Description

@gjcolombo

Repro steps: start a VM with an invalid configuration (e.g. an attached NIC that refers to a nonexistent host VNIC).

Expected: initialization fails and returns a nice error message to the instance_ensure caller.

Observed: Propolis panics with a tokio "can't drop a runtime in this context" error.


The dropped runtime is the per-VMM runtime that gets created during VM initialization and used to initialize the VMM, run per-component tasks, and the like. This doesn't happen during orderly VM shutdown because Vm::complete_rundown calls shutdown_background on this runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething that isn't working.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions