From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: 李义 <33186108@qq.com>
Cc: xs-devel <xs-devel@lists.xenserver.org>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [xen-devel] Q:xen/dom0: Use host E820 map
Date: Wed, 15 Apr 2015 14:11:20 -0400 [thread overview]
Message-ID: <20150415181120.GD15256@l.oracle.com> (raw)
In-Reply-To: <tencent_66CCDBCD3C326A9819BD6B8A@qq.com>
On Wed, Apr 15, 2015 at 10:35:33PM +0800, 李义 wrote:
> Sorry, there is some mistake.
>
>
> >1: This issue just happened on 32bit dom0.(the xen VMM is 64bit).
> >i have test on [VMM: xen4.4 (64bit) dom0 kernel 3.10 (64bit)], this issue can reproduce.
>
> ---------the reproduce environment [VMM: xen4.4 (64bit) dom0 kernel 3.10 (32bit)]. it will work correctly when dom0 is 64bit.
Could you attach the full serial console please? Does this happen with the latest kernel (4.0)?
>
>
> >2: xen VMM e820 info:
> >(XEN) 0000000000000000 - 000000000009ac00 (usable)
> >.....................
> >(XEN) 0000000000100000 - 000000007df7f000 (usable)
> >.........................
> >(XEN) 0000000100000000 - 0000000880000000 (usable)
> >
> >3: 32bit dom0 get host e820 info by XENMEM_machine_memory_map
> >[ 0.000000] Xen: 0000000000000000 - 000000000009a000 (usable
> >......
> >[ 0.000000] Xen: 0000000000100000 - 000000007df7f000 (usable)
> >.....
> >
> >so the dom0 last_pfn = 0x7df7f
> >
> >domo info:
> >[root@devserver-173 ~]# xl info | grep xen_commandline
> >xen_commandline : mem=1024G lowmem_emergency_pool=1M crashkernel=64M@32M loglvl=all >guest_loglvl=all dom0_mem=3072M,max:3072M
> >
> >[root@devserver-173 ~]# free
> > total used free shared buffers cached
> >Mem: 1960848 240108 1720740 0 8268 88812
> >-/+ buffers/cache: 143028 1817820
> >Swap: 2096476 0 2096476
>
> >
> >
> >My Debug:
> >
> >using the XENMEM_memory_map to get pseudo-e820 map on dom0, the dom0 mem can work >correctly.
>
> >but the dom0 console is blank.
>
>
>
>
>
>
> Date: Wed, Apr 15, 2015 09:13 PM
> To: "李义"<33186108@qq.com>;
> Cc: "xs-devel"<xs-devel@lists.xenserver.org>; "xen-devel"<xen-devel@lists.xen.org>;
> Subject: Re: [Xen-devel] [xen-devel] Q:xen/dom0: Use host E820 map
>
>
>
> On Wed, Apr 15, 2015 at 03:46:37PM +0800, 李义 wrote:
> > Hi ALL,
> >
> >
> > Environment
> > VMM: Xen-4.1.6.1
> > dom0: 3.0.101
>
> 3.0? Whoa. Yes you will hit issues with that. Please upgrade
> to latest kernels.
> >
> >
> > Quesition:
> > Set dom0 mem using the kernel cmdline: dom0_mem=3072M,max:3072M, after booting, the dom0 mem is 1914M.
> > the others (3072M-1914M) has returned to xen vmm. maybe it is the e820 hole issue.
> >
> >
> > can you help me to fix this issue.
> >
> >
> > Thanks a lot
> >
> >
> >
> >
> >
> > pls,
> > dom0 e820 Info:
> > ...
> > [ 0.000000] BIOS-provided physical RAM map:
> > [ 0.000000] Xen: 0000000000000000 - 000000000009a000 (usable)
> > [ 0.000000] Xen: 000000000009ac00 - 0000000000100000 (reserved)
> > [ 0.000000] Xen: 0000000000100000 - 000000007df7f000 (usable)
> > [ 0.000000] Xen: 000000007df7f000 - 000000007e0f7000 (reserved)
> > [ 0.000000] Xen: 000000007e0f7000 - 000000007e2f0000 (ACPI NVS)
> > [ 0.000000] Xen: 000000007e2f0000 - 000000007f36b000 (reserved)
> > [ 0.000000] Xen: 000000007f36b000 - 000000007f800000 (ACPI NVS)
> > [ 0.000000] Xen: 0000000080000000 - 0000000090000000 (reserved)
> > [ 0.000000] Xen: 00000000fec00000 - 00000000fec02000 (reserved)
> > [ 0.000000] Xen: 00000000fec40000 - 00000000fec41000 (reserved)
> > [ 0.000000] Xen: 00000000fed1c000 - 00000000fed40000 (reserved)
> > [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved)
> > [ 0.000000] Xen: 00000000ff000000 - 0000000100000000 (reserved)
> > [ 0.000000] Notice: NX (Execute Disable) protection missing in CPU!
> > [ 0.000000] SMBIOS 2.7 present.
> > [ 0.000000] DMI: Supermicro X9DRL-3F/iF/X9DRL-3F/iF, BIOS 3.0a 08/08/2013
> > [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
> > [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
> > [ 0.000000] last_pfn = 0x7df7f max_arch_pfn = 0x1000000
> >
> >
> >
> >
> >
> > XEN e820 Info:
> > (XEN) Xen-e820 RAM map:
> > (XEN) 0000000000000000 - 000000000009ac00 (usable)
> > (XEN) 000000000009ac00 - 00000000000a0000 (reserved)
> > (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> > (XEN) 0000000000100000 - 000000007df7f000 (usable)
> > (XEN) 000000007df7f000 - 000000007e0f7000 (reserved)
> > (XEN) 000000007e0f7000 - 000000007e2f0000 (ACPI NVS)
> > (XEN) 000000007e2f0000 - 000000007f36b000 (reserved)
> > (XEN) 000000007f36b000 - 000000007f800000 (ACPI NVS)
> > (XEN) 0000000080000000 - 0000000090000000 (reserved)
> > (XEN) 00000000fed1c000 - 00000000fed40000 (reserved)
> > (XEN) 00000000ff000000 - 0000000100000000 (reserved)
> > (XEN) 0000000100000000 - 0000000880000000 (usable)
> > (XEN) Kdump: 64MB (65536kB) at 0x2000000
> > (XEN) ACPI: RSDP 000F04A0, 0024 (r2 ALASKA)
> > (XEN) ACPI: XSDT 7E208088, 008C (r1 ALASKA A M I 1072009 AMI 10013)
> > (XEN) ACPI: FACP 7E214EA0, 010C (r5 ALASKA A M I 1072009 AMI 10013)
> > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI 2.0 version, truncating length 0x10C to 0xF4 [20070126]
> > (XEN) ACPI: DSDT 7E2081A8, CCF8 (r2 ALASKA A M I 15 INTL 20051117)
> > (XEN) ACPI: FACS 7E2E7080, 0040
> > (XEN) ACPI: APIC 7E214FB0, 00D4 (r3 ALASKA A M I 1072009 AMI 10013)
> > (XEN) ACPI: FPDT 7E215088, 0044 (r1 ALASKA A M I 1072009 AMI 10013)
> > (XEN) ACPI: MCFG 7E2150D0, 003C (r1 ALASKA OEMMCFG. 1072009 MSFT 97)
> > (XEN) ACPI: SRAT 7E215110, 0330 (r1 A M I AMI SRAT 1 AMI. 0)
> > (XEN) ACPI: SLIT 7E215440, 0030 (r1 A M I AMI SLIT 0 AMI. 0)
> > (XEN) ACPI: SPMI 7E215470, 0040 (r5 A M I OEMSPMI 0 AMI. 0)
> > (XEN) ACPI: SSDT 7E2154B0, D0CB0 (r2 INTEL CpuPm 4000 INTL 20051117)
> > (XEN) ACPI: EINJ 7E2E6160, 0130 (r1 AMI AMI EINJ 0 0)
> > (XEN) ACPI: ERST 7E2E6290, 0230 (r1 AMIER AMI ERST 0 0)
> > (XEN) ACPI: HEST 7E2E64C0, 00A8 (r1 AMI AMI HEST 0 0)
> > (XEN) ACPI: BERT 7E2E6568, 0030 (r1 AMI AMI BERT 0 0)
> > (XEN) ACPI: DMAR 7E2E6598, 0120 (r1 A M I OEMDMAR 1 INTL 1)
> > (XEN) System RAM: 32735MB (33520740kB)
>
> > _______________________________________________
> > 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
next prev parent reply other threads:[~2015-04-15 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_4510343505CCA3B3572E2190@qq.com>
2015-04-15 13:13 ` [xen-devel] Q:xen/dom0: Use host E820 map Konrad Rzeszutek Wilk
2015-04-15 14:29 ` =?gb18030?B?wO7S5Q==?=
[not found] ` <tencent_04939ADD0F5646C94156E750@qq.com>
2015-04-15 14:35 ` =?gb18030?B?wO7S5Q==?=
2015-04-15 18:11 ` Konrad Rzeszutek Wilk [this message]
2015-04-27 2:54 ` =?gb18030?B?wO7S5Q==?=
2015-04-15 7:46 =?gb18030?B?wO7S5Q==?=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150415181120.GD15256@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=33186108@qq.com \
--cc=xen-devel@lists.xen.org \
--cc=xs-devel@lists.xenserver.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.