When starting WildFly 10.0.0.Beta1 in --admin-only mode to perform :migrate operations on old subsystems, using an unmodified standalone-full-ha.xml configuration file from EAP 6.4.0, I'm getting errors.

Based on http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004306.html, I'm expecting that I don't have to perform any changes to the EAP 6.4 configuration file, yet in order to successfully boot the new server with the old configuration file, I have to perform the following set of changes:

• remove the cmp, jaxr and threads extensions and subsystems (this seems to be already covered by WFCORE-875)
• copy the entire configuration of the ejb3 subsystem (version 3.0) from a new standalone-full-ha.xml to the old one, because I'm not able to fix the old subsystem (version 1.5) from the error message [1]
• add the io extension and subsystem from a new standalone-full-ha.xml to the old one, because remoting needs it to boot [2]

[1]

16:31:35,167 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: "WFLYEJB0451: Attribute 'default-clustered-sfsb-cache' is not supported on current version servers; it is only allowed if its value matches 'default-sfsb-cache'"

[2]

16:34:35,376 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=remoting' are not available:
    org.wildfly.io.worker.default

In http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004303.html, I also mentioned datasources, but that was a false alarm – that was from normal server boot, not --admin-only, and hence invalid.