Re: Windows domu DRBD backend problem

[Kotán Attila <info@xxxxxxxx>]

    Hello, 
    
    I downloaded the latest drivers from here: 
    https://xenproject.org/resources/downloads/
    
    This driver is working only the windows testsigning mode and
    included the symbols .pdb files.
    When im create the output, i loaded the xenbus and xenvdb symbols to
    windbg.

I thought the stack trace was what I sent in the windbg_otuput.txt file, but excuse me, I don't know what I should do to extract the relevant information for you. Are the downloaded symbol files not enough? Do I have to compile it anyway? I've never managed to compile anything on Windows, I work mainly on Linux (possibly OSX).

After break the running:
*** Fatal System Error: 0x000001aa
in windbg, I used the command: k
And on the Linux i used the "xenstore-ls -fp" commands.

Can I run another command to get more information?

Best Regards,
Attila

2025. 05. 20. 20:51 keltezéssel, Tu Dinh írta:

> Hello Attila,
>
> On 20/05/2025 20:38, Kotán Attila wrote:
> > Hello Tu Dinh,
> >
> > The data was useful?
> > Is there any other information I can extract that might be useful?
> >
> > Attila
> >
> > 2025. 05. 10. 15:19 keltezéssel, Kotán Attila írta:
> > > Hello Tu Dinh,
> > >
> > > I attached the file windbg_output.txt and xenstore_output.txt 
> > > (xenstore-ls -fp command output).
> > > The C: drive is:  /local/domain/0/backend/vbd/13/51712
> > >
> > > I hope this is the info what you ask.
> > >
> > > Thank you and Best Regards,
> > > Attila
> > >
> > >         
> >       
> Apologies, I couldn't find the time to respond or reproduce the issue 
> lately. I've looked into the Windbg output, but without a full stack 
> trace it's difficult to know what's going on.
>
> To enhance the debug info, you will want to build your own drivers and 
> load the resulting symbols in Windbg. Each driver repo from xenbits 
> contains a `build.ps1` file that could be run from within the VS 
> developer shell. You can use `-type free` for a release build or 
> (preferably) `-type checked` for a debug build. You'll have to bring 
> your VM into test mode to load your own build.
>
> Once you have attached your VM to Windbg, you could run the command
> `!analyze -v` to get a full report.
>
> Feel free to reply if you need help with building the drivers or 
> debugging the VM.
>
> I hope that helps.
>
> Best regards,
>
>
> Ngoc Tu Dinh | Vates XCP-ng Developer
>
> XCP-ng & Xen Orchestra - Vates solutions
>
> web: https://vates.tech
>
>
>
>