Hi,
On 4/23/13 12:44 , "Tomoki Sekiyama" <tomoki.sekiy...@hds.com> wrote:
>> 2 executing the command "{"execute":"guest-fsfreeze-freeze"}"
>>failed,the output is:
><snip>
>> {"execute":"guest-fsfreeze-freeze"}
>> {"error": {"class": "GenericError", "desc": "Failed to
>>pVssbc->SetContext. (Error: 8004231b) "}}
>>
>> Could you give me some advise to debug this problem ? I can provide more
>>information if need.
>
>Is there any logs corresponding to the error in Event Viewer?
>
>And this might be caused by unsupported VSS_VOLSNAP_ATTR_* flags in
>SetContext()
>called from qga_vss_fsfreeze_freeze() at qga/vss-win32-requester.cpp,
>but I couldn't find out flags not supported on Windows 7 from VSS
>references.I'm investigating this issue. Some versions of Windows seem to ignore VSS_VOLSNAP_ATTR_NO_AUTORECOVERY, and to cause an error with VSS_VOLSNAP_ATTR_TRANSPORTABLE. In such cases, we cannot disable Auto-recovery that requires writable snapshots we don't yet support. Because of this, even if we remove TRANSPORTABLE flag, auto-recovery would be enabled and cause another error (VSS_E_OBJECT_NOT_FOUND) on thaw. The patch attached (to be applied after v2 patch) removes TRANSPORTABLE flag, and ignores the VSS_E_OBJECT_NOT_FOUND error on thaw. I think this should resolve the issue in Windows 7, and also works in the other versions of Windows. Could you try this? If it works, I will merge this into my path set and resend it as v3. Thanks, Tomoki Sekiyama
ignore-notfound.patch
Description: ignore-notfound.patch
