I''ve managed to compile my dom0 kernel, however on attempting to boot
to it, I
get a kernel panic. After much fiddling aronud with a serial link I have
managed to get this output.
Any ideas or feedback are most welcome.
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen).
Linux version 2.6.12.6.5-xen (root@bb3) (gcc version 3.4.4 (Gentoo 3.4.4-r1,
ssp-3.4.4-1.0, pie-8.7.8)) #4 SMP Fri Nov 18 04:14:23 GMT 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000006000000 (usable)
104MB LOWMEM available.
On node 0 totalpages: 26624
DMA zone: 26624 pages, LIFO batch:15
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
found SMP MP-table at 000fe710
DMI 2.3 present.
ACPI: RSDP (v000 DELL ) @ 0x000fd650
ACPI: RSDT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd664
ACPI: FADT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd6b0
ACPI: MADT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd724
ACPI: SPCR (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd7c0
ACPI: HPET (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd810
ACPI: MCFG (v001 DELL PESC1425 0x00000001 MSFT 0x0100000a) @ 0x000fd848
ACPI: DSDT (v001 DELL PESC1425 0x00000001 MSFT 0x0100000e) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[32])
IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 32-55
ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[64])
IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
IRQ lockup detection disabled
Allocating PCI resources starting at 80000000 (gap: 7ffff000:60001000)
Built 1 zonelists
Kernel command line: root=/dev/sda3 noreboot console=ttyS0 debug
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 2800.114 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Software IO TLB disabled
vmalloc area: c7000000-fbee6000, maxmem 34000000
Memory: 93952k/106496k available (1907k kernel code, 4100k reserved, 513k
data, 180k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5596.77 BogoMIPS (lpj=27983872)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000
0000641d 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000641d
00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: After all inits, caps: bfebd3f1 20100000 00000000 00000080 0000641d
00000000 00000000
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
ENABLING IO-APIC IRQs
Initializing CPU#1
Initializing CPU#2
Brought up 4 CPUs
Initializing CPU#3
domain 0: span 0
ERROR: domain->span does not contain CPU0
CPU0 attaching sched-domain:
ERROR: domain->groups does not contain CPU0
groups:
ERROR: empty group
0
ERROR: group is NULL
domain 1: span f
groups: f
CPU1 attaching sched-domain:
domain 0: span 0
ERROR: domain->span does not contain CPU1
ERROR: domain->groups does not contain CPU1
groups:
ERROR: empty group
0
ERROR: group is NULL
domain 1: span f
groups: f
Unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
c0119b94
*pde = ma 00000000 pa 55555000
Oops: 0000 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c0119b94>] Not tainted VLI
EFLAGS: 00010286 (2.6.12.6.5-xen)
EIP is at find_busiest_group+0x42/0x2e9
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
esi: c10d5e00 edi: 00000020 ebp: c1131dd0 esp: c1131d90
ds: 007b es: 007b ss: 0069
Process swapper (pid: 1, threadinfo=c1130000 task=c03c1a20)
Stack: 000000d0 00000100 c111c900 0000000c c111c910 00000000 00000080 00000000
00000000 00000000 00000000 00000000 00000000 c10d5e00 c10d54a0 c1131eac
c1131e00 c011a093 c10d5e00 00000000 c1131df0 00000002 c10d54a0 c1131e00
Call Trace:
[<c011a093>] load_balance_newidle+0x33/0xa0
[<c01187fd>] deactivate_task+0x20/0x2d
[<c02dac51>] schedule+0x8bd/0xc94
[<c0111755>] __down_trylock+0x65/0x7c
[<c02da34f>] __down_failed_trylock+0x7/0xc
[<c023247d>] scnprintf+0x28/0x35
[<c02db0ad>] wait_for_completion+0x85/0xca
[<c011a9c7>] default_wake_function+0x0/0x12
[<c011a9c7>] default_wake_function+0x0/0x12
[<c0118e45>] wake_up_process+0x1e/0x20
[<c036b21d>] cpu_attach_domain+0xe2/0xef
[<c036b3ad>] init_sched_build_groups+0x12d/0x166
[<c036b838>] arch_init_sched_domains+0x401/0x45c
[<c0104115>] init+0xb3/0x196
[<c0104062>] init+0x0/0x196
[<c0107589>] kernel_thread_helper+0x5/0xb
Code: 8b 45 08 8b 40 04 c7 45 d8 00 00 00 00 c7 45 e0 00 00 00 00 89 45 e8 c7
45 dc 00 00 00 00 c7 45 e4 00 00 00 00 8b 4d 0c 8b 55 e8 <0f> a3 4a 04 19
d2
8b 75 e8 89 55 d4 b9 0
<0>Kernel panic - not syncing: Attempted to kill init!
stop_this_cpu disable_local_APIC
stop_this_cpu disable_local_APIC
Kind Regards,
--
Ian P. Christian ~ http://pookey.co.uk
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Friday 18 November 2005 04:41, Ian P. Christian wrote:> I''ve managed to compile my dom0 kernel, however on attempting to boot to > it, I get a kernel panic. After much fiddling aronud with a serial link I > have managed to get this output. > > Any ideas or feedback are most welcome. >,,,> Initializing CPU#1 > Initializing CPU#2 > Brought up 4 CPUs > Initializing CPU#3 > domain 0: span 0 > ERROR: domain->span does not contain CPU0 > CPU0 attaching sched-domain: > ERROR: domain->groups does not contain CPU0 > groups: > ERROR: empty group > 0 > ERROR: group is NULL > > domain 1: span f > groups: f > CPU1 attaching sched-domain: > domain 0: span 0 > ERROR: domain->span does not contain CPU1 > ERROR: domain->groups does not contain CPU1 > groups: > ERROR: empty group > 0 > ERROR: group is NULLHad the same problem, disabling "SMT (Hyperthreading) scheduler support" (found in "Processor type and features") in the domU kernel seems to work arround it. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ernst Bachmann wrote:> Had the same problem, disabling "SMT (Hyperthreading) scheduler > support" (found in "Processor type and features") in the domU kernel seems to > work arround it.Thanks very much! That''s solved it and I can now boot. On booting though, there is a kernel opps - e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex Unable to read memory/target Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c03e0d86 *pde = ma 00000000 pa 55555000 Oops: 0002 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c03e0d86>] Not tainted VLI EFLAGS: 00010247 (2.6.12.6.5-xen) EIP is at cpu_up+0x0/0x133 eax: 00000000 ebx: c1167f18 ecx: c1166000 edx: 00000000 esi: c1167eff edi: c0349905 ebp: 00000000 esp: c1167ee0 ds: 007b es: 007b ss: 0069 Process xenwatch (pid: 16, threadinfo=c1166000 task=c112aa20) Stack: c0107097 00000000 c1167f18 c03498f1 c0349e28 c1167ef8 696c6e6f c400656e ffffffff c1167f58 c02326a4 c4942e4c c1167f24 0000000a 2f757063 ffff0030 00000001 c4942e4d c1167f8c c1167f98 c4942ec0 c1167f6c c1167f8c c1167f98 Call Trace: [<c0107097>] vcpu_hotplug+0x10c/0x111 [<c02326a4>] vsscanf+0x368/0x526 [<c01070df>] handle_vcpu_hotplug_event+0x43/0x47 [<c0291f49>] xenwatch_thread+0x10e/0x133 [<c0131922>] autoremove_wake_function+0x0/0x57 [<c0131922>] autoremove_wake_function+0x0/0x57 [<c0291e3b>] xenwatch_thread+0x0/0x133 [<c0131454>] kthread+0xba/0xf0 [<c013139a>] kthread+0x0/0xf0 [<c0107589>] kernel_thread_helper+0x5/0xb Code: 00 00 00 00 00 00 00 00 00 e7 bf 7c 0d f0 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ed 81 00 00 6e 00 <00> 00 75 f8 77 43 76 f8 77 43 75 f8 77 43 00 00 00 00 00 00 01 Kind Regards, _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Ernst Bachmann wrote: > > Had the same problem, disabling "SMT (Hyperthreading) scheduler > > support" (found in "Processor type and features") in the > domU kernel seems to > > work arround it.I''m suspicious that this Oops is also due to a kernel config file difference. What happens if you try a stock -xen kernel? BTW, what kind of box is this? Thanks, Ian> Thanks very much! That''s solved it and I can now boot. On booting > though, there is a kernel opps - > > e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex > Unable to read memory/target > Unable to handle kernel NULL pointer dereference at virtual > address 00000000 > printing eip: > c03e0d86 > *pde = ma 00000000 pa 55555000 > Oops: 0002 [#1] > SMP > Modules linked in: > CPU: 0 > EIP: 0061:[<c03e0d86>] Not tainted VLI > EFLAGS: 00010247 (2.6.12.6.5-xen) > EIP is at cpu_up+0x0/0x133 > eax: 00000000 ebx: c1167f18 ecx: c1166000 edx: 00000000 > esi: c1167eff edi: c0349905 ebp: 00000000 esp: c1167ee0 > ds: 007b es: 007b ss: 0069 > Process xenwatch (pid: 16, threadinfo=c1166000 task=c112aa20) > Stack: c0107097 00000000 c1167f18 c03498f1 c0349e28 c1167ef8 696c6e6f > c400656e > ffffffff c1167f58 c02326a4 c4942e4c c1167f24 0000000a > 2f757063 > ffff0030 > 00000001 c4942e4d c1167f8c c1167f98 c4942ec0 c1167f6c > c1167f8c > c1167f98 > Call Trace: > [<c0107097>] vcpu_hotplug+0x10c/0x111 > [<c02326a4>] vsscanf+0x368/0x526 > [<c01070df>] handle_vcpu_hotplug_event+0x43/0x47 > [<c0291f49>] xenwatch_thread+0x10e/0x133 > [<c0131922>] autoremove_wake_function+0x0/0x57 > [<c0131922>] autoremove_wake_function+0x0/0x57 > [<c0291e3b>] xenwatch_thread+0x0/0x133 > [<c0131454>] kthread+0xba/0xf0 > [<c013139a>] kthread+0x0/0xf0 > [<c0107589>] kernel_thread_helper+0x5/0xb > Code: 00 00 00 00 00 00 00 00 00 e7 bf 7c 0d f0 01 01 00 00 > 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ed 81 00 00 6e > 00 <00> 00 > 75 f8 77 43 76 f8 77 43 75 f8 77 43 00 00 00 00 00 00 01 > > > > Kind Regards, > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 18 November 2005 14:53, Ian Pratt wrote:> I''m suspicious that this Oops is also due to a kernel config file > difference. What happens if you try a stock -xen kernel?This wouldn''t be possible due to the hardware in the box.> BTW, what kind of box is this?It''s nothing exotic, standard hardware. It''s a Dell 1425, dual Intel(R) Xeon(TM) CPU 2.80GHz. 3ware 9xxx SATA RAID I''ll try again from scratch with the kernel config now. I''m also having problems booting a domU at the moment: 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(0,0) I''ll recompile a kernel starting with teh defaults specified in xen0_defconfig, and see how things go. Thank god for KVMs with VNC capabilities :) -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 18 November 2005 14:59, Ian P. Christian wrote:> I''ll recompile a kernel starting with teh defaults specified in > xen0_defconfig, and see how things go.Well, no opps on boot now, but having attempted to start a domU, I''m seeing what apepars to the the same opps as before. Thanks for your help people, much appreciated # xm create /etc/xen/auto/ttylinux -c Using config file "/etc/xen/auto/ttylinux". Started domain ttylinux Linux version 2.6.12.6.5-xen (root@bb3) (gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #2 SMP Fri Nov 18 15:47:14 GMT 2005 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000004000000 (usable) 0MB HIGHMEM available. 72MB LOWMEM available. IRQ lockup detection disabled Built 1 zonelists Kernel command line: ip=1.2.3.4:1.2.3.4::::eth0:off root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Xen reported: 2800.104 MHz processor. Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) vmalloc area: c5000000-fb7fe000, maxmem 34000000 Memory: 62320k/73728k available (1369k kernel code, 3072k reserved, 404k data, 128k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled Brought up 1 CPUs NET: Registered protocol family 16 xenbus_probe_init Brought up 1 CPUs xen_mem: Initialising balloon driver. SCSI subsystem initialized Grant table initialized Number of CPUs sharing cache didn''t match any known set of CPUs Number of CPUs sharing cache didn''t match any known set of CPUs Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. xen_net: Initialising virtual ethernet driver. 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 00000104 printing eip: c01dfaa7 *pde = ma 00000000 pa 55555000 Oops: 0002 [#1] SMP Modules linked in: CPU: 0 EIP: 0061:[<c01dfaa7>] Not tainted VLI EFLAGS: 00010296 (2.6.12.6.5-xen) EIP is at blk_start_queue+0x8/0x4f eax: 00000000 ebx: 00000000 ecx: 00000000 edx: fbfc4000 esi: c039c004 edi: c03fbc23 ebp: c0345f6c esp: c0345efc ds: 007b es: 007b ss: 0069 Process xenwatch (pid: 7, threadinfo=c0344000 task=c032fa20) Stack: 00000000 c039c000 c01f107a 00000000 c039c000 c01f1aa3 c039c000 00000000 00000801 00000000 00000200 c039c000 c02640d1 c0345f48 c026a147 c0263cc7 c0345f4c 00000000 00007d00 00000000 00000200 c0345f8c c0345f98 c03fbac0 Call Trace: [<c01f107a>] kick_pending_request_queues+0x1e/0x33 [<c01f1aa3>] watch_for_status+0xed/0x135 [<c01ef665>] xenwatch_thread+0x10e/0x133 [<c01317f2>] autoremove_wake_function+0x0/0x57 [<c01317f2>] autoremove_wake_function+0x0/0x57 [<c01ef557>] xenwatch_thread+0x0/0x133 [<c0131324>] kthread+0xba/0xf0 [<c013126a>] kthread+0x0/0xf0 [<c0107911>] kernel_thread_helper+0x5/0xb Code: d2 75 01 c3 89 44 24 04 8b 48 60 ff e1 8b 44 24 04 8b 48 60 ff e1 81 44 24 04 a0 00 00 00 e9 95 24 00 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 512 buckets, 4Kbytes TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) NET: Registered protocol family 1 NET: Registered protocol family 17 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(0,0) -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Are you importing the block device as scsi? e.g. sda? If so, try IDE hda. The scsi major has already been grabbed. Ian> -----Original Message----- > From: Ian P. Christian [mailto:pookey@pookey.co.uk] > Sent: 18 November 2005 15:21 > To: xen-users@lists.xensource.com > Cc: Ian Pratt; Ernst Bachmann; xen-devel; ian.pratt@cl.cam.ac.uk > Subject: Re: [Xen-users] kernel panic on boot of dom0 > > On Friday 18 November 2005 14:59, Ian P. Christian wrote: > > I''ll recompile a kernel starting with teh defaults specified in > > xen0_defconfig, and see how things go. > > Well, no opps on boot now, but having attempted to start a > domU, I''m seeing what apepars to the the same opps as before. > > Thanks for your help people, much appreciated > > # xm create /etc/xen/auto/ttylinux -c > Using config file "/etc/xen/auto/ttylinux". > Started domain ttylinux > Linux version 2.6.12.6.5-xen (root@bb3) (gcc version 3.4.4 > (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #2 SMP Fri Nov > 18 15:47:14 GMT 2005 BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000004000000 (usable) 0MB > HIGHMEM available. > 72MB LOWMEM available. > IRQ lockup detection disabled > Built 1 zonelists > Kernel command line: ip=1.2.3.4:1.2.3.4::::eth0:off > root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: > 512 (order: 9, 8192 bytes) Xen reported: 2800.104 MHz processor. > Dentry cache hash table entries: 16384 (order: 4, 65536 > bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 > bytes) vmalloc area: c5000000-fb7fe000, maxmem 34000000 > Memory: 62320k/73728k available (1369k kernel code, 3072k > reserved, 404k data, 128k init, 0k highmem) Checking if this > processor honours the WP bit even in supervisor mode... Ok. > Mount-cache hash table entries: 512 > CPU: Trace cache: 12K uops, L1 D cache: 16K > CPU: L2 cache: 1024K > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking ''hlt'' instruction... disabled > Brought up 1 CPUs > NET: Registered protocol family 16 > xenbus_probe_init > Brought up 1 CPUs > xen_mem: Initialising balloon driver. > SCSI subsystem initialized > Grant table initialized > Number of CPUs sharing cache didn''t match any known set of > CPUs Number of CPUs sharing cache didn''t match any known set > of CPUs Initializing Cryptographic API io scheduler noop > registered io scheduler anticipatory registered io scheduler > deadline registered io scheduler cfq registered RAMDISK > driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Xen virtual console successfully installed as tty1 > Event-channel device installed. > xen_net: Initialising virtual ethernet driver. > 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 00000104 printing eip: > c01dfaa7 > *pde = ma 00000000 pa 55555000 > Oops: 0002 [#1] > SMP > Modules linked in: > CPU: 0 > EIP: 0061:[<c01dfaa7>] Not tainted VLI > EFLAGS: 00010296 (2.6.12.6.5-xen) > EIP is at blk_start_queue+0x8/0x4f > eax: 00000000 ebx: 00000000 ecx: 00000000 edx: fbfc4000 > esi: c039c004 edi: c03fbc23 ebp: c0345f6c esp: c0345efc > ds: 007b es: 007b ss: 0069 > Process xenwatch (pid: 7, threadinfo=c0344000 task=c032fa20) > Stack: 00000000 c039c000 c01f107a 00000000 c039c000 c01f1aa3 > c039c000 00000000 > 00000801 00000000 00000200 c039c000 c02640d1 c0345f48 > c026a147 c0263cc7 > c0345f4c 00000000 00007d00 00000000 00000200 c0345f8c > c0345f98 c03fbac0 Call Trace: > [<c01f107a>] kick_pending_request_queues+0x1e/0x33 > [<c01f1aa3>] watch_for_status+0xed/0x135 [<c01ef665>] > xenwatch_thread+0x10e/0x133 [<c01317f2>] > autoremove_wake_function+0x0/0x57 [<c01317f2>] > autoremove_wake_function+0x0/0x57 [<c01ef557>] > xenwatch_thread+0x0/0x133 [<c0131324>] kthread+0xba/0xf0 > [<c013126a>] kthread+0x0/0xf0 [<c0107911>] > kernel_thread_helper+0x5/0xb > Code: d2 75 01 c3 89 44 24 04 8b 48 60 ff e1 8b 44 24 04 8b > 48 60 ff e1 81 44 > 24 04 a0 00 00 00 e9 95 24 00 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 512 buckets, 4Kbytes TCP > established hash table entries: 4096 (order: 3, 32768 bytes) > TCP bind hash table entries: 4096 (order: 3, 32768 bytes) > TCP: Hash tables configured (established 4096 bind 4096) > NET: Registered protocol family 1 > NET: Registered protocol family 17 > 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(0,0) > > -- > Ian P. Christian ~ http://pookey.co.uk >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 18 November 2005 15:55, Ian Pratt wrote:> Are you importing the block device as scsi? e.g. sda? > > If so, try IDE hda. > > The scsi major has already been grabbed.Yes, sorry. I solved the VFS: Cannot open root device "sda1" or unknown-block(0,0)'' issue, I just wasn''t sure if the opps above it was related. I now how a working domU! Thanks again for your help -- Ian P. Christian ~ http://pookey.co.uk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users