Date: Sun, 17 Jan 2016 01:41:40 -0800
From: John Nemeth <jnem...@cue.bc.ca>
Message-ID: <201601170941.u0h9fe7r020...@server.cornerstoneservice.ca>
| It's [$xparams] the path to the file to be used as backing store
Then that should be fine.
| As shown in the script fragment, $xparams has nothing to do with
| the choice of which vnd to use.
No, but if it had a geometry in it, as well as a path, that could cause
vnconfig to fail, that's why I asked.
If it doesn't, and
| and as you saw it is nothing more then:
| vnconfig /dev/vnd<n>d <file>
I didn't actually see, as I didn't see the setting of xparams, which (since
it wasn't quoted) could have contained multiple words. But I believe you,
and in that case (as in the reply to Manuel) we need to figure out why
it is failing - perhaps the logic isn't correctly finding an idle vnd,
or perhaps something weird is happening in the kernel.
kre
