9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike <mc-al34luc@sbcglobal.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not recognized.
Date: Wed,  4 Jul 2007 09:40:04 -0700	[thread overview]
Message-ID: <468BCD64.10709@sbcglobal.net> (raw)

Greetings,

I followed these instructions:

http://www.cs.bell-labs.com/wiki/plan9/Installing_in_Xen/index.html


for installing plan9 in a Xen domU. It appeared to go swimmingly, until
I tried booting the image file after my successful install:

216# xm create -c plan9.py
Using config file "./plan9.py".
Error: unknown image type: plan9
217# file plan9.img
plan9.img: x86 boot sector
218# ls -l plan9.img
-rw-r--r-- 1 root root 1073741824 2007-07-04 08:56 plan9.img
219#

My plan9.py looks like:

kernel = "/export/2/Guests/Plan9/9xenpcf.gz"
builder = "plan9"
memory = 256
name = "plan9"
vif = [ 'mac=aa:00:10:00:00:1b, bridge=xen-br0' ]
disk = [ 'file:/export/2/Guests/Plan9/plan9.img,loop0,w' ]
ip = "10.10.0.9/24"         # <- IP you will give to xen9
#restart = 'never'
console = 999

# This is the equivalent of plan9.ini:
extra="""
nobootprompt=local
"""

My dom0 is Fedora 7 + Xen 3.1, both compiled with PAE turned off.

Apparently, Xen on F7 doesn't recognize the boot image plan9.img,
created by the plan9 install.

Any hints as to what incantations I may have missed?

Thank you,

Mike


             reply	other threads:[~2007-07-04 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 16:40 Mike [this message]
2007-07-04 17:05 ` [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not Richard Miller
2007-07-04 17:26   ` ron minnich
2007-07-06 13:21     ` Richard Miller
2007-07-06 14:43       ` ron minnich
2007-07-06 15:03         ` Richard Miller
2007-07-04 23:07   ` Mike
2007-07-05  7:01     ` ron minnich
2007-07-05 14:17       ` Mike
2007-07-05  8:39     ` Richard Miller
2007-07-05 14:11       ` Mike

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=468BCD64.10709@sbcglobal.net \
    --to=mc-al34luc@sbcglobal.net \
    --cc=9fans@cse.psu.edu \
    /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).