Hi, I asked upstream about this and they say it is fixed in Vserver 2.0.2.2-rc9. I tried the latest version of vserver and it is indeed fixed.