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

Re: [Xen-users] Max memory



From what you pasted below, it looks like something to do with
NUMA is failing. Have you checked that Xen 4.2.x behaves the
same way?

On Wed, 31 Jul 2013 06:22:58 -0600, jacek burghardt <jaceksburghardt@xxxxxxxxx> wrote:
I have couple of amd based systems. I haveÂopteron 2373 e with 32 gb
of ram and it will not let me assign 12 gb of ram. The most I could
assign is 6GB
xc: error: Could not allocate memory for HVM guest. (16 = Device or
resource bus                   Â
                      Â
 Ây): Internal error
libxl: error: libxl_dom.c:620:libxl__build_hvm: hvm building failed
libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot
(re-)build domai                  Â
                      Â
  Ân: -3
libxl: error: libxl_dm.c:1312:libxl__destroy_device_model: could not
find device                   Â
                      Â
 Â-model's pid for dom 4
libxl: error: libxl.c:1422:libxl__destroy_domid:
libxl__destroy_device_model fai             Â
                      Â
       Âled for 4
[root@xen2hebe xen]# nano /var/log/xen/*
[root@xen2hebe xen]# rm Â/var/log/xen/*
[root@xen2hebe xen]# xl create archlinuxa.cfg
Parsing config from archlinuxa.cfg
got a tsc mode string: "default"
libxl: notice: libxl_numa.c:491:libxl__get_numa_candidate: NUMA
placement failed                  Â
                      Â
  Â, performance might be affected
xc: info: VIRTUAL MEMORY ARRANGEMENT:
 Loader:    Â0000000000100000->000000000019eb64
 Modules:    0000000000000000->0000000000000000
 TOTAL:     0000000000000000->00000002fe000000
 ENTRY ADDRESS: 0000000000100000
xc: error: Could not allocate memory for HVM guest. (16 = Device or
resource bus                   Â
                      Â
 Ây): Internal error
libxl: error: libxl_dom.c:620:libxl__build_hvm: hvm building failed
libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot
(re-)build domai                  Â
                      Â
  Ân: -3
libxl: error: libxl_dm.c:1312:libxl__destroy_device_model: could not
find device                   Â
                      Â
 Â-model's pid for dom 5
libxl: error: libxl.c:1422:libxl__destroy_domid:
libxl__destroy_device_model fai ÂÂ

On Wed, Jul 31, 2013 at 6:14 AM, Gordan Bobic  wrote:
 What exactly is the error you are seeing? I have a hardware bug
 that prevents me from using more RAM than the lowest BAR with
 PCI passthrough (which in my case happens to be 2688MB), but
 without PCI passthrough I can easily set the VM for 8GB or
 16GB and it just works.

 Are you using PCI passthrough? What are your dom0 and domU
 E820 maps?

 On Wed, 31 Jul 2013 05:56:12 -0600, jacek burghardt  wrote:

So is no one using xen or no body has any issues with memory limits ?
 ÂIt xen limited to only 6 gb of ram per vm ? I am unable to assign
 anything above 6 gb KVM does not have any problem but xen will not
let
 me assign more than 6 gb to vm machine. I use xen-4.3-gitÂ

 On Tue, Jul 30, 2013 at 6:59 AM, jacek burghardt Âwrote:

 I wonder what is the maximum memory allocated with Xen 4.3 for
windows
 . Is everyone just allocating 4 - 6 GB or more. I had been testing
with opetron e2320 and the system has 32 GB of ram so I had failed at
 assigning more than 6gb. I use windows 2012 upstream qemu. Server
2012
 will not boot with anything more than 6gb.I wonder if any of guy had
 managed to assign more than 6gb.

 Links:
 ------
 [1] mailto:jaceksburghardt@xxxxxxxxx [3]



Links:
------
[1] mailto:gordan@xxxxxxxxxx
[2] mailto:jaceksburghardt@xxxxxxxxx
[3] mailto:jaceksburghardt@xxxxxxxxx


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

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