Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining a specific MAC address during the XVA import wizard does not persist during import #128

Closed
De-Occultist opened this issue Jan 9, 2019 · 4 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@De-Occultist
Copy link

Moved from xcp-ng/xcp#109

XCP-ng version 7.6 using XCP-ng Center 7.6.0

  • Import XVA specify the MAC address as aa:bb:cc:11:22:33 in the wizard
  • Start the VM, check the Networking tab, the MAC address is a random MAC address.

I've tested import with
xe vm-import filename=xxx.xva preserve=true and the MAC address is preserved.

But when exporting with XCP-ng Center 7.6.0, the import will begin immediately after the "Storage" selection in the"Import XVA" wizard. Changing the Network MAC address in the "Network" dialog will display the new MAC address but upon starting the VM it will revert back to the random MAC address it initially displayed in the "Import XVA" wizard.

@borzel borzel added bug Something isn't working and removed not reproduced labels May 11, 2019
@borzel borzel added this to the 8.0.1 milestone May 11, 2019
@borzel borzel changed the title Defining a specific MAC address during the XVA import wizard does not persist when VM starts up Defining a specific MAC address during the XVA import wizard does not persist during import May 11, 2019
@borzel
Copy link
Member

borzel commented May 11, 2019

Problem

Changes on the MAC adress in the import wizard are saved via

VIF.move(Session, vif, matchingProxyVif.network);

But VIF.move only changes the network properly, but not the MAC address. The new MAC address is showed in the xenadmins GUI, but on the first power on of the VM the old MAC address is used and showed.

Solution
a) Use the old way and delete and recreate the VIF. So also the MAC address is saved properly.
b) only if the MAC address is changed, use the old way

borzel added a commit that referenced this issue May 11, 2019
…ess. If the MAC is changed, recreate the interface instead.

Backgound: VIF.move can just move a VIF to another network, but not change the MAC properly (and this is also not expected from an action named move).

#128
@borzel borzel self-assigned this May 11, 2019
@borzel
Copy link
Member

borzel commented May 11, 2019

Upstream bug report: xenserver#2433

@borzel
Copy link
Member

borzel commented May 21, 2019

merged to development and release-xcp-ng-8.0

@borzel borzel closed this as completed May 21, 2019
borzel added a commit that referenced this issue May 21, 2019
…ess. If the MAC is changed, recreate the interface instead.

Backgound: VIF.move can just move a VIF to another network, but not change the MAC properly (and this is also not expected from an action named move).

#128
@borzel
Copy link
Member

borzel commented Jul 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants