Description of problem

If you enable vsock support with use_vsock = true in the runtime config file, but, you don't happen to have the vsock kernel modules loaded, the kata-env output is a bit confusing, as it implies it has not seen the use_vsock...

$ kata-runtime kata-env | fgrep -i vsocks
  UseVSock = false
  SupportVSocks = false

The hint is there, that the host does not support vsocks (for whatever reason) - the second line comes from the [Host] section - but, it is not obvious, as the UseVSock line comes out first in the kata-env, and 'feels' like it reflects the config file setting... I started off wondering if the runtime had managed to pick up my config file change for instance.

Expected result

I think it would be nice if on the UseVSock line, maybe it could be appended with kernel module not loaded? - if use_vsock is set to true in the config file.

I think this is a touch tricky, as the kata-env code afaik pretty much just prints out the internal status structures, and thus this level of detail doesn't currently fit in with that. But, if we can make it a little more obvious that the runtime knows you asked for vsock, but could not load it... that'd be nice.