From: "Kenneth L Van Alstyne" <plan9@kvanals.org>
To: 9fans@9fans.net
Subject: [9fans] Plan 9 on Xen 3.2.1 / 32-bit PAE Kernel / 64-bit Hypervisor
Date: Tue, 9 Feb 2010 20:04:14 +0000 [thread overview]
Message-ID: <04d528b4d839223d477d07e520f7af3f.squirrel@webmail.kvanals.org> (raw)
Wow, thanks for the fast responses!
For what it's worth, the following is my Xen config:
kernel = "/home/kvanals/plan9/9xeninst-pae.gz"
memory = 32
vcpus = '1'
name = "plan9.kvanals.org"
vif = [ 'mac=00:16:3E:9F:FF:01' ]
disk = [ 'file:/home/kvanals/plan9/plan9.img,sda,w',
'file:/home/kvanals/plan9/plan9.iso,sdb,r' ]
reboot = 'never'
extra="""
nobootprompt=local!/boot/bzroot
bootfile=sd01!cdboot!bootdisk.img
"""
Furthermore, this box only has 4GB of physical memory:
wired:~# xm info | grep total_memory
total_memory : 4095
Mr. Miller: I attempted to use your newly uploaded kernel, but was
greeted with a very similar panic:
wired:~# xm create -c /home/kvanals/plan9/boot.conf
Using config file "/home/kvanals/plan9/boot.conf".
Plan 9
127 holes free
0018a000 00dba000 12779520
12779520 bytes free
cpu0: 2792MHz AuthenticAMD AMD64 (cpuid: AX 0x20F51 DX 0x78BFBFF)
Started domain plan9.kvanals.org
panic: xenupdatema - pte 80184010 value
23c9b027
panic: xenupdatema - pte 80184010 value 23c9b027
dumpstack
ktrace /kernel/path 8001444c 80002e2c <<EOF
estackx 80003000
80002dcc=8001428d 80002dd8=80040836 80002ddc=8006bac4 80002de4=8006bb25
80002df0=80072d0c 80002e00=8004097d 80002e10=8006d0ba 80002e14=8001444c
80002e28=8001444c 80002e2c=80014291 80002e34=80040da3 80002e48=8006aa5a
80002e84=80073a0a 80002e90=80074844 80002ea4=80073c44 80002ed0=8006d0f9
80002ed4=8006aa5a 80002edc=80072d0c 80002ef0=80070200 80002ef4=80070206
80002f00=8006d0ba 80002f0c=8006d0ba 80002f10=80070438 80002f18=8007071c
80002f24=8006aa5a 80002f38=80070823 80002f44=8006c5a9 80002f60=8006cbf2
80002f8c=80011cc5 80002fac=80011be5 80002fb8=8001220a 80002fc4=80012256
80002fe4=00000000 80002fe8=801c5ff8 80002fec=80010a37 80002ff0=800b0147
80002ff4=00000000 80002ff8=8001001f 80002ffc=00000000
EOF
cpu0: exiting
cpu0: spurious interrupt 102, last 0
cpu0: spurious interrupt 102, last 0
cpu0: spurious interrupt 102, last 0
cpu0: spurious interrupt 102, last 0
...
Upon doing some "Googling" I came across one other mention of this problem
on 9fans, but it was never solved:
http://9fans.net/archive/2009/12/67
Thanks,
Kenny
next reply other threads:[~2010-02-09 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 20:04 Kenneth L Van Alstyne [this message]
2010-02-10 15:43 ` Richard Miller
2010-02-11 9:41 ` Jano
2010-02-11 10:30 ` [9fans] Plan 9 on Xen 3.2.1 / 32-bit PAE Kernel / 64-bit Richard Miller
2010-02-13 10:18 ` Richard Miller
2010-02-15 9:39 ` Jano
-- strict thread matches above, loose matches on Subject: below --
2010-02-09 8:10 [9fans] Plan 9 on Xen 3.2.1 / 32-bit PAE Kernel / 64-bit Hypervisor Wolfgang Kunz
2010-02-09 1:12 Kenneth L Van Alstyne
2010-02-09 10:36 ` Richard Miller
2010-02-09 15:01 ` erik quanstrom
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=04d528b4d839223d477d07e520f7af3f.squirrel@webmail.kvanals.org \
--to=plan9@kvanals.org \
--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).