From: "Stanley Lieber" <stanley.lieber@gmail.com>
To: rhoyerboat@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] recent plan9.iso on hosted kvm/qemu
Date: Wed, 2 Mar 2011 08:53:27 -0600 [thread overview]
Message-ID: <e6f136f32f42d29642de47a9fa413195@EXAMPLE> (raw)
In-Reply-To: <AANLkTinx-2imYKM2W3Xva9ucLXwNFPcQ++XUG6qG59+T@mail.gmail.com>
> I have plan9 running on a qemu installation, and I had a similiar problem
> installing it.
>
> The --no-kvm-irqchip option on the command line may have solved the problem.
>
>
> I also may have walked away from the machine for 6 hours only to return and
> find that it had installed, .... only to tear down the ubuntu distro
> based VM and replace the thing with a gentoo kernel specifically for hosting
> kvm.
>
> The gentoo qemu + --no-kvm-irqchip thing has definately kept the plan9.iso
> installation online. Here is my command-line, its miniscule compared to
> yours.
>
> qemu-system-x86_64 --enable-kvm -net nic,macaddr=45:45:45:45:45:45 -net
> tap,ifname=9tap,script=no,downscript=no -vga std --no-kvm-irqchip -vnc:1
> -hda /home/kvm9/plan9.img -m 256 -daemonize
Thanks, I'll experiment with these options.
> Or perhaps this, --no-kqemu since this is BSD complaining about an invalid
> nvram checksum, other threads seem to indicate the CMOS layout error google
> search pops on BSD across softwares.
>
> http://qemu-forum.ipi.fi/viewtopic.php?f=7&t=1921
As far as I know, KVM/qemu is hosted on Linux. The dmesg in my previous e-mail
was OpenBSD booted on the same instance of KVM/qemu; primarily so I could
get an idea of what hardware KVM/qemu was presenting to the Plan 9 installer.
-sl
next prev parent reply other threads:[~2011-03-02 14:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10045_2495_16663b8cca278b776372dbc44b36387b57580924_6@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_5@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_4@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_3@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_2@arpnetworks.tenderapp>
[not found] ` <10045_2495_16663b8cca278b776372dbc44b36387b57580924_7@arpnetwork>
2011-03-02 10:12 ` Stanley Lieber
2011-03-01 19:49 ` a z
2011-03-02 14:53 ` Stanley Lieber [this message]
2011-03-03 15:20 ` Stanley Lieber
2011-03-06 6:45 ` Jack
2011-03-06 14:09 ` erik quanstrom
2011-03-06 16:00 ` Jack
2011-03-06 17:15 ` erik quanstrom
2011-03-06 19:36 ` Stanley Lieber
2011-03-06 19:41 ` erik quanstrom
2011-03-06 20:42 ` Stanley Lieber
2011-03-07 3:32 ` Stanley Lieber
2011-03-07 3:45 ` erik quanstrom
2011-03-07 4:04 ` Stanley Lieber
2011-03-07 15:11 ` Jack Norton
2011-03-07 16:24 ` erik quanstrom
2011-03-07 17:04 ` Stanley Lieber
2011-03-07 17:11 ` erik quanstrom
2011-03-07 23:27 ` Federico G. Benavento
2011-03-08 5:37 ` Stanley Lieber
2011-03-08 14:40 ` Jack Norton
2011-03-09 9:41 ` Stanley Lieber
2011-03-07 18:06 ` Jack Norton
2011-03-01 20:13 erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2011-02-24 13:40 Stanley Lieber
2011-02-24 19:57 ` Eric Van Hensbergen
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=e6f136f32f42d29642de47a9fa413195@EXAMPLE \
--to=stanley.lieber@gmail.com \
--cc=9fans@9fans.net \
--cc=rhoyerboat@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).