[Qemu-devel] [Bug 529008] Re: Should emulate /proc/cpuinfo

[Qemu-devel] [Bug 529008] Re: Should emulate /proc/cpuinfo

[DaveHansen]

If you're chroot'ing anyway, then you should have privileged access.
You could probably do this entirely in userspace, without even specially
intercepting the syscalls.  When you set up the chroot, just get a copy
of how you want cpuinfo to look, and bind mount it on top of the
existing cpuinfo file:

root@nimitz:~# egrep cache.size\|^processor /proc/cpuinfo 
processor	: 0
cache size	: 4096 KB
processor	: 1
cache size	: 4096 KB
root@nimitz:~# cat /proc/cpuinfo | perl -pe 's/4096 KB/8192 KB/g' > cpuinfo.lie
root@nimitz:~# mount --bind cpuinfo.lie /proc/cpuinfo 
root@nimitz:~# egrep cache.size\|^processor /proc/cpuinfo 
processor	: 0
cache size	: 8192 KB
processor	: 1
cache size	: 8192 KB

Would that work?

-- 
Should emulate /proc/cpuinfo
https://bugs.launchpad.net/bugs/529008
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New
Status in “qemu-kvm” package in Ubuntu: Confirmed

Bug description:
Binary package hint: qemu-kvm

qemu should emulate /proc/cpuinfo contents as some apps parse it to find out which CPU they are running on.

[Qemu-devel] [Bug 529008] Re: Should emulate /proc/cpuinfo

[Anthony Liguori]

I think the preferred way to do this is just to create a /proc/cpuinfo
file within the root file system.  It's impossible for qemu to know
which file is /proc/cpuinfo because you can technically mount procfs
anywhere.

** Changed in: qemu
       Status: New => Invalid

-- 
Should emulate /proc/cpuinfo
https://bugs.launchpad.net/bugs/529008
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid
Status in “qemu-kvm” package in Ubuntu: Confirmed

Bug description:
Binary package hint: qemu-kvm

qemu should emulate /proc/cpuinfo contents as some apps parse it to find out which CPU they are running on.