[Xen-users] Problem upgrading from Xen 2.0 to Xen 3.0

[Nate Carlson <natecars@xxxxxxxxxxxxxxx>]

Hey all,

I'm attempting to migrate a Xen 2.0 box to Xen 3.0, and having some 
issues. I'm using the Debian packages posted by Ralph Passgang the other 
day (look good - thanks!), and built my own custom kernel. Dom0 is booting 
fine; I'm having problems when trying to start a DomU.
Config files and such are posted at:
http://www.natecarlson.com/~natecars/xen-problems/config-2.6.12.6-xenu-1
http://www.natecarlson.com/~natecars/xen-problems/domU-output
http://www.natecarlson.com/~natecars/xen-problems/xen-config
http://www.natecarlson.com/~natecars/xen-problems/xen-info
http://www.natecarlson.com/~natecars/xen-problems/xen-dmesg

Let me know if you need any other debug info.

I get the following output at the end of the boot process:

NET: Registered protocol family 2
Registering block device major 8
register_blkdev: cannot get major 8 for sd
xen_blk: can't get major 8 with name sd
Unable to handle kernel NULL pointer dereference at virtual address 
000000f0
 printing eip:
c0283696
*pde = ma 00000000 pa 55555000
Oops: 0002 [#1]
Modules linked in:
CPU:    0
EIP:    0061:[<c0283696>]    Not tainted VLI
EFLAGS: 00010086   (2.6.12.6-xenu-1)
EIP is at blk_start_queue+0x8/0x4e
eax: 00000000   ebx: 00000000   ecx: c06a9740   edx: 00000000
esi: c05f2280   edi: c00f8000   ebp: c00f9f9c   esp: c00f9f30
ds: 007b   es: 007b   ss: 0069
Process xenwatch (pid: 6, threadinfo=c00f8000 task=c16eb020)
Stack: 00000004 c0688000 c029f0c0 00000000 c0688000 c029efea c0688000 00000000
       00000004 00000000 00000200 c0688000 c03688ce c00f9f78 c036a6ea c035bb73
       c00f9f7c 00000000 00000000 00000200 00a00000 c029d839 c029cc7a c0688000
Call Trace:
 [<c029f0c0>] kick_pending_request_queues+0x1e/0x33
 [<c029efea>] connect+0xe9/0x131
 [<c029d839>] otherend_changed+0x0/0x75
 [<c029cc7a>] xenwatch_thread+0x64/0x116
 [<c012af1c>] autoremove_wake_function+0x0/0x4b
 [<c029cc16>] xenwatch_thread+0x0/0x116
 [<c012ab19>] kthread+0x9d/0xa1
 [<c012aa7c>] kthread+0x0/0xa1
 [<c0106709>] kernel_thread_helper+0x5/0xb
Code: 48 54 85 c9 74 06 89 44 24 04 ff e1 c3 8b 44 24 04 8b 48 54 ff e1 81 
44 24 04 90 00 00 00 e9 b3 22 00 00 53 83 ec 04 8b 5c 24 0c <0f> ba b3 f0 
00 00 00 02 0f ba ab f0 00 00 00 06 19 c0 85 c0 75
 <6>IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

Any ideas? Thanks!

------------------------------------------------------------------------
| nate carlson | natecars@xxxxxxxxxxxxxxx | http://www.natecarlson.com |
|       depriving some poor village of its idiot since 1981            |
------------------------------------------------------------------------

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users