<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>Hi,</p><p>could you maybe send your configuration of the template?</p><p>(should be under /etc/pve/qemu/106.conf)</p><p>I can reproduce the issue, but only when the cache mode of the disk is writeback or writeback(unsafe)</p><p>regards<br>Dominik</p><blockquote type="cite">On March 16, 2016 at 7:15 PM Gaël Jobin <gael.jobin@switzerlandmail.ch> wrote:<br><br><div>Hi all,</div><div><br></div><div>I'm using Proxmox with the testing repo.</div><div><br></div><div>I successfully installed a Windows 7 VM and made a template of it. Then, I tried to create a new VM by cloning the previous template (full clone). Unfortunately, the new VM cannot boot Windows. On the other hand, with a "linked-clone", it works fine.</div><div><br></div><div>I noticed that the cloning was internally doing a "qemu-img convert". More precisely in my case, "/usr/bin/qemu-img convert -p -f raw -O raw /var/lib/vz/images/106/base-106-disk-1.raw /var/lib/vz/images/109/vm-109-disk-1.raw".</div><div><br></div><div>I did the same command manually and was quiet surprised to see that the new disk has the exact same size but not the same MD5 hash (md5sum command).</div><div><br></div><div>Any idea why qemu-img corrupt the disk?</div><div><br></div><div>For the moment, I just manually "cp" the base disk to my newly created VM directory and it's working. Also, I tried to convert the base disk from raw to qcow2 and back qcow2 to raw and the new raw disk is booting fine ! The problem seems related to "raw to raw" conversion...</div><div><br></div><div>qemu-img version 2.5.0pve-qemu-kvm_2.5-9</div><div><br></div><div>Thank you for your help,</div><div><br></div><div>Regards,</div><div>Gaël</div></blockquote><p><br> </p><blockquote type="cite">_______________________________________________<br>pve-user mailing list<br>pve-user@pve.proxmox.com<br>http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user<br></blockquote></body></html>