[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] HVM memory upper limit


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Marcos Paulo Serafim <mpserafim@xxxxxxxxx>
  • Date: Thu, 07 Dec 2006 08:33:29 -0200
  • Delivery-date: Thu, 07 Dec 2006 02:34:41 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=ijRSZSAPuwpnWT4LNcS8T5jf4O5nFXrGrwAZRERxoMwDxKM+tO6Pf4E3ytjFAGDmjVC5HeLXvJ7MRAF/dXvOoZ8WvYIMmUsA0KvYfitdbD/ATmF+/hMoAjbZqsmpIgChhcPM8ECFe1eJngKlR5mybXRgI3i4/voZfcwe31ADKEM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Petersson, Mats escreveu:
> Is this 32-bit PAE or 64-bit guest? I believe a 64-bit guest would work, but 
> 32-bit guest would not, as the entire guest-memory is also mapped into QEMU, 
> which fails to find a contiguous memory block of 3GB (as the overall limit of 
> user-space memory is 3GB, and that space has already been fragmented by 
> loading the qemu-dm executable as well as any other memory allocation 
> happening before the mapping of the guest memory. 2GB may well work, but 3GB 
> is definitely more than a 32-bit guest can handle). There was a patch to 
> dynamically map memory, which was sent in the last couple of days - that will 
> solve this problem, and you could, should you wish, give a 32-bit PAE guest 
> 8GB of memory - at least if the patch "does what it says on the label". I 
> haven't seen it go into the tree itself, so I guess it's not going to make 
> 3.0.4, as it's been feature frozen. 
>
> --
> Mats 

Mats, thanks for your answer and I'm sorry about the lack of
information. I'm using Xen 3.0.3 with a 32-bit PAE system.

The xm dmesg for this vm only shows me:

(XEN) vmx_do_launch(): GUEST_CR3<=00b89da0, HOST_CR3<=00b89ca0


xm info:

host                   : xen2
release                : 2.6.16.29-xen
version                : #5 SMP Wed Nov 29 11:55:33 BRST 2006
machine                : i686
nr_cpus                : 16
nr_nodes               : 1
sockets_per_node       : 4
cores_per_socket       : 2
threads_per_core       : 2
cpu_mhz                : 2992
hw_caps                :
bfebfbff:20100000:00000000:00000180:000064bd:00000000:00000001
total_memory           : 15611
free_memory            : 5757
xen_major              : 3
xen_minor              : 0
xen_extra              : .3-0
xen_caps               : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : Sun Oct 15 13:19:07 2006 +0100 11774:620cb0064d9b
cc_compiler            : gcc version 3.4.4 20050314 (prerelease) (Debian
3.4.3-13)
cc_compile_by          : shand
cc_compile_domain      : localdomain
cc_compile_date        : Sun Oct 15 13:19:23 BST 2006
xend_config_format     : 2


And xm list shows the vm (telnetx) but the CPU time remains on 0:

Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0      511    16 r-----   4234.5
db2x                                       2     4096     2 -b----    502.6
fsx                                       14     2000     1 -b----    221.2
telnetx                                   17     3072     1 ------      0.0


The Xen qemu-dm log points a error:

domid: 19
qemu: the number of cpus is 1
malloc returned error 12


Well, I'll look for this patch. :D

Thanks again!

-- 
Marcos Paulo Serafim
Analista de Suporte Técnico / Support Analyst
mpserafim (at) gmail (dot) com
Orlandia/SP - Brazil
MSN: mpserafim (at) gmail (dot) com; Linux User: #171191;
FP: EB38 D704 A4FD 2677 A2B2 A052 F44E CAA5 45FB 1F42


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.