Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Custom substrate node does not start in a VM without --wasm-execution interpreted-i-know-what-i-do #12073

@gdethier

Description

@gdethier

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

After an upgrade of the dependencies of our node implementation from substrate polkadot-v0.9.25 to polkadot-v0.9.26, our nodes do not start up on some machines. The following error message is shown:

Cannot create a runtime error=Other("cannot create module: compilation settings are not compatible with the native host")

In this issue, it is mentioned that the problem could come from virtualization, which is indeed the case here (we are using a fully virtualized test infrastructure). Running the same executable on a bare metal machine does not produce the problem which enforces the hypothesis.

A workaround is to pass the option --wasm-execution interpreted-i-know-what-i-do, then the nodes start up as usual and everything works as expected.

The issue above suggests that the problem is coming from wasmtime which has been upgraded to 0.38.x end of June. Maybe that another upgrade would help?

Steps to reproduce

  1. Build this version of our node
  2. Run it in a qemu VM with --dev flag
  3. The node does not start and an error message is displayed

Metadata

Metadata

Assignees

No one assigned

    Labels

    J2-unconfirmedIssue might be valid, but it’s not yet known.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions