Xen project Mailing List

I can't boot my PV domU domain using a pv_ops 2.6.30.1 kernel.
Using the xenified standard debian kernel (2.6.26, the same as in dom0) in
DomU it does boot with pvgrub.

Any clues, to what to try or test ?

Regards,

Sander

xm dmesg gives:

traps.c:437:d12 Unhandled general protection fault fault/trap [#13] on VCPU 0 [ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 12 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.1-rc7 x86_64 debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff813ce1df>]
(XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
(XEN) rax: 000000008000c068   rbx: ffffffff817e8740   rcx: 0000000000000068
(XEN) rdx: 0000000000000cf8   rsi: 000000000000c000   rdi: 0000000000000000
(XEN) rbp: ffffffff817f5e68   rsp: ffffffff817f5e20   r8: ffffffff817f5e84
(XEN) r9: 00000000ffffffff   r10: ffffffff817f5e80   r11: 00000000ffffffff
(XEN) r12: 0000000000000018   r13: ffffffff817f5f80   r14: 0000002010403eb0
(XEN) r15: 00000000003f6000   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 000000014f372000   cr2: 00000020117cb000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff817f5e20:
(XEN) 0000000000000068 00000000ffffffff 0000000000000000 ffffffff813ce1df
(XEN) 000000010000e030 0000000000010082 ffffffff817f5e68 000000000000e02b
(XEN) ffffffff817e8740 ffffffff817f5e98 ffffffff814e766c 0000000000000018
(XEN) 0000000100000000 0000302800000000 ffffffff81724500 ffffffff817f5ec8
(XEN) ffffffff81829333 ffffffff817f5eb8 0000000000000246 0000000000000000
(XEN) ffffffffffffffff ffffffff817f5f68 ffffffff81825ed4 ffffffff8167708f
(XEN) ffffffff816727bf 0000000000000040 ffffffff817f5f58 ffffffff817335b0
(XEN) 0000000000000000 ffffffffffffffff 0000002010403eb0 ffffffff817f5f38
(XEN) ffffffff817f5fa8 ffffffff8100d231 ffffffff81860d00 ffffffff817f5f58
(XEN) 0000000000000000 ffffffffffffffff ffffffff8185d920 0000002010403eb0
(XEN) 00000000003f6000 ffffffff817f5fa8 ffffffff818219fe ffffffff817f5fa8
(XEN) ffffffff81827b17 00000000019be188 0000000000004000 000000201178c7d0
(XEN) 0000002010403eb0 ffffffff817f5fc8 ffffffff818212bf 0000000000000018
(XEN) ffffffff81e58000 ffffffff817f5ff8 ffffffff81824d0e 0000000000000000
(XEN) 0000000000000000 0000000000000000 ffffffff81e6b000 0000000000b5fd78
(XEN) ffffffff81dd5000 ffffffff81dd6000 ffffffff81dd7000 ffffffff81dd8000
(XEN) ffffffff81dd9000 ffffffff81dda000 ffffffff81ddb000 ffffffff81ddc000
(XEN) ffffffff81ddd000 ffffffff81dde000 ffffffff81ddf000 ffffffff81de0000
(XEN) ffffffff81de1000 ffffffff81de2000 ffffffff81de3000 ffffffff81de4000
(XEN) ffffffff81de5000 ffffffff81de6000 ffffffff81de7000 ffffffff81de8000
(END)

On the domU console trying to boot the pv_ops 2.6.30.1 kernel with pvgrub:

Started domain security (id=13)
   Xen Minimal OS!
start_info: 0xa12000(VA)
nr_pages: 0x10000
shared_inf: 0xb3ad0000(MA)
   pt_base: 0xa15000(VA)
nr_pt_frames: 0x9
mfn_list: 0x992000(VA)
   mod_start: 0x991000(VA)
   mod_len: 4096
   flags: 0x0
cmd_line:
stack: 0x950860-0x970860
MM: Init
_text: 0x0(VA)
   _etext: 0x617a4(VA)
   _erodata: 0x79000(VA)
   _edata: 0x81b00(VA)
stack start: 0x950860(VA)
   _end: 0x990e68(VA)
start_pfn: a21
max_pfn: 10000
Mapping memory range 0xc00000 - 0x10000000
setting 0x0-0x79000 readonly
skipped 0x1000
MM: Initialise page allocator for a9b000(a9b000)-10000000(10000000)
MM: done
Demand map pfns at 10001000-2010001000.
Heap resides at 2010002000-4010002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x10001000.
Initialising scheduler
Thread "Idle": pointer: 0x2010002010, stack: 0xb30000
Initialising xenbus
Thread "xenstore": pointer: 0x20100027c0, stack: 0xb40000
Dummy main: start_info=0x970960
Thread "main": pointer: 0x2010002f70, stack: 0xb50000
"main"
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********

backend at /local/domain/0/backend/vbd/13/2049
Failed to read /local/domain/0/backend/vbd/13/2049/feature-flush-cache.
1048576 sectors of 512 bytes
**************************
vbd 2050 is hd1
******************* BLKFRONT for device/vbd/2050 **********

backend at /local/domain/0/backend/vbd/13/2050
Failed to read /local/domain/0/backend/vbd/13/2050/feature-flush-cache.
8388608 sectors of 512 bytes
**************************

GNU GRUB version 0.97 (262144K lower / 0K upper memory)

+-------------------------------------------------------------------------+
| Debian GNU/Linux, vmlinuz-2.6.30-1-amd64 |
|    |
|    |
|    |
|    |
|    |
|    |
|    |
|    |
|    |
|    |
|    |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.
Booting 'Debian GNU/Linux, vmlinuz-2.6.30-1-amd64'

lock
root (hd1)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.30.1
initrd /boot/initrd.img-2.6.30.1

block error -2 for op 2
close blk: backend at /local/domain/0/backend/vbd/13/2049
block error -2 for op 2
close blk: backend at /local/domain/0/backend/vbd/13/2050
serveerstertje:~#

--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx

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

Re: [Xen-devel] pv_ops DomU boot problem using pvgrub, xen 3.4.1-rc7, debian 2.6.26 dom0