Bug #15314
openbhyve state restore should be safe
0%
Description
When save/restore of kernel device state was added to bhyve in #14261, the ability to restore (read: import) state into devices was guarded with a default-off variable switch vmm_allow_state_writes
. This was done with the assumption that there would be lingering bugs in and exposed by the ability to import device state. Keeping it as opt-in via mdb -kw
meant that we could move forward with integration, and then remove that guard once confidence had been built around that state importation and the emulation logic impacted by it. A few bugs have been found so far (#15118 , #15312, #15251). Once all of those are addressed, it is worth considering the removal of the vmm_allow_state_writes
guard, or at least changing it to default-allow.
Related issues
Updated by Patrick Mooney 22 days ago
- Related to Bug #15118: bhyve too strict over vmm_data lengths added
Updated by Patrick Mooney 22 days ago
- Related to Bug #15312: bhyve has overzealous vlapic ID check added
Updated by Patrick Mooney 22 days ago
- Related to Bug #15251: panic in vlapic_get_ccr after live migration added
Updated by Patrick Mooney 22 days ago
- Related to Bug #15326: bhyve vrtc fails ASSERT after migration added