mdb-bhyve mishandles memseg offsets
The library shim over libvmmapi which mdb uses to debug bhyve instances (libvmm) is in charge of mapping in the various memory segments allocated to the instance in order for mdb to inspect and manipulate them. When this was originally implemented, memory segments were never mapped in from an offset (where the start of the mapping in the VM does not correspond to the start of the memseg). As of #12792, this changed for the bootrom segment, which has lead to several challeges for mdb-bhyve (see also: #13008). Since such mapping offsets can be (and are now) a reality,
vmm_map should properly handle them.
Updated by Patrick Mooney 10 months ago
Updated by Electric Monk 9 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit c3d209cab1511045e9bb1a521f1bd85995d4fd7e Author: Patrick Mooney <firstname.lastname@example.org> Date: 2020-08-10T22:55:03.000Z 13008 bhyve devmem could match better 13009 mdb-bhyve mishandles memseg offsets 13010 bhyve should not exit when VM debugged Reviewed by: Andy Fiddaman <email@example.com> Reviewed by: Hans Rosenfeld <firstname.lastname@example.org> Approved by: Robert Mustacchi <email@example.com>