Bug 250671 - error reporting with bhyvectl could be improved
Summary: error reporting with bhyvectl could be improved
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bhyve (show other bugs)
Version: 12.1-STABLE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-virtualization (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-27 13:13 UTC by marko
Modified: 2020-11-05 06:52 UTC (History)
1 user (show)

See Also:


Attachments
svn diff output of the relevant changes (742 bytes, text/plain)
2020-10-27 13:13 UTC, marko
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description marko 2020-10-27 13:13:55 UTC
Created attachment 219145 [details]
svn diff output of the relevant changes

Currently bhyvectl only can have only one type of message when it is unable to establish comms with VM.
---8<----
VM:free12.1 is not created.
---8<----
First time I encountered this lead me astray, as the access issue had to do with user permissions.

Easy way to get more info is to report what system call gave as an error code.

Including a patch as attachment which should address this issue. The libvmmapi change is there so that sysctlbyname() done within vm_destroy() would not override errno set by earlier syscall to open().
Comment 1 Peter Grehan freebsd_committer 2020-11-05 06:52:04 UTC
This looks fine.