From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 529008] Re: Should emulate /proc/cpuinfo
Date: Wed, 02 Jun 2010 19:19:15 -0000 [thread overview]
Message-ID: <20100602191915.14807.99371.malone@wampee.canonical.com> (raw)
In-Reply-To: 20100227142202.21488.20001.malonedeb@soybean.canonical.com
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.
prev parent reply other threads:[~2010-06-02 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100227142202.21488.20001.malonedeb@soybean.canonical.com>
2010-06-02 16:27 ` [Qemu-devel] [Bug 529008] Re: Should emulate /proc/cpuinfo DaveHansen
2010-06-02 19:19 ` Anthony Liguori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100602191915.14807.99371.malone@wampee.canonical.com \
--to=anthony@codemonkey.ws \
--cc=529008@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).