[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Windows domu DRBD backend problem


  • To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
  • From: "Tu Dinh" <ngoc-tu.dinh@xxxxxxxxxx>
  • Date: Tue, 20 May 2025 19:42:42 +0000
  • Delivery-date: Tue, 20 May 2025 19:42:50 +0000
  • Feedback-id: 30504962:30504962.20250520:md
  • List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>

Hi,

On 20/05/2025 21:30, Kotán Attila wrote:
> 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
>
You could run `!analyze -v` in Windbg to do a full analysis of the crash.

It'd be great to see the full windbg output (from boot to after !analyze
-v was run, annotated with the moment of failover) to at least
understand the context of the crash.

Best regards,


Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech





 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.