OS-7508: mdb: assertion tripped in libvmm when bhyve VM halts while mdb is attached

Details

Issue Type:Bug
Priority:4 - Normal
Status:Resolved
Created at:2019-01-11T17:06:10.046Z
Updated at:2019-02-13T23:33:29.845Z

People

Created by:Hans Rosenfeld [X]
Reported by:Hans Rosenfeld [X]
Assigned to:Hans Rosenfeld [X]

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2019-02-13T23:33:29.834Z)

Fix Versions

2019-02-14 Liz Lemon (Release Date: 2019-02-14)

Related Links

Labels

bhyve

Description

When I attach mdb to a VM and let it continue to run (::cont), then halt the VM from the inside so that it is moved to a deferred-destroy state, mdb will abort due to an assertion being tripped in libvmm as soon as it's returning from ::cont (by Ctrl-C). This used to work, but a change I made during code review apparently broke it and I failed to re-test this particular use case.

Libvmm needs to be prepared to handle this failure (indicated by ENXIO), and mdb-bhyve needs to handle it as well.

Comments

Comment by Hans Rosenfeld [X]
Created at 2019-02-08T17:38:46.467Z

Testing: Same as for OS-7424. mdb did not trip over that assertion in libvmm, instead it stopped and then exited normally.


Comment by Jira Bot
Created at 2019-02-13T23:32:33.766Z

illumos-joyent commit 2d1a8a4a97fe44c06e3fedddbb32f89fc2755a3e (branch master, by Hans Rosenfeld)

OS-7508 mdb: assertion tripped in libvmm when bhyve VM halts while mdb is attached
OS-7519 mdb: bhyve target can attach before the first vCPU is configured