problem management cpuset

[captainlinux]

Hello, I contact because I would find a solution to avoid that customers who order a vps server with a CPU can do with the cpu Htop master (cluster) because I really find this not secure and not insist that the customer to upgrade their offer.
So I ask if there would be no solution to correct this flaw and others.

I have already added this command "lxc.cgroup.cpuset Cpus = 2.3" in a config file / etc / PvE / lxc / VMID>. conf, then I wonder if he has no remedy if it is possible to know which file generates the <VMID> file. conf / etc / PvE / lxc so I can add to each automatic creation.
I use proxmox 4.2.
cordially

 

[dcsapak]

the correct syntax for the line is

lxc.cgroup.cpuset.cpus = 2,3

but beware, the container will only use your 3rd and 4th core, no matter they are already at capacity
and others are idle

 

[captainlinux]

Thank you for your return, what I would like is to know if it is possible that each client lxc when there are a htop he sees that their cpu that one.

also know what creates the file /etc/pve/lxc/<VMID>.conf file, so I can add by default to create the CT

 

[captainlinux]

?

 

[dcsapak]

i do not understand what you want to know.
the .conf files are being generated by proxmox itself, so everytime you create a container/vm the conf file gets generated.

 

[captainlinux]

Hello, yes I understand my whether it would be possible to add the command line in the file. his help me because I can not let this and I prefer otherwise proxmox left to go on vmware or SolusVM.
If not help me correct, it is ok pratque the new version of the PvE my cpu Verily problem and a big problem and I'm not alone I think. the other person prefers not migrais following this problem. it would be possible to find a soltuion for the client to see that their CT cpu command or configurais.
Or add the default file each CT "lxc.cgroup.cpuset.cpus = 2,3" is a plus.

cordially

 

[dcsapak]

sadly i still do not fully understand what you want to know.

with our containers (which are lxc), there is currently no way to fully hide the host cpu information from the containers.
the config line you added just pins the the container to the selected cores, which is not desired in most situations

if you really want to hide the host from your guests, you should use kvm vms (named VM or Virtual Machine in proxmox)