From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Bug 1563887 <1563887@bugs.launchpad.net>,
Mike Rushton <mike.rushton@canonical.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Date: Tue, 05 Apr 2016 17:18:53 -0500 [thread overview]
Message-ID: <20160405221853.589.14087@loki> (raw)
In-Reply-To: <20160405214729.32473.76723.malone@wampee.canonical.com>
Quoting Mike Rushton (2016-04-05 16:47:29)
> @mdroth
>
> I don't think PPC supports kvm the same way as x86:
>
> ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::2222-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio
> Could not access KVM kernel module: Permission denied
> failed to initialize KVM: Permission denied
-enable-kvm should work as expected on Power machines that support
KVM.
You seem to be running the command as a normal user. KVM generally
requires a priviledged user.
next prev parent reply other threads:[~2016-04-05 22:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160330141641.3353.24299.malonedeb@chaenomeles.canonical.com>
2016-03-31 18:12 ` [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le Serge Hallyn
2016-03-31 19:36 ` Mike Rushton
2016-04-01 0:42 ` Serge Hallyn
2016-04-01 4:48 ` Serge Hallyn
2016-04-01 4:58 ` Serge Hallyn
2016-04-01 15:30 ` Serge Hallyn
2016-04-01 16:56 ` Serge Hallyn
2016-04-02 14:33 ` Michael Roth
2016-04-03 5:14 ` Serge Hallyn
2016-04-03 5:43 ` Serge Hallyn
2016-04-03 6:00 ` [Qemu-devel] [Bug 1563887] Status changed to Confirmed Brad Figg
2016-04-04 5:21 ` [Qemu-devel] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le Serge Hallyn
2016-04-04 14:49 ` Mike Rushton
2016-04-04 17:12 ` Michael Roth
2016-04-04 16:34 ` Serge Hallyn
2016-04-04 16:40 ` Serge Hallyn
2016-04-05 18:10 ` Mike Rushton
2016-04-05 19:34 ` Serge Hallyn
2016-04-05 19:40 ` Michael Roth
2016-04-05 21:44 ` Mike Rushton
2016-04-05 21:47 ` Mike Rushton
2016-04-05 22:18 ` Michael Roth [this message]
2016-04-05 22:22 ` Mike Rushton
2016-04-05 23:10 ` Michael Roth
2016-04-06 3:46 ` Mike Rushton
2016-04-06 20:10 ` Serge Hallyn
2016-04-06 20:20 ` Scott Moser
2016-04-06 20:40 ` Mike Rushton
2016-04-06 20:43 ` Mike Rushton
2016-04-06 21:10 ` Scott Moser
2016-04-06 21:12 ` Scott Moser
2016-04-06 23:13 ` Serge Hallyn
2016-04-07 22:20 ` Jon Grimm
2016-04-08 19:16 ` Alberto Salvia Novella
2016-04-13 1:22 ` Ryan Harper
2016-04-13 14:38 ` Ryan Harper
2016-04-13 15:43 ` Michael Hohnbaum
2016-04-13 16:59 ` Jon Grimm
2016-04-13 17:45 ` Ryan Harper
2017-11-10 23:22 ` Robin H. Johnson
2017-11-13 13:08 ` ChristianEhrhardt
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=20160405221853.589.14087@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=1563887@bugs.launchpad.net \
--cc=mike.rushton@canonical.com \
--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).