From: Thomas Huth <thuth@redhat.com>
To: Wayne Li <waynli329@gmail.com>
Cc: KONRAD Frederic <frederic.konrad@adacore.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: Missing PVR setting capability
Date: Tue, 22 Oct 2019 20:46:42 +0200 [thread overview]
Message-ID: <b6ef8a2d-04aa-aa73-a8f3-ef649786a163@redhat.com> (raw)
In-Reply-To: <CAM2K0nox06JcmjfM20G1-p2Vwq5Xb7hRAX0DVBfdCepnqUiZQg@mail.gmail.com>
On 22/10/2019 18.24, Wayne Li wrote:
> If I run "lsmod | grep kvm" nothing shows up but if I just do a "find .
> -name "kvm"" I get the following:
[...]
> ./sys/devices/virtual/misc/kvm
> ./sys/class/misc/kvm
> ./sys/kernel/debug/kvm
> ./sys/module/kvm
>
> I guess this shows my OS does have KVM on it?
Alright, I guess that means that KVM compiled into the kernel ... should
be fine, I think.
> I added the two flags you
> mentioned when running QEMU (the -cpu and the -machine flags) but the
> -cpu flag doesn't seem like it's doing anything as even when I put a
> clearly wrong argument after the flag no error related to the cpu is
> thrown. Also it says ppce500 is not a machine type and that the
> supported machines are:
>
> bamboo bamboo
> boeing-machine Boeing Machine
> none empty machine
> ref405ep ref405ep
> taihu taihu
> virtex-ml507 Xilinx Virtex ML507 reference design
Oh, are you running qemu-system-ppc instead of qemu-system-ppc64? I
thought these e*500 CPUs are 64-bit? Is your host kernel 64-bit or 32-bit?
Anyway, if you're using a modified version of QEMU, you should
definitely ask the people who did the modifications there.
Thomas
next prev parent reply other threads:[~2019-10-22 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 21:06 Missing PVR setting capability Wayne Li
2019-10-22 7:04 ` Thomas Huth
2019-10-22 16:24 ` Wayne Li
2019-10-22 16:27 ` Wayne Li
2019-10-22 18:46 ` Thomas Huth [this message]
2019-10-31 20:26 ` Wayne Li
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=b6ef8a2d-04aa-aa73-a8f3-ef649786a163@redhat.com \
--to=thuth@redhat.com \
--cc=frederic.konrad@adacore.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=waynli329@gmail.com \
/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).