All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [Xen-users] xl info displays less ram than the total available
       [not found]   ` <20161005125229.ixcvhldn4ra62prn@riseup.net>
@ 2016-10-05 13:02     ` George Dunlap
  2016-10-05 13:06       ` Andrew Cooper
  0 siblings, 1 reply; 16+ messages in thread
From: George Dunlap @ 2016-10-05 13:02 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, Jan Beulich, xen-devel

On 05/10/16 13:52, blallo@riseup.net wrote:
> George Dunlap:
>> On Wed, Oct 5, 2016 at 11:16 AM,  <blallo@riseup.net> wrote:
>>>
>>> Hi all,
>>> I have been wondering if I could manage to make Xen function on my
>>> laptop, using as dom0 my Arch Linux installation. As far as I understood
>>> there is no currently supported package in the AUR nor, obviously, in
>>> the official repos. What to do? Compile it by myself! I went under all
>>> the process, in particular
>>>
>>> % PYTHON="/usr/bin/python2" ./configure --enable-stubdom \
>>>                --enable-systemd --prefix=/usr
>>>
>>> % PYTHON="/usr/bin/python2" NO_WERROR=1 make dist
>>>
>>> % sudo PYTHON="/usr/bin/python2" NO_WERROR=1 make install
>>>
>>> After that I manually added a grub entry to boot into my dom0
>>> chainbooted by Xen.
>>>
>>> And it seemed I succeeded, as far as I manage to boot into my system.
>>> Everything seem to work, except that if I look at the features of my
>>> system
>>>
>>> % sudo xl info
>>>
>>> I get a discouraging indication on the total amount of ram I have on my
>>> system
>>>
>>> total_memory           : 1948
>>> free_memory            : 120
>>>
>>> while the total memory is (as measured from Arch booted without Xen)
>>>
>>> % free -m
>>>            total       used     free     shared  buff/cache  available
>>>    Mem:    15924       8756     2206     737     4961        6100
>>>    Swap:   8191        0        8191
>>>
>>> What to do? I am very new to Xen, how can I debug it?
>>
>> Thanks for your report.  Can you please attach the full output of "xl
>> info", as well as the output of "xl dmesg"?
>>
>> Thanks,
>> -George
> 
> I attach the output of xl info, xl dmesg in dom0 *and* dmesg in a normal
> Arch Linux boot (without Xen).

That's quite strange -- the e820 maps reported by Linux and Xen appear
to be almost completely different:

(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000079cbe000 (usable)
(XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
(XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
(XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
(XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed08000 - 00000000fed09000 (reserved)
(XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 000000043e600000 (reserved)

BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
BIOS-e820: [mem 0x0000000000059000-0x000000000008bfff] usable
BIOS-e820: [mem 0x000000000008c000-0x00000000000bffff] reserved
BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000007b82dfff] usable
BIOS-e820: [mem 0x000000007b82e000-0x000000007ba2ffff] reserved
BIOS-e820: [mem 0x000000007ba30000-0x00000000ba1fcfff] usable
BIOS-e820: [mem 0x00000000ba1fd000-0x00000000ba3fcfff] type 20
BIOS-e820: [mem 0x00000000ba3fd000-0x00000000bcd2efff] reserved
BIOS-e820: [mem 0x00000000bcd2f000-0x00000000bce7efff] ACPI NVS
BIOS-e820: [mem 0x00000000bce7f000-0x00000000bcefefff] ACPI data
BIOS-e820: [mem 0x00000000bceff000-0x00000000bcefffff] usable
BIOS-e820: [mem 0x00000000bcf00000-0x00000000bf9fffff] reserved
BIOS-e820: [mem 0x00000000f80f8000-0x00000000f80f8fff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000043e5fffff] usable

With the key thing being that Xen's version has the range from ~2G-3G
and 4G-17G as 'reserved', while Linux's version has those ranges as
'usable'.

Jan / Andy, any idea what's going on here?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-05 13:02     ` [Xen-users] xl info displays less ram than the total available George Dunlap
@ 2016-10-05 13:06       ` Andrew Cooper
  2016-10-05 13:32         ` blallo
  0 siblings, 1 reply; 16+ messages in thread
From: Andrew Cooper @ 2016-10-05 13:06 UTC (permalink / raw)
  To: George Dunlap, blallo; +Cc: Jan Beulich, xen-devel

