[Devel] [PATCH rh7] ve: remove fairsched node only in the legacy mode

Konstantin Khorenko khorenko at virtuozzo.com
Thu Jun 4 03:43:49 PDT 2015


On 05/29/2015 02:05 PM, Cyrill Gorcunov wrote:
> On Fri, May 29, 2015 at 01:58:15PM +0300, Vladimir Davydov wrote:
>> Currently, we try and fail to remove the fairsched node of a UUID-named
>> container from the kernel on stop:
>>
>>   CT: 956ebfc3-3ca9-44e0-9739-ab8abbe50edc: started
>>   Can't remove fairsched node 1073741823 err=-2
>>   CT: 956ebfc3-3ca9-44e0-9739-ab8abbe50edc: stopped
>>
>> We should only do that for containers created via the legacy API (vzctl
>> ioctl), because for UUID-named containers this is a duty of vzctl.
>>
>> https://jira.sw.ru/browse/PSBM-33833
>>
>> Signed-off-by: Vladimir Davydov <vdavydov at parallels.com>
> Acked-by: Cyrill Gorcunov <gorcunov at openvz.org>
> 
> Guys, we have a few fields already
> 
> struct ve_struct {
> 	...
> 	int is_running;
> 	int is_locked;
> 	...
> }
> 
> and now new one @legacy. Maybe it worth to merge them all
> into some bitfield?

Well, why not.
Please do it once you have free time => thus i believe not in the near future, right? :)

Or may be someone will do it faster and contribute.

Guys, see - quite many places to fix, but the logic is easy: a good patch to start, you are welcome! :)



More information about the Devel mailing list