Better diagnostic when attempting to run inside an OS that is not a Xen guest
When the user runs a nested Xen and expects dom0 to report its information down to the toolstack below, the error is cryptic:
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
This comes from error propagation using ?
of an error generated inside libxenstore
.
Opened https://github.com/Wenzel/xenstore/issues/22 to get a slightly better error, but knowing that xenstore_rm("attr/vif")
failed is not going to help the user that much.
What we need is early check that we are not in a Xen guest.