This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: xc: error: xc_machphys_mfn_list: 83 != 129 when suspendi

To: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: xc: error: xc_machphys_mfn_list: 83 != 129 when suspending 32GB PV DomU
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Fri, 11 Mar 2011 19:21:35 +0000
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxx>
Delivery-date: Fri, 11 Mar 2011 11:22:24 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=Fnd1vQWmwHR7Bc9bNafeDbQbnKxnm1GLuDpQsV54vhs=; b=kT1+tlHI3xnaxyG4HBMHPOfhX0DyHrX8xp1maRc27oLIFZ6a4rgZBHtF3c2221z8Rr ltTGzPfwpmEVT5D3oUB2cOxaNq6qDTzhnnd/Au8+2ztoCAt74h1OECNt+lhFtOA2yg/I 1cLd0g9pXSzg8F3W4/ECP3HUjVLJJnU5YC/qM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=QVgIll79prU+3JnfhRYfWvXQ1nzXWMlRFurtEy03aqH4pkD9RzzrAGczrQejsG1bku E+3pWcn6er8xd6UOWb7Lj49cqnga0/0ElDhSxxf2p9G+l2x4Wm2jvlyvuPH5VP64vgYi WrS1V6WWzkoG3z64CKoJ6RkHMLyoiIQJfGxf4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1299869540.17229.72.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvgIYkq28o2uv9W60eOzJNdeGeASA==
Thread-topic: xc: error: xc_machphys_mfn_list: 83 != 129 when suspending 32GB PV DomU
User-agent: Microsoft-Entourage/
On 11/03/2011 18:52, "Gianni Tedesco" <gianni.tedesco@xxxxxxxxxx> wrote:

> Further debugging reveals the variables are set as such:
>  (XEN) compat_machine_to_phys_mapping = 18446606377058041856
>  (XEN) max_page = 67272704
>  (XEN) MACH2PHYS_COMPAT_NR_ENTRIES(current->domain) = 43515904
>  (XEN) RDWR_COMPAT_MPT_VIRT_START = 18446606377058041856
>  (XEN) RDWR_COMPAT_MPT_VIRT_END = 18446606378131783680
>  (XEN) limit = 18446606377232105472, (1 << L2_PAGETABLE_SHIFT) = 2097152
> Could it be that the compat mach-to-phys conversion table size of 1GB is
> too small?

It is insufficient to cover all of the system's memory. The reason for the
limit is that a 1GB M2P table is all that is reasonable to map into a 32-bit
domain's address space while still leaving space for the guest's own

We could make the compat m2p bigger solely for mapping by dom0 when doing
save/restore? However, you'd likely still soon hit the mmap limit for the
save/restore process in dom0. It might extend the lifetime of your 32-bit
dom0 for a bit longer however. Long enough for the lightweight HVM container
for PV guests work to get checked in and make our PV 64-bit guest
performance better.

 -- Keir

> Or that there exists some other arbitrary limit on the size
> of domains that can be suspended [when using a 32bit dom0] ?

Xen-devel mailing list