linked clone clones older underlying disk

[Joshua Laferriere]

Proxmox 5.2

I have a vm that I installed kernel 4.4 to and resized the fs to use more space

Attempts at creating a linked clone fail to capture these changes. In fact, the linked clone skips the disks in this VM and goes back to an older set of disks to work from (i.e. I'm on kernel 2.6 after the linked clone completes).

Any ideas? If I edit the .conf file and point to the same disks that the VM that I based the linked clone on, the new clone works just fine. But this voids the purpose of the snapshot as I'm now using the disk that the snapshot was based on.

I'm trying alternative methods (such as qm), but even with "qm clone 106 107 --name test" results in the same

Yet, if I do a full clone (nano the .conf file and remove the template line), the resulting VM works as expected.

 

[Richard]

Proxmox 5.2

I have a vm that I installed kernel 4.4 to and resized the fs to use more space

Attempts at creating a linked clone fail to capture these changes. In fact, the linked clone skips the disks in this VM and goes back to an older set of disks to work from (i.e. I'm on kernel 2.6 after the linked clone completes).

A template for linked clones must not be changed after it has been converted to a template.

Possible solution:

cleate a (full) clone from the template, change it (e.g. resoze the disk) and convert it afterwards to your new template.