Page MenuHomeFreeBSD

bhyve: [snapshot] Do not flush readonly device at blockif_pause()
ClosedPublic

Authored by gusev.vitaliy_gmail.com on Mar 2 2023, 6:08 PM.
Tags
Referenced Files
Unknown Object (File)
Sun, Apr 6, 12:47 AM
Unknown Object (File)
Sun, Mar 9, 12:26 AM
Unknown Object (File)
Feb 21 2025, 8:13 AM
Unknown Object (File)
Feb 21 2025, 1:04 AM
Unknown Object (File)
Feb 9 2025, 7:29 PM
Unknown Object (File)
Feb 4 2025, 10:05 AM
Unknown Object (File)
Jan 26 2025, 6:30 PM
Unknown Object (File)
Jan 3 2025, 12:03 AM

Details

Summary

Part of Capsicum integration for snapshots.

Eliminates error:

blockif_pause: [WARN] failed to flush backing file.

Sponsored by: vStack

Test Plan

Compile, run VM, suspend/resume.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

markj added inline comments.
usr.sbin/bhyve/block_if.c
1012

BTW, the BOP_FLUSH handler does not check whether the device is read-only before calling blockif_flush_bc(). Perhaps it should be a no-op in that situation?

This revision is now accepted and ready to land.Mar 2 2023, 9:55 PM
gusev.vitaliy_gmail.com added inline comments.
usr.sbin/bhyve/block_if.c
1012

BOP_FLUSH() is called when emulated device directly calls blockif_flush(). Look at ahci_handle_flush() and nvme_opc_flush()) or pci_vtblk_proc().
In all cases it is just handle of guest's requests. So guest is aware about readonly device and shouldn't call flush commands.