Before opening an FR, I wanted to check here to see if I may have missed something:
While integrating our CI I noticed that on restore of a VM to a new VM ID the MAC and SMBIOS stay the same (arguably as expected). However, unlike vzdump, qmrestore does not appear to have a "--script" option with defined phases where VM could be made unique.
This presents a usability issue, as duplicate MACs can cause a production outage. Of course, this won't be the case with in-place restore but good administrative practices would be to restore to a new location, if possible.
At the very least I recommend documenting this behavior. If I missed something do let me know.
Thanks!
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
While integrating our CI I noticed that on restore of a VM to a new VM ID the MAC and SMBIOS stay the same (arguably as expected). However, unlike vzdump, qmrestore does not appear to have a "--script" option with defined phases where VM could be made unique.
This presents a usability issue, as duplicate MACs can cause a production outage. Of course, this won't be the case with in-place restore but good administrative practices would be to restore to a new location, if possible.
At the very least I recommend documenting this behavior. If I missed something do let me know.
Thanks!
Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
