Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Andrew Cooper]

On 20/11/15 15:41, Andrew Cooper wrote:
> On 20/11/15 15:34, Wei Liu wrote:
>> On Fri, Nov 20, 2015 at 04:29:04PM +0100, Juergen Gross wrote:
>>> On 20/11/15 16:14, Jan Beulich wrote:
>>> On 19.11.15 at 12:47,  wrote:
> On 19/11/15 11:30, Ian Campbell wrote:
>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>>> On 18/11/15 15:49, Wei Liu wrote:
 Hi Juergen

 Looks like there is something we missed after all.

 On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> flight 64494 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64494/ 
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> vs. 64035
 Nov 18 05:11:19.753014 (d2) Bootstrapping...
 Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
 Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
 Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
 Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
 Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
 Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
 Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
 Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
 Nov 18 05:11:19.785135 (d2)  mod_len: 0
 Nov 18 05:11:19.793047 (d2)flags: 0x0
 Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
 Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
 Nov 18 05:11:19.801150 (d2) MM: Init
 Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
 Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
 Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
 Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
 Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
 Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
 Nov 18 05:11:19.817099 (d2)   start_pfn: a24
 Nov 18 05:11:19.817125 (d2) max_pfn: 2
 Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
 Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
 Nov 18 05:11:19.825100 (d2) skipped 1000
 Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
 b1c000(b1c000)-2000(2000)
 Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
 Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
 invalid memory?).

 The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
 be working fine.
>>> Okay, I'm hitting this issue, too. I'll investigate further.
>> Do we want to revert $something in the meantime? If so, what...
>>
> The problem is really located in pvgrub:
 One question I have here: Even if this gets fixed in pvgrub (or
 mini-os, as it now seems), can we tolerate all existing mini-os
 clones now being broken on -unstable (and hence then also
 eventually on 4.7)?
>>> It would be rather inconvenient if not. The problem is mini-os is
>>> relying on an interface which was never meant to be this way. grub-xen
>>> is already breaking this interface today, and I think this is okay.
>>>
>>> Is mini-os shipped independent of Xen in any other product or stand
>>> alone?
>> Rump kernel has quite a bit of code based on mini-os. I will take care
>> of that. That's the only "real" thing based on mini-os that I'm aware
>> of.
>>
>> Given that we split mini-os out just last release, I don't expect there
>> are many clones in the wild.
> Mirage microkernels use a mini-os base as well.
>
> Having said that, I don't think we should not block this change because
> mini-os has been broken in a dumb way for ages.
>
> People using mini-os based things will have to take a "stable update" of
> their mini-os to run on Xen 4.7 when it is release.  Linux is treated
> exactly the same with bugs like this.

Apologies - too many negatives.  "I don't think we should block this
change".

~Andrew

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Jan Beulich]

>>> On 19.11.15 at 12:47,  wrote:
> On 19/11/15 11:30, Ian Campbell wrote:
>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>>> On 18/11/15 15:49, Wei Liu wrote:
 Hi Juergen

 Looks like there is something we missed after all.

 On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> flight 64494 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64494/ 
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:

>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> vs. 64035

 Nov 18 05:11:19.753014 (d2) Bootstrapping...
 Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
 Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
 Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
 Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
 Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
 Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
 Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
 Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
 Nov 18 05:11:19.785135 (d2)  mod_len: 0
 Nov 18 05:11:19.793047 (d2)flags: 0x0
 Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
 Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
 Nov 18 05:11:19.801150 (d2) MM: Init
 Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
 Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
 Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
 Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
 Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
 Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
 Nov 18 05:11:19.817099 (d2)   start_pfn: a24
 Nov 18 05:11:19.817125 (d2) max_pfn: 2
 Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
 Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
 Nov 18 05:11:19.825100 (d2) skipped 1000
 Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
 b1c000(b1c000)-2000(2000)
 Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
 Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
 invalid memory?).

 The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
 be working fine.
>>>
>>> Okay, I'm hitting this issue, too. I'll investigate further.
>> 
>> Do we want to revert $something in the meantime? If so, what...
>> 
> 
> The problem is really located in pvgrub:

One question I have here: Even if this gets fixed in pvgrub (or
mini-os, as it now seems), can we tolerate all existing mini-os
clones now being broken on -unstable (and hence then also
eventually on 4.7)?

Jan


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Fri, Nov 20, 2015 at 08:14:00AM -0700, Jan Beulich wrote:
> >>> On 19.11.15 at 12:47,  wrote:
> > On 19/11/15 11:30, Ian Campbell wrote:
> >> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> >>> On 18/11/15 15:49, Wei Liu wrote:
>  Hi Juergen
> 
>  Looks like there is something we missed after all.
> 
>  On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> > flight 64494 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/64494/ 
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> 
> >  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> > vs. 64035
> 
>  Nov 18 05:11:19.753014 (d2) Bootstrapping...
>  Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
>  Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
>  Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
>  Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
>  Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
>  Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
>  Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
>  Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
>  Nov 18 05:11:19.785135 (d2)  mod_len: 0
>  Nov 18 05:11:19.793047 (d2)flags: 0x0
>  Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
>  Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
>  Nov 18 05:11:19.801150 (d2) MM: Init
>  Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
>  Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
>  Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
>  Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
>  Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
>  Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
>  Nov 18 05:11:19.817099 (d2)   start_pfn: a24
>  Nov 18 05:11:19.817125 (d2) max_pfn: 2
>  Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
>  Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
>  Nov 18 05:11:19.825100 (d2) skipped 1000
>  Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
>  b1c000(b1c000)-2000(2000)
>  Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
>  5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
>  Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
>  invalid memory?).
> 
>  The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
>  be working fine.
> >>>
> >>> Okay, I'm hitting this issue, too. I'll investigate further.
> >> 
> >> Do we want to revert $something in the meantime? If so, what...
> >> 
> > 
> > The problem is really located in pvgrub:
> 
> One question I have here: Even if this gets fixed in pvgrub (or
> mini-os, as it now seems), can we tolerate all existing mini-os
> clones now being broken on -unstable (and hence then also
> eventually on 4.7)?
> 

I think all mini-os clones should pick up the change Juergen posted.
It's mini-os having wrong assumption in the first place.

Wei.

> Jan
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 20/11/15 16:14, Jan Beulich wrote:
 On 19.11.15 at 12:47,  wrote:
>> On 19/11/15 11:30, Ian Campbell wrote:
>>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
 On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
>
> Looks like there is something we missed after all.
>
> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>> flight 64494 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/64494/ 
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>
>>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
>> vs. 64035
>
> Nov 18 05:11:19.753014 (d2) Bootstrapping...
> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> Nov 18 05:11:19.785135 (d2)  mod_len: 0
> Nov 18 05:11:19.793047 (d2)flags: 0x0
> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> Nov 18 05:11:19.801150 (d2) MM: Init
> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> Nov 18 05:11:19.817125 (d2) max_pfn: 2
> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> Nov 18 05:11:19.825100 (d2) skipped 1000
> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> b1c000(b1c000)-2000(2000)
> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> invalid memory?).
>
> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> be working fine.

 Okay, I'm hitting this issue, too. I'll investigate further.
>>>
>>> Do we want to revert $something in the meantime? If so, what...
>>>
>>
>> The problem is really located in pvgrub:
> 
> One question I have here: Even if this gets fixed in pvgrub (or
> mini-os, as it now seems), can we tolerate all existing mini-os
> clones now being broken on -unstable (and hence then also
> eventually on 4.7)?

It would be rather inconvenient if not. The problem is mini-os is
relying on an interface which was never meant to be this way. grub-xen
is already breaking this interface today, and I think this is okay.

Is mini-os shipped independent of Xen in any other product or stand
alone?

I'd advocate to backport the mini-os patch to older versions of it
if this should be a problem.


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Fri, Nov 20, 2015 at 04:29:04PM +0100, Juergen Gross wrote:
> On 20/11/15 16:14, Jan Beulich wrote:
>  On 19.11.15 at 12:47,  wrote:
> >> On 19/11/15 11:30, Ian Campbell wrote:
> >>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>  On 18/11/15 15:49, Wei Liu wrote:
> > Hi Juergen
> >
> > Looks like there is something we missed after all.
> >
> > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> >> flight 64494 xen-unstable real [real]
> >> http://logs.test-lab.xenproject.org/osstest/logs/64494/ 
> >>
> >> Regressions :-(
> >>
> >> Tests which did not succeed and are blocking,
> >> including tests which could not be run:
> >
> >>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> >> vs. 64035
> >
> > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > Nov 18 05:11:19.801150 (d2) MM: Init
> > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > Nov 18 05:11:19.825100 (d2) skipped 1000
> > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> > b1c000(b1c000)-2000(2000)
> > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> > 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> > invalid memory?).
> >
> > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> > be working fine.
> 
>  Okay, I'm hitting this issue, too. I'll investigate further.
> >>>
> >>> Do we want to revert $something in the meantime? If so, what...
> >>>
> >>
> >> The problem is really located in pvgrub:
> > 
> > One question I have here: Even if this gets fixed in pvgrub (or
> > mini-os, as it now seems), can we tolerate all existing mini-os
> > clones now being broken on -unstable (and hence then also
> > eventually on 4.7)?
> 
> It would be rather inconvenient if not. The problem is mini-os is
> relying on an interface which was never meant to be this way. grub-xen
> is already breaking this interface today, and I think this is okay.
> 
> Is mini-os shipped independent of Xen in any other product or stand
> alone?

Rump kernel has quite a bit of code based on mini-os. I will take care
of that. That's the only "real" thing based on mini-os that I'm aware
of.

Given that we split mini-os out just last release, I don't expect there
are many clones in the wild.

Wei.

> 
> I'd advocate to backport the mini-os patch to older versions of it
> if this should be a problem.
> 
> 
> Juergen
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Andrew Cooper]

On 20/11/15 15:34, Wei Liu wrote:
> On Fri, Nov 20, 2015 at 04:29:04PM +0100, Juergen Gross wrote:
>> On 20/11/15 16:14, Jan Beulich wrote:
>> On 19.11.15 at 12:47,  wrote:
 On 19/11/15 11:30, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
 flight 64494 xen-unstable real [real]
 http://logs.test-lab.xenproject.org/osstest/logs/64494/ 

 Regressions :-(

 Tests which did not succeed and are blocking,
 including tests which could not be run:
  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
 vs. 64035
>>> Nov 18 05:11:19.753014 (d2) Bootstrapping...
>>> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
>>> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
>>> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
>>> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
>>> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
>>> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
>>> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
>>> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
>>> Nov 18 05:11:19.785135 (d2)  mod_len: 0
>>> Nov 18 05:11:19.793047 (d2)flags: 0x0
>>> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
>>> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
>>> Nov 18 05:11:19.801150 (d2) MM: Init
>>> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
>>> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
>>> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
>>> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
>>> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
>>> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
>>> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
>>> Nov 18 05:11:19.817125 (d2) max_pfn: 2
>>> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
>>> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
>>> Nov 18 05:11:19.825100 (d2) skipped 1000
>>> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
>>> b1c000(b1c000)-2000(2000)
>>> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
>>> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
>>> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
>>> invalid memory?).
>>>
>>> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
>>> be working fine.
>> Okay, I'm hitting this issue, too. I'll investigate further.
> Do we want to revert $something in the meantime? If so, what...
>
 The problem is really located in pvgrub:
>>> One question I have here: Even if this gets fixed in pvgrub (or
>>> mini-os, as it now seems), can we tolerate all existing mini-os
>>> clones now being broken on -unstable (and hence then also
>>> eventually on 4.7)?
>> It would be rather inconvenient if not. The problem is mini-os is
>> relying on an interface which was never meant to be this way. grub-xen
>> is already breaking this interface today, and I think this is okay.
>>
>> Is mini-os shipped independent of Xen in any other product or stand
>> alone?
> Rump kernel has quite a bit of code based on mini-os. I will take care
> of that. That's the only "real" thing based on mini-os that I'm aware
> of.
>
> Given that we split mini-os out just last release, I don't expect there
> are many clones in the wild.

Mirage microkernels use a mini-os base as well.

Having said that, I don't think we should not block this change because
mini-os has been broken in a dumb way for ages.

People using mini-os based things will have to take a "stable update" of
their mini-os to run on Xen 4.7 when it is release.  Linux is treated
exactly the same with bugs like this.

~Andrew

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > On 18/11/15 15:49, Wei Liu wrote:
> > > Hi Juergen
> > > 
> > > Looks like there is something we missed after all.
> > > 
> > > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> > > > flight 64494 xen-unstable real [real]
> > > > http://logs.test-lab.xenproject.org/osstest/logs/64494/
> > > > 
> > > > Regressions :-(
> > > > 
> > > > Tests which did not succeed and are blocking,
> > > > including tests which could not be run:
> > > 
> > > >  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> > > > vs. 64035
> > > 
> > > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > > Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> > > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > > Nov 18 05:11:19.801150 (d2) MM: Init
> > > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> > > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > > Nov 18 05:11:19.825100 (d2) skipped 1000
> > > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> > > b1c000(b1c000)-2000(2000)
> > > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> > > 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> > > invalid memory?).
> > > 
> > > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> > > be working fine.
> > 
> > Okay, I'm hitting this issue, too. I'll investigate further.
> 
> Do we want to revert $something in the meantime? If so, what...
> 

Given the thorny nature of PV page table construction code I would
revert the whole series...

But let's wait a bit to see if Juergen can come up with a fix for this
today.

Wei.

> Ian.
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 19/11/15 11:30, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
 flight 64494 xen-unstable real [real]
 http://logs.test-lab.xenproject.org/osstest/logs/64494/

 Regressions :-(

 Tests which did not succeed and are blocking,
 including tests which could not be run:
>>>
  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
 vs. 64035
>>>
>>> Nov 18 05:11:19.753014 (d2) Bootstrapping...
>>> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
>>> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
>>> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
>>> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
>>> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
>>> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
>>> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
>>> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
>>> Nov 18 05:11:19.785135 (d2)  mod_len: 0
>>> Nov 18 05:11:19.793047 (d2)flags: 0x0
>>> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
>>> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
>>> Nov 18 05:11:19.801150 (d2) MM: Init
>>> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
>>> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
>>> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
>>> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
>>> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
>>> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
>>> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
>>> Nov 18 05:11:19.817125 (d2) max_pfn: 2
>>> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
>>> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
>>> Nov 18 05:11:19.825100 (d2) skipped 1000
>>> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
>>> b1c000(b1c000)-2000(2000)
>>> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
>>> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
>>> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
>>> invalid memory?).
>>>
>>> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
>>> be working fine.
>>
>> Okay, I'm hitting this issue, too. I'll investigate further.
> 
> Do we want to revert $something in the meantime? If so, what...

I'm rather sure this problem is present in 32 bit pvgrub only. I've
found a suspicious test for the need of allocating a new page table.
pvgrub seems to make assumptions which level 2 page tables are to
be present and which not. I'm quite sure it wouldn't be able to be
started by grub-xen as well...

In case I'm right I should be able to correct this until today
evening.


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 19/11/15 13:19, Wei Liu wrote:
> On Thu, Nov 19, 2015 at 12:47:41PM +0100, Juergen Gross wrote:
>> On 19/11/15 11:30, Ian Campbell wrote:
>>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
 On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
>
> Looks like there is something we missed after all.
>
> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>> flight 64494 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/64494/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>
>>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
>> vs. 64035
>
> Nov 18 05:11:19.753014 (d2) Bootstrapping...
> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> Nov 18 05:11:19.785135 (d2)  mod_len: 0
> Nov 18 05:11:19.793047 (d2)flags: 0x0
> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> Nov 18 05:11:19.801150 (d2) MM: Init
> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> Nov 18 05:11:19.817125 (d2) max_pfn: 2
> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> Nov 18 05:11:19.825100 (d2) skipped 1000
> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> b1c000(b1c000)-2000(2000)
> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> invalid memory?).
>
> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> be working fine.

 Okay, I'm hitting this issue, too. I'll investigate further.
>>>
>>> Do we want to revert $something in the meantime? If so, what...
>>>
>>
>> The problem is really located in pvgrub:
>>
> 
> To be precise, the problem is in mini-os, which is used by rump kernel
> as well. :-(
> 
>> pvgrub is making assumptions about the page table allocation scheme
>> of the toolset starting pvgrub. It is calculating the first not yet
>> mapped pfn by:
>>
>> pfn_to_map =
>> (start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES;
>>
>> NOT_L1_FRAMES is 3 for 64 bit and 32 bit:
>>
>> 64 bit: 1 level 4 + 1 level 4 + 1 level 2
>> 32 bit: 1 level 3 + 2 level 2 (assuming level 2 pt are allocated
>>   for the first and the last GB)
>>
>> This is wrong now, as for 32 bit I'm allocating all level 2 page
>> tables from the lowest needed address up to 0x, resulting
>> in 4 level 2 page tables in pvgrub case.
>>
>> Setting NOT_L1_FRAMES to 5 for 32 bit pvgrub makes the system boot
>> again.
>>
>> I think it is wrong for pvgrub to assume a fixed allocation scheme
>> of the page tables. The question is how to fix it: either via
>> changing NOT_L1_FRAMES or by doing it in a clean but more complicated
>> way.
>>
> 
> In the mean time, shall we revert the series and think about this a bit
> more?
> 
> How complicated will be clean fix be?

I think I can fix it today. I can just count the not_l1_frames
dynamically by walking through the higher level page tables. This
will work for 32 and 64 bit and with and without my patch series
and even for 32 bit mini-os started via grub-xen.

> Does changing NOT_L1_FRAMES break mini-os boot with toolstack prior to
> your series?

Yes.

Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Thu, Nov 19, 2015 at 01:29:01PM +0100, Juergen Gross wrote:
[...]
> > To be precise, the problem is in mini-os, which is used by rump kernel
> > as well. :-(
> > 
> >> pvgrub is making assumptions about the page table allocation scheme
> >> of the toolset starting pvgrub. It is calculating the first not yet
> >> mapped pfn by:
> >>
> >> pfn_to_map =
> >> (start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES;
> >>
> >> NOT_L1_FRAMES is 3 for 64 bit and 32 bit:
> >>
> >> 64 bit: 1 level 4 + 1 level 4 + 1 level 2
> >> 32 bit: 1 level 3 + 2 level 2 (assuming level 2 pt are allocated
> >>   for the first and the last GB)
> >>
> >> This is wrong now, as for 32 bit I'm allocating all level 2 page
> >> tables from the lowest needed address up to 0x, resulting
> >> in 4 level 2 page tables in pvgrub case.
> >>
> >> Setting NOT_L1_FRAMES to 5 for 32 bit pvgrub makes the system boot
> >> again.
> >>
> >> I think it is wrong for pvgrub to assume a fixed allocation scheme
> >> of the page tables. The question is how to fix it: either via
> >> changing NOT_L1_FRAMES or by doing it in a clean but more complicated
> >> way.
> >>
> > 
> > In the mean time, shall we revert the series and think about this a bit
> > more?
> > 
> > How complicated will be clean fix be?
> 
> I think I can fix it today. I can just count the not_l1_frames
> dynamically by walking through the higher level page tables. This

This seems sensible.

> will work for 32 and 64 bit and with and without my patch series
> and even for 32 bit mini-os started via grub-xen.
> 
> > Does changing NOT_L1_FRAMES break mini-os boot with toolstack prior to
> > your series?
> 
> Yes.
> 

In that case I think a clean fix is required.

Wei.

> Juergen
> 
> 
> ___
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 19/11/15 11:30, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
 flight 64494 xen-unstable real [real]
 http://logs.test-lab.xenproject.org/osstest/logs/64494/

 Regressions :-(

 Tests which did not succeed and are blocking,
 including tests which could not be run:
>>>
  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
 vs. 64035
>>>
>>> Nov 18 05:11:19.753014 (d2) Bootstrapping...
>>> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
>>> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
>>> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
>>> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
>>> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
>>> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
>>> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
>>> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
>>> Nov 18 05:11:19.785135 (d2)  mod_len: 0
>>> Nov 18 05:11:19.793047 (d2)flags: 0x0
>>> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
>>> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
>>> Nov 18 05:11:19.801150 (d2) MM: Init
>>> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
>>> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
>>> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
>>> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
>>> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
>>> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
>>> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
>>> Nov 18 05:11:19.817125 (d2) max_pfn: 2
>>> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
>>> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
>>> Nov 18 05:11:19.825100 (d2) skipped 1000
>>> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
>>> b1c000(b1c000)-2000(2000)
>>> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
>>> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
>>> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
>>> invalid memory?).
>>>
>>> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
>>> be working fine.
>>
>> Okay, I'm hitting this issue, too. I'll investigate further.
> 
> Do we want to revert $something in the meantime? If so, what...
> 

The problem is really located in pvgrub:

pvgrub is making assumptions about the page table allocation scheme
of the toolset starting pvgrub. It is calculating the first not yet
mapped pfn by:

pfn_to_map =
(start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES;

NOT_L1_FRAMES is 3 for 64 bit and 32 bit:

64 bit: 1 level 4 + 1 level 4 + 1 level 2
32 bit: 1 level 3 + 2 level 2 (assuming level 2 pt are allocated
  for the first and the last GB)

This is wrong now, as for 32 bit I'm allocating all level 2 page
tables from the lowest needed address up to 0x, resulting
in 4 level 2 page tables in pvgrub case.

Setting NOT_L1_FRAMES to 5 for 32 bit pvgrub makes the system boot
again.

I think it is wrong for pvgrub to assume a fixed allocation scheme
of the page tables. The question is how to fix it: either via
changing NOT_L1_FRAMES or by doing it in a clean but more complicated
way.


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Thu, Nov 19, 2015 at 12:47:41PM +0100, Juergen Gross wrote:
> On 19/11/15 11:30, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> >> On 18/11/15 15:49, Wei Liu wrote:
> >>> Hi Juergen
> >>>
> >>> Looks like there is something we missed after all.
> >>>
> >>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>  flight 64494 xen-unstable real [real]
>  http://logs.test-lab.xenproject.org/osstest/logs/64494/
> 
>  Regressions :-(
> 
>  Tests which did not succeed and are blocking,
>  including tests which could not be run:
> >>>
>   test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
>  vs. 64035
> >>>
> >>> Nov 18 05:11:19.753014 (d2) Bootstrapping...
> >>> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> >>> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> >>> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> >>> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> >>> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> >>> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> >>> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> >>> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> >>> Nov 18 05:11:19.785135 (d2)  mod_len: 0
> >>> Nov 18 05:11:19.793047 (d2)flags: 0x0
> >>> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> >>> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> >>> Nov 18 05:11:19.801150 (d2) MM: Init
> >>> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> >>> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> >>> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> >>> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> >>> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> >>> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> >>> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> >>> Nov 18 05:11:19.817125 (d2) max_pfn: 2
> >>> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> >>> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> >>> Nov 18 05:11:19.825100 (d2) skipped 1000
> >>> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> >>> b1c000(b1c000)-2000(2000)
> >>> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> >>> 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> >>> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> >>> invalid memory?).
> >>>
> >>> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> >>> be working fine.
> >>
> >> Okay, I'm hitting this issue, too. I'll investigate further.
> > 
> > Do we want to revert $something in the meantime? If so, what...
> > 
> 
> The problem is really located in pvgrub:
> 

To be precise, the problem is in mini-os, which is used by rump kernel
as well. :-(

> pvgrub is making assumptions about the page table allocation scheme
> of the toolset starting pvgrub. It is calculating the first not yet
> mapped pfn by:
> 
> pfn_to_map =
> (start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES;
> 
> NOT_L1_FRAMES is 3 for 64 bit and 32 bit:
> 
> 64 bit: 1 level 4 + 1 level 4 + 1 level 2
> 32 bit: 1 level 3 + 2 level 2 (assuming level 2 pt are allocated
>   for the first and the last GB)
> 
> This is wrong now, as for 32 bit I'm allocating all level 2 page
> tables from the lowest needed address up to 0x, resulting
> in 4 level 2 page tables in pvgrub case.
> 
> Setting NOT_L1_FRAMES to 5 for 32 bit pvgrub makes the system boot
> again.
> 
> I think it is wrong for pvgrub to assume a fixed allocation scheme
> of the page tables. The question is how to fix it: either via
> changing NOT_L1_FRAMES or by doing it in a clean but more complicated
> way.
> 

In the mean time, shall we revert the series and think about this a bit
more?

How complicated will be clean fix be?

Does changing NOT_L1_FRAMES break mini-os boot with toolstack prior to
your series?

Wei.

> 
> Juergen
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
> 
> Looks like there is something we missed after all.
> 
> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>> flight 64494 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/64494/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
> 
>>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR. vs. 
>> 64035
> 
> Nov 18 05:11:19.753014 (d2) Bootstrapping...
> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> Nov 18 05:11:19.785135 (d2)  mod_len: 0
> Nov 18 05:11:19.793047 (d2)flags: 0x0
> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> Nov 18 05:11:19.801150 (d2) MM: Init
> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> Nov 18 05:11:19.817125 (d2) max_pfn: 2
> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> Nov 18 05:11:19.825100 (d2) skipped 1000
> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for 
> b1c000(b1c000)-2000(2000)
> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip 5fc70, 
> regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid 
> memory?).
> 
> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> be working fine.

Okay, I'm hitting this issue, too. I'll investigate further.


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Ian Campbell]

On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> On 18/11/15 15:49, Wei Liu wrote:
> > Hi Juergen
> > 
> > Looks like there is something we missed after all.
> > 
> > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> > > flight 64494 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/64494/
> > > 
> > > Regressions :-(
> > > 
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > 
> > >  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR.
> > > vs. 64035
> > 
> > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > Nov 18 05:11:19.801150 (d2) MM: Init
> > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > Nov 18 05:11:19.825100 (d2) skipped 1000
> > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> > b1c000(b1c000)-2000(2000)
> > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip
> > 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> > invalid memory?).
> > 
> > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> > be working fine.
> 
> Okay, I'm hitting this issue, too. I'll investigate further.

Do we want to revert $something in the meantime? If so, what...

Ian.


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Ian Campbell]

On Thu, 2015-11-19 at 10:50 +, Wei Liu wrote:
> On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > > On 18/11/15 15:49, Wei Liu wrote:
> > > > Hi Juergen
> > > > 
> > > > Looks like there is something we missed after all.
> > > > 
> > > > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner
> > > > wrote:
> > > > > flight 64494 xen-unstable real [real]
> > > > > http://logs.test-lab.xenproject.org/osstest/logs/64494/
> > > > > 
> > > > > Regressions :-(
> > > > > 
> > > > > Tests which did not succeed and are blocking,
> > > > > including tests which could not be run:
> > > > 
> > > > >  test-amd64-amd64-i386-pvgrub 10 guest-start   fail
> > > > > REGR.
> > > > > vs. 64035
> > > > 
> > > > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > > > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > > > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > > > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > > > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > > > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > > > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > > > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > > > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > > > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > > > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > > > Nov 18 05:11:19.793077 (d2) cmd_line:
> > > > (hd0,0)/boot/grub/menu.lst
> > > > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > > > Nov 18 05:11:19.801150 (d2) MM: Init
> > > > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > > > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > > > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > > > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > > > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > > > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > > > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > > > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > > > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 -
> > > > 0x2000
> > > > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > > > Nov 18 05:11:19.825100 (d2) skipped 1000
> > > > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> > > > b1c000(b1c000)-2000(2000)
> > > > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8,
> > > > eip
> > > > 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > > > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> > > > invalid memory?).
> > > > 
> > > > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed
> > > > to
> > > > be working fine.
> > > 
> > > Okay, I'm hitting this issue, too. I'll investigate further.
> > 
> > Do we want to revert $something in the meantime? If so, what...
> > 
> 
> Given the thorny nature of PV page table construction code I would
> revert the whole series...

Please assume I've forgotten what series that is...

> But let's wait a bit to see if Juergen can come up with a fix for this
> today.

... sure.

Ian.

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Thu, Nov 19, 2015 at 10:55:13AM +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 10:50 +, Wei Liu wrote:
> > On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> > > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > > > On 18/11/15 15:49, Wei Liu wrote:
> > > > > Hi Juergen
> > > > > 
> > > > > Looks like there is something we missed after all.
> > > > > 
> > > > > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner
> > > > > wrote:
> > > > > > flight 64494 xen-unstable real [real]
> > > > > > http://logs.test-lab.xenproject.org/osstest/logs/64494/
> > > > > > 
> > > > > > Regressions :-(
> > > > > > 
> > > > > > Tests which did not succeed and are blocking,
> > > > > > including tests which could not be run:
> > > > > 
> > > > > >  test-amd64-amd64-i386-pvgrub 10 guest-start   fail
> > > > > > REGR.
> > > > > > vs. 64035
> > > > > 
> > > > > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > > > > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > > > > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > > > > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > > > > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > > > > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > > > > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > > > > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > > > > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > > > > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > > > > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > > > > Nov 18 05:11:19.793077 (d2) cmd_line:
> > > > > (hd0,0)/boot/grub/menu.lst
> > > > > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > > > > Nov 18 05:11:19.801150 (d2) MM: Init
> > > > > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > > > > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > > > > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > > > > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > > > > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > > > > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > > > > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > > > > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > > > > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 -
> > > > > 0x2000
> > > > > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > > > > Nov 18 05:11:19.825100 (d2) skipped 1000
> > > > > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for
> > > > > b1c000(b1c000)-2000(2000)
> > > > > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8,
> > > > > eip
> > > > > 5fc70, regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > > > > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to
> > > > > invalid memory?).
> > > > > 
> > > > > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed
> > > > > to
> > > > > be working fine.
> > > > 
> > > > Okay, I'm hitting this issue, too. I'll investigate further.
> > > 
> > > Do we want to revert $something in the meantime? If so, what...
> > > 
> > 
> > Given the thorny nature of PV page table construction code I would
> > revert the whole series...
> 
> Please assume I've forgotten what series that is...
> 

Don't worry. I will prepare a branch. :-)

> > But let's wait a bit to see if Juergen can come up with a fix for this
> > today.
> 
> ... sure.
> 
> Ian.

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
> 
> Looks like there is something we missed after all.
> 
> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>> flight 64494 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/64494/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
> 
>>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR. vs. 
>> 64035
> 
> Nov 18 05:11:19.753014 (d2) Bootstrapping...
> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> Nov 18 05:11:19.785135 (d2)  mod_len: 0
> Nov 18 05:11:19.793047 (d2)flags: 0x0
> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> Nov 18 05:11:19.801150 (d2) MM: Init
> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> Nov 18 05:11:19.817125 (d2) max_pfn: 2
> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> Nov 18 05:11:19.825100 (d2) skipped 1000
> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for 
> b1c000(b1c000)-2000(2000)
> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip 5fc70, 
> regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid 
> memory?).
> 
> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> be working fine.

Hmm. I'll try again to make pvgrub work (more or less).

Wei, in case you want to try to reproduce the problem: could you
try to map the eip to function + offset?


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

On Wed, Nov 18, 2015 at 04:54:34PM +0100, Juergen Gross wrote:
> On 18/11/15 15:49, Wei Liu wrote:
> > Hi Juergen
> > 
> > Looks like there is something we missed after all.
> > 
> > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> >> flight 64494 xen-unstable real [real]
> >> http://logs.test-lab.xenproject.org/osstest/logs/64494/
> >>
> >> Regressions :-(
> >>
> >> Tests which did not succeed and are blocking,
> >> including tests which could not be run:
> > 
> >>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR. vs. 
> >> 64035
> > 
> > Nov 18 05:11:19.753014 (d2) Bootstrapping...
> > Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
> > Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
> > Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
> > Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
> > Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
> > Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
> > Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
> > Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
> > Nov 18 05:11:19.785135 (d2)  mod_len: 0
> > Nov 18 05:11:19.793047 (d2)flags: 0x0
> > Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
> > Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
> > Nov 18 05:11:19.801150 (d2) MM: Init
> > Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
> > Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
> > Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
> > Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
> > Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
> > Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
> > Nov 18 05:11:19.817099 (d2)   start_pfn: a24
> > Nov 18 05:11:19.817125 (d2) max_pfn: 2
> > Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
> > Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
> > Nov 18 05:11:19.825100 (d2) skipped 1000
> > Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for 
> > b1c000(b1c000)-2000(2000)
> > Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip 5fc70, 
> > regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
> > Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid 
> > memory?).
> > 
> > The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
> > be working fine.
> 
> Hmm. I'll try again to make pvgrub work (more or less).
> 
> Wei, in case you want to try to reproduce the problem: could you
> try to map the eip to function + offset?
> 

I'm working on something else at the moment. I will have a go at this
tomorrow.

Wei.

> 
> Juergen
> 

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Juergen Gross]

On 18/11/15 16:59, Wei Liu wrote:
> On Wed, Nov 18, 2015 at 04:54:34PM +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
 flight 64494 xen-unstable real [real]
 http://logs.test-lab.xenproject.org/osstest/logs/64494/

 Regressions :-(

 Tests which did not succeed and are blocking,
 including tests which could not be run:
>>>
  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR. vs. 
 64035
>>>
>>> Nov 18 05:11:19.753014 (d2) Bootstrapping...
>>> Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
>>> Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
>>> Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
>>> Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
>>> Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
>>> Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
>>> Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
>>> Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
>>> Nov 18 05:11:19.785135 (d2)  mod_len: 0
>>> Nov 18 05:11:19.793047 (d2)flags: 0x0
>>> Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
>>> Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
>>> Nov 18 05:11:19.801150 (d2) MM: Init
>>> Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
>>> Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
>>> Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
>>> Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
>>> Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
>>> Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
>>> Nov 18 05:11:19.817099 (d2)   start_pfn: a24
>>> Nov 18 05:11:19.817125 (d2) max_pfn: 2
>>> Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
>>> Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
>>> Nov 18 05:11:19.825100 (d2) skipped 1000
>>> Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for 
>>> b1c000(b1c000)-2000(2000)
>>> Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip 5fc70, 
>>> regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
>>> Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid 
>>> memory?).
>>>
>>> The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
>>> be working fine.
>>
>> Hmm. I'll try again to make pvgrub work (more or less).
>>
>> Wei, in case you want to try to reproduce the problem: could you
>> try to map the eip to function + offset?
>>
> 
> I'm working on something else at the moment. I will have a go at this
> tomorrow.

Don't hurry. I hope to get it running somehow.


Juergen


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [xen-unstable test] 64494: regressions - FAIL

[Wei Liu]

Hi Juergen

Looks like there is something we missed after all.

On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> flight 64494 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64494/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:

>  test-amd64-amd64-i386-pvgrub 10 guest-start   fail REGR. vs. 
> 64035

Nov 18 05:11:19.753014 (d2) Bootstrapping...
Nov 18 05:11:19.769108 (d2) Xen Minimal OS!
Nov 18 05:11:19.769134 (d2)   start_info: 0xa13000(VA)
Nov 18 05:11:19.769158 (d2) nr_pages: 0x2
Nov 18 05:11:19.777046 (d2)   shared_inf: 0xca1fc000(MA)
Nov 18 05:11:19.777072 (d2)  pt_base: 0xa16000(VA)
Nov 18 05:11:19.785042 (d2) nr_pt_frames: 0xb
Nov 18 05:11:19.785077 (d2) mfn_list: 0x993000(VA)
Nov 18 05:11:19.785108 (d2)mod_start: 0x0(VA)
Nov 18 05:11:19.785135 (d2)  mod_len: 0
Nov 18 05:11:19.793047 (d2)flags: 0x0
Nov 18 05:11:19.793077 (d2) cmd_line: (hd0,0)/boot/grub/menu.lst
Nov 18 05:11:19.793108 (d2)stack: 0x972580-0x992580
Nov 18 05:11:19.801150 (d2) MM: Init
Nov 18 05:11:19.801181 (d2)   _text: 0x0(VA)
Nov 18 05:11:19.801197 (d2)  _etext: 0x7b22d(VA)
Nov 18 05:11:19.809104 (d2)_erodata: 0xa4000(VA)
Nov 18 05:11:19.809123 (d2)  _edata: 0xa81a8(VA)
Nov 18 05:11:19.809138 (d2) stack start: 0x972580(VA)
Nov 18 05:11:19.817062 (d2)_end: 0x992b30(VA)
Nov 18 05:11:19.817099 (d2)   start_pfn: a24
Nov 18 05:11:19.817125 (d2) max_pfn: 2
Nov 18 05:11:19.825037 (d2) Mapping memory range 0x100 - 0x2000
Nov 18 05:11:19.825071 (d2) setting 0x0-0xa4000 readonly
Nov 18 05:11:19.825100 (d2) skipped 1000
Nov 18 05:11:19.833049 (d2) MM: Initialise page allocator for 
b1c000(b1c000)-2000(2000)
Nov 18 05:11:19.833089 (d2) Page fault at linear address c8, eip 5fc70, 
regs 0x98ff28, sp b1c000, our_sp 0x98fefc, code 2
Nov 18 05:11:19.849044 (d2) Page fault in pagetable walk (access to invalid 
memory?).

The pvgrub in used is 32 bit. 64 bit (which I myself tested) seemed to
be working fine.

Wei.

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel