Jump to content
Welcome to our new Citrix community!
  • 0

VM often fails to start after opening DMC

di zhang1709161066


My host memory information is as follows:

Totoal memory: 1534GB
Currently used: 1499GB
Control domain memory: 32GB
Available memory: 420GB
Total max memory: 1610GB
(105% of total memory)

When I start a large memory VM, it often fails and throws the following log

  Async.VM.start_on R:03b0e8614933 failed with exception Server_error(INTERNAL_ERROR, [ xenopsd internal error: (Failure#012 "Error from xenguesthelper: xenguest: xc_dom_boot_mem_init: [4] panic: xc_dom_boot.c:141: xc_dom_boot_mem_init: can't" ) ])

Isn't my available memory still 420G? Why is it still wrong?


How should I avoid this happening?

Link to comment

9 answers to this question

Recommended Posts

  • 0

I also found a brand new server to add to the cluster.

Start 13 UBUNTU 14.04 HVM test VMs in the new server, each VM 130G memory, no application running after system startup (free -g, display 129G available memory)

When booting to the 13th, xenserver starts to compress memory;

At this time, the 12th VM fails to start and must be completed after multiple starts.

In the log:

Jun 25 09:03:53 wxac6017 xapi: [error|node06|44888 |Async.VM.start_on R:1b54abbb8b94|xenops] Caught exception starting VM: Xenops_interface.Internal_error("(Failure\n  \"Error from xenguesthelper: xenguest: xc_dom_boot_mem_init: [4] panic: xc_dom_boot.c:141: xc_dom_boot_mem_init: can't\")")



The conclusion is that whenever large memory needs to be compressed, errors will occur.:13_upside_down::13_upside_down:

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...