KR> Let say the user only specifies the RefConfig plus an additional net
KR> device for the ResourceSettings. The value for count is 1 (because
KR> that's the size of the array passed in). The net device isn't a
KR> dup, so the value of index is bumped up to 1, and we return an
KR> error.
Oh, right, hmm. That must have been broken with refconf before, I
think. That scenario worked for me in my testing, but I think I
actually lucked out because of the way I was doing my resources.
Hrm, I'll have to think about the best way to fix up the list max
length.
Thanks!
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com