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/cpui
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 fil
