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
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
Tagged linux-user as I think that describes well what codebase I mean.
** Tags added: linux-user
--
Should emulate /proc/cpuinfo
https://bugs.launchpad.net/bugs/529008
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
To your last question, Loic, tags, no, QEMU upstream hasn't yet really
made use of tags. Feel free to add one ;-)
--
Should emulate /proc/cpuinfo
https://bugs.launchpad.net/bugs/529008
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This is about qemu-arm as in the syscall emulation version of qemu;
/proc/cpuinfo is simply the host's /proc/cpuinfo, but when one emulates
e.g. an ARM program which reads /proc/cpuinfo to find out on which
architecture it's running (or which features the CPU has), it wont find
the relevant info.
NB: qemu in machine emulation mode doesn't have this problem obviously,
since an emulated kernel is returning the /proc/cpuinfo for the virtual
hardware it's running on.
Is there a way to tag qemu-kvm bugs related to qemu syscall versus
machine emulation?
--
Should emulate /proc/cpuinfo
Adding an upstream task.
Anthony will be able to tell us if this is possible, and why
/proc/cpuinfo is structured the way it currently is in QEMU.
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Wishlist
** Changed
I don't know what is meant by should emulate /proc/cpuinfo. Can you
please be more specific?
NB, the default CPU that is exposed is a generic one which allows for
maximum portability with respect to live migration. You can use the
'-cpu host' option to expose the underlying host CPU although
