When try to use either sda1/sda2 sdb1/sdb2 root/swap combo I get
tracebacks when launching domu.
netfront: Initialising virtual ethernet driver.
Registering block device major 8
register_blkdev: cannot get major 8 for sd
xen_blk: can't get major 8 with name sd
NET: Registered protocol family 2
Unable to handle kernel NULL pointer dereference at virtual address
00000104
printing eip:
c0222268
*pde = ma 00000000 pa 55555000
Oops: 0002 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c0222268>] Not tainted VLI
EFLAGS: 00010086 (2.6.12.6-xenU)
EIP is at blk_start_queue+0x8/0x60
eax: 00000000 ebx: 00000000 ecx: fbf8c000 edx: 00000000
esi: cbc24aa0 edi: c1278000 ebp: c1279f9c esp: c1279f30
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, threadinfo=c1278000 task=c1226560)
Stack: 00000004 cbc08000 c023507e 00000000 cbc08000 c0234f98 cbc08000
00000000
00000004 00000000 00000200 cbc08000 c02c50a0 c1279f78
c02ce518 c02c3a9f
c1279f7c 00000000 00000000 00000200 00b00000 c02333e0
c02327a7 cbc08000
Call Trace:
[<c023507e>] kick_pending_request_queues+0x1e/0x40
[<c0234f98>] connect+0xe8/0x130
[<c02333e0>] otherend_changed+0x0/0xa0
[<c02327a7>] xenwatch_thread+0x87/0x140
[<c01353d0>] autoremove_wake_function+0x0/0x60
[<c0232720>] xenwatch_thread+0x0/0x140
[<c0134ee7>] kthread+0xc7/0xd0
[<c0134e20>] kthread+0x0/0xd0
[<c01077fd>] kernel_thread_helper+0x5/0x18
Code: 00 00 00 8b 44 24 04 8b 48 60 ff e1 8d b4 26 00 00 00 00 81 44
24 04 a0 00 00 00 e9 d3 25 00 00 8d 76 00 53 83 ec 04 8b 5c 24 0c
<f0> 0f ba b3 04 01 00 00 02 f0 0f ba ab 04 01 00 00 06 19 c0 85
<6>IP: routing cache hash table of 2048 buckets, 16Kbytes
I switched to using hda1/hda2 combo and the domU came up. This may be
particular to my mobo setup, have seen this type of problem on and
off since testing the hg stuff before 3.0 was released.
disk = [ 'phy:VolGroup01/debian,hda1,w' , 'phy:VolGroup01/
debswap,hda2,w']
The part that really messes with me is the domU is a debian image
from jailtime.org and its fstab is
dev/sdd1 / ext3 errors=remount-ro 0 1
/dev/sdd2 none swap sw 0 0
proc /proc proc defaults 0 0
I am a tad out of the loop, but from what I recall in the past the
fstab had to match what was provided in the domU's config.
kernel-xenU-2.6.16-1.2080_FC5
kernel-xen0-2.6.16-1.2080_FC5
This also was a yum upgrade.
Should I bugzilla this or is the target still moving :-)
Regards,
Ted
