Do you have CONFIG_VZ_QUOTA enabled in kernel .config? Do you have vzquota kernel module loaded? I guess the problem is in that.

PS please do not use personal developers' emails -- we have users@ mailing list for such inquiries. See http://wiki.openvz.org/Mailing_lists for more info

Zhaohui Wang wrote:

Hi  Kir and Alexandr,

I am a student at GMU and doing a project need to use openvz. I found that vzquota seems not functioning well on x64 platform. Now it is 3.0.11. But I checked git tree at openvz.org and found that 3.0.12 is there.

Can you tell me how to checkout this new version so that I may have a try?

BTW,the error showing on my system while creating a ve is:

# vzctl create 3 --ostemplate ubuntu-7.10-amd64-minimal

Creating VE private area (ubuntu-7.10-amd64-minimal)

vzquota : (error) Quota getstat syscall for id 3: Inappropriate ioctl for device

vzquota init failed [3]

vzquota : (error) Can't open quota file for id 3, maybe you need to reinitialize quota: No such file or directory

vzquota : (error) Quota getstat syscall for id 3: Inappropriate ioctl for device

vzquota init failed [3]

vzquota on failed [61]

vzquota : (error) Can't open quota file for id 3, maybe you need to reinitialize quota: No such file or directory

vzquota off failed [11]

vzquota : (error) Can't open quota file for id 3, maybe you need to reinitialize quota: No such file or directory

vzquota setlimit failed [11]

Performing postcreate actions

VE private area was created

# vzctl start 3

Starting VE ...

Initializing quota ...

vzquota : (error) Quota getstat syscall for id 3: Inappropriate ioctl for device

vzquota init failed [3]

It’s a x86_64 system,while fc8 is the host.The kernel is compiled by myself .I checked /var/vzquota and nothing is there. It seems that it can not create it by ioctl??

Any hints or suggestions would be greatly appreciated,

Thank you.

Best Regards

Zhaohui Wang


_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users

Reply via email to