Skip to content

Better error message on VM.start when topology is wrong #5968

Open
@olivierlambert

Description

@olivierlambert

Hi,

If you start a VM with 8 sockets with 1 core per socket, it will fail with:

INTERNAL_ERROR(xenopsd internal error: File \"ocaml/xenopsd/xc/domain.ml\", line 1125, characters 2-8: Assertion failed)

Would it be possible to get a more obvious error message? Changing the topology to something more sane will work, but we cannot control what users might decide (or we need a way to avoid selecting any configurations).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions