clone vm fails - beginner problem?

[defi00]

Hi, when cloning a linux vm I always get the clone without the newest changes.
E.g. I only add a file or an alias or install a new package on the original vm, which all runs fine.
But after cloning (or templating and cloning) and using the new cloned vm, all my changes are lost - what am I doing wrong?
My proxmox is running on a raspberry pi (bookwormI and I did all so far with the web frontend.
TIA for your help and suggestions!

 

[bbgeek17]

But after cloning (or templating and cloning) and using the new cloned vm, all my changes are lost - what am I doing wrong?

You could also try to run "sync" inside the VM prior to cloning.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[defi00]

You could also try to run "sync" inside the VM prior to cloning.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I just tried with sync from within the VM. But I still have the same behavior: my cloned vm is reset to the initial state.
And: Should a proper stop from proxmox not take care about the syncing?

What is the problem here? I'm quite puzzled and 404. The snapshotting works fine but cloning?!
Is it possible that this is because of the RaspberryPI environment and the arch64? .. strange to belief because everything else seems to be working.
Would it make a difference if the cloning would happen from CLI and not from web-GUI?

 

[fiona]

Hi,
is the guest agent enabled in the VM and running when you clone from a running VM? Please make sure to cleanly shutdown the VM before creating a template.

 

[defi00]

Hi,
Thanks for the hint with the guest agent. Now I updated my vm with the guest agent but still have problems when cloning. No matter how I do clone (from running or stopped or shutdown, with or without sync) and with the actual or any other snapshot - I always get a clone that is my initial vm (that is without any changes (files, installed packages) I made).
BTW: Also when I restart my vm after a shutdown - it is again in its initial state and I have to rollback to the last snapshot. Here I would expect my vm to start with its last used configuration. What's wrong here?
Thanks for helping, best regards!

 

[Onslow]

Quite weird, indeed. For a comparison, just a few days ago I made a clone of a running Linux VM and after I started the clone, it was a "carbon copy" (minus the MAC address of course) of the original VM to the moment of cloning, even the logs contained the latest activities.
And the log of the cloning task.

Maybe if you post the details of your system and configurations of the hypervisor, the storages and the VMs, someone will find a reason.

 

[defi00]

Thanks Onslow. I finally got it up and running as expected. The problem was that I did not properly set up the disks and so my changes were never made persistent. With the command "df -h" I could have seen that the non-cloneable VM used only a temporary filesystem (which of course disappears after a reboot). But by running the script "setup-alpine" this problem was solved and everything was set up correctly.