Hello everyone,

I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.

Benjamin

Hi all!

After 4 months of effort we are very happy to provide a 1st test ISO with IPv6 support in XCP-ng dom0.

Read our devblog here: https://xcp-ng.org/blog/2021/02/09/ipv6-in-xcp-ng/

The ISO is available here and the corresponding SHA is: 177eade2efa8b6c989847c970e5cab3e6eb24de5a2eef153a0fc422071f9234b.

Keep in mind this is a test ISO so do NOT use it in production and please report in this thread if you encounter any issue or if your tests are going well.

The devblog contains the known limitation of the ISO, updates will be provided in this thread when fixes and features are available.

I hope you'll have fun with it!

Hi!

In your Pool view there's a network tab where you can rename your networks by clicking on their name and enter a new one.

Regards.

@McHenry on the host you want to join: check if /etc/stunnel/certs/sdn-controller-ca.pem exists - if not create it: touch /etc/stunnel/certs/sdn-controller-ca.pem and then
xe pool-certificate-uninstall name=sdn-controller-ca.pem then retry the join.

@McHenry not sure what you mean.

You can easily join the host with no VMs to the other one by calling xe pool-join master-address=<ip of other host> master-username=... master-password=...

Then you should have a 2 hosts pool.

What make you think it's not possible?

@olivierlambert Pretty easy since everything is stored in the network other_config field.

@gb-123 Hi!

All the info are available on the host by running
ovs-vsctl show and look a the lines relevant to your bridge.
Also the following fields are available in your private network other_config:

  - `other_config`:
    - `xo:sdn-controller:encapsulation`       : encapsulation protocol used for tunneling (either `gre` or `vxlan`)
    - `xo:sdn-controller:encrypted`           : `true` if the network is encrypted
    - `xo:sdn-controller:pif-device`          : PIF device on which the tunnels are created, must be physical or VLAN or bond master and have an IP configuration
    - `xo:sdn-controller:preferred-center`    : The host UUID to prioritize as network center (or not defined)
    - `xo:sdn-controller:private-network-uuid`: UUID of the private network, same across pools
    - `xo:sdn-controller:vlan`                : VLAN of the PIFs on which the network is created
    - `xo:sdn-controller:vni`                 : VxLAN Network Identifier,

and the MTU is a field of the network as well.

So xe network-param-get uuid=<your network uuid> param-name=MTU
and xe network-param-get uuid=<your network uuid> param-name=other-config param-key=xo:sdn-controller:encrypted

Or should give everything you need!

Regards

@brezlord If it's not to much a bother that would be great yeah.
Comparing the xen-cmdline when doing the passthrough manually on 8.2 VS how it looks on 8.3 and when done via the XAPI.

@jivanpal you wrote in the 8.3 beta thread:

There is no way to configure IPv6 on the management interface via xsconsole, such as if one wants to switch between static configuration, autoconf via RAs, or DHCPv6.

True but we'll soon release an new version of xsconsole adapted for IPV6 allowing to configure IPv6 for management interface

There is apparently no support for IPv6 DNS servers, only IPv4. For example, if I try to add an IPv6 address like fd00::1 or [fd00::1] as a DNS server via xsconsole, there is apparently no change to the configuration. Editing /etc/resolv.conf works to achieve this (e.g. adding the line nameserver fd00::1), but this is known not to persist across reboots.

Should be solved by the future xsconsole release as well

There is apparently no support for RDNSS (advertisement of DNS servers in RAs rather than via DHCPv6).

DHCPv6 is one of the major blindspot for now indeed, I'm working on it but I don't have much knowledge on this so any hints are welcome if you spot if something is missing somewhere.

The "autoconf" option (available during installation, after choosing IPv6-only or dual-stack, and then being asked which mode to use to configure IPv6 addresses) appears to only be used at installation time to determine values such as the gateway's link-local address, the available address prefixes, and perform SLAAC and DAD, but then the resulting values are hard-coded and don't change according to changes in the environment, such as an upstream change in network prefix. (I will need to do some more testing to really confirm this, but this seems to be the case in my experience.) Compare this to when IPv4 is configured to use DHCP(v4), in which the management interface may have a different IPv4 address at different times, namely if it's assigned a different address by the DHCP server when it attempts to get or renew a lease.

I'm not aware of this issue, i'll try to reproduce in our env.

Some repos are unreachable in IPv6-only environments, which I'm aware is already known, and I can get around this by using NAT64 (either with CLAT to perform 464XLAT; or with DNS64), but this fact is currently a blocker for me to move to being IPv6-only.

We contacted the mirrors many times, still trying to have'em all advertising IPv4 and 6 and also trying to find a solution that could "smartly" redirect towards a compatible mirror.

Speaking of NAT64, this is just a question, I haven't tested or looked into this myself: Does XCP-ng include a CLAT daemon and support for auto-configuring 464XLAT using either the "PREF64" RA option (RFC8781) or resolution of ipv4only.arpa via a DNS64 server (RFC7050)?

Haven't tested either for now, feel free to do and report if you get here before me.

Again, thank you for the report, this is greatly appreciated and any info about what's missing for IPv6 (and perhaps how to achieve it when possible) is welcomed.

Regards!

In order to upgrade an XCP-ng host and put in IPv6 what could be done also:

• Do the upgrade
• xe host-management-disable && xe pif-set-primary-address-type uuid=<udid> primary_address_type=IPv6 ; xe host-management-reconfigure pif-uuid=<uuid>

@Fungusware Hi!

Yes this feature is supported at XAPI level, the VM.snapshot method now has a ignore_vdis field which is a list of VDI ref to not include in the snapshot.
This also available through xe:

xe vm-snapshot vm=... ignore-vdi-uuids=uuid1,uuid2...

Regards

Hi all!

8.2.1 IPv6 ISO available!

Here's a new ISO for IPv6 based on XCP-ng 8.2.1!
The ISO can be used to upgrade an existing server installed with the previous IPv6 test ISO or install a brand new XCP-ng 8.2.1 with IPv6 support on management interface.

A non-IPv6 8.2.0 would remain non-IPv6 after an upgrade as it's not possible to edit the management interface's primary adress type.

An 8.2.0 IPv6 hosts can also be upgraded via yum: yum upgrade --enablerepo=xcp-ng-updates,xcp-ng-ipv6.

What's new

• All 8.2.1 fixes
• Better DNS management in the case of both IPv4 and IPv6 configured on a PIF
• Partial support of IPv6 DHCP and autoconf

What to test

• Your daily uses of XCP-ng but with IPv6
• DHCP and autoconf (I have reached the limits of my knowledge so help from the community with more IPv6 expertise would be very VERY VERY helpful! :D)
  The goal of this ISO release is mainly to get help and leads about what's missing in DHCP and Autoconf.

Any issue encountered (and what works fine also) can be reported in this thread.

Usual warning

This a test ISO with an experimental feature still in development.
IPv6 on management interface is not officially supported by XCP-ng yet and so, we do not recommend to use it for a production environment.

Thanks a lot for the help and I hope the ISO will work well for everyone.

New xsconsole fix to test for 8.2

New update candidate are available for testing and due to be released as official updates.

Original topic:

• https://xcp-ng.org/forum/topic/3886/xcp-ng-8-2-dns-settings-gone-after-reboot
• https://xcp-ng.org/forum/topic/3277/dns-config-on-8-1-hosts-disappearing

yum clean metadata --enablerepo=xcp-ng-testing
yum update xsconsole --enablerepo=xcp-ng-testing
systemctl restart xsconsole.service 

What to test

Changing the DNS settings from the XSConsole and the change is retain after a reboot.

Good news, ISCSI shared storage already works in IPv6 with no package update!

An update will be released in the coming weeks for NFS support in the IPv6 case!

Has anyone play with the ISO? Any kind of feedback is very welcomed!

First update available!

The xsconsole rpm can be updated via: yum update --disablerepo='*' --enablerepo=ipv6 xsconsole.

The issue fixed was that the DNS couldn't modified via XSConsole when configured in static IPv6, it's now possible.

@kiu I reproduced your issue.

The issue comes from a lib used by xscontainer as a SSH Client which use a deprecated algo ssh-rsa so all modern (>=8.7) OpenSSH reject the connexion.

@fred974 you can look at https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/

This is what's followed by the recipe.

There's a evacuation-batch-size in /etc/xapi.conf that can be overridden (not edited directly in the file, see the warning in the header about this) by putting a new configuration file in /etc/xapi.conf.d/, to tell how many VMs to migrate at the same time when evacuating an host.

[Updated by Stormi to avoid letting think that it's OK to edit /etc/xapi.conf]

It's in the backlog indeed but I don't know when the ETA to start this.
I guess an issue in the xen-api repo would be a good first step to see what the XAPI team think of the feature.

@McHenry The import should have given you an uuid once finished which si the uuid of the VM.

It should also appears when doing an xe vm-list