Windows Xen Guest Agent (Rust-based) - Not reporting the IP address to Xen Orchestra
-
On some of our VMs that we migrated over from ESXi, we have found that the new Xen Guest Agent (the one included in the new xcpng-winpv ISO) sometimes will not report the IP address of the Guest after a reboot.
So far this has happened on several of our Windows Server 2016 and 2019 VMs. When the reboot occurs, the IP address will display briefly after booting back up, but once the Management agent is detected, the IP will go back to saying there is no IPv4 address.
If I log into the Guest OS and restart the Xen Guest Agent (Rust-based) Windows Service, the IP address will show up immediately in XO. If I set the Xen Guest Agent Windows Service to Startup Type Automatic (Delayed Start) and reboot, the IP address will eventually be reported once the Service starts.
This isn't a major issue, since we can work around it by setting the Xen Guest Agent Service to Delayed Start in Windows, but we thought we would provide some feedback in case others are experiencing it too.
Note: We updated XO last week just before starting to install the new drivers/agents and our Pool is up to date according to the Pool Master.
-
@plaidypus I'm not sure why it's failing to report. Could you check the event logs?
-
@dinhngtu On the Windows Event Viewer, I didn't see anything out of the ordinary. Unfortunately, Ansible posts a lot of info in there so it may be getting drowned out. If I get a chance to test with another migrated VM, I will check again.
-
@dinhngtu Below is what I can find on the latest VM where this occurred. I saw a Windows report error that said it might have info, but there is nothing there.
Faulting application name: xen-guest-agent.exe, version: 9.0.9137.2, time stamp: 0x68e7c2e8 Faulting module name: xen-guest-agent.exe, version: 9.0.9137.2, time stamp: 0x68e7c2e8 Exception code: 0xc0000409 Fault offset: 0x00000000000a2c39 Faulting process id: 0xa20 Faulting application start time: 0x01dc439b0e299e74 Faulting application path: C:\Program Files\XCP-ng\Windows PV Drivers\XenGuestAgent\xen-guest-agent.exe Faulting module path: C:\Program Files\XCP-ng\Windows PV Drivers\XenGuestAgent\xen-guest-agent.exe Report Id: 145e6fdf-9c31-408c-a704-f09b923f957d Faulting package full name: Faulting package-relative application ID:Fault bucket , type 0 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: xen-guest-agent.exe P2: 9.0.9137.2 P3: 68e7c2e8 P4: xen-guest-agent.exe P5: 9.0.9137.2 P6: 68e7c2e8 P7: 00000000000a2c39 P8: c0000409 P9: 0000000000000007 P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_xen-guest-agent._3e70918689a16355b26c3269beb18dcb31a29bf_48acc870_17b92d64 Analysis symbol: Rechecking for solution: 0 Report Id: 145e6fdf-9c31-408c-a704-f09b923f957d Report Status: 4 Hashed bucket: -
@plaidypus Could you configure your VM to collect a program crash dump (full dump)? https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps