From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Experiences with qemu-system-ppc
Date: Tue, 4 Apr 2006 15:13:41 +0100 [thread overview]
Message-ID: <200604041513.43135.jseward@acm.org> (raw)
What are the prospects for qemu-system-ppc being improved to the
point where I can do a vanilla install of popular ppc32-linux
distros?
I've tried a vanilla install of Debian Sarge (3.1). That went
smoothly, except for the stage right at the end, where the disk
image is made bootable. The resulting disk image is, despite
much messing around, not bootable (using QEMU from cvs).
Vesselin Peev made a ppc32 Debian Sarge image with a specially
modified external kernel to work around this problem
(http://free.oszoo.org/ftp/images/debian_sarge_ppc.tar.torrent)
and that does work. Unfortunately QEMU consumes 100% host CPU
even when the virtual machine is idle, which means it's not useful
for a long-running virtual server. And the reliance on a specially
modified kernel means normal updating/upgrading of the virtual
machine isn't possible.
My goal is to run a farm of QEMU virtual ppc32 machines to do
overnight builds/tests of Valgrind on different ppc32 distros.
J
reply other threads:[~2006-04-04 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200604041513.43135.jseward@acm.org \
--to=jseward@acm.org \
--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).