Hi folks,
when cloning a VM (linked or full clone), proxmox sets a new UUID. It seems that this was not always done like this, because it causes problems in my infrastructure since some time that have not been there some years ago.
I understand that not changing the UUID can cause issues in some use cases and that changing the UUID feels more "natural" more like "other bare metal system" and that probably for this reason it was chosen that way. However again, this way causes issues as well, specially licensing issues.
It would be great, if there was an per-machine option "keep UUID for clones".
Another good option would be to have a setting "change/keep/ask" for the cloning process.
But both options are not available, are there?
Let me explain my use case:
I have a software that works with sensitive data in a VM. Such sensitive, that I want to eliminate any risk that its data is leaked to the internet.
For this reason I have two instances A and B of this VM.
A is connected to the internet to allow updates, but it never sees the "production data"
B is a clone of A which does the actual processing and is never connected to the internet.
From time to time I destroy B and create a new clone of A to effectively update VM B.
when cloning a VM (linked or full clone), proxmox sets a new UUID. It seems that this was not always done like this, because it causes problems in my infrastructure since some time that have not been there some years ago.
I understand that not changing the UUID can cause issues in some use cases and that changing the UUID feels more "natural" more like "other bare metal system" and that probably for this reason it was chosen that way. However again, this way causes issues as well, specially licensing issues.
It would be great, if there was an per-machine option "keep UUID for clones".
Another good option would be to have a setting "change/keep/ask" for the cloning process.
But both options are not available, are there?
Let me explain my use case:
I have a software that works with sensitive data in a VM. Such sensitive, that I want to eliminate any risk that its data is leaked to the internet.
For this reason I have two instances A and B of this VM.
A is connected to the internet to allow updates, but it never sees the "production data"
B is a clone of A which does the actual processing and is never connected to the internet.
From time to time I destroy B and create a new clone of A to effectively update VM B.