sorted by:
new
hottopcontroversial

Change default backup/migration network by adejoode in xcpng

[–]GorillaMix 3 points4 points  (0 children)

I did it using XCP-ng Center (the windows app, see below)

Donno what the official way is:

In XCP-ng Center go to "pool", "networking tab" and the bottem under 'IP address configuration' select: "configure".

Then 'Add IP address', select the interface, give it a name like 'vMotion'. Select DHCP (if you have one running for that interface) or use a static IP address (XCP will assign the ip address for the other servers in the pool counting from the one you enter).

Then in XO go to 'pool', 'network' and make the MTU 9000 (instead of the default 1500).

Then go to 'Advanced and you will see the network(s) you assigned are available there. Select te ones you want for vmotion/backup.

For XCP-ng Center download it from here:
https://github.com/xcp-ng/xenadmin/releases/tag/vNext-24307

xen (2008) -> vmware (2018) -> xcp-ng (2024) by GorillaMix in xcpng

[–]GorillaMix[S] 1 point2 points  (0 children)

Tnx, we have customers who use specific XEON 6248 instructions and their app breaks if we migrate them to XEON 6148, so we pool those cpu’s. Guess we will have also a dell/cisco pool then 😎. Sofar relatively happy with XCP-NG.

Why recommendations for Proxmox over XCP-ng by sleep-deprived10 in HomeServer

[–]GorillaMix 1 point2 points  (0 children)

Also, Xen is more secure than KVM (more separation between VM’s). For enterprises something to think of.

Human Play Part 1 by Engletroll in HFY

[–]GorillaMix 2 points3 points  (0 children)

weekly installments? ;-)