@mbunkus thanks for the report.
About entering an IPv6 address for NFS in XOA: did you put the [] around the IPv6?
If so and it still failed you can indeed create an issue on vatesfr/xen-orchestra repo (make sure to reference this thread if you do).
For the rest, no need to create issues, i'm aware of them and I'll note them in our internal board for next devs. 
Regards
I think it was another issue regarding the RPU algorythm.
This is an issue with the xapi-plugins code.
@olivierlambert the issue is within the xapi-plugins package on XCP-ng.
A release candidate with the fis is on testing and will be released with next train of XCP-ng updates.
For now the update should be done in CLI with the yum command.
@AtaxyaNetwork thanks for the report.
I reproduced the issue, for some reason at first boot XCP-ng launch an IPv4 dhclient request (even though IPv4 is not configured on the management interface...) which overrides the DNS set after the request is replied to.
Hi all!
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.
Any issue encountered (and what works fine also) can be reported in this thread.
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.
@AtaxyaNetwork so infact the issue was with our IPv6 lab config (lol) so XOA is reachable in fact with an IPv6 address ahah.
So you can play with it.
Now i'm back on my DHCPv6/Autoconf/SLAAC investigations
@AtaxyaNetwork there are some issues, but on XOA's side.
For now the deploy script specifically wait for an IPv4 to complete succesfully so it won't even though the XOA VM is up and running.
For some reason it seems the XO app is not reachable with the IPv6 address in a web browser. I'm still investigating that.
@AtaxyaNetwork also, i tried to reproduce you XOA deploy issue buf failed, did you add [] around the IPv6 of your XCP-ng when filling up the deploy form?
Thanks.
Hi all! Long time no see ^^
I'm glad to say i'm back on IPv6 and will (soon-ish) provide a new IPv6 iso to test XCP-ng with an IPv6 management interface.
I've made some fixes to DNS management.
Before the new ISO i'd like to support ideally DHCPv6 and autoconf.
For now I managed to :
I'm looking for help as my field of expertise is more ocaml dev than IPv6.
I'm thinking especially of @AtaxyaNetwork and @bnerickson that I know have more knowledge than me for IPv6. Any help from a forum users would be greatly appreciated.
For DHCPv6 this is the conf of dhclient:
interface "xenbr0" {
send fqdn.fqdn = gethostname();
request subnet-mask, broadcast-address, time-offset, host-name, interface-mtu, dhcp6.nis-servers, dhcp6.nisp-servers, nis-domain-name, nisp-domain-name, dhcp6.sntp-servers, dhcp6.fqdn, routers, dhcp6.domain-search, dhcp6.name-servers;
}
For Autoconf here's what's done:
/sbin/sysctl -q -w net.ipv6.conf.xenbr0.autoconf=1
/sbin/sysctl -q -w net.ipv6.conf.xenbr0.accept_ra=1
Am I missing something obvious? I can provide more info if requested.
Also I can made available a test iso before the real one but it'd be really a experimental ISO.
Thanks!
Hi @paulcunnane,
Thanks for the report.
Are you using XO from the sources of the Appliance?
The recipe doesn't work anymore but next XOA release will fix it, the recipe has been migrated to use Debian11 instead of Debian10.
The tasks thing has nothing to do with the kubernetes recipe, it's just XO regularly calling the updater plugin to look for updates.
@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.
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!
@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.