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!

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.

a little recap of the thread for anyone who'd like to help us by testing the feature.

XCP-ng IPv6 recap

A test ISO is available to test a new feature: having your XCP-ng hosts with an IPv6 management interface.

To have an IPv6 host, you must either install a new host or upgrade one with the test ISO.

More info on the dedicated blogpost
Please give any feedback in this thread!

Known limitations

• IPv6 Static only for now
• HA not tested yet
• Dual stack (both IPv4 and IPv6) can lead to DNS issues and the host will use IPv4 for its XAPI operations.

Experimental feature: select a network to evacuate an host
A new feature is available in our testing repo: select a network for host evacuation, this would allow to evacuate an host on any (faster) given network instead of the management one.

To access the feature, on all your hosts (always starting with master when in a pool):
yum update --enablerepo=xcp-ng-testing xapi-core-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-xe-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-tests-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64
And restart your hosts.

WHAT TO TEST
Host evacuation not on the management network (probably a 10G storage network to go faster!)
You can run xe host-evacuate host=<host_uuid> network-uuid=<network_uuid>
Or a XAPI client can call host.evacuate with a network ref parameter.
Host evacuation without the optionnal new parameter should behave as before the update.

Please report here if anything goes wrong (or right hopefully ) and if you spot a regression as well.

Thanks!

Edit: there are no plans for now to add this feature in 8.2 LTS, the package will probably stay in the testing repo for 8.2 and will be available in 8.3. It means that the package would be erased at next xapi update.

Just realised the IPv6 rpm repo isn't configured in the ISO... ^^'

so just add:

[xcp-ng-ipv6]
name=XCP-ng IPv6 Repository
baseurl=http://mirrors.xcp-ng.org/8/8.2/ipv6/x86_64/ http://updates.xcp-ng.org/8/8.2/ipv6/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng

in /etc/yum.repo.d/xcp-ng.repo.

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.

The issue has been fixed on this branch, it'll be merged into master soon.

@ataxyanetwork you're right. I just wanted to know to reproduce as much as possible your environment. Plus IPv6 only will be easier to debug, dual mode can have some weird magic happening at time!

I'll take a look ASAP and post here about my findings

@ataxyanetwork hi! Thanks for the feedback.

Did you set your host in both ipv4 & ipv6?

a little recap of the thread for anyone who'd like to help us by testing the feature.

XCP-ng IPv6 recap

A test ISO is available to test a new feature: having your XCP-ng hosts with an IPv6 management interface.

To have an IPv6 host, you must either install a new host or upgrade one with the test ISO.

More info on the dedicated blogpost
Please give any feedback in this thread!

Known limitations

• IPv6 Static only for now
• HA not tested yet
• Dual stack (both IPv4 and IPv6) can lead to DNS issues and the host will use IPv4 for its XAPI operations.

@bberndt the sdn controller communicate with the hosts on port 6640, opening it on the host should be enough.
I don't know what's happening. !this TLS error should have been solved by the override-certs option set to on.

@bberndt I'd need logs to tell you.
Just the error displayed in XO is not enough.

@bberndt can you try to set on in the settings of sdn-controller plugin override-certs to on?
And then try again.

In XCP-Center, Co-worker used something like this, and it created it, but Im not sure its actually working yet, he's still working on it, AFAIK and a Win7, and 2 WinXP VMs.

In XCP-ng Center you can create an Internal network which only works for the VMs on the SAME hosts. this is different than XO private neworks which work across hosts and even pools.

It does show as a regular network in XO, not under the Private list.

This is another thing, the private network you're trying to create is accessible by the VMs so it won't be listed here either.

@bberndt okay can you capture the logs of your XO while attempting to create a network?
Can you try to create a normal network on the same pool?

Can you try on another pool?

Thanks

@bberndt do you have access to the hosts console from the host view?
In Settings > Server is there an error appearing for this pool?

@bberndt AFAIK XCP-ng Center doesn't have the feature since it'd requires a proprietary citrix DVSC.

From the error message it seems XO has trouble connecting to your pool. Can you check the pool is properly connected to your XO and the pool's master is reachable from it?

Regards

@theaeon Hi!

I've just setup an runx host following @olivierlambert instructions.
I've reproduced your error when --log-level debug is put in the podman command.

Do you still have an error without it?
podman start archlinux shoud create a VM named container:<something> that starts, stops and then is removed like a container would do.