leolns commented on issue #7572: URL: https://github.com/apache/cloudstack/issues/7572#issuecomment-2296867637
> > > this issue still exist in 4.19.0.0 RC4, so VMware 8.0.1 is still unsupported. > > >  > > > cc @vladimirpetrov @shwstppr > > > > > > I was able to workaround this problem forcing a fsck on first image boot. To do this you need to do a "touch /forcefsck" > > It worked on 8.0u3 with vsan esa. > > Detailed description bellow: > > ``` > > tar -xf systemvmtemplate-4.19.1-vmware.ova > > qemu-img convert -O raw systemvmtemplate-4.19.1-vmware-disk1.vmdk your_file.raw > > losetup -fP your_file.raw > > mount /dev/loop0p6 /mnt > > touch /mnt/forcefsck > > umount /mnt > > losetup -d /dev/loop0 > > qemu-img convert -O vmdk -o subformat=streamOptimized your_file.raw systemvmtemplate-4.19.1-vmware-disk1.vmdk > > ls -la systemvmtemplate-4.19.1-vmware-disk1.vmdk > > # Changed ovf:size with the new image size in bytes from "ls -la systemvmtemplate-4.19.1-vmware-disk1.vmdk" inside file systemvmtemplate-4.19.1-vmware.ovf > > sha256sum --tag systemvmtemplate-4.19.1-vmware.ovf > systemvmtemplate-4.19.1-vmware.mf > > sha256sum --tag systemvmtemplate-4.19.1-vmware-disk1.vmdk >> systemvmtemplate-4.19.1-vmware.mf > > tar -cvf systemvmtemplate-4.19.1-vmware.ova systemvmtemplate-4.19.1-vmware.ovf systemvmtemplate-4.19.1-vmware-disk1.vmdk systemvmtemplate-4.19.1-vmware.mf > > # Published a new template image inside UI > > # Changed global settings router.template.vmware to new image name > > ``` > > thanks a lot for the update @leolns > > how long `fsck` take in your environment ? I took only a few seconds and it only runs on the first boot. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
