On Wed, 1 Jan 2020, Julien Grall wrote:
> On 31/12/2019 22:48, Roman Shaposhnik wrote:
> > Hi!
>
> Hi,
>
> >
> > Good news: one that type was fixed Xen booted just fine and detected
> > all the available 2G of memory.
>
> Thank you for testing. @Stefano are you going to prepare and submit the p
On 31/12/2019 22:48, Roman Shaposhnik wrote:
Hi!
Hi,
Good news: one that type was fixed Xen booted just fine and detected
all the available 2G of memory.
Thank you for testing. @Stefano are you going to prepare and submit the
patch?
Cheers,
--
Julien Grall
__
Hi Julien,
On Sun, Dec 29, 2019 at 10:01 AM Julien Grall wrote:
>
> Hi,
>
> On 21/12/2019 01:37, Roman Shaposhnik wrote:
> > On Thu, Dec 19, 2019 at 4:01 PM Stefano Stabellini
> > wrote:
> >>
> >> On Thu, 19 Dec 2019, Julien Grall wrote:
> > In fact most of people on Arm are using GRUB rathe
Hi,
On 21/12/2019 01:37, Roman Shaposhnik wrote:
On Thu, Dec 19, 2019 at 4:01 PM Stefano Stabellini
wrote:
On Thu, 19 Dec 2019, Julien Grall wrote:
In fact most of people on Arm are using GRUB rather than EFI directly as
this is more friendly to use.
Regarding the devicetree, Xen and Linux
On Thu, Dec 19, 2019 at 4:01 PM Stefano Stabellini
wrote:
>
> On Thu, 19 Dec 2019, Julien Grall wrote:
> > > > In fact most of people on Arm are using GRUB rather than EFI directly as
> > > > this is more friendly to use.
> > > >
> > > > Regarding the devicetree, Xen and Linux will completely igno
Hi,
On 20/12/2019 00:01, Stefano Stabellini wrote:
On Thu, 19 Dec 2019, Julien Grall wrote:
In fact most of people on Arm are using GRUB rather than EFI directly as
this is more friendly to use.
Regarding the devicetree, Xen and Linux will completely ignore the
memory nodes in Xen if using EFI
On Thu, 19 Dec 2019, Julien Grall wrote:
> > > In fact most of people on Arm are using GRUB rather than EFI directly as
> > > this is more friendly to use.
> > >
> > > Regarding the devicetree, Xen and Linux will completely ignore the
> > > memory nodes in Xen if using EFI. This because the EFI me
Hi Roman,
On 19/12/2019 00:28, Roman Shaposhnik wrote:
On Wed, Dec 18, 2019 at 2:17 PM Julien Grall wrote:
Hi Roman,
On 18/12/2019 17:03, Roman Shaposhnik wrote:
On Wed, Dec 18, 2019 at 3:50 AM Julien Grall wrote:
So -- nothing boots directly by UEFI -- everything goes through GRUB.
Howev
Hi Julien! First of all -- thank you so much for detailed explanations
-- this is very much appreciated.
A few questions still (if you don't mind):
On Wed, Dec 18, 2019 at 2:17 PM Julien Grall wrote:
>
> Hi Roman,
>
> On 18/12/2019 17:03, Roman Shaposhnik wrote:
> > On Wed, Dec 18, 2019 at 3:50
Hi,
On 18/12/2019 17:09, Roman Shaposhnik wrote:
Hi,
On Wed, Dec 18, 2019 at 4:56 AM Julien Grall wrote:
So that is, in fact, my first question -- why is Xen not showing
available memory in xl info?
I am not entirely sure what exact information you want.
The output you dumped above contain
Hi Roman,
On 18/12/2019 17:03, Roman Shaposhnik wrote:
On Wed, Dec 18, 2019 at 3:50 AM Julien Grall wrote:
So -- nothing boots directly by UEFI -- everything goes through GRUB.
However, my understanding is that GRUB will detect devicetree
information provided by UEFI (even though devicetree co
Hi,
On Wed, Dec 18, 2019 at 4:56 AM Julien Grall wrote:
> > So that is, in fact, my first question -- why is Xen not showing
> > available memory in xl info?
>
> I am not entirely sure what exact information you want.
>
> The output you dumped above contain the available memory for the memory
> (
On Wed, Dec 18, 2019 at 3:50 AM Julien Grall wrote:
>
> Hi,
>
> On 18/12/2019 07:36, Roman Shaposhnik wrote:
> > On Tue, Dec 17, 2019 at 6:56 PM Roman Shaposhnik wrote:
> >> Exactly! That's the other surprising bit -- I noticed that too -- its not
> >> like
> >> Xen doesn't see any of the memory
On 18/12/2019 02:56, Roman Shaposhnik wrote:
On Tue, Dec 17, 2019 at 5:51 PM Stefano Stabellini
wrote:
Interestingly enough, Xen booted, and complained about only 192MB
unallocated this time.
So, I dropped the size of Dom0 to 640M and I got it boot and here's
what I'm seeing as
an output of x
Hi,
On 18/12/2019 00:04, Roman Shaposhnik wrote:
memory {
device_type = "memory";
reg = <0x0 0x0 0x0 0x5e0 0x0 0x5f0 0x0 0x1000
0x0 0x5f02000 0x0 0xefd000 0x0 0x6e0 0x0 0x60f000 0x0 0x741
0x0 0x1aaf 0x0 0x21f0 0x0 0x10 0x0 0x
Hi,
On 18/12/2019 07:36, Roman Shaposhnik wrote:
On Tue, Dec 17, 2019 at 6:56 PM Roman Shaposhnik wrote:
Exactly! That's the other surprising bit -- I noticed that too -- its not like
Xen doesn't see any of the memory above 1G -- it just doesn't see enough of it.
So the question is -- what is
On Tue, Dec 17, 2019 at 6:56 PM Roman Shaposhnik wrote:
>
> On Tue, Dec 17, 2019 at 5:51 PM Stefano Stabellini
> wrote:
> >
> > On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> > > On Tue, Dec 17, 2019 at 11:26 AM Stefano Stabellini
> > > wrote:
> > > >
> > > > On Tue, 17 Dec 2019, Roman Shaposhni
On Tue, Dec 17, 2019 at 5:51 PM Stefano Stabellini
wrote:
>
> On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> > On Tue, Dec 17, 2019 at 11:26 AM Stefano Stabellini
> > wrote:
> > >
> > > On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> > > > On Tue, Dec 17, 2019 at 10:30 AM Stefano Stabellini
> > >
On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> On Tue, Dec 17, 2019 at 11:26 AM Stefano Stabellini
> wrote:
> >
> > On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> > > On Tue, Dec 17, 2019 at 10:30 AM Stefano Stabellini
> > > wrote:
> > > >
> > > > On Tue, 17 Dec 2019, Julien Grall wrote:
> > > >
On Tue, Dec 17, 2019 at 11:26 AM Stefano Stabellini
wrote:
>
> On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> > On Tue, Dec 17, 2019 at 10:30 AM Stefano Stabellini
> > wrote:
> > >
> > > On Tue, 17 Dec 2019, Julien Grall wrote:
> > > > Hi,
> > > >
> > > > On 17/12/2019 04:39, Roman Shaposhnik wro
On Tue, 17 Dec 2019, Roman Shaposhnik wrote:
> On Tue, Dec 17, 2019 at 10:30 AM Stefano Stabellini
> wrote:
> >
> > On Tue, 17 Dec 2019, Julien Grall wrote:
> > > Hi,
> > >
> > > On 17/12/2019 04:39, Roman Shaposhnik wrote:
> > > > On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
> > > > wrote:
On Tue, Dec 17, 2019 at 10:30 AM Stefano Stabellini
wrote:
>
> On Tue, 17 Dec 2019, Julien Grall wrote:
> > Hi,
> >
> > On 17/12/2019 04:39, Roman Shaposhnik wrote:
> > > On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
> > > wrote:
> > > > On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> > > > I
Hi Julien,
On Tue, Dec 17, 2019 at 3:30 AM Julien Grall wrote:
>
> Hi,
>
> On 17/12/2019 04:39, Roman Shaposhnik wrote:
> > On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
> > wrote:
> >> On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> >> If I sum all the memory sizes together I get 0x3ddfd000
On Tue, 17 Dec 2019, Julien Grall wrote:
> Hi,
>
> On 17/12/2019 04:39, Roman Shaposhnik wrote:
> > On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
> > wrote:
> > > On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> > > If I sum all the memory sizes together I get 0x3ddfd000 which is 990M.
> > > I
Hi,
On 17/12/2019 04:39, Roman Shaposhnik wrote:
On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
wrote:
On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
If I sum all the memory sizes together I get 0x3ddfd000 which is 990M.
If so, I wonder how you could boot succesfully with dom0_mem=1024M even
On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
wrote:
>
> On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> > Hi!
> >
> > it appears that something has broken in 4.13 RC5 so that
> > I'm now getting the following on ARM (full logs are attached).
> >
> > (XEN) *
On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> Hi!
>
> it appears that something has broken in 4.13 RC5 so that
> I'm now getting the following on ARM (full logs are attached).
>
> (XEN)
> (XEN) Panic on CPU 0:
> (XEN) Failed to allocate requested dom0 mem
Thanks for the report, I'll give it a look!
On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> Hi!
>
> it appears that something has broken in 4.13 RC5 so that
> I'm now getting the following on ARM (full logs are attached).
>
> (XEN)
> (XEN) Panic on CPU 0:
28 matches
Mail list logo
