Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
You guys have any words of wisdom?
Many thanks, -T
Windows Server: first the expense, the ooo and the aaahhh and the excitement, then the crashing, the screaming, the running in terror, the early morning panic phone calls.
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
Hi Samuel,
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
Thank you!
-T
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
That's weird. I wonder what's trying to access "QEMU-GA" then. What are the details of that log message?
On 3/25/25 3:22 PM, Samuel Sieb wrote:
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
That's weird. I wonder what's trying to access "QEMU-GA" then. What are the details of that log message?
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
On 3/25/25 4:58 PM, ToddAndMargo via users wrote:
On 3/25/25 3:22 PM, Samuel Sieb wrote:
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
That's weird. I wonder what's trying to access "QEMU-GA" then. What are the details of that log message?
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
But what's the context? Source, event ID, etc. You can use the "copy->copy details as text" option to get it all. Redact any bits you think are sensitive.
On 3/25/25 5:12 PM, Samuel Sieb wrote:
On 3/25/25 4:58 PM, ToddAndMargo via users wrote:
On 3/25/25 3:22 PM, Samuel Sieb wrote:
On 3/25/25 3:13 PM, ToddAndMargo via users wrote:
On 3/25/25 12:43 PM, Samuel Sieb wrote:
On 3/25/25 12:28 PM, ToddAndMargo via users wrote:
Hi All,
Fedora 41 qemu-kvm-9.1.3-2.fc41.x86_64 Windows Server 2025 STD virto-win-0.1.240.1
I am constantly getting this error in my Windows System log. Googling tells me what it is but not how to fix it. But does tell me that if if crashes, it could crash the OS.
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
I don't see anything specific for that from Google and I really don't think that will crash the OS. That's just the Guest Agent. If you don't need that, you could disable the service. I see mention of enabling it in KVM, but I don't see where that is. I've never had to configure anything, it just works. Make sure you have the Spice channel in the VM config. That might be how it works.
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
That's weird. I wonder what's trying to access "QEMU-GA" then. What are the details of that log message?
A timeout was reached (45000 milliseconds) while waiting for the QEMU-GA service to connect.
But what's the context? Source, event ID, etc. You can use the "copy->copy details as text" option to get it all. Redact any bits you think are sensitive.
- System
- Provider
[ Name] Service Control Manager [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4} [ EventSourceName] Service Control Manager
- EventID 7009
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2025-03-15T01:57:21.0198885Z
EventRecordID 2506
Correlation
- Execution
[ ProcessID] 816 [ ThreadID] 3300
Channel System
Computer WIN-QA0TO7878F7
Security
- EventData
param1 45000 param2 QEMU-GA 510045004D0055002D00470041000000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 00450051 0055004D 0047002D 00000041
In Bytes
0000: 51 00 45 00 4D 00 55 00 Q.E.M.U. 0008: 2D 00 47 00 41 00 00 00 -.G.A...
On 3/25/25 6:01 PM, ToddAndMargo via users wrote:
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
I just rebooted and cleared the system log. Now we wait.
On 3/25/25 6:05 PM, ToddAndMargo via users wrote:
On 3/25/25 6:01 PM, ToddAndMargo via users wrote:
I never installed "qemu-ga-x86_64.msi" on the guest.
I just did. I have to wait till after hours to reboot the thing to see if it is fixed and the UAC gets enabled.
I just rebooted and cleared the system log. Now we wait.
I have been watching the system error log for several hours now. Nothing but "Information" entries. So I am going to declare it is fixed!
:-)
-
Samuel Sieb -
ToddAndMargo