Hi everybody!
I am using Proxmox 1.9 and I greatly appreciate this appliance, keep up the good work.
This being said, I have a little problem regarding the CPUs setting of OpenVZ containers. In short it has no visible effect.
If I set Container 101 to 1 CPU using the Proxmox webgui and afterwards enter the container I can see all hostsystem cores when
doing cat /proc/cpuinfo. I tried to manually "enforce" it by using vzctl directly (vzctl set 101 --cpus 1 --save). It seems to work fine (meaning it displays
no error, neither on stdout/stderr nor in the syslog files) But again I can see all cores when entering the Container. I already restarted the container but the behaviour is the same.
In the openvz irc channel I was told this is related to the debian OpenVZ kernel. (Which is probably the one being used with proxmox?) as this kernel lacks
support for that (among other things the RHEL kernel supports). Now I was wondering is it safe to try using the RHEL kernel? (or do you modify thing in the kernel directly to do the proxmox-pve magic?
) Also I wanted to ask if it really IS related to the debian kernel and if others also see this behaviour or if I just misconfigured something horribly wrong.
proxmox 1.9 pve-manager/1.9/6542
kernel: 2.6.32-4-pve
I am using Proxmox 1.9 and I greatly appreciate this appliance, keep up the good work.
This being said, I have a little problem regarding the CPUs setting of OpenVZ containers. In short it has no visible effect.
If I set Container 101 to 1 CPU using the Proxmox webgui and afterwards enter the container I can see all hostsystem cores when
doing cat /proc/cpuinfo. I tried to manually "enforce" it by using vzctl directly (vzctl set 101 --cpus 1 --save). It seems to work fine (meaning it displays
no error, neither on stdout/stderr nor in the syslog files) But again I can see all cores when entering the Container. I already restarted the container but the behaviour is the same.
In the openvz irc channel I was told this is related to the debian OpenVZ kernel. (Which is probably the one being used with proxmox?) as this kernel lacks
support for that (among other things the RHEL kernel supports). Now I was wondering is it safe to try using the RHEL kernel? (or do you modify thing in the kernel directly to do the proxmox-pve magic?
) Also I wanted to ask if it really IS related to the debian kernel and if others also see this behaviour or if I just misconfigured something horribly wrong.proxmox 1.9 pve-manager/1.9/6542
kernel: 2.6.32-4-pve
