Bug 202321
| Summary: | [bhyve,patch] More verbose error reporting in bhyve for backing images | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Willem Jan Withagen <wjw> | ||||
| Component: | bin | Assignee: | freebsd-virtualization (Nobody) <virtualization> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Some People | CC: | grehan | ||||
| Priority: | --- | Keywords: | patch | ||||
| Version: | CURRENT | Flags: | wjw:
mfc-stable10?
|
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Fix assignment. This is a useful change: I'll get it in. A commit references this bug: Author: bapt Date: Fri May 27 11:46:54 UTC 2016 New revision: 300843 URL: https://svnweb.freebsd.org/changeset/base/300843 Log: Improve error message when failing to open a backing file When bhyve cannot open a backing file, it now says explicitly which file could not be opened Note that the change has only be maed in block_if.c and not in pci_virtio_block.c as the error will always be catched by the first PR: 202321 (different patch) Reviewed by: grehan MFC after: 3 day Sponsored by: Gandi.net Differential Revision: https://reviews.freebsd.org/D6576 Changes: head/usr.sbin/bhyve/block_if.c |
Created attachment 159856 [details] more verbose errors when loading a backing file When starting a bhyve proces with an erroneous backing image, then error report does give the info which device we are talking about, or what file is in error. The the patch generates a bit more info. Save a lot of soul searching if one has a lot of devices connected.