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

[Xen-users] 32Bit domus and RAM between 128GB and 168 GB

  • To: xen-users@xxxxxxxxxxxxx
  • From: Jan Marquardt <jm@xxxxxxxxxxx>
  • Date: Wed, 4 Jan 2017 15:50:41 +0100
  • Delivery-date: Wed, 04 Jan 2017 16:13:55 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>


unfortunately we still have a lot of paravirtual guests with 32 Bit OS
and are currently running in some problems.

As far as I understand the documentation in xend-config.sxp, if a
physical machine has between 128 GB and 168 GB RAM, 32 Bit guests should
be able to consume up to 168 GB.

# 32-bit paravirtual domains can only consume physical
# memory below 168GB. On systems with memory beyond that address,
# they'll be confined to memory below 128GB.
# Using total_available_memory (in GB) to specify the amount of memory
# in the memory pool exclusively for 32-bit paravirtual domains.
# Additionally you should use dom0_mem = <-Value> as a parameter in
# xen kernel to reserve the memory for 32-bit paravirtual domains, default
# is "0" (0GB).

In our case we have four systems with 160 GB RAM, but the guests are not
able to start if there are already guests running which are consuming
128 GB RAM in sum.

Is this a bug or do we miss something?

We are running Xen 4.1 from Debian Wheezy with backports kernel
3.16.0-0.bpo.4-amd64 in dom0s.

Best Regards


Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg
Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
E-Mail: support@xxxxxxxxxxx | Web: http://www.artfiles.de
Geschäftsführer: Harald Oltmanns | Tim Evers
Eingetragen im Handelsregister Hamburg - HRB 81478

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-users mailing list



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