blob: 3c5bf79b37f96a470b6c325706ec6f6c83952e4e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, let's break down this bug report step by step to figure out the category.
The user is using QEMU version 5.0 on a Fedora 30 system. They're trying to cross-compile a Windows guest agent (QGA) for Windows 10. The main issue they're facing is that when they include the VSS SDK in their build configuration, the installation of QEMU GA MSI fails with an error. However, when they omit the VSS SDK during configuration, the installation succeeds.
After successfully installing the GA without the SDK, they proceed to recompile with the SDK and replace the QEMU GA EXE file. Upon rebooting the GA service and attempting `virsh domfsfreeze`, they encounter an error related to freezing filesystems. The Windows Event Viewer shows that there's an access denied issue when querying for the IVssWriterCallback interface.
Looking into the provided link, it suggests that this error often relates to permissions or incorrect configuration in Volume Shadow Copy Service (VSS). Since the user followed the document but didn't resolve the issue, it points towards a problem with how QEMU interacts with the VSS on Windows.
The categories include things like hypervisor, network, device, etc. The bug seems related to the guest agent's ability to interact with the host's Volume Shadow Copy Service, which is part of the system's subsystems and permissions. Since the issue arises when using the VSS SDK, it points towards a problem in how QEMU handles this specific feature.
Therefore, the category that best fits this bug report is likely 'hypervisor' since it involves interaction with the guest OS features that rely on the hypervisor's capabilities or configuration.
</think>
hypervisor
|