It might record the max static RAM (IDK)

Hi,

You need to add more memory in your Dom0

@edisoninfo Great!

This warning is a life saver and did perfectly its job, allowing you to discover a hidden issue Glad you found the root cause!

Ping @julien-f if you remember/have more info on this

I would recommend Intel or Mellanox NICs, and generally avoid Broadcom due to sub-par drivers.

Hmm could the module causing the crash if the device isn't accessible?

@TeddyAstie any opinion?

First, let's collect the exact commands you are using to hide it from the Dom0, in case there's a typo

Hello and welcome here!

That's weird than just hiding the device from the Dom0 is causing an issue Do you have any logs during the crash we can check?

If the message is displayed, there is a reason. Please do a timdatectl status on your XOA

That you have NTP correctly configured/enabled everywhere

What about the browser console?

That's because you are using DMC (dynamic memory control). Try on a VM with static == dynamic.

Feedback for you @florent

If you want to test, you can switch to the relevant branch, which is fix_replication

https://github.com/vatesfr/xen-orchestra/pull/8971

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed fix(backups): replication doing always a full #8971

It's indeed pretty long. I would maybe use a local SR as suspend SR to check if it's very different, that could help to pinpoint the issue.

Let's try to grep 127.0.0.1 in the XAPI DB file then

I would print the result of the command xe host-param-list uuid=<problematic host UUID> to see where this localhost IP is set somlewhere.

Then, there is one machine thinking its management IP is 127.0.0.1

@cgasser said in Nos stats problem (but not the know one I guess):

connect ECONNREFUSED 127.0.0.1:443

That's the issue. XO needs to have access to all hosts management IPs, not just the master. I assume you made a tunnel or something specific to make XO connecting to the master. It's not related to 8.2 or 8.3, it's an architecture thing on pools since XCP exists

Hi,

1. The suspend SR is the place to store the virtual drive containing the memory.
2. The VM is paused and all the RAM is copied to the storage. Depending on how much RAM you have it can take some time.

How much RAM your VM had?