From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Migration crashes domU
Date: Sun, 11 Jun 2006 10:39:10 -0700 [thread overview]
Message-ID: <448C553E.5060405@hp.com> (raw)
I built xen-unstable changeset 10314 for x86_64 and when I try a
migration, domU panics. (See below.) Has anyone seen this or should I
disassemble the kernel and figure out where things are going wrong?
On a migration related note, how stable is live migration in the testing
tree on x86_64? I am seeing memory corruption in the domU with the
latest SuSE SLES build (9726). I built unstable (with the SuSE config)
to see if it was any better. ("Dead" migration seems to be solid.)
John Byrne
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<ffffffff88002f10>{:xennet:backend_changed+419}
PGD 3d211067 PUD 3de5b067 PMD 0
Oops: 0002 [1] SMP
CPU 0
Modules linked in: ipv6 af_packet loop dm_mod xenblk xennet
Pid: 7, comm: xenwatch Tainted: GF 2.6.16.13-xen-xen #1
RIP: e030:[<ffffffff88002f10>]
<ffffffff88002f10>{:xennet:backend_changed+419}
RSP: e02b:ffff880000a41e68 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff880000c90500 RCX: ffff880000a41d00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880000c90604
RBP: 0000000000000000 R08: 000000000000000a R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000000
R13: 0000000000000100 R14: ffff880000c90000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffffffff8040a000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process xenwatch (pid: 7, threadinfo ffff880000a40000, task
ffff880000a8c810)
Stack: ffff880000a89400 ffff88003e0c3e80 ffffffff8023fc13 ffff880000c81d58
0000000000000000 ffff880000c81d48 ffffffff8013dec6 ffffffff8023f27a
0000000000000000 ffffffff8023fd54
Call Trace: <ffffffff8023fc13>{xenwatch_thread+0}
<ffffffff8013dec6>{keventd_create_kthread+0}
<ffffffff8023f27a>{xenwatch_handle_callback+21}
<ffffffff8023fd54>{xenwatch_thread+321}
<ffffffff8013dec6>{keventd_create_kthread+0}
<ffffffff8013e2cd>{autoremove_wake_function+0}
<ffffffff8013dec6>{keventd_create_kthread+0}
<ffffffff8023fc13>{xenwatch_thread+0}
<ffffffff8013e193>{kthread+212} <ffffffff8010b46a>{child_rip+8}
<ffffffff8013dec6>{keventd_create_kthread+0}
<ffffffff8013e0bf>{kthread+0}
<ffffffff8010b462>{child_rip+0}
Code: 89 02 48 8b 94 eb 78 09 00 00 48 b8 ff ff ff ff ff 87 ff ff
RIP <ffffffff88002f10>{:xennet:backend_changed+419} RSP <ffff880000a41e68>
CR2: 0000000000000000
reply other threads:[~2006-06-11 17:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=448C553E.5060405@hp.com \
--to=john.l.byrne@hp.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.