Disk truncated after restore on different machine [SOLVED]

[warner_k]

I try to move a vm from one server to another. I have made a backup on the first with the backup-flag on (default) in the diskconfig.
After the restore the system truncates the disk from 4M to 17K. Sadly I cannot copy the output, I only have a screenshot.
What to do about this? I restored with the flag "--storage data" as the 2nd server did not have the same disk where the vm was stored.

 

[gfngfn256]

Does the VM work correctly on the new server?

AFAIK the "space reduction due to 4K zero blocks ...." is just the process used to lose zero areas of disk. See here.

If for some reason, the total disk size is in fact too small for the VM to work correctly, you may have to increase the disk size to 4M.
You will have to use CLI to do this (as only GBs can be entered in GUI). So maybe something like this:

qm disk resize 104 tpmstate0 4M

 

[warner_k]

No, the VM could not be started. I'll look further tomorrow as I'm now at home (and forgot to take the backup with me)

 

[warner_k]

should tmpstate0 not be tpmstate0?

 

[gfngfn256]

should tmpstate0 not be tpmstate0?

Yes it should be. My typo. That is the name of the said disk in your output. (Edited above).

 

[gfngfn256]

No, the VM could not be started

Bear in mind; we don't actually know why it is not booting on the new server. You have not provided any details/errors/logs of the VM boot process.

 

[warner_k]

I managed to get the machine running after having given your command with tpmstate0 and removing a link to a cdrom on a device that is not present in the new server.

 

[gfngfn256]

I managed to get the machine running after having given your command with tpmstate0 and removing a link to a cdrom on a device that is not present in the new server.

So I guess we will never definitely know which one actually caused the no-boot.
Anyway, it seems all is good now, so maybe tag prefix the thread-title with [SOLVED], (upper right hand corner under title).