From: Karl Rister <kmr@us.ibm.com>
To: virtualization@lists.osdl.org
Subject: lhype guest oops
Date: Fri, 5 Jan 2007 16:14:30 -0600 [thread overview]
Message-ID: <200701051614.31125.kmr@us.ibm.com> (raw)
I am trying to experiment with lhype on a 32bit Intel box and when I launch a
guest I get the following oops message:
-----------
invalid opcode: 0000 [#1]
Modules linked in:
CPU: 0
EIP: 0061:[<c0101223>] Not tainted VLI
EFLAGS: 00010246 (2.6.20-rc2 #1)
EIP is at mwait_idle_with_hints+0x1e/0x3a
eax: c03c8008 ebx: 00000000 ecx: 00000000 edx: 00000000
esi: 00000000 edi: c03c8008 ebp: 4c687970 esp: c03c9f74
ds: 007b es: 007b ss: 0069
Process swapper (pid: 0, ti=c03c8000 task=c039c420 task.ti=c03c8000)
Stack: 00000000 c040102c c03fd120 c0101333 c03ca693 c0344d03 c03ca1b8 c03fd120
c03fe320 c03d5b56 00000000 00000000 00401000 00000001 00000000 00000000
c03fd120 c040102c 00000100 c040101c c03fd020 92000000 0000000f c039fee0
Call Trace:
[<c0101333>] cpu_idle+0x39/0x4e
[<c03ca693>] start_kernel+0x2d9/0x2dd
[<c03ca1b8>] unknown_bootoption+0x0/0x202
[<c03d5b56>] lhype_init+0x35f/0x366
[<c03d5b5d>] lhype_maybe_init+0x0/0x1a
=======================
Code: 11 00 00 00 e8 13 0e 01 00 83 c4 0c c3 57 56 53 89 c6 89 d3 89 e0 25 00
e0 ff ff 8d 78 08 8b 40 08 a8 08 75 1e 31 c9 89 f8 89 ca <0f> 01 c8 89 e0 25
00 e0 ff ff 8b 40 08 a8 08 75 07 89 f0 89 d9
EIP: [<c0101223>] mwait_idle_with_hints+0x1e/0x3a SS:ESP 0069:c03c9f74
<0>Kernel panic - not syncing: Attempted to kill the idle task!
lhype_add: CRASH: Attempted to kill the idle task!
-----------
The invocation of lhype_add that I made is:
./linux-2.6.20-rc2/drivers/lhype/lhype_add --verbose 64m
0 /boot/vmlinux-2.6.20-rc2-lhype --tunnet=192.168.0.1 --block=linux-test/linux.img
root=/dev/lhba
Can anyone point me in the direction of figuring this out?
Thanks.
--
Karl Rister
next reply other threads:[~2007-01-05 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 22:14 Karl Rister [this message]
2007-01-06 5:23 ` lhype guest oops Rusty Russell
2007-01-08 20:26 ` Karl Rister
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=200701051614.31125.kmr@us.ibm.com \
--to=kmr@us.ibm.com \
--cc=virtualization@lists.osdl.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).