[Bug 262113] bhyveclt: Every second attempt to destroy->run fails with: invalid argument error

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 22 Feb 2022 23:50:31 UTC

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
              Flags|                            |maintainer-feedback?(markj@
                   |                            |FreeBSD.org),
                   |                            |maintainer-feedback?(manu@f
                   |                            |reebsd.org),
                   |                            |maintainer-feedback?(rew@Fr
                   |                            |eeBSD.org)
             Status|New                         |Open
            Summary|bhyve fails every other     |bhyveclt: Every second
                   |attempt to run              |attempt to destroy->run
                   |                            |fails with: invalid
                   |                            |argument error
                 CC|                            |manu@freebsd.org,
                   |                            |markj@FreeBSD.org,
                   |                            |rew@FreeBSD.org,
                   |                            |virtualization@FreeBSD.org
           Keywords|                            |needs-qa

--- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> ---
@Reporter Are you able to run these under truss, dtrace or similar and include
the trace output as an attachment, compressed if necessary?

Note: For triage/resolution purposes, re comment 2, we have two issues

- the docs issue that would seem to imply destroy is necessary in certain
cases. Is this true or required for any cases at present, and if so, are there
alternative changes that may be made to preclude the need for this?

- presumably we'd like a destroy/run cycle/procedure to either a) work, or, at
least b) have an improved user experience that an error every second attempt.

^Triage: Request feedback from folks playing in the bhyve tree recently in the
event they have opinions or suggestions for resolution of this issue.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.