Bug 250671
| Summary: | error reporting with bhyvectl could be improved | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | marko | ||||
| Component: | bhyve | Assignee: | freebsd-virtualization (Nobody) <virtualization> | ||||
| Status: | New --- | ||||||
| Severity: | Affects Some People | CC: | grehan | ||||
| Priority: | --- | ||||||
| Version: | 12.1-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
This looks fine. |
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().