ISO NFS can't seem to mount with an IPv6 address as it leads to a "DNS Error."
Error code: SR_BACKEND_FAILURE_140
Error parameters: , Incorrect DNS name, unable to resolve.,
sr-probe is able to find the target/paths and VDI SR NFS is able to mount using the same path. Tried with and without brackets but no success on the NFS ISO side
@jivanpal It's good that that works but I can see high change for data loss if the installation changes or adjusts the partition size during the install. It could wipe the data and prevent recovery of the SR. That's also not mentioning any local modifications done to the hosts that may be required and have to be redone.
As a side note, I don't need to do a migration of the management interface and was just theorizing that it looked possible to do via xAPI without reinstalling based on documentation I was reading. I ran into a situation on one of my lab servers where running an emergency reset broke v6 management interfaces. I just reinstalled but was curious of how one could recover from that state.
The only way to enable IPv6 for the management interface is at boot time. It's something that can't be modified afterwards in XAPI.
@stormi Wouldn't it possible to change afterwards by following a similar procedure to replacing an interface card that has the management interface on it? Disable host management, modify PIF with v6 as primary address type (forget/reintroduce/reconfigure), then reset the host management.
It's definitely a process but seems possible
Has the emergency network reset and xe been updated to handle IPv6 only configurations with patches after Beta2 ISO or is there something special that needs to be done?
I'm not able to pull patches atm and after running the resets it didn't seem to like the v6 addressing and xe refused to set the management interface without v4 set. Couldn't drop the temporary v4 address either.
Looks like the answer is yes but only at boot? "The only way to enable IPv6 for the management interface is at boot time. It's something that can't be modified afterwards in XAPI."
Old topic but figured I'd put this information here in case anyone else runs into a similar issue.
This fix only works for BIOS/Legacy boot not UEFI because UEFI doesn't use VGA directly. There's not a solution for UEFI at this point but there should be one when XCP-ng moves to Xen 4.17+ in 8.3 release.
Bit more information regarding the future potential fix is documented in xen commit 927aee5