thr3ads.net - Xen devel - [Xen-devel] 2.6.38 PV Guest boot failure

If this information is useful, please help other people find it:
Share via:

Shriram Rajagopalan

2011-Mar-20 01:22 UTC

[Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

The kernel is built from konrad''s tree, devel/next-2.6.39
commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04

64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
I have not been able to boot a pv domU, with the above kernel.

xl debug shows:
(XEN) mm.c:2389:d26 Bad type (saw 7400000000000001 != exp 1000000000000000)
for mfn 6650b5 (pfn 7cfcc)
(XEN) mm.c:2965:d26 Error while pinning mfn 6650b5
(XEN) traps.c:451:d26 Unhandled invalid opcode fault/trap [#6] on VCPU 0
[ec=0000]
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 26 (vcpu#0) crashed on cpu#7:
(XEN) ----[ Xen-4.1.0-rc7-pre  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    7
(XEN) RIP:    e033:[<ffffffff81004a75>]
(XEN) RFLAGS: 0000000000000282   EM: 1   CONTEXT: pv guest
(XEN) rax: 00000000ffffffea   rbx: ffff88007cfcc000   rcx: ffffffff81a3e000
(XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi: 00000000deadbeef
(XEN) rbp: ffffffff81801c18   rsp: ffffffff81801bb8   r8:  00003ffffffff000
(XEN) r9:  ffff880000000000   r10: 00000000deadbeef   r11: 0000000000000000
(XEN) r12: ffffffffff4b8f40   r13: 00000000000001e8   r14: ffffffffff4f8000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 00000004040b7000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff81801bb8:
(XEN)    ffffffff81a3e000 0000000000000000 ffffffff81004a75 000000010000e030
(XEN)    0000000000010082 ffffffff81801bf8 000000000000e02b ffffffff81004a71
(XEN)    ffffffff00000000 00000000006650b5 ffffffffff4f8000 ffff88007cfcc000
(XEN)    ffffffff81801c38 ffffffff8189b73d 000000007d000000 000000000007cfcc
(XEN)    ffffffff81801c58 ffffffff8102f4bc ffffffffff4b8f40 000000007d000000
(XEN)    ffffffff81801cf8 ffffffff818d6b35 ffffffff8100654b 8000000000000163
(XEN)    0000000100000001 ffffffffff4b8000 0000000000001000 80000000000001e3
(XEN)    8000000000000163 000000007d800000 000000007d200000 0000000000000000
(XEN)    ffffffff81801cc8 000000007cfcc000 ffffffff81801cf8 ffffffffff478008
(XEN)    ffffffffff4b8000 0000000040000000 0000000040000000 000000007d800000
(XEN)    ffffffff81801d88 ffffffff818d6d75 ffff88007d800000 8000000000000163
(XEN)    ffffffffff478000 0000000000000000 0000000000000000 0000000000000000
(XEN)    000000017d800000 0000000000000000 ffff88007d800000 000000007cde3000
(XEN)    ffffffff81801d68 ffffffffff478000 ffff88007d800000 0000000000000000
(XEN)    ffff88007d800000 0000000000000000 ffffffff81801df8 ffffffff818d6ee5
(XEN)    ffffffff81801df8 000000007d800000 ffff880000000000 000000007d800000
(XEN)    ffffffff81801dc8 00000000003ef000 0000000000000001 0000000000000000
(XEN)    0000000000000001 ffffffff81801e30 0000000000000001 ffffffff81734cc2
(XEN)    ffffffff81801ec8 ffffffff81473a10 ffffffff81801e98 0000000000000000
(XEN)    0000000000000000 000000007d800000 0000000000000000 0000000040000000

xenctx output:
rip: ffffffff81004a75 pin_pagetable_pfn+0x31
flags: 00001282 i s nz
rsp: ffffffff81801bb8
rax: 00000000ffffffea    rcx: ffffffff81a3e000    rdx: 00000000deadbeef
rbx: ffff88007cfcc000    rsi: 00000000deadbeef    rdi: 00000000deadbeef
rbp: ffffffff81801c18     r8: 00003ffffffff000     r9: ffff880000000000
r10: 00000000deadbeef    r11: 0000000000000000    r12: ffffffffff4b8f40
r13: 00000000000001e8    r14: ffffffffff4f8000    r15: 0000000000000000
 cs: e033     ss: e02b     ds: 0000     es: 0000
 fs: 0000 @ 0000000000000000
 gs: 0000 @ ffffffff81882000/0000000000000000
Code (instr addr ffffffff81004a75)
01 00 00 00 31 d2 41 ba f0 7f 00 00 e8 cf c8 ff ff 85 c0 74 04 <0f> 0b eb
fe
c9 c3 55 48 89 e5 53


Stack:
 ffffffff81a3e000 0000000000000000 ffffffff81004a75 000000010000e030
 0000000000010082 ffffffff81801bf8 000000000000e02b ffffffff81004a71
 ffffffff00000000 00000000006650b5 ffffffffff4f8000 ffff88007cfcc000
 ffffffff81801c38 ffffffff8189b73d 000000007d000000 000000000007cfcc

Stack Trace:
* [<ffffffff81004a75>] pin_pagetable_pfn+0x31  <--
    ffffffff81a3e000
    0000000000000000
  [<ffffffff81004a75>] pin_pagetable_pfn+0x31
    000000010000e030
    0000000000010082
    ffffffff81801bf8
    000000000000e02b
  [<ffffffff81004a71>] pin_pagetable_pfn+0x2d
    ffffffff00000000
    00000000006650b5
    ffffffffff4f8000
    ffff88007cfcc000
    ffffffff81801c38
  [<ffffffff8189b73d>] xen_alloc_pte_init+0x30
    000000007d000000
    000000000007cfcc
    ffffffff81801c58
  [<ffffffff8102f4bc>] T.927+0x2a
    ffffffffff4b8f40
    000000007d000000
    ffffffff81801cf8
  [<ffffffff818d6b35>] phys_pmd_init+0x212
  [<ffffffff8100654b>] __raw_callee_save_xen_restore_fl+0x11
    8000000000000163
    0000000100000001
    ffffffffff4b8000
    0000000000001000
    80000000000001e3
    8000000000000163
    000000007d800000
    000000007d200000
    0000000000000000
    ffffffff81801cc8
    000000007cfcc000
    ffffffff81801cf8
    ffffffffff478008
    ffffffffff4b8000
    0000000040000000
    0000000040000000
    000000007d800000
    ffffffff81801d88
  [<ffffffff818d6d75>] phys_pud_init+0x1f5
    ffff88007d800000
    8000000000000163
    ffffffffff478000
    0000000000000000
    0000000000000000
    0000000000000000
    000000017d800000
    0000000000000000
    ffff88007d800000
    000000007cde3000
    ffffffff81801d68
    ffffffffff478000
    ffff88007d800000
    0000000000000000
    ffff88007d800000
    0000000000000000
    ffffffff81801df8
  [<ffffffff818d6ee5>] kernel_physical_mapping_init+0xd8
    ffffffff81801df8
    000000007d800000
    ffff880000000000
    000000007d800000
    ffffffff81801dc8
    00000000003ef000
    0000000000000001
    0000000000000000
    0000000000000001
    ffffffff81801e30
    0000000000000001
    ffffffff81734cc2
    ffffffff81801ec8
  [<ffffffff81473a10>] init_memory_mapping+0x40c
    ffffffff81801e98
    0000000000000000
    0000000000000000
    000000007d800000
    0000000000000000
    0000000040000000
    000000007d800000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000005000
    0000000000000001
    0000000001a4f000
    0000000000000000
    ffffffff81801f80
    ffffffffffffffff
    0000000000000000
    ffffffff81801f68
  [<ffffffff8189d044>] setup_arch+0x618
    0000000000000000
    ffffffff818d87d0
    0000000000000000
    0000000000000000
    ffffffffffffffff
    0000000000000000
    ffffffff81801f68
  [<ffffffff8148baf6>] printk+0x3c
    ffffffff00000010
    ffffffff81801f78
    ffffffff81801f38
  [<ffffffff8106cc7b>] clockevents_register_notifier+0x3e
    0000000000000000
    ffffffff818d87d0
    0000000000000000
    0000000000000000
    ffffffffffffffff
    0000000000000000
    ffffffff81801fa8
  [<ffffffff81897a3e>] start_kernel+0x90
    ffffffff81801fa8
    ffffffff818da7b0
    0000000001a3c000
    0000000000000000
    0000000000000000
    0000000000000000
    ffffffff81801fc8
  [<ffffffff818972cd>] x86_64_start_reservations+0xb8
    ffffffff8188e610
    ffffffff851cf000
    ffffffff81801ff8
  [<ffffffff8189a799>] xen_start_kernel+0x5ad
    0000000000000001
    0000000000000000
    0000000000000000
    0000000000000000
    0000000000000000
--------------
Any pointers?
p2m_size < nr_pages -1 (0 < 7cfff

The domU kernel config is available at
http://pastebin.com/bq0VeeXY

shriram


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

Konrad Rzeszutek Wilk

2011-Mar-20 20:05 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan
wrote:> The kernel is built from konrad''s tree, devel/next-2.6.39
> commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
> 
> 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
> I have not been able to boot a pv domU, with the above kernel.
You might need this git commit:
31fd38842ab07b95440f24c6180d9a2c14b35111

tc/cmos: Check if ACPI is disabled, and if so don''t attempt

If you pull my tree, you should be able to cherrypick.

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

Konrad Rzeszutek Wilk

2011-Mar-20 20:45 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk
wrote:> On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan wrote:
> > The kernel is built from konrad''s tree, devel/next-2.6.39
> > commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
Ok. So you got Stefano''s latest goodies:

* devel/bootup-fixes.v3:
      watchdog, SP5100: Check if firmware has set correct value in tcobase.
      xen: update mask_rw_pte after kernel page tables init changes
      xen: set max_pfn_mapped to the last pfn mapped
      x86: Cleanup highmap after brk is concluded
> > 
> > 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
Is the 64-bit dom0 kernel == 64-bit domu kernel?
> > I have not been able to boot a pv domU, with the above kernel.
> 
> You might need this git commit:
> 31fd38842ab07b95440f24c6180d9a2c14b35111
> 
> tc/cmos: Check if ACPI is disabled, and if so don''t attempt
> 
> If you pull my tree, you should be able to cherrypick.
Also do ''earlyprintk=xenboot'' in your PV guest and see what it
tells you
(if anything).
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Shriram Rajagopalan

2011-Mar-20 21:05 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Sun, Mar 20, 2011 at 1:45 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan wrote:
> > > The kernel is built from konrad''s tree,
devel/next-2.6.39
> > > commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
>
> Ok. So you got Stefano''s latest goodies:
>
> * devel/bootup-fixes.v3:
>      watchdog, SP5100: Check if firmware has set correct value in tcobase.
>      xen: update mask_rw_pte after kernel page tables init changes
>      xen: set max_pfn_mapped to the last pfn mapped
>      x86: Cleanup highmap after brk is concluded
>
> > >
> > > 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
>
> Is the 64-bit dom0 kernel == 64-bit domu kernel?
>no. dom0 is 2.6.32.27 (from xenbits pvops tree).
>
> > > I have not been able to boot a pv domU, with the above kernel.
> >
> > You might need this git commit:
> > 31fd38842ab07b95440f24c6180d9a2c14b35111
> >
> > tc/cmos: Check if ACPI is disabled, and if so don''t attempt
> >
> > If you pull my tree, you should be able to cherrypick.
>
> Did that. No use. Still same error.FYI, this throws a warning
linux-2.6/drivers/rtc/rtc-cmos.c:1000: warning: ‘return’ with no value, in
function returning non-void

>  Also do ''earlyprintk=xenboot'' in your PV guest and see
what it tells you
> (if anything).
>
> No extra messages in xen''s log.
shriram
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

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

Shriram Rajagopalan

2011-Mar-20 21:19 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Sun, Mar 20, 2011 at 2:05 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> On Sun, Mar 20, 2011 at 1:45 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
>> On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk wrote:
>> > On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan
wrote:
>> > > The kernel is built from konrad''s tree,
devel/next-2.6.39
>> > > commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
>>
>> Ok. So you got Stefano''s latest goodies:
>>
>> * devel/bootup-fixes.v3:
>>      watchdog, SP5100: Check if firmware has set correct value in
tcobase.
>>      xen: update mask_rw_pte after kernel page tables init changes
>>      xen: set max_pfn_mapped to the last pfn mapped
>>      x86: Cleanup highmap after brk is concluded
>>
>> > >
>> > > 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
>>
>> Is the 64-bit dom0 kernel == 64-bit domu kernel?
>>
> no. dom0 is 2.6.32.27 (from xenbits pvops tree).
>
>>
>> > > I have not been able to boot a pv domU, with the above
kernel.
>> >
>> > You might need this git commit:
>> > 31fd38842ab07b95440f24c6180d9a2c14b35111
>> >
>> > tc/cmos: Check if ACPI is disabled, and if so don''t
attempt
>> >
>> > If you pull my tree, you should be able to cherrypick.
>>
>> Did that. No use. Still same error.
> FYI, this throws a warning
> linux-2.6/drivers/rtc/rtc-cmos.c:1000: warning: ‘return’ with no value, in
> function returning non-void
>
>
>>  Also do ''earlyprintk=xenboot'' in your PV guest and
see what it tells you
>> (if anything).
>>
>> No extra messages in xen''s log.
>
> Just for the heck of it, I copied out an .config from a pvops domU (2.6.32)
and tweaked it a bit - basically disabling backend drivers, rtc,
hpet_emulate_rtc.

I got this in console (xm create -c)
Started domain ubuntu-pv64 (id=5)
(early) [    0.000000] Initializing cgroup subsys cpuset
(early) [    0.000000] Initializing cgroup subsys cpu
(early) [    0.000000] Linux version 2.6.38-xenu (root@athos) (gcc version
4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #28 SMP Sun Mar 20 14:05:47 PDT 2011
(early) [    0.000000] Command line: root=/dev/xvda1 ro earlyprintk=xenboot
console=hvc0 3
(early) [    0.000000] ACPI in unprivileged domain disabled
(early) [    0.000000] released 0 pages of unused memory
(early) [    0.000000] Set 0 page(s) to 1-1 mapping.
(early) [    0.000000] BIOS-provided physical RAM map:
(early) [    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
(early) [    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
(early) [    0.000000]  Xen: 0000000000100000 - 000000007d800000 (usable)
(early) [    0.000000] bootconsole [xenboot0] enabled
(early) [    0.000000] NX (Execute Disable) protection: active
(early) [    0.000000] DMI not present or invalid.
(early) [    0.000000] No AGP bridge found
(early) [    0.000000] last_pfn = 0x7d800 max_arch_pfn = 0x400000000
(early) [    0.000000] init_memory_mapping:
0000000000000000-000000007d800000

The errors on xen''s side are still same. MFN mapping error as stated
earlier.
xenctx also shows same output (error coming from pin_pagetable_pfn)

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

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

Konrad Rzeszutek Wilk

2011-Mar-21 11:30 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Sun, Mar 20, 2011 at 02:19:43PM -0700, Shriram Rajagopalan
wrote:> On Sun, Mar 20, 2011 at 2:05 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> 
> > On Sun, Mar 20, 2011 at 1:45 PM, Konrad Rzeszutek Wilk <
> > konrad.wilk@oracle.com> wrote:
> >
> >> On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk
wrote:
> >> > On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram Rajagopalan
wrote:
> >> > > The kernel is built from konrad''s tree,
devel/next-2.6.39
> >> > > commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
> >>
> >> Ok. So you got Stefano''s latest goodies:
> >>
> >> * devel/bootup-fixes.v3:
> >>      watchdog, SP5100: Check if firmware has set correct value in
tcobase.
> >>      xen: update mask_rw_pte after kernel page tables init changes
> >>      xen: set max_pfn_mapped to the last pfn mapped
> >>      x86: Cleanup highmap after brk is concluded
> >>
> >> > >
> >> > > 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
> >>
> >> Is the 64-bit dom0 kernel == 64-bit domu kernel?
> >>
> > no. dom0 is 2.6.32.27 (from xenbits pvops tree).
> >
> >>
> >> > > I have not been able to boot a pv domU, with the above
kernel.
> >> >
> >> > You might need this git commit:
> >> > 31fd38842ab07b95440f24c6180d9a2c14b35111
> >> >
> >> > tc/cmos: Check if ACPI is disabled, and if so don''t
attempt
> >> >
> >> > If you pull my tree, you should be able to cherrypick.
> >>
> >> Did that. No use. Still same error.
> > FYI, this throws a warning
> > linux-2.6/drivers/rtc/rtc-cmos.c:1000: warning: ‘return’ with no
value, in
> > function returning non-void
> >
> >
> >>  Also do ''earlyprintk=xenboot'' in your PV guest
and see what it tells you
> >> (if anything).
> >>
> >> No extra messages in xen''s log.
> >
> > Just for the heck of it, I copied out an .config from a pvops domU
(2.6.32)
> 
> and tweaked it a bit - basically disabling backend drivers, rtc,
> hpet_emulate_rtc.
> 
> I got this in console (xm create -c)
> Started domain ubuntu-pv64 (id=5)
> (early) [    0.000000] Initializing cgroup subsys cpuset
> (early) [    0.000000] Initializing cgroup subsys cpu
> (early) [    0.000000] Linux version 2.6.38-xenu (root@athos) (gcc version
> 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #28 SMP Sun Mar 20 14:05:47 PDT 2011
> (early) [    0.000000] Command line: root=/dev/xvda1 ro earlyprintk=xenboot
> console=hvc0 3
> (early) [    0.000000] ACPI in unprivileged domain disabled
> (early) [    0.000000] released 0 pages of unused memory
> (early) [    0.000000] Set 0 page(s) to 1-1 mapping.
> (early) [    0.000000] BIOS-provided physical RAM map:
> (early) [    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
> (early) [    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
> (early) [    0.000000]  Xen: 0000000000100000 - 000000007d800000 (usable)
> (early) [    0.000000] bootconsole [xenboot0] enabled
> (early) [    0.000000] NX (Execute Disable) protection: active
> (early) [    0.000000] DMI not present or invalid.
> (early) [    0.000000] No AGP bridge found
> (early) [    0.000000] last_pfn = 0x7d800 max_arch_pfn = 0x400000000
> (early) [    0.000000] init_memory_mapping:
> 0000000000000000-000000007d800000
> 
> The errors on xen''s side are still same. MFN mapping error as
stated
> earlier.
And you are using ''xm'' or ''xl''? Try the
either one just to make sure it is
not something silly there.


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

Shriram Rajagopalan

2011-Mar-21 14:50 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On 2011-03-21, at 4:30 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
wrote:
> On Sun, Mar 20, 2011 at 02:19:43PM -0700, Shriram Rajagopalan wrote:
>> On Sun, Mar 20, 2011 at 2:05 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
>> 
>>> On Sun, Mar 20, 2011 at 1:45 PM, Konrad Rzeszutek Wilk <
>>> konrad.wilk@oracle.com> wrote:
>>> 
>>>> On Sun, Mar 20, 2011 at 04:05:43PM -0400, Konrad Rzeszutek Wilk
wrote:
>>>>> On Sat, Mar 19, 2011 at 06:22:17PM -0700, Shriram
Rajagopalan wrote:
>>>>>> The kernel is built from konrad''s tree,
devel/next-2.6.39
>>>>>> commit:f4ddaaf4338999227b3f724615d8aecbe88d3f04
>>>> 
>>>> Ok. So you got Stefano''s latest goodies:
>>>> 
>>>> * devel/bootup-fixes.v3:
>>>>     watchdog, SP5100: Check if firmware has set correct value
in tcobase.
>>>>     xen: update mask_rw_pte after kernel page tables init
changes
>>>>     xen: set max_pfn_mapped to the last pfn mapped
>>>>     x86: Cleanup highmap after brk is concluded
>>>> 
>>>>>> 
>>>>>> 64 bit PV guest, 64 bit dom0, xen 4.1.0-rc7-pre
>>>> 
>>>> Is the 64-bit dom0 kernel == 64-bit domu kernel?
>>>> 
>>> no. dom0 is 2.6.32.27 (from xenbits pvops tree).
>>> 
>>>> 
>>>>>> I have not been able to boot a pv domU, with the above
kernel.
>>>>> 
>>>>> You might need this git commit:
>>>>> 31fd38842ab07b95440f24c6180d9a2c14b35111
>>>>> 
>>>>> tc/cmos: Check if ACPI is disabled, and if so
don''t attempt
>>>>> 
>>>>> If you pull my tree, you should be able to cherrypick.
>>>> 
>>>> Did that. No use. Still same error.
>>> FYI, this throws a warning
>>> linux-2.6/drivers/rtc/rtc-cmos.c:1000: warning: ‘return’ with no
value, in
>>> function returning non-void
>>> 
>>> 
>>>> Also do ''earlyprintk=xenboot'' in your PV
guest and see what it tells you
>>>> (if anything).
>>>> 
>>>> No extra messages in xen''s log.
>>> 
>>> Just for the heck of it, I copied out an .config from a pvops domU
(2.6.32)
>> 
>> and tweaked it a bit - basically disabling backend drivers, rtc,
>> hpet_emulate_rtc.
>> 
>> I got this in console (xm create -c)
>> Started domain ubuntu-pv64 (id=5)
>> (early) [    0.000000] Initializing cgroup subsys cpuset
>> (early) [    0.000000] Initializing cgroup subsys cpu
>> (early) [    0.000000] Linux version 2.6.38-xenu (root@athos) (gcc
version
>> 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #28 SMP Sun Mar 20 14:05:47 PDT 2011
>> (early) [    0.000000] Command line: root=/dev/xvda1 ro
earlyprintk=xenboot
>> console=hvc0 3
>> (early) [    0.000000] ACPI in unprivileged domain disabled
>> (early) [    0.000000] released 0 pages of unused memory
>> (early) [    0.000000] Set 0 page(s) to 1-1 mapping.
>> (early) [    0.000000] BIOS-provided physical RAM map:
>> (early) [    0.000000]  Xen: 0000000000000000 - 00000000000a0000
(usable)
>> (early) [    0.000000]  Xen: 00000000000a0000 - 0000000000100000
(reserved)
>> (early) [    0.000000]  Xen: 0000000000100000 - 000000007d800000
(usable)
>> (early) [    0.000000] bootconsole [xenboot0] enabled
>> (early) [    0.000000] NX (Execute Disable) protection: active
>> (early) [    0.000000] DMI not present or invalid.
>> (early) [    0.000000] No AGP bridge found
>> (early) [    0.000000] last_pfn = 0x7d800 max_arch_pfn = 0x400000000
>> (early) [    0.000000] init_memory_mapping:
>> 0000000000000000-000000007d800000
>> 
>> The errors on xen''s side are still same. MFN mapping error as
stated
>> earlier.
> 
> And you are using ''xm'' or ''xl''? Try the
either one just to make sure it is
> not something silly there.
> Tried both. Same issue.
Btw, if you have a working domU, can you please test Rafael''s patch for
the HIBERNATE_INTERFACE ? he replied to my
"PATCH v3 3/5 Add visible HIBERNATION_INTERFACE and hide HIBERNATION"
with his version of the refactoring patch.
I can compile the code but am not able to test it due to this boot issue. And
before you ask, yes, all bugs reported here were without his patch.

 If it works out okay, we might be able to push the remaining 3 bits of the
freeze-thaw patch via his tree, hopefully.
Shriram
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad Rzeszutek Wilk

2011-Mar-22 17:00 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

> Btw, if you have a working domU, can you please test Rafael''s
patch for the HIBERNATE_INTERFACE ? he replied to my
> "PATCH v3 3/5 Add visible HIBERNATION_INTERFACE and hide
HIBERNATION" with his version of the refactoring patch.
> I can compile the code but am not able to test it due to this boot issue.
And before you ask, yes, all bugs reported here were without his patch.
Will try this week . Do you have a branch on which you put all of the patches
that you were trying to test?
> 
>  If it works out okay, we might be able to push the remaining 3 bits of the
freeze-thaw patch via his tree, hopefully.
> Shriram
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Shriram Rajagopalan

2011-Mar-22 17:16 UTC

head link

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

On Tue, Mar 22, 2011 at 10:00 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:
> > Btw, if you have a working domU, can you please test Rafael''s
patch for
> the HIBERNATE_INTERFACE ? he replied to my
> > "PATCH v3 3/5 Add visible HIBERNATION_INTERFACE and hide
HIBERNATION"
> with his version of the refactoring patch.
> > I can compile the code but am not able to test it due to this boot
issue.
> And before you ask, yes, all bugs reported here were without his patch.
>
> Will try this week . Do you have a branch on which you put all of the
> patches that you were trying to test?
>
> git://athos.nss.cs.ubc.ca/gitorama/konrad/linux-2.6 shriram/hibernate
This branch tracks your devel/next-2.6.39
I have committed both patches (hibernate_interface and the xen config fixes)
into that branch. I
didnt commit the rtc/cmos bug fix as it didnt seem to help.

shriram
>  >
> >  If it works out okay, we might be able to push the remaining 3 bits
of
> the freeze-thaw patch via his tree, hopefully.
> > Shriram
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

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

Xen devel - Mar 2011 - 2.6.38 PV Guest boot failure - error while pinning mfn..

[Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..

Re: [Xen-devel] 2.6.38 PV Guest boot failure - error while pinning mfn..