Add --no-sparse parameter with virt-resize to avoid filesystem issues in KVM VM.
During the VM creation, solusvm slave uses
virt-resize --expand /dev/sda1 template.gz /dev/dm-x to expand the template and to write to the LV. However, if LV has obsolete data on it, and virt-resize copies template with sparse mode, the obsolete data could occupy the space where superblocks are supposed to write to and it leads to no bootable device error.
I understand this behaviour can be avoided if we already zeroed the Volume Group, but it's still affecting the Windows guests.
Please add a toggle to enable/disable the --no-sparse mode for each template in Template settings page.
This function has been tested with Windows template, and behaves correctly.
This suggestion can be closed as resolved.
Nikolay Zhmuk commented
https://support.solusvm.com/hc/en-us/articles/360020814031 - here is the article with patches available. Note that it should be applied only on CentOS 7 only
SolusVM provided a patch to this problem which seems to have fixed the Windows template provisioning boot error in our initial testing. We are told development is evaluating for permanent fix.
Sparsed Windows templates are suffering from this issue. Would love to see a toggle option on template so that we can support deploying Windows templates.