Hi,

I have a PFsense VM that is showing this message continously:

xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip
xenstore: could not write path attr/eth2.110/ip
xenstore: could not write path attr/eth0.401/ip

I already did a xe-toolstack-restart in the host, but no lucky.
These are nics of the VM:

Any Ideas?

Hi:

We established a VPN-IPSEC between our Pool and a remote XCP-ng Host. We had a MPLS before change to IPSEC and the host was integrated to the pool. Now we cannot connect anymore.

It's "enabled" but we cannot reach its pool, so we cannot manage it nor see any VMS within it. Is there any port to deal? Any IPSEC setting to enable?

Trying by XCP-ng Center is not better...

The log says just it, endlessly, no error message:

2024-03-14 17:20:53,926 INFO  XenAPI.Session [Connection to 172.24.52.141] - Invoking XML-RPC method session.login_with_password
2024-03-14 17:20:54,733 INFO  XenAPI.Session [Connection to 172.24.52.141] - Invoking XML-RPC method pool.get_all_records

| can access the host normally, by SSH, for example.
Any ideas?

@olivierlambert I made a system update (yum update) and rebooted the server without interfering on grub menu... So it persisted on the same error... I nad to choose the second option again to do a good boot. I tried to find where those faulty grub log lines where saved, but journalctl just stored healthy boot.

@olivierlambert I did right now a fresh install of XCP-ng 8.2.1 in this server. Grub menu is this:

choosing the first item (default) I get this error(so it begins looping):
the second item (XCP-ng (Serial)) got a successfull boot.

Now I remember what I did... I tried to make XCP-ng (Serial) the default option but I ended corrupting grub... Tell me how I turn it the default option?

@olivierlambert Look, I rebooted now the server using this settting:
Now the host has this dashboard values:
and this htop
Now Dom0 busy RAM is 0.
I try to start a VM, I have this error:

I'll redo a fresh installation of xcp-ng on this server.

@olivierlambert here is XOA view:

And this is htop:

I must tell you, I had to change boot grub order, giving priority to Xen hypervisor (second option) because when it boot to first option GNU/Linux, the server start in Recovery Mode, with just 1 core processor.

Hi:

I have a Host with 24Gb RAM. Actually it hasn't any VM running on it.
It's because Control Domain Memory is using almost all the Server memory:

Accordingly to the manual, I executed this command:
/opt/xensource/libexec/xen-cmdline --set-xen dom0_mem=4096M,max:4096M
and rebooted it, but no changes were done.

My Server is a HP Proliant Gen8 24Gb RAM, I installed xcp-ng 8.21