From: John Soros <sorosj@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] plan9 on amd64 xen hypervisor and dom0
Date: Sat, 5 Dec 2009 23:09:27 +0100 [thread overview]
Message-ID: <200912052309.27827.sorosj@gmail.com> (raw)
Hello,
I've come around a nice hardware to do VM stuff on, so i installed a Debian
xen host (amd64 hypervisor and dom0) on it, and then started to play with
plan9. I followed the
http://www.9grid.fr/wiki/plan9/installing_in_xen_3.0/index.html document to
set up the guest, but right when i try to boot the installation, i get:
"cpu0: spurious interrupt 102, last 0"
This line is spat out at a very high speed, it takes over my terminal in less
than a second...
I was told in #plan9 this was probably due to my having installed a 64bit os.
My question is 1; is that correct and 2; how difficult is it to fix?
I'm really bummed i can't run plan9, as all of my hardware that could support
it died off me.
Thanks
John
next reply other threads:[~2009-12-05 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 22:09 John Soros [this message]
2009-12-05 22:16 ` John Soros
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=200912052309.27827.sorosj@gmail.com \
--to=sorosj@gmail.com \
--cc=9fans@9fans.net \
/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).