OpenVZ Forum: Support » *SOLVED* is it possible to control what /proc/cpuinfo says?

Home » General » Support » *SOLVED* is it possible to control what /proc/cpuinfo says?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*SOLVED* is it possible to control what /proc/cpuinfo says? [message #10319]

Wed, 14 February 2007 23:06

mora
Messages: 37
Registered: October 2006

Member

Hello
is it possible to specify a fake output for a certain VE regarding the system CPU brand

for example i have 2 cpus but i want the VE only display one of them in /proc/cpuinfo

or change brand from perntium to celeron or from xeon to amd

[Updated on: Thu, 15 February 2007 14:17] by Moderator

Report message to a moderator

Re: is it possible to control what /proc/cpuinfo says? [message #10328 is a reply to message #10319]

Thu, 15 February 2007 10:34

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

There are such VE parameters: CPUS and CPULIMIT (--cpus and --cpulimit), that control how much cpu power to give to VE. This parameters also affect contents of /proc/cpuinfo. For example, if you give
# vzctl set 103 --cpus 1 --save
command on the node with two cpus, only one cpu will be visible from VE 103.
If you give:
# vzctl set 103 --cpulimit 50 --save
command on the node with CPU of 2400Mhz, only 1200 Mhz will be visible from /proc/cpuinfo

Read man-page on vzctl for more information.

There is no possibility to change CPU Vendor/Model/features...

Report message to a moderator

Re: is it possible to control what /proc/cpuinfo says? [message #10349 is a reply to message #10328]

Thu, 15 February 2007 13:56

mora
Messages: 37
Registered: October 2006

Member

Thanks for your info very very much

Report message to a moderator

Previous Topic:	VE's and OVZ kernel versions...
Next Topic:	Multiple interfaces eth0, eth1 on different subnets

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Sep 02 04:55:45 GMT 2026

Total time taken to generate the page: 0.61378 seconds