data did not match any variant of untagged enum QmpMessage

[bradleyd]

Hey, thanks for putting this crate out.

I am using latest release and when using aarch64 qemu I get this error:

got qmp error on execute: Io(Custom { kind: InvalidData, error: Error("data did not match any variant of untagged enum QmpMessage", line: 0, column: 0) })

Qemu version 9.0.0

It works fine on x86_64.

Any ideas?

[p-alik]

If I see that correctly, the last qapi-rs release v0.14.0 was built for qemu v8.1.0. So for qemu 9.0 you have either to use main branch in your Cargo.toml or to wait for the next release.

[arcnmx]

If this is still failing on 0.15.0 (9.1.0 schema), try producing logs that include the JSON message using RUST_LOG=trace or similar.

[Apokleos]

Similar issue when I upgrade the qapi version from v0.14.0 to v0.15.0.

# qapi = { version = "0.14", features = [ "qmp", "async-tokio-all" ] }
# qapi-spec = "0.3.1"
# qapi-qmp = "0.14.0"
qapi = { version = "0.15", features = ["qmp", "async-tokio-all"] }
qapi-spec = "0.3.2"
qapi-qmp = { version = "0.15", optional = true }

# cd /root/kata-containers/src/runtime-rs/ 
# make
....
error: failed to run custom build command for `qapi-qmp v0.15.0`

Caused by:
  process didn't exit successfully: `/root/kata-containers/src/runtime-rs/target/release/build/qapi-qmp-24e6533a81b02948/build-script-build` (exit status: 101)
  --- stdout
  rerun-if-changed=build.rs

  --- stderr
  thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/qapi-qmp-0.15.0/build.rs:8:19:
  Custom { kind: InvalidData, error: Error("data did not match any variant of untagged enum Spec", line: 0, column: 0) }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

@arcnmx How to address this ? Thx