On 05/10/16 14:02, George Dunlap wrote:
> On 05/10/16 13:52, blallo@riseup.net wrote:
>> George Dunlap:
>>> On Wed, Oct 5, 2016 at 11:16 AM,  <blallo@riseup.net> wrote:
>>>> Hi all,
>>>> I have been wondering if I could manage to make Xen function on my
>>>> laptop, using as dom0 my Arch Linux installation. As far as I understood
>>>> there is no currently supported package in the AUR nor, obviously, in
>>>> the official repos. What to do? Compile it by myself! I went under all
>>>> the process, in particular
>>>>
>>>> % PYTHON="/usr/bin/python2" ./configure --enable-stubdom \
>>>>                --enable-systemd --prefix=/usr
>>>>
>>>> % PYTHON="/usr/bin/python2" NO_WERROR=1 make dist
>>>>
>>>> % sudo PYTHON="/usr/bin/python2" NO_WERROR=1 make install
>>>>
>>>> After that I manually added a grub entry to boot into my dom0
>>>> chainbooted by Xen.
>>>>
>>>> And it seemed I succeeded, as far as I manage to boot into my system.
>>>> Everything seem to work, except that if I look at the features of my
>>>> system
>>>>
>>>> % sudo xl info
>>>>
>>>> I get a discouraging indication on the total amount of ram I have on my
>>>> system
>>>>
>>>> total_memory           : 1948
>>>> free_memory            : 120
>>>>
>>>> while the total memory is (as measured from Arch booted without Xen)
>>>>
>>>> % free -m
>>>>            total       used     free     shared  buff/cache  available
>>>>    Mem:    15924       8756     2206     737     4961        6100
>>>>    Swap:   8191        0        8191
>>>>
>>>> What to do? I am very new to Xen, how can I debug it?
>>> Thanks for your report.  Can you please attach the full output of "xl
>>> info", as well as the output of "xl dmesg"?
>>>
>>> Thanks,
>>> -George
>> I attach the output of xl info, xl dmesg in dom0 *and* dmesg in a normal
>> Arch Linux boot (without Xen).
> That's quite strange -- the e820 maps reported by Linux and Xen appear
> to be almost completely different:
>
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
> (XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ffc00000 - 000000043e600000 (reserved)
>
> BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
> BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
> BIOS-e820: [mem 0x0000000000059000-0x000000000008bfff] usable
> BIOS-e820: [mem 0x000000000008c000-0x00000000000bffff] reserved
> BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
> BIOS-e820: [mem 0x0000000000100000-0x000000007b82dfff] usable
> BIOS-e820: [mem 0x000000007b82e000-0x000000007ba2ffff] reserved
> BIOS-e820: [mem 0x000000007ba30000-0x00000000ba1fcfff] usable
> BIOS-e820: [mem 0x00000000ba1fd000-0x00000000ba3fcfff] type 20
> BIOS-e820: [mem 0x00000000ba3fd000-0x00000000bcd2efff] reserved
> BIOS-e820: [mem 0x00000000bcd2f000-0x00000000bce7efff] ACPI NVS
> BIOS-e820: [mem 0x00000000bce7f000-0x00000000bcefefff] ACPI data
> BIOS-e820: [mem 0x00000000bceff000-0x00000000bcefffff] usable
> BIOS-e820: [mem 0x00000000bcf00000-0x00000000bf9fffff] reserved
> BIOS-e820: [mem 0x00000000f80f8000-0x00000000f80f8fff] reserved
> BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
> BIOS-e820: [mem 0x0000000100000000-0x000000043e5fffff] usable
>
> With the key thing being that Xen's version has the range from ~2G-3G
> and 4G-17G as 'reserved', while Linux's version has those ranges as
> 'usable'.
>
> Jan / Andy, any idea what's going on here?

Not specifically.  Can you boot with e820-verbose on the Xen command
line, which will provide more information?

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-05 13:06       ` Andrew Cooper
@ 2016-10-05 13:32         ` blallo
  2016-10-05 14:01           ` Jan Beulich
  0 siblings, 1 reply; 16+ messages in thread
From: blallo @ 2016-10-05 13:32 UTC (permalink / raw)
  To: Andrew Cooper; +Cc: George Dunlap, Jan Beulich, xen-devel

[-- Attachment #1: Type: text/plain, Size: 4429 bytes --]

Andrew Cooper:
>On 05/10/16 14:02, George Dunlap wrote:
>> On 05/10/16 13:52, blallo@riseup.net wrote:
>>> George Dunlap:
>>>> On Wed, Oct 5, 2016 at 11:16 AM,  <blallo@riseup.net> wrote:
>>>>> Hi all,
>>>>> I have been wondering if I could manage to make Xen function on my
>>>>> laptop, using as dom0 my Arch Linux installation. As far as I understood
>>>>> there is no currently supported package in the AUR nor, obviously, in
>>>>> the official repos. What to do? Compile it by myself! I went under all
>>>>> the process, in particular
>>>>>
>>>>> % PYTHON="/usr/bin/python2" ./configure --enable-stubdom \
>>>>>                --enable-systemd --prefix=/usr
>>>>>
>>>>> % PYTHON="/usr/bin/python2" NO_WERROR=1 make dist
>>>>>
>>>>> % sudo PYTHON="/usr/bin/python2" NO_WERROR=1 make install
>>>>>
>>>>> After that I manually added a grub entry to boot into my dom0
>>>>> chainbooted by Xen.
>>>>>
>>>>> And it seemed I succeeded, as far as I manage to boot into my system.
>>>>> Everything seem to work, except that if I look at the features of my
>>>>> system
>>>>>
>>>>> % sudo xl info
>>>>>
>>>>> I get a discouraging indication on the total amount of ram I have on my
>>>>> system
>>>>>
>>>>> total_memory           : 1948
>>>>> free_memory            : 120
>>>>>
>>>>> while the total memory is (as measured from Arch booted without Xen)
>>>>>
>>>>> % free -m
>>>>>            total       used     free     shared  buff/cache  available
>>>>>    Mem:    15924       8756     2206     737     4961        6100
>>>>>    Swap:   8191        0        8191
>>>>>
>>>>> What to do? I am very new to Xen, how can I debug it?
>>>> Thanks for your report.  Can you please attach the full output of "xl
>>>> info", as well as the output of "xl dmesg"?
>>>>
>>>> Thanks,
>>>> -George
>>> I attach the output of xl info, xl dmesg in dom0 *and* dmesg in a normal
>>> Arch Linux boot (without Xen).
>> That's quite strange -- the e820 maps reported by Linux and Xen appear
>> to be almost completely different:
>>
>> (XEN) Xen-e820 RAM map:
>> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
>> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
>> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
>> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
>> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
>> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
>> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
>> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
>> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
>> (XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
>> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
>> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>> (XEN)  00000000ffc00000 - 000000043e600000 (reserved)
>>
>> BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
>> BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
>> BIOS-e820: [mem 0x0000000000059000-0x000000000008bfff] usable
>> BIOS-e820: [mem 0x000000000008c000-0x00000000000bffff] reserved
>> BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
>> BIOS-e820: [mem 0x0000000000100000-0x000000007b82dfff] usable
>> BIOS-e820: [mem 0x000000007b82e000-0x000000007ba2ffff] reserved
>> BIOS-e820: [mem 0x000000007ba30000-0x00000000ba1fcfff] usable
>> BIOS-e820: [mem 0x00000000ba1fd000-0x00000000ba3fcfff] type 20
>> BIOS-e820: [mem 0x00000000ba3fd000-0x00000000bcd2efff] reserved
>> BIOS-e820: [mem 0x00000000bcd2f000-0x00000000bce7efff] ACPI NVS
>> BIOS-e820: [mem 0x00000000bce7f000-0x00000000bcefefff] ACPI data
>> BIOS-e820: [mem 0x00000000bceff000-0x00000000bcefffff] usable
>> BIOS-e820: [mem 0x00000000bcf00000-0x00000000bf9fffff] reserved
>> BIOS-e820: [mem 0x00000000f80f8000-0x00000000f80f8fff] reserved
>> BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
>> BIOS-e820: [mem 0x0000000100000000-0x000000043e5fffff] usable
>>
>> With the key thing being that Xen's version has the range from ~2G-3G
>> and 4G-17G as 'reserved', while Linux's version has those ranges as
>> 'usable'.
>>
>> Jan / Andy, any idea what's going on here?
>
>Not specifically.  Can you boot with e820-verbose on the Xen command
>line, which will provide more information?
>

Here it comes xl dmesg with Xen booted with e820-verbose=true

Thanks

--
Leonardo

[-- Attachment #2: xl.dmesg.2.log --]
[-- Type: text/plain, Size: 6968 bytes --]

 __  __            _  _   _____ ___  
 \ \/ /___ _ __   | || | |___  / _ \ 
  \  // _ \ '_ \  | || |_   / / | | |
  /  \  __/ | | | |__   _| / /| |_| |
 /_/\_\___|_| |_|    |_|(_)_/(_)___/ 
                                     
(XEN) Xen version 4.7.0 (root@) (gcc (GCC) 6.2.1 20160830) debug=n Thu Sep 29 15:21:36 CEST 2016
(XEN) Latest ChangeSet: 
(XEN) Bootloader: GRUB 2.02~beta3
(XEN) Command line: e820-verbose=true
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 0 EDD information structures
(XEN) Initial Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000079cbe000 (usable)
(XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
(XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
(XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
(XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed08000 - 00000000fed09000 (reserved)
(XEN)  00000000fed10000 - 00000000fed18000 (reserved)
(XEN)  00000000fed18000 - 00000000fed19000 (reserved)
(XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000043e600000 (reserved)
(XEN) Checking MTRR ranges...
(XEN)  MTRR cap: d0a type: c06
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000079cbe000 (usable)
(XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
(XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
(XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
(XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed08000 - 00000000fed09000 (reserved)
(XEN)  00000000fed10000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 000000043e600000 (reserved)
(XEN) System RAM: 1948MB (1995120kB)
(XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO)
(XEN) ACPI: XSDT BCEFE170, 00E4 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: FACP BCEF8000, 010C (r5 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: DSDT BCEE1000, 119F3 (r1 LENOVO TP-GM        2040 INTL 20120711)
(XEN) ACPI: FACS BCE4A000, 0040
(XEN) ACPI: SLIC BCEFD000, 0176 (r1 LENOVO TP-GM        2040 PTEC        1)
(XEN) ACPI: DBGP BCEFB000, 0034 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: ECDT BCEFA000, 0052 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: HPET BCEF7000, 0038 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: APIC BCEF6000, 0098 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: MCFG BCEF5000, 003C (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: SSDT BCEF4000, 0033 (r1 LENOVO TP-SSDT1      100 INTL 20120711)
(XEN) ACPI: SSDT BCEF3000, 044F (r1 LENOVO TP-SSDT2      200 INTL 20120711)
(XEN) ACPI: SSDT BCEE0000, 0B78 (r1 LENOVO SataAhci     1000 INTL 20120711)
(XEN) ACPI: SSDT BCEDF000, 07D3 (r1 LENOVO  Cpu0Ist     3000 INTL 20120711)
(XEN) ACPI: SSDT BCEDE000, 0AD8 (r1 LENOVO    CpuPm     3000 INTL 20120711)
(XEN) ACPI: SSDT BCEDC000, 1215 (r1 LENOVO  SaSsdt      3000 INTL 20120711)
(XEN) ACPI: SSDT BCEDB000, 0379 (r1 LENOVO CppcTabl     1000 INTL 20120711)
(XEN) ACPI: PCCT BCEDA000, 006E (r5 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: SSDT BCED9000, 0AC4 (r1 LENOVO Cpc_Tabl     1000 INTL 20120711)
(XEN) ACPI: TCPA BCED8000, 0032 (r2    PTL   LENOVO  6040000 LNVO        1)
(XEN) ACPI: UEFI BCED7000, 0042 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: MSDM BCDB2000, 0055 (r3 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: ASF! BCEFC000, 00A5 (r32 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: BATB BCED6000, 0046 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: FPDT BCED5000, 0064 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: UEFI BCED4000, 02E2 (r1 LENOVO TP-GM        2040 PTEC        2)
(XEN) ACPI: SSDT BCED3000, 047F (r1 LENOVO IsctTabl     1000 INTL 20120711)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - bce4a000/0000000000000000, using 32
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2394.474 MHz processor.
(XEN) Initing memory sharing.
(XEN) I/O virtualisation disabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN)  - VM Functions
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 8 CPUs
(XEN) Dom0 has maximum 792 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1b7e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000072000000->0000000074000000 (443310 pages to be allocated)
(XEN)  Init. ramdisk: 00000000770aa000->00000000797ffe00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff81b7e000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008000385820
(XEN)  Start info:    ffffffff81b7e000->ffffffff81b7e4b4
(XEN)  Page tables:   ffffffff81b7f000->ffffffff81b92000
(XEN)  Boot stack:    ffffffff81b92000->ffffffff81b93000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82000000
(XEN)  ENTRY ADDRESS: ffffffff8190e180
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) ....done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 308kB init memory.

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-05 13:32         ` blallo
@ 2016-10-05 14:01           ` Jan Beulich
  2016-10-06 10:55             ` George Dunlap
  0 siblings, 1 reply; 16+ messages in thread
From: Jan Beulich @ 2016-10-05 14:01 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, George Dunlap, xen-devel

>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
> Here it comes xl dmesg with Xen booted with e820-verbose=true

I have to admit that the only way I can see

(XEN) Initial Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000079cbe000 (usable)
(XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
(XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
(XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
(XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed08000 - 00000000fed09000 (reserved)
(XEN)  00000000fed10000 - 00000000fed18000 (reserved)
(XEN)  00000000fed18000 - 00000000fed19000 (reserved)
(XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000043e600000 (reserved)

having all those reserved regions above 2Gb is for the boot
loader to behave oddly. Since Linux and Xen use different paths
in the boot loader, one can't really draw conclusions from Linux
getting to see a better memory map.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-05 14:01           ` Jan Beulich
@ 2016-10-06 10:55             ` George Dunlap
  2016-10-06 10:59               ` Blallo
  0 siblings, 1 reply; 16+ messages in thread
From: George Dunlap @ 2016-10-06 10:55 UTC (permalink / raw)
  To: Jan Beulich; +Cc: Andrew Cooper, blallo, xen-devel

On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
>> Here it comes xl dmesg with Xen booted with e820-verbose=true
>
> I have to admit that the only way I can see
>
> (XEN) Initial Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 000000043e600000 (reserved)
>
> having all those reserved regions above 2Gb is for the boot
> loader to behave oddly. Since Linux and Xen use different paths
> in the boot loader, one can't really draw conclusions from Linux
> getting to see a better memory map.

Do you have any suggestions for how to check whether it really is the
bootloader?

Leonardo, are you using grub2 or a different bootloader?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 10:55             ` George Dunlap
@ 2016-10-06 10:59               ` Blallo
  2016-10-06 12:06                 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 16+ messages in thread
From: Blallo @ 2016-10-06 10:59 UTC (permalink / raw)
  To: George Dunlap, Jan Beulich; +Cc: Andrew Cooper, xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]

I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.


On 6 October 2016 12:55:16 CEST, George Dunlap <george.dunlap@citrix.com> wrote:
>On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
>>> Here it comes xl dmesg with Xen booted with e820-verbose=true
>>
>> I have to admit that the only way I can see
>>
>> (XEN) Initial Xen-e820 RAM map:
>> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
>> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
>> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
>> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
>> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
>> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
>> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
>> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
>> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
>> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
>> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
>> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
>> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
>> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
>> (XEN)  0000000100000000 - 000000043e600000 (reserved)
>>
>> having all those reserved regions above 2Gb is for the boot
>> loader to behave oddly. Since Linux and Xen use different paths
>> in the boot loader, one can't really draw conclusions from Linux
>> getting to see a better memory map.
>
>Do you have any suggestions for how to check whether it really is the
>bootloader?
>
>Leonardo, are you using grub2 or a different bootloader?
>
> -George

-- 
Leonardo

[-- Attachment #1.2: Type: text/html, Size: 2826 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 10:59               ` Blallo
@ 2016-10-06 12:06                 ` Konrad Rzeszutek Wilk
  2016-10-06 12:39                   ` blallo
                                     ` (2 more replies)
  0 siblings, 3 replies; 16+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-10-06 12:06 UTC (permalink / raw)
  To: Blallo, daniel.kiper; +Cc: Andrew Cooper, George Dunlap, Jan Beulich, xen-devel

On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
> I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.

Cc-ing Daniel (who is now an GRUB2 maintainer).

Is this by chance an EFI box?And you are booting using EFI GRUB2?
> 
> 
> On 6 October 2016 12:55:16 CEST, George Dunlap <george.dunlap@citrix.com> wrote:
> >On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
> >>> Here it comes xl dmesg with Xen booted with e820-verbose=true
> >>
> >> I have to admit that the only way I can see
> >>
> >> (XEN) Initial Xen-e820 RAM map:
> >> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> >> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> >> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> >> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
> >> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
> >> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
> >> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
> >> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
> >> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
> >> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> >> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
> >> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
> >> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
> >> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
> >> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
> >> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> >> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
> >> (XEN)  0000000100000000 - 000000043e600000 (reserved)
> >>
> >> having all those reserved regions above 2Gb is for the boot
> >> loader to behave oddly. Since Linux and Xen use different paths
> >> in the boot loader, one can't really draw conclusions from Linux
> >> getting to see a better memory map.
> >
> >Do you have any suggestions for how to check whether it really is the
> >bootloader?
> >
> >Leonardo, are you using grub2 or a different bootloader?
> >
> > -George
> 
> -- 
> Leonardo

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 12:06                 ` Konrad Rzeszutek Wilk
@ 2016-10-06 12:39                   ` blallo
  2016-10-06 13:00                     ` Jan Beulich
  2016-10-06 12:56                   ` blallo
       [not found]                   ` <20161006125650.ww7lq7gpn7ovvqrr@supernova>
  2 siblings, 1 reply; 16+ messages in thread
From: blallo @ 2016-10-06 12:39 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: Andrew Cooper, daniel.kiper, George Dunlap, Jan Beulich, xen-devel

[-- Attachment #1: Type: text/plain, Size: 2668 bytes --]

Konrad Rzeszutek Wilk:
>On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
>> I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.
>
>Cc-ing Daniel (who is now an GRUB2 maintainer).
>
>Is this by chance an EFI box?And you are booting using EFI GRUB2?
>>
>>
>> On 6 October 2016 12:55:16 CEST, George Dunlap <george.dunlap@citrix.com> wrote:
>> >On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
>> >>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
>> >>> Here it comes xl dmesg with Xen booted with e820-verbose=true
>> >>
>> >> I have to admit that the only way I can see
>> >>
>> >> (XEN) Initial Xen-e820 RAM map:
>> >> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>> >> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
>> >> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
>> >> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
>> >> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
>> >> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
>> >> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
>> >> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
>> >> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
>> >> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>> >> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
>> >> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
>> >> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
>> >> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
>> >> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
>> >> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>> >> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
>> >> (XEN)  0000000100000000 - 000000043e600000 (reserved)
>> >>
>> >> having all those reserved regions above 2Gb is for the boot
>> >> loader to behave oddly. Since Linux and Xen use different paths
>> >> in the boot loader, one can't really draw conclusions from Linux
>> >> getting to see a better memory map.
>> >
>> >Do you have any suggestions for how to check whether it really is the
>> >bootloader?
>> >
>> >Leonardo, are you using grub2 or a different bootloader?
>> >
>> > -George

Hi everybody,
I'm amazed at and grateful for your interest in my issue. It is an efi
system and the grub2 version is:

% grub-install -V
grub-install (GRUB) 2.02~beta3

The menu entry is obtained by the following script in /etc/grub.d/

/etc/grub.d/43_custom_xen

It's attached (largely mutuated by the one I use to boot the Arch Kernel
without Xen)

I do apologize for the top quoting in the preceding mail: I was on my
mobile.


Greetings

--
Leonardo

[-- Attachment #2: 43_custom_xen --]
[-- Type: text/plain, Size: 898 bytes --]

#! /bin/sh

set -e

cat <<EOF
menuentry 'Xen (dom0 Arch Linux)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-0acddf1f-7cd2-4cd2-a89f-8f8b00707f71' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt5'
	if [ x\$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  6ead6645-7675-49bd-b0f5-ed9738843a9d
	else
	  search --no-floppy --fs-uuid --set=root 6ead6645-7675-49bd-b0f5-ed9738843a9d
	fi
	multiboot /xen.gz
	echo	'Loading Xen with linux-grsec...'
	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
	module  /initramfs-linux.img
}
EOF

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 12:06                 ` Konrad Rzeszutek Wilk
  2016-10-06 12:39                   ` blallo
@ 2016-10-06 12:56                   ` blallo
       [not found]                   ` <20161006125650.ww7lq7gpn7ovvqrr@supernova>
  2 siblings, 0 replies; 16+ messages in thread
From: blallo @ 2016-10-06 12:56 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: Andrew Cooper, daniel.kiper, George Dunlap, Jan Beulich, xen-devel

Konrad Rzeszutek Wilk:
>On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
>> I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.
>
>Cc-ing Daniel (who is now an GRUB2 maintainer).
>
>Is this by chance an EFI box?And you are booting using EFI GRUB2?
>>
>>
>> On 6 October 2016 12:55:16 CEST, George Dunlap <george.dunlap@citrix.com> wrote:
>> >On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
>> >>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
>> >>> Here it comes xl dmesg with Xen booted with e820-verbose=true
>> >>
>> >> I have to admit that the only way I can see
>> >>
>> >> (XEN) Initial Xen-e820 RAM map:
>> >> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>> >> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
>> >> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
>> >> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
>> >> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
>> >> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
>> >> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
>> >> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
>> >> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
>> >> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>> >> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
>> >> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
>> >> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
>> >> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
>> >> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
>> >> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>> >> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
>> >> (XEN)  0000000100000000 - 000000043e600000 (reserved)
>> >>
>> >> having all those reserved regions above 2Gb is for the boot
>> >> loader to behave oddly. Since Linux and Xen use different paths
>> >> in the boot loader, one can't really draw conclusions from Linux
>> >> getting to see a better memory map.
>> >
>> >Do you have any suggestions for how to check whether it really is the
>> >bootloader?
>> >
>> >Leonardo, are you using grub2 or a different bootloader?


Hi everybody,
first of all, thanks for all the effort you're putting in this issue of
mine. Secondly, I apologize for the top quoting of my last email: I was
on my mobile.

Konrad, yes, I boot using efi grub2. The version is

% grub-install -V
grub-install (GRUB) 2.02~beta3

as obtained from the Arch repos.

I attach the custom /etc/grub.d/ script I use to generate the grub menu
entry for Xen booting. It is largely taken by the original one I use to
boot into the ordinary Arch kernel.


Greetings

--
Leonardo

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
       [not found]                   ` <20161006125650.ww7lq7gpn7ovvqrr@supernova>
@ 2016-10-06 12:58                     ` blallo
  2016-10-06 13:16                       ` Daniel Kiper
       [not found]                     ` <20161006125857.7kavmrfe27yudsud@supernova>
  1 sibling, 1 reply; 16+ messages in thread
From: blallo @ 2016-10-06 12:58 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: Andrew Cooper, daniel.kiper, George Dunlap, Jan Beulich, xen-devel

[-- Attachment #1: Type: text/plain, Size: 2801 bytes --]

blallo@riseup.net:
>Konrad Rzeszutek Wilk:
>>On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
>>>I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.
>>
>>Cc-ing Daniel (who is now an GRUB2 maintainer).
>>
>>Is this by chance an EFI box?And you are booting using EFI GRUB2?
>>>
>>>
>>>On 6 October 2016 12:55:16 CEST, George Dunlap <george.dunlap@citrix.com> wrote:
>>>>On Wed, Oct 5, 2016 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>>>>> On 05.10.16 at 15:32, <blallo@riseup.net> wrote:
>>>>>> Here it comes xl dmesg with Xen booted with e820-verbose=true
>>>>>
>>>>> I have to admit that the only way I can see
>>>>>
>>>>> (XEN) Initial Xen-e820 RAM map:
>>>>> (XEN)  0000000000000000 - 000000000009ec00 (usable)
>>>>> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
>>>>> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
>>>>> (XEN)  0000000000100000 - 0000000079cbe000 (usable)
>>>>> (XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
>>>>> (XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
>>>>> (XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
>>>>> (XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
>>>>> (XEN)  00000000f8000000 - 00000000fc000000 (reserved)
>>>>> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
>>>>> (XEN)  00000000fed08000 - 00000000fed09000 (reserved)
>>>>> (XEN)  00000000fed10000 - 00000000fed18000 (reserved)
>>>>> (XEN)  00000000fed18000 - 00000000fed19000 (reserved)
>>>>> (XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
>>>>> (XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
>>>>> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
>>>>> (XEN)  00000000ffc00000 - 0000000100000000 (reserved)
>>>>> (XEN)  0000000100000000 - 000000043e600000 (reserved)
>>>>>
>>>>> having all those reserved regions above 2Gb is for the boot
>>>>> loader to behave oddly. Since Linux and Xen use different paths
>>>>> in the boot loader, one can't really draw conclusions from Linux
>>>>> getting to see a better memory map.
>>>>
>>>>Do you have any suggestions for how to check whether it really is the
>>>>bootloader?
>>>>
>>>>Leonardo, are you using grub2 or a different bootloader?
>
>
>Hi everybody,
>first of all, thanks for all the effort you're putting in this issue of
>mine. Secondly, I apologize for the top quoting of my last email: I was
>on my mobile.
>
>Konrad, yes, I boot using efi grub2. The version is
>
>% grub-install -V
>grub-install (GRUB) 2.02~beta3
>
>as obtained from the Arch repos.
>
>I attach the custom /etc/grub.d/ script I use to generate the grub menu
>entry for Xen booting. It is largely taken by the original one I use to
>boot into the ordinary Arch kernel.
>
>
Sorry, forgot to attach the file :)

Here it is.

--
Leonardo





[-- Attachment #2: 43_custom_xen --]
[-- Type: text/plain, Size: 898 bytes --]

#! /bin/sh

set -e

cat <<EOF
menuentry 'Xen (dom0 Arch Linux)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-0acddf1f-7cd2-4cd2-a89f-8f8b00707f71' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt5'
	if [ x\$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  6ead6645-7675-49bd-b0f5-ed9738843a9d
	else
	  search --no-floppy --fs-uuid --set=root 6ead6645-7675-49bd-b0f5-ed9738843a9d
	fi
	multiboot /xen.gz
	echo	'Loading Xen with linux-grsec...'
	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
	module  /initramfs-linux.img
}
EOF

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 12:39                   ` blallo
@ 2016-10-06 13:00                     ` Jan Beulich
  0 siblings, 0 replies; 16+ messages in thread
From: Jan Beulich @ 2016-10-06 13:00 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, daniel.kiper, George Dunlap, xen-devel

>>> On 06.10.16 at 14:39, <blallo@riseup.net> wrote:
> I'm amazed at and grateful for your interest in my issue. It is an efi
> system 

In this case please retry using xen.efi instead of indirecting via
grub.efi. See http://xenbits.xen.org/docs/unstable/misc/efi.html
for what you may need to set up. If that works we can be pretty
certain that the (beta) version of grub2 you use fools up xen.gz
at least as far as the memory map goes.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
       [not found]                     ` <20161006125857.7kavmrfe27yudsud@supernova>
@ 2016-10-06 13:03                       ` blallo
  0 siblings, 0 replies; 16+ messages in thread
From: blallo @ 2016-10-06 13:03 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk
  Cc: Andrew Cooper, daniel.kiper, George Dunlap, Jan Beulich, xen-devel

blallo@riseup.net:
>blallo@riseup.net:
>>Konrad Rzeszutek Wilk:
>>>On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
>>>>I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.
>>>
>>>Cc-ing Daniel (who is now an GRUB2 maintainer).
>>>
>>>Is this by chance an EFI box?And you are booting using EFI GRUB2?
>>Hi everybody,
>>first of all, thanks for all the effort you're putting in this issue of
>>mine. Secondly, I apologize for the top quoting of my last email: I was
>>on my mobile.
>>
>>Konrad, yes, I boot using efi grub2. The version is
>>
>>% grub-install -V
>>grub-install (GRUB) 2.02~beta3
>>
>>as obtained from the Arch repos.
>>
>>I attach the custom /etc/grub.d/ script I use to generate the grub menu
>>entry for Xen booting. It is largely taken by the original one I use to
>>boot into the ordinary Arch kernel.
>>
>>
>Sorry, forgot to attach the file :)
>
>Here it is.
>

Worth to mention that, despite the "echo" in the menu entry seem to
suggest that I'm chainbooting a grsec-patched kernel and initrd, they
are not. They are indeed the ordinary Arch 4.7 kernel and initrd.
I tried to boot the grsec versios, but Xen failed.
Anyway, this is the subject of a new thread :)

Sorry for the number of emails :)


Greetings

--
Leonardo

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-06 12:58                     ` blallo
@ 2016-10-06 13:16                       ` Daniel Kiper
       [not found]                         ` <53339FBD-ABBC-4047-A787-74F97867015A@riseup.net>
  0 siblings, 1 reply; 16+ messages in thread
From: Daniel Kiper @ 2016-10-06 13:16 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, xen-devel, George Dunlap, Jan Beulich

On Thu, Oct 06, 2016 at 02:58:57PM +0200, blallo@riseup.net wrote:

[...]

> 	multiboot /xen.gz
> 	echo	'Loading Xen with linux-grsec...'
> 	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
> 	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
> 	module  /initramfs-linux.img

Forget about multiboot on EFI platforms. It does not work.
At least with Xen. Please load xen.efi binary directly
(as Jan suggested) or if you wish GRUB2 then you must use
relevant patches for Xen and GRUB2. Check this threads for
more details:
  - http://lists.gnu.org/archive/html/grub-devel/2016-03/msg00299.html
  - https://lists.xen.org/archives/html/xen-devel/2016-09/msg03330.html

Daniel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
       [not found]                         ` <53339FBD-ABBC-4047-A787-74F97867015A@riseup.net>
@ 2016-10-26  8:30                           ` blallo
  2016-10-26 13:26                             ` Konrad Rzeszutek Wilk
  2016-10-27  8:24                             ` Daniel Kiper
  0 siblings, 2 replies; 16+ messages in thread
From: blallo @ 2016-10-26  8:30 UTC (permalink / raw)
  To: Daniel Kiper; +Cc: Andrew Cooper, xen-devel, George Dunlap, Jan Beulich

Blallo:
>
>
>
>-------- Original Message --------
>From: Daniel Kiper <daniel.kiper@oracle.com>
>Sent: 6 October 2016 15:16:18 CEST
>To: blallo@riseup.net
>Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <george.dunlap@citrix.com>, Jan Beulich <JBeulich@suse.com>, Andrew Cooper <andrew.cooper3@citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
>Subject: Re: [Xen-devel] [Xen-users] xl info displays less ram than the total available
>
>On Thu, Oct 06, 2016 at 02:58:57PM +0200, blallo@riseup.net wrote:
>
>[...]
>
>> 	multiboot /xen.gz
>> 	echo	'Loading Xen with linux-grsec...'
>> 	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
>> 	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
>> 	module  /initramfs-linux.img
>
>Forget about multiboot on EFI platforms. It does not work.
>At least with Xen. Please load xen.efi binary directly
>(as Jan suggested) or if you wish GRUB2 then you must use
>relevant patches for Xen and GRUB2. Check this threads for
>more details:
>  - http://lists.gnu.org/archive/html/grub-devel/2016-03/msg00299.html
>  - https://lists.xen.org/archives/html/xen-devel/2016-09/msg03330.html
>
>Daniel
>
>

Ok, I've been stuck at this point. I am not able, just following the two
strategies suggested in the wiki [*] to obtain a working efi image of xen. If I
understood well, the cross toolchain is a compiler/linker that outputs PE efi
images, so I tried in three different ways:

1. As suggested here [1] I recompiled binutils with x86_64-pep support
and did a make && configure. The build process exited with errors [2].
Nevertheless I got an efi image in dist/install/usr/lib64/efi/

% ls dist/install/usr/lib64/efi/

xen-4.8.0-rc.efi
xen-4.8.efi -> xen-4.8.0-rc.efi
xen-4.efi -> xen-4.8.0-rc.efi
xen.efi -> xen-4.8.0-rc.efi

Note: I set EFI_VENDOR=archlinux and mkdir'd
dist/install/boot/efi/efi/archlinux

I will explain later as I tried to boot these images.

2. I installed mingw from the Arch Linux repos. Then configure && I set

CROSSCOMPILE=x86_64-w64-mingw32- make world -j8

at compile time. But again no xen.efi image in dist/install/ and a non
bootable dist/install/usr/lib64/efi/. After the build I get [3].

3. At last I manually implemented [4] the Fedora patch [5] (because I'm trying to
compile 4.8.0-rc3 and that patch is for another version, don't know which).
Again, same result as before: no efi image in dist/install and those in
dist/install/usr/lib64/efi/ are not bootable.

I switched to systemd-boot to chainload the xen.efi image. I
successfully boot my Arch Linux system, therefore i assume that this
bootloader works. I have (hopefully) properly configured [6] a xen.cfg file
in the same path as the xen.efi images obtained before.
I can't boot yet.
Trying to bypass the bootloader I created an efi boot entry with
efibootmgr and, via the laptop firmware interface, I tried to boot
directly in xen.
Again no results.

Is there anybody patient enough to explain to me how to proceed?

Greetings :)

--
Leonardo

[*] https://wiki.xen.org/wiki/Xen_EFI#Compiling_Xen_as_EFI
[1] https://bbs.archlinux.org/viewtopic.php?id=174226
[2] http://pastebin.com/bEVvX8w6
[3] http://pastebin.com/cfZLbeC3
[4] http://pastebin.com/vDVqn9it
[5] http://pkgs.fedoraproject.org/cgit/rpms/xen.git/tree/xen.fedora.efi.build.patch
[6] http://pastebin.com/FPg6DcPa

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-26  8:30                           ` blallo
@ 2016-10-26 13:26                             ` Konrad Rzeszutek Wilk
  2016-10-27  8:24                             ` Daniel Kiper
  1 sibling, 0 replies; 16+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-10-26 13:26 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, Daniel Kiper, George Dunlap, Jan Beulich, xen-devel

On Wed, Oct 26, 2016 at 10:30:18AM +0200, blallo@riseup.net wrote:
> Blallo:
> > 
> > 
> > 
> > -------- Original Message --------
> > From: Daniel Kiper <daniel.kiper@oracle.com>
> > Sent: 6 October 2016 15:16:18 CEST
> > To: blallo@riseup.net
> > Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <george.dunlap@citrix.com>, Jan Beulich <JBeulich@suse.com>, Andrew Cooper <andrew.cooper3@citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
> > Subject: Re: [Xen-devel] [Xen-users] xl info displays less ram than the total available
> > 
> > On Thu, Oct 06, 2016 at 02:58:57PM +0200, blallo@riseup.net wrote:
> > 
> > [...]
> > 
> > > 	multiboot /xen.gz
> > > 	echo	'Loading Xen with linux-grsec...'
> > > 	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
> > > 	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
> > > 	module  /initramfs-linux.img
> > 
> > Forget about multiboot on EFI platforms. It does not work.
> > At least with Xen. Please load xen.efi binary directly
> > (as Jan suggested) or if you wish GRUB2 then you must use
> > relevant patches for Xen and GRUB2. Check this threads for
> > more details:
> >  - http://lists.gnu.org/archive/html/grub-devel/2016-03/msg00299.html
> >  - https://lists.xen.org/archives/html/xen-devel/2016-09/msg03330.html
> > 
> > Daniel
> > 
> > 
> 
> Ok, I've been stuck at this point. I am not able, just following the two
> strategies suggested in the wiki [*] to obtain a working efi image of xen. If I
> understood well, the cross toolchain is a compiler/linker that outputs PE efi
> images, so I tried in three different ways:
> 
> 1. As suggested here [1] I recompiled binutils with x86_64-pep support
> and did a make && configure. The build process exited with errors [2].
> Nevertheless I got an efi image in dist/install/usr/lib64/efi/
> 
> % ls dist/install/usr/lib64/efi/
> 
> xen-4.8.0-rc.efi
> xen-4.8.efi -> xen-4.8.0-rc.efi
> xen-4.efi -> xen-4.8.0-rc.efi
> xen.efi -> xen-4.8.0-rc.efi
> 
> Note: I set EFI_VENDOR=archlinux and mkdir'd
> dist/install/boot/efi/efi/archlinux
> 
> I will explain later as I tried to boot these images.
> 
> 2. I installed mingw from the Arch Linux repos. Then configure && I set
> 
> CROSSCOMPILE=x86_64-w64-mingw32- make world -j8

Never used that.
> 
> at compile time. But again no xen.efi image in dist/install/ and a non
> bootable dist/install/usr/lib64/efi/. After the build I get [3].
> 
> 3. At last I manually implemented [4] the Fedora patch [5] (because I'm trying to
> compile 4.8.0-rc3 and that patch is for another version, don't know which).

Yeah that one needs a bit of tweaking.
> Again, same result as before: no efi image in dist/install and those in
> dist/install/usr/lib64/efi/ are not bootable.

You can also look at this:

https://bugzilla.redhat.com/show_bug.cgi?id=1376870

and recompile binutils with the patch.
> 
> I switched to systemd-boot to chainload the xen.efi image. I
> successfully boot my Arch Linux system, therefore i assume that this
> bootloader works. I have (hopefully) properly configured [6] a xen.cfg file
> in the same path as the xen.efi images obtained before.
> I can't boot yet.
> Trying to bypass the bootloader I created an efi boot entry with
> efibootmgr and, via the laptop firmware interface, I tried to boot
> directly in xen.
> Again no results.
> 
> Is there anybody patient enough to explain to me how to proceed?
> 
> Greetings :)
> 
> --
> Leonardo
> 
> [*] https://wiki.xen.org/wiki/Xen_EFI#Compiling_Xen_as_EFI
> [1] https://bbs.archlinux.org/viewtopic.php?id=174226
> [2] http://pastebin.com/bEVvX8w6
> [3] http://pastebin.com/cfZLbeC3
> [4] http://pastebin.com/vDVqn9it
> [5] http://pkgs.fedoraproject.org/cgit/rpms/xen.git/tree/xen.fedora.efi.build.patch
> [6] http://pastebin.com/FPg6DcPa

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: [Xen-users] xl info displays less ram than the total available
  2016-10-26  8:30                           ` blallo
  2016-10-26 13:26                             ` Konrad Rzeszutek Wilk
@ 2016-10-27  8:24                             ` Daniel Kiper
  1 sibling, 0 replies; 16+ messages in thread
From: Daniel Kiper @ 2016-10-27  8:24 UTC (permalink / raw)
  To: blallo; +Cc: Andrew Cooper, xen-devel, George Dunlap, Jan Beulich

On Wed, Oct 26, 2016 at 10:30:18AM +0200, blallo@riseup.net wrote:
> Blallo:
> >-------- Original Message --------
> >From: Daniel Kiper <daniel.kiper@oracle.com>
> >Sent: 6 October 2016 15:16:18 CEST
> >To: blallo@riseup.net
> >Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, George Dunlap <george.dunlap@citrix.com>, Jan Beulich <JBeulich@suse.com>, Andrew Cooper <andrew.cooper3@citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
> >Subject: Re: [Xen-devel] [Xen-users] xl info displays less ram than the total available
> >
> >On Thu, Oct 06, 2016 at 02:58:57PM +0200, blallo@riseup.net wrote:
> >
> >[...]
> >
> >>	multiboot /xen.gz
> >>	echo	'Loading Xen with linux-grsec...'
> >>	module	/vmlinuz-linux root=/dev/mapper/leonovo-rootvol rw  cryptdevice=UUID=02bbde36-5fda-478f-a54f-b6f495e24961:leonovo root=/dev/mapper/leonovo-rootvol
> >>	echo	'Loading initial ramdisk to launch dom0 (linux-grsec)...'
> >>	module  /initramfs-linux.img
> >
> >Forget about multiboot on EFI platforms. It does not work.
> >At least with Xen. Please load xen.efi binary directly
> >(as Jan suggested) or if you wish GRUB2 then you must use
> >relevant patches for Xen and GRUB2. Check this threads for
> >more details:
> > - http://lists.gnu.org/archive/html/grub-devel/2016-03/msg00299.html
> > - https://lists.xen.org/archives/html/xen-devel/2016-09/msg03330.html
> >
> >Daniel
>
> Ok, I've been stuck at this point. I am not able, just following the two
> strategies suggested in the wiki [*] to obtain a working efi image of xen. If I
> understood well, the cross toolchain is a compiler/linker that outputs PE efi
> images, so I tried in three different ways:
>
> 1. As suggested here [1] I recompiled binutils with x86_64-pep support
> and did a make && configure. The build process exited with errors [2].

I suppose that you thought about configure then make. Vice versa does not make sense.

> Nevertheless I got an efi image in dist/install/usr/lib64/efi/
>
> % ls dist/install/usr/lib64/efi/
>
> xen-4.8.0-rc.efi
> xen-4.8.efi -> xen-4.8.0-rc.efi
> xen-4.efi -> xen-4.8.0-rc.efi
> xen.efi -> xen-4.8.0-rc.efi

That is great!

> Note: I set EFI_VENDOR=archlinux and mkdir'd
> dist/install/boot/efi/efi/archlinux
>
> I will explain later as I tried to boot these images.
>
> 2. I installed mingw from the Arch Linux repos. Then configure && I set
>
> CROSSCOMPILE=x86_64-w64-mingw32- make world -j8

I have never used mingw. Anyway, IIRC, there were some issues with it and it
was discussed on Xen-devel. Even there were fixes for them but I am not sure
they were applied. Look for relevant thread for more details.

> at compile time. But again no xen.efi image in dist/install/ and a non
> bootable dist/install/usr/lib64/efi/. After the build I get [3].

If you use -j make option and you encounter build errors then please drop it
from make command line and restart build. This way every build step is executed
in sequence and error messages follow related command line. Otherwise sometimes
errors are printed under not relevant command line and it could be impossible
to tell what really happened.

> 3. At last I manually implemented [4] the Fedora patch [5] (because I'm trying to
> compile 4.8.0-rc3 and that patch is for another version, don't know which).
> Again, same result as before: no efi image in dist/install and those in
> dist/install/usr/lib64/efi/ are not bootable.

I am not able to say anything if I do not have at least single line from
serial console or screen dump (latter could be much more difficult to get).
So, please configure Xen serial console and try to catch some stuff.

> I switched to systemd-boot to chainload the xen.efi image. I

I am not sure that chainload is sufficiently reliable here.

> successfully boot my Arch Linux system, therefore i assume that this
> bootloader works.

I am not sure what you mean by that. Is Xen involved here or not?

> I have (hopefully) properly configured [6] a xen.cfg file
> in the same path as the xen.efi images obtained before.
> I can't boot yet.

Please provide serial console dump...

> Trying to bypass the bootloader I created an efi boot entry with
> efibootmgr and, via the laptop firmware interface, I tried to boot
> directly in xen.

Please provide at least efibootmgr command line...

> Again no results.

Serial console is you friend...

> Is there anybody patient enough to explain to me how to proceed?

Yes, but you must provide valuable details. Otherwise we cannot help.

> Greetings :)

Have a nice day,

Daniel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 16+ messages in thread
end of thread, other threads:[~2016-10-27  8:24 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20161005101600.odbvl632lmjigvsi@riseup.net>
     [not found] ` <CAFLBxZYWiGWTf2zhVOF3yfWQvtNpndF9avcOVgEGPDg7PZ1wog@mail.gmail.com>
     [not found]   ` <20161005125229.ixcvhldn4ra62prn@riseup.net>
2016-10-05 13:02     ` [Xen-users] xl info displays less ram than the total available George Dunlap
2016-10-05 13:06       ` Andrew Cooper
2016-10-05 13:32         ` blallo
2016-10-05 14:01           ` Jan Beulich
2016-10-06 10:55             ` George Dunlap
2016-10-06 10:59               ` Blallo
2016-10-06 12:06                 ` Konrad Rzeszutek Wilk
2016-10-06 12:39                   ` blallo
2016-10-06 13:00                     ` Jan Beulich
2016-10-06 12:56                   ` blallo
     [not found]                   ` <20161006125650.ww7lq7gpn7ovvqrr@supernova>
2016-10-06 12:58                     ` blallo
2016-10-06 13:16                       ` Daniel Kiper
     [not found]                         ` <53339FBD-ABBC-4047-A787-74F97867015A@riseup.net>
2016-10-26  8:30                           ` blallo
2016-10-26 13:26                             ` Konrad Rzeszutek Wilk
2016-10-27  8:24                             ` Daniel Kiper
     [not found]                     ` <20161006125857.7kavmrfe27yudsud@supernova>
2016-10-06 13:03                       ` blallo

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.