Description of problem: One can expect the VM has network connectivity after importing / starting it in the destination environment, but actually, VM has no network connectivity if it was configured in the source environment with a vNIC profile/Logical Network that doesn't exist in the destination environment, which is an expected behavior, but still I think a note clarifying this would be nice to have in the VMM Guide under section "6.12 Exporting and importing virtual machines and templates", maybe as a general note or even in 6.12.3 section Version-Release number of selected component (if applicable): RHVM 4.0.x VMM Guide Actual results: == No information about importing a VM with a vNIC profile which doesn't exist in the destination environment. One has to re-configure VM's network devices to have a working connectivity again Expected results: == I think we should add a note in the documentation stating that the vNIC profile must exist in destination environment to avoid re-configuring VM's network devices once they are imported. Also, MAC address ranges modifications to match what was configured in the source environment, should be added
This will be included in 4.1 GA which will be out soon. Therefore closing. See RFE BZ #1226206 and BZ #1277675. *** This bug has been marked as a duplicate of bug 1226206 ***