XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Application on VM causing BSOD

    Scheduled Pinned Locked Moved Compute
    11 Posts 5 Posters 32 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      tsukraw
      last edited by

      For anyone who is smarter than I am here is the Stack Text from the crash dump. From what I can decipher it has something to do with the CPU debug registers

      STACK_TEXT:
      ffffde00fd2bc128 fffff806500b449e : 00000000000001aa 000000000009ed00 0000000000000003 ffffde00fd2bc900 : nt!KeBugCheckEx
      ffffde00fd2bc130 fffff8064fee3d88 : 000000000009ed00 fffff8065003f0d2 0000000000000000 0000000000000000 : nt!RtlpGetStackLimitsEx+0x1d0cfe
      ffffde00fd2bc180 fffff8064fee8294 : fffffb02e3ca2300 ffffde00fd2bce00 fffffb02e3ca2300 0000000000000000 : nt!RtlDispatchException+0x508
      ffffde00fd2bc8d0 fffff8065002f442 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x304
      ffffde00fd2bcfb0 fffff8065002f410 : fffff80650043d47 0000000000000000 0000000000000000 ffff9508e2b7b080 : nt!KxExceptionDispatchOnExceptionStack+0x12
      fffffb02e3ca2118 fffff80650043d47 : 0000000000000000 0000000000000000 ffff9508e2b7b080 fffffb02e3ca1930 : nt!KiExceptionDispatchOnExceptionStackContinue
      fffffb02e3ca2120 fffff8065003edf0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0x107
      fffffb02e3ca2300 fffff8065002e847 : fffff8065003f0d2 ffff9508e2b70000 0000000000000006 000000000009fda0 : nt!KiGeneralProtectionFault+0x330
      fffffb02e3ca2498 fffff8065003f0d2 : ffff9508e2b70000 0000000000000006 000000000009fda0 ffff950800000000 : nt!KiSaveDebugRegisterState+0xc7
      fffffb02e3ca24a0 00000000771416e5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x2d2
      000000000009ed00 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x771416e5

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        Pilow @tsukraw
        last edited by

        @tsukraw disable VIRIDIAN in advanced tab of the VM ? and put network card in E1000 (I think this one is taken into account only if PV Tools are not present)

        restart VM and relaunch app ?

        you could also try to prevent debug registers to happen, in the VM :

        bcdedit /enum

        to check current config

        bcdedit /debug off
shutdown /r /t 0

        to disable debug

        T 1 Reply Last reply Reply Quote 0
        • T Offline
          tsukraw @Pilow
          last edited by

          @Pilow said:

          bcdedit /debug off

          Thank you @pilow fir the ideas but neither were fruitful 😞
          I have disabled VIRIDIAN and set the debug to off and both resulted in the system crashing and rebooting.

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            Pilow @tsukraw
            last edited by

            @tsukraw if it's working on VMWARE, and same OS/same app, there is some cpu flag that is not presented in xen/xcp to the app that provoke the crash I guess

            above my level of competency to know for sure how to mask CPU flags in a VM params

            does bcdedit /enum tells auto for hypervisorlaunchtype ?

            if yes, try to

            bcdedit /set hypervisorlaunchtype off
shutdown /r /t 0

            summoning some pro support guru ... @danp ?

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              flakpyro @Pilow
              last edited by

              After the VM crashes check for output from "xl dmesg" on the hypervisor via ssh. It may provide some information on why the VM crashed.

              I ran into an issue with Blue Iris crashing on recent Intel CPUs and the fix was to relax MSR enforcement on the VM by running:

              xe vm-param-add uuid=VM_UUID param-name=platform msr-relaxed=true

              However this was after determining this was the issue via xl dmesg.

              1 Reply Last reply Reply Quote 0
              • T Offline
                tsukraw
                last edited by

                I tried bcdedit /set hypervisorlaunchtype off
                This did not make any difference.

                Attached is the output form the "xl dmesg"
                Not 100% sure what I would expect to see in here.
                One thing i thought was odd and maybe it isnt but the fact is asy VIRIDIAN even though i turned that off under the advanced settings for the VM in question.
                xl dmesg.txt

                F 1 Reply Last reply Reply Quote 0
                • T Offline
                  tsukraw
                  last edited by

                  Hot damn!!

                  @flakpyro
                  For kicks and giggles I tried what you had sent

                  xe vm-param-add uuid=VM_UUID param-name=platform msr-relaxed=true

                  And sure enough it worked!!
                  Not exactly sure the technical details on what setting msr-relaxed=true does but hey if it works it works 🙂

                  1 Reply Last reply Reply Quote 0
                  • F Offline
                    flakpyro @tsukraw
                    last edited by

                    @tsukraw Another thing i remember from my time troubleshooting blue iris was capturing a crash dump using Xentrace:

                    xentrace -D -e 0x0008f000 xentrace.dmp

                    From there i was able to determine the MSR related issue. Not at all saying thats the issue you are having but it may shed some light or be useful for those more knowledgeable with Xen than myself.

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      dinhngtu Vates 🪐 XCP-ng Team
                      last edited by dinhngtu

                      Hi, it's a known issue on newer CPUs: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#bsod-0x3b-system_service_exception-on-newer-intel-cpus

                      What's your CPU Vendor value shown in xl dmesg?

                      Never mind, I missed your log: CPU Vendor: Intel, Family 6 (0x6), Model 143 (0x8f), Stepping 8 (raw 000806f8)

                      1 Reply Last reply Reply Quote 0
                      • TeddyAstieT Offline
                        TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @tsukraw
                        last edited by

                        @tsukraw Can you give the output of xen-cpuid -p (in Dom0) ?

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post