Re: Windows domu DRBD backend problem

[Kotán Attila <info@xxxxxxxx>]

    Hello Tu Dinh, 
    
    I created an debug environment for Qemu, but the Qemu debug not
    provide any info after the XEn drivers loaded in windows. 
    
    Then i make an windbg connection to Domu and try to DEbug with
    windbg. 
    
    When the DRBD backend status is change the following DEBUG info
    coming to windbg: 
    
    -----
    xenvbd|TargetReset:[0] =====>
    xenvbd|__FrontendSetState:Target[0] : ENABLED ----> CONNECTED
    xenvbd|__BlkifRingCompleteResponse:Target[0][0] : WRITE
    BLKIF_RSP_ERROR
    xenvbd|__FrontendSetState:Target[0] : in state CONNECTED
    xenvbd|__FrontendSetState:Target[0] : CONNECTED ----> ENABLED
    xenvbd|__FrontendSetState:Target[0] : in state ENABLED
    xenvbd|TargetReset:[0] <=====
    xenvbd|__BlkifRingCompleteResponse:Target[0][0] : WRITE
    BLKIF_RSP_ERROR
    Terminating critical process 0xFFFFD18EFF72A140 (services.exe)
    -----
    
    It was a very difficult to make the Debug environment for me. 
    
    I really don't understand why detecting the xenvbd driver the DRBD
    status change. 
    
    If you need more debug info, then please instruct me about how can i
    got it from windbg.
    
    Thank you and best regards. 
    
    Attila

2025. 04. 25. 10:00 keltezéssel, Kotán Attila írta:

Hello Tu Dinh, The debian defaults Qemu log is no have info about this event, then i didn't attached. Only the console show the following error when is destroy the Domu. "libxl: error: libxl_exec.c:117:libxl_report_child_exitstatus: /etc/xen/scripts/block-drbd remove [1841] exited with error status 1 libxl: error: libxl_device.c:1351:device_hotplug_child_death_cb: script: /etc/xen/scripts/block-drbd failed; error detected. " I know this is not help... I will try to debug Qemu. Thanks a lot. Attila

2025. 04. 25. 9:32 keltezéssel, Tu Dinh írta:

Hi Attila,

On 24/04/2025 20:45, Kotán Attila wrote:

Hello,

Thank you the info, but i can't figure out how can i debug Domu via qemu 
yet.
I try to add another disk(1) to Windows, and if the disk1 drdb status 
change then no problem.
I moved to pagefile and the event logs to D: drive. I tought the 
pagefile caused the error, but no luck.
But at least i have windows error log about the problem:




"The description for Event ID 129 from source xenvbd cannot be found. 
Either the component that raises this event is not installed on your 
local computer or the installation is corrupted. You can install or 
repair the component on the local computer.

If the event originated on another computer, the display information had 
to be saved with the event.

The following information was included with the event:

\Device\RaidPort0

The message resource is present but the message was not found in the 
message table"

Maybe you have any tipp what xen (xl.cfg or something else) parameter is 
affected.

Thank you and Best Regards

Attila

System event ID 129 means some VM disk requests have timed out.

We really need to see your Windows PV driver debug logs to know what's 
going on (look in /var/log for QEMU logs, or alternatively attach a 
kernel debugger)

Best regards,


Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech