* i386 boot problem on xen/next
[not found] ` <alpine.LFD.2.00.1002192120330.29668@vega1.dur.ac.uk>
@ 2010-02-19 21:39 ` M A Young
2010-02-20 0:11 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 4+ messages in thread
From: M A Young @ 2010-02-19 21:39 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: TEXT/PLAIN, Size: 284 bytes --]
I have now got xen/next to boot on x86_64, though I can't start the client
(which may be the issue with xen 4 rc4 and pygrub which I think someone
mentioned). However with i386 it crashes on boot. The crash is in
xen_set_pte, some logs and debugging are attached.
Michael Young
[-- Attachment #2: Type: TEXT/plain, Size: 14183 bytes --]
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: com1=19200 console=com1
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000001f740000 (usable)
(XEN) 000000001f740000 - 000000001f750000 (ACPI data)
(XEN) 000000001f750000 - 000000001f800000 (ACPI NVS)
(XEN) System RAM: 471MB (482876kB)
(XEN) ACPI: RSDP 000F7970, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT 1F740000, 0030 (r1 INTEL D845GRG 20020909 MSFT 97)
(XEN) ACPI: FACP 1F740200, 0081 (r2 INTEL D845GRG 20020909 MSFT 97)
(XEN) ACPI: DSDT 1F740400, 3F21 (r1 INTEL D845GRG 10A MSFT 100000D)
(XEN) ACPI: FACS 1F750000, 0040
(XEN) ACPI: APIC 1F740300, 0068 (r1 INTEL D845GRG 20020909 MSFT 97)
(XEN) ACPI: ASF! 1F744330, 0084 (r16 AMIASF I845GASF 1 MSFT 100000D)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000001f740000
(XEN) Xen heap: 9MB (9332kB)
(XEN) Domain heap initialised
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0]
(XEN) ACPI: wakeup_vec[1f75000c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:2 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2400.155 MHz processor.
(XEN) Initing memory sharing.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
(XEN) CPU: L2 cache: 512K
(XEN) CPU: Hyper-Threading is disabled
(XEN) CPU0: Intel Extended MCE MSRs (12) available
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM1)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) I/O virtualisation disabled
(XEN) CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 1 CPUs
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x400000 memsz=0x56b000
(XEN) elf_parse_binary: phdr: paddr=0x96b000 memsz=0x32c000
(XEN) elf_parse_binary: memory: 0x400000 -> 0xc97000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc09fd000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc0402000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xf5800000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xc0000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xc0000000
(XEN) virt_kstart = 0xc0400000
(XEN) virt_kend = 0xc0c97000
(XEN) virt_entry = 0xc09fd000
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xc97000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000001a000000->000000001c000000 (108521 pages to be all
ocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0400000->c0c97000
(XEN) Init. ramdisk: c0c97000->c1545600
(XEN) Phys-Mach map: c1546000->c15b7fa4
(XEN) Start info: c15b8000->c15b847c
(XEN) Page tables: c15b9000->c15ca000
(XEN) Boot stack: c15ca000->c15cb000
(XEN) TOTAL: c0000000->c1800000
(XEN) ENTRY ADDRESS: c09fd000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xc0400000 -> 0xc096b000
(XEN) elf_load_binary: phdr 1 at 0xc096b000 -> 0xc0a92000
(XEN) Scrubbing Free RAM: done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen
)
(XEN) Freed 132kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
Reserving virtual address space above 0xf5800000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.8-1.2.87.xendom0.fc12.i686.PAE (mockbuild@x86-03.phx2.fedor
aproject.org) (gcc version 4.4.3 20100127 (Red Hat 4.4.3-4) (GCC) ) #1 SMP Wed F
eb 17 23:45:37 UTC 2010
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000000009fc00 (usable)
Xen: 000000000009fc00 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 000000001c7e9000 (usable)
Xen: 000000001f740000 - 000000001f750000 (ACPI data)
Xen: 000000001f750000 - 000000001f800000 (ACPI NVS)
Xen: 00000000fec00000 - 00000000fec01000 (reserved)
Xen: 00000000fee00000 - 00000000fee01000 (reserved)
bootconsole [xenboot0] enabled
DMI 2.3 present.
last_pfn = 0x1c7e9 max_arch_pfn = 0x1000000
init_memory_mapping: 0000000000000000-000000001c7e9000
Using x86 segment limits to approximate NX protection
RAMDISK: 00c97000 - 01545600
ACPI: RSDP 000f7970 00014 (v00 ACPIAM)
ACPI: RSDT 1f740000 00030 (v01 INTEL D845GRG 20020909 MSFT 00000097)
ACPI: FACP 1f740200 00081 (v02 INTEL D845GRG 20020909 MSFT 00000097)
ACPI: DSDT 1f740400 03F21 (v01 INTEL D845GRG 0000010A MSFT 0100000D)
ACPI: FACS 1f750000 00040
ACPI: APIC 1f740300 00068 (v01 INTEL D845GRG 20020909 MSFT 00000097)
ACPI: ASF! 1f744330 00084 (v16 AMIASF I845GASF 00000001 MSFT 0100000D)
0MB HIGHMEM available.
455MB LOWMEM available.
mapped low ram: 0 - 1c7e9000
low ram: 0 - 1c7e9000
node 0 low ram: 00000000 - 1c7e9000
node 0 bootmap 00002000 - 00005900
(10 early reservations) ==> bootmem [0000000000 - 001c7e9000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [00015b9000 - 00015ca000] XEN PAGETABLES ==> [00015b9000 - 00015ca000]
#2 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#3 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#4 [0000400000 - 0000b71118] TEXT DATA BSS ==> [0000400000 - 0000b71118]
#5 [0000c97000 - 0001545600] RAMDISK ==> [0000c97000 - 0001545600]
#6 [0001546000 - 00015b9000] XEN START INFO ==> [0001546000 - 00015b9000]
#7 [0000b72000 - 0000b72178] BRK ==> [0000b72000 - 0000b72178]
#8 [0000100000 - 00001d7000] PGTABLE ==> [0000100000 - 00001d7000]
#9 [0000002000 - 0000006000] BOOTMAP ==> [0000002000 - 0000006000]
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x0001c7e9
HighMem 0x0001c7e9 -> 0x0001c7e9
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000000 -> 0x0000009f
0: 0x00000100 -> 0x0001c7e9
Using APIC driver default
ACPI: PM-Timer IO Port: 0x408
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) mm.c:1746:d0 Bad L1 flags 80000100
(XEN) mm.c:778:d0 Bad L1 flags 80000100
(XEN) mm.c:4637:d0 ptwr_emulate: could not get_page_from_l1e()
(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c01d6fd0:
(XEN) L3[0x003] = 000000001aa9c001 00000a9c
(XEN) L2[0x000] = 000000001b5be067 000015be
(XEN) L1[0x1d6] = 000000001a1d6061 000001d6
(XEN) domain_crash_sync called from entry.S (ff1cb712)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.0-rc4 x86_32p debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: e019:[<c04060dd>]
(XEN) EFLAGS: 00000296 EM: 1 CONTEXT: pv guest
(XEN) eax: 00000000 ebx: c01d6fd0 ecx: 80000000 edx: 1aa9d163
(XEN) esi: 80000000 edi: 00000000 ebp: c096de54 esp: c096de34
(XEN) cr0: 8005003b cr4: 000006f0 cr3: 00bc4ca0 cr2: c01d6fd0
(XEN) ds: e021 es: e021 fs: 00d8 gs: 0000 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c096de34:
(XEN) 00000003 c04060dd 0001e019 00010096 1aa9d163 deadbeef deadbeef f57fa000
(XEN) c096de74 c0406240 c01d6fd0 80000000 1aa9d163 80000000 c01d6fd0 f57fa000
(XEN) c096de98 c042b702 1aa9d163 80000000 80000000 00a9d163 00005000 f57ff000
(XEN) 0000017b c096dea8 c042a8fb 00000005 80000000 c096dec4 c0405254 c08bd670
(XEN) c096dec4 00000000 00000000 00000001 c096dee0 c0a0e72c 0000017b 80000000
(XEN) f510035c f510035c c08bd670 c096deec c0a093fe 00000001 c096df10 c0a23e1d
(XEN) f5100368 00000001 00000068 f5100300 00000000 00000000 c1545600 c096df20
(XEN) c0a23e93 c0a093d1 00000040 c096df30 c0a099cc 0e3f4800 1c7e9000 c096dfac
(XEN) c0a028de 00000000 00000024 01545600 00000000 00000035 00c97000 00000000
(XEN) 000000bb c05c3b77 00c97000 1c7e9000 00000000 1c7e9000 00000000 c09a98a4
(XEN) 00000002 c09a98a4 00000002 00000000 00000000 c09a26bc c096df9c 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 c09a26bc c096dfc4 c09fd62f
(XEN) c08b39a7 c07ac010 c0a36714 00c97000 c096dfd4 c09fd0af 00c97000 c0a35500
(XEN) c096dffc c0a002ad 1fc89375 80000400 00010809 00000f27 00000001 00000000
(XEN) c15b8000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
Reading symbols from /tmp/usr/lib/debug/lib/modules/2.6.32.8-1.2.87.xendom0.fc12
.i686.PAE/vmlinux...done.
(gdb) x/i 0xc04060dd
0xc04060dd <xen_set_pte+142>: mov %edx,(%ebx)
(gdb) x/48i xen_set_pte
0xc040604f <xen_set_pte>: push %ebp
0xc0406050 <xen_set_pte+1>: mov %esp,%ebp
0xc0406052 <xen_set_pte+3>: push %edi
0xc0406053 <xen_set_pte+4>: push %esi
0xc0406054 <xen_set_pte+5>: push %ebx
0xc0406055 <xen_set_pte+6>: sub $0x4,%esp
0xc0406058 <xen_set_pte+9>: call 0xc040a498
0xc040605d <xen_set_pte+14>: mov %eax,%ebx
0xc040605f <xen_set_pte+16>: mov %edx,%eax
0xc0406061 <xen_set_pte+18>: and $0x400,%eax
0xc0406066 <xen_set_pte+23>: mov %ecx,%esi
0xc0406068 <xen_set_pte+25>: je 0xc0406079 <xen_set_pte+42>
0xc040606a <xen_set_pte+27>: mov %ebx,%eax
0xc040606c <xen_set_pte+29>: push $0x7ff1
0xc0406071 <xen_set_pte+34>: call 0xc0405fa9 <xen_set_domain_pte>
0xc0406076 <xen_set_pte+39>: pop %eax
0xc0406077 <xen_set_pte+40>: jmp 0xc04060df <xen_set_pte+144>
0xc0406079 <xen_set_pte+42>: cmpb $0x0,0xc0aa134c
0xc0406080 <xen_set_pte+49>: je 0xc0406095 <xen_set_pte+70>
0xc0406082 <xen_set_pte+51>: mov $0x33,%ecx
0xc0406087 <xen_set_pte+56>: mov $0xc0aa1280,%edi
0xc040608c <xen_set_pte+61>: rep stos %eax,%es:(%edi)
0xc040608e <xen_set_pte+63>: movb $0x0,0xc0aa134c
0xc0406095 <xen_set_pte+70>: incl 0xc0aa12a4
0xc040609b <xen_set_pte+76>: cmpb $0x0,0xc0aa134c
0xc04060a2 <xen_set_pte+83>: je 0xc04060b9 <xen_set_pte+106>
0xc04060a4 <xen_set_pte+85>: mov $0x33,%ecx
0xc04060a9 <xen_set_pte+90>: mov $0xc0aa1280,%edi
0xc04060ae <xen_set_pte+95>: xor %eax,%eax
0xc04060b0 <xen_set_pte+97>: rep stos %eax,%es:(%edi)
0xc04060b2 <xen_set_pte+99>: movb $0x0,0xc0aa134c
0xc04060b9 <xen_set_pte+106>: mov 0xc0aa12ac,%edi
0xc04060bf <xen_set_pte+112>: mov %edx,-0x10(%ebp)
0xc04060c2 <xen_set_pte+115>: call 0xc04266cf <paravirt_get_lazy_mode>
0xc04060c7 <xen_set_pte+120>: dec %eax
0xc04060c8 <xen_set_pte+121>: sete %al
0xc04060cb <xen_set_pte+124>: movzbl %al,%eax
0xc04060ce <xen_set_pte+127>: lea (%eax,%edi,1),%edi
0xc04060d1 <xen_set_pte+130>: mov %edi,0xc0aa12ac
0xc04060d7 <xen_set_pte+136>: mov %esi,0x4(%ebx)
0xc04060da <xen_set_pte+139>: mov -0x10(%ebp),%edx
0xc04060dd <xen_set_pte+142>: mov %edx,(%ebx)
0xc04060df <xen_set_pte+144>: lea -0xc(%ebp),%esp
0xc04060e2 <xen_set_pte+147>: pop %ebx
0xc04060e3 <xen_set_pte+148>: pop %esi
0xc04060e4 <xen_set_pte+149>: pop %edi
0xc04060e5 <xen_set_pte+150>: pop %ebp
0xc04060e6 <xen_set_pte+151>: ret
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i386 boot problem on xen/next
2010-02-19 21:39 ` i386 boot problem on xen/next M A Young
@ 2010-02-20 0:11 ` Jeremy Fitzhardinge
2010-02-20 0:27 ` M A Young
2010-02-20 20:29 ` M A Young
0 siblings, 2 replies; 4+ messages in thread
From: Jeremy Fitzhardinge @ 2010-02-20 0:11 UTC (permalink / raw)
To: M A Young; +Cc: xen-devel
On 02/19/2010 01:39 PM, M A Young wrote:
> I have now got xen/next to boot on x86_64, though I can't start the
> client (which may be the issue with xen 4 rc4 and pygrub which I think
> someone mentioned). However with i386 it crashes on boot. The crash is
> in xen_set_pte, some logs and debugging are attached.
You're booting a PV domU using a stock Fedora kernel?
You're doing better than me in that case; I get a sullen hang in
pvgrub. I can boot hvm domains OK, so I think the backends/xenstore are
all OK.
Are you using pygrub or pvgrub? If the latter, can you post whatever
output it generates?
J
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i386 boot problem on xen/next
2010-02-20 0:11 ` Jeremy Fitzhardinge
@ 2010-02-20 0:27 ` M A Young
2010-02-20 20:29 ` M A Young
1 sibling, 0 replies; 4+ messages in thread
From: M A Young @ 2010-02-20 0:27 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
On Fri, 19 Feb 2010, Jeremy Fitzhardinge wrote:
> On 02/19/2010 01:39 PM, M A Young wrote:
>> I have now got xen/next to boot on x86_64, though I can't start the client
>> (which may be the issue with xen 4 rc4 and pygrub which I think someone
>> mentioned). However with i386 it crashes on boot. The crash is in
>> xen_set_pte, some logs and debugging are attached.
>
> You're booting a PV domU using a stock Fedora kernel?
No, I am booting a Fedora + xen/next based dom0 kernel. This now works for
me on x86_64 but not i686.
> You're doing better than me in that case; I get a sullen hang in pvgrub. I
> can boot hvm domains OK, so I think the backends/xenstore are all OK.
>
> Are you using pygrub or pvgrub? If the latter, can you post whatever output
> it generates?
I was trying pygrub which gets an elf warning suggesting that it is thinks
pygrub is an incorrect kernel rather than a boot loader. I will try pvgrub
to see if I am any more successful.
Michael Young
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: i386 boot problem on xen/next
2010-02-20 0:11 ` Jeremy Fitzhardinge
2010-02-20 0:27 ` M A Young
@ 2010-02-20 20:29 ` M A Young
1 sibling, 0 replies; 4+ messages in thread
From: M A Young @ 2010-02-20 20:29 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
On Fri, 19 Feb 2010, Jeremy Fitzhardinge wrote:
> On 02/19/2010 01:39 PM, M A Young wrote:
>> I have now got xen/next to boot on x86_64, though I can't start the client
>> (which may be the issue with xen 4 rc4 and pygrub which I think someone
>> mentioned). However with i386 it crashes on boot. The crash is in
>> xen_set_pte, some logs and debugging are attached.
>
> You're booting a PV domU using a stock Fedora kernel?
>
> You're doing better than me in that case; I get a sullen hang in pvgrub. I
> can boot hvm domains OK, so I think the backends/xenstore are all OK.
>
> Are you using pygrub or pvgrub? If the latter, can you post whatever output
> it generates?
With pvgrub I get the following after the boot menu
Error ENOENT when reading the backend path device/vkbd/0/backend
Page fault at linear address 0x1c, eip 0x51b6e, regs 0x3ff5ff7c, sp
0x3ff5fff0,
our_sp 0x3ff5ff50, code 2
Thread: kbdfront
EIP: 51b6e, EFLAGS 10002.
EBX: 746f6f72 ECX: 00000401 EDX: 00000000
ESI: 3ff3fe98 EDI: 00000001 EBP: 3ff5ffb0 EAX: 00000000
DS: c2c2e021 ES: e021 orig_eax: ffffffff, eip: 00051b6e
CS: 1e019 EFLAGS: 00010002 esp: 3ff5fff0 ss: 37eb
base is 0x3ff5ffb0 caller is 0x37eb
base is 0x3ff5fff0 caller is 0x31ad
3ff5ffe0: c2 c2 c2 c2 8f 37 00 00 26 00 00 00 40 f0 ff bf
3ff5fff0: 00 00 00 00 ad 31 00 00 94 fe f3 3f 00 00 00 00
3ff60000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
3ff60010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
3ff5ffa0: ff ff ff ff 6e 1b 05 00 19 e0 01 00 02 00 01 00
3ff5ffb0: f0 ff f5 3f eb 37 00 00 00 00 00 00 01 00 00 00
3ff5ffc0: c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2 c2
3ff5ffd0: c2 c2 c2 c2 c2 c2 c2 00 c2 c2 c2 c2 c2 c2 c2 c2
51b50: e5 8b 45 08 c7 40 1c 00 00 00 00 c7 40 20 00 00
51b60: 00 00 83 60 18 fe 5d c3 55 89 e5 8b 45 08 c7 40
51b70: 1c 00 00 00 00 c7 40 20 00 00 00 00 83 48 18 01
51b80: 5d c3 55 89 e5 53 83 ec 14 a1 e0 b1 94 00 8b 58
Pagetable walk from virt 1c, base a74000:
L3 = 00000000dc7b9027 (0xa75000) [offset = 0]
L2 = 00000000dc7b7067 (0xa77000) [offset = 0]
L1 = 0000000000000000 [offset = 0]
One thing that may or may not be an issue, is that this xen guest has a
LVM partition mapped to xvda1 so it is possible grub is getting confused
because there is no partition table, just a single partition. But it
doesn't boot (this is on a 64-bit dom0 trying to boot 32-bit pvgrub and
guest OS).
Michael Young
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-02-20 20:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <alpine.LFD.2.00.1002192033200.29668@vega1.dur.ac.uk>
[not found] ` <alpine.LFD.2.00.1002192120330.29668@vega1.dur.ac.uk>
2010-02-19 21:39 ` i386 boot problem on xen/next M A Young
2010-02-20 0:11 ` Jeremy Fitzhardinge
2010-02-20 0:27 ` M A Young
2010-02-20 20:29 ` M A Young
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.