andrijapanicsb opened a new issue #4024: qemu 2.10+: consider adding --force-share flag URL: https://github.com/apache/cloudstack/issues/4024 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report [*] Improvement Request * Enhancement Request * Feature Idea * Documentation Report * Other Investigate a possible usage of "--force-share" parameter when accessing qcow2 files, due to "Qemu 2.10 added the requirement of a --force-share flag to qemu-img info when reading information about a disk that is in use by a guest." Not sure if this is applicable to qemu itself or just qemu-img (nothing to do here...) - but the way to reproduce the issue where this would help is: qemu 2.10+, NFS v3 (v4 is not affected) kill (power off) the host hosting a running VM qemu-img info can not access the qcow2 file and also the VM can't be started - so VM HA actions are affected (this is in contrast to when you kill the qemu process only - then the lock is immidately releases, so this is not a valid test) Adding the --force-share option might help in VM HA cases, where NFSv3 is used, so that the VM can be started on another host.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
