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

    Windows server 2025 VM's stuk after some hours/days after migrating fro m xenserver to xcp-ng

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    6 Posts 2 Posters 30 Views 2 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.
    • R Offline
      rniesen
      last edited by

      Hello,

      I migrated an older xenserver 8.2 cu1 to xcp-ng 8.3.
      This was because we replaced the old server with a new HP ML350 Gen 11 with Xeon sivler 4510 CPU.

      We see that the vm's are unrespnive sometime.
      Sometime they react again after a while, sometime I can do a reboot but sometime tehy hang 100%

      I dit already past week an update of xcp-ng (yum update).

      I know there si a new firmware release wich I will try these weekend.
      But does anyone knows why we have this issu on this new hardware.

      What is the corret settings for an HP ML350 server?
      Is there still an issue with C-states?

      Or must I create a new vm and attached the old disk to the new vm's?

      We use the latest xcp-ng pv singed drivers.

      I also will start an VM wiht a ubuntu live and see if that will stuck to.

      All imput are welcome.

      Kr,

      Roel Niesen

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

        @rniesen

        Hi,

        Could you check the VM's Viridian settings from the host:

        xe vm-param-get uuid=... param-name=platform

        Followed by checking the Windows BCDEDIT settings:

        bcdedit /enum all
        R 1 Reply Last reply Reply Quote 0
        • R Offline
          rniesen @dinhngtu
          last edited by

          @dinhngtu

          xe vm-param-get uuid=... param-name=platform

          timeoffset: 3600; device-model: qemu-upstream-compat; viridian: true; nx: true; acpi: 1; vga: std; cores-per-socket: 4; videoram: 8; device_id: 0002; pae: true; apic: true

          bcdedit /enum all

          Windows Boot Manager

          identifier {bootmgr}
          device partition=\Device\HarddiskVolume1
          path \bootmgr
          description Windows Boot Manager
          locale en-US
          inherit {globalsettings}
          bootshutdowndisabled Yes
          default {current}
          resumeobject {47923867-fe76-11f0-a541-a1997f3f5417}
          displayorder {current}
          toolsdisplayorder {memdiag}
          timeout 30

          Windows Boot Loader

          identifier {47923868-fe76-11f0-a541-a1997f3f5417}
          device unknown
          path \WINDOWS\system32\winload.exe
          description Windows Server
          locale en-US
          inherit {bootloadersettings}
          displaymessageoverride Recovery
          recoveryenabled No
          allowedinmemorysettings 0x15000075
          osdevice unknown
          systemroot \WINDOWS
          resumeobject {47923867-fe76-11f0-a541-a1997f3f5417}
          nx OptOut

          Windows Boot Loader

          identifier {6864c4f3-5a46-11e4-a1c9-d440f7c4f103}
          device unknown
          path \Windows\system32\winload.exe
          description Windows Server 2012 R2
          locale en-US
          inherit {bootloadersettings}
          recoveryenabled Yes
          allowedinmemorysettings 0x15000075
          osdevice unknown
          systemroot \Windows
          resumeobject {6864c4f2-5a46-11e4-a1c9-d440f7c4f103}
          nx OptOut

          Windows Boot Loader

          identifier {d773e1b8-3100-11eb-925c-c8f93fef49ee}
          device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{d773e1b9-3100-11eb-925c-c8f93fef49ee}
          path \windows\system32\winload.exe
          description Windows Recovery Environment
          locale en-US
          inherit {bootloadersettings}
          displaymessage Recovery
          osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{d773e1b9-3100-11eb-925c-c8f93fef49ee}
          systemroot \windows
          nx OptIn
          bootmenupolicy Standard
          winpe Yes

          Windows Boot Loader

          identifier {current}
          device partition=C:
          path \Windows\system32\winload.exe
          description Windows Server 2025 Standard
          locale en-US
          recoverysequence {e3bdfdfb-ff9e-11f0-bbc4-a11e900eeb0f}
          recoveryenabled Yes
          osdevice partition=C:
          systemroot \Windows
          resumeobject {93da3896-ff53-11f0-815a-806e6f6e6963}
          bootmenupolicy Legacy

          Windows Boot Loader

          identifier {e3bdfdfb-ff9e-11f0-bbc4-a11e900eeb0f}
          device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{e3bdfdfc-ff9e-11f0-bbc4-a11e900eeb0f}
          path \windows\system32\winload.exe
          description Windows Recovery Environment
          locale en-US
          inherit {bootloadersettings}
          displaymessage Recovery
          osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{e3bdfdfc-ff9e-11f0-bbc4-a11e900eeb0f}
          systemroot \windows
          nx OptIn
          bootmenupolicy Standard
          winpe Yes

          Resume from Hibernate

          identifier {47923867-fe76-11f0-a541-a1997f3f5417}
          device unknown
          path \WINDOWS\system32\winresume.exe
          description Windows Resume Application
          locale en-US
          inherit {resumeloadersettings}
          recoveryenabled No
          allowedinmemorysettings 0x15000075
          filedevice unknown
          custom:21000026 unknown
          filepath \hiberfil.sys
          debugoptionenabled No

          Resume from Hibernate

          identifier {6864c4f2-5a46-11e4-a1c9-d440f7c4f103}
          device unknown
          path \Windows\system32\winresume.exe
          description Windows Resume Application
          locale en-US
          inherit {resumeloadersettings}
          recoveryenabled Yes
          allowedinmemorysettings 0x15000075
          filedevice unknown
          filepath \hiberfil.sys
          debugoptionenabled No

          Resume from Hibernate

          identifier {93da3896-ff53-11f0-815a-806e6f6e6963}
          device partition=C:
          path \Windows\system32\winresume.exe
          description Windows Server 2025 Standard
          locale en-US
          inherit {resumeloadersettings}
          recoverysequence {e3bdfdfb-ff9e-11f0-bbc4-a11e900eeb0f}
          recoveryenabled Yes
          filedevice partition=C:
          custom:21000026 partition=C:
          filepath \hiberfil.sys
          debugoptionenabled No

          Windows Memory Tester

          identifier {memdiag}
          device partition=\Device\HarddiskVolume1
          path \boot\memtest.exe
          description Windows Memory Diagnostic
          locale en-US
          inherit {globalsettings}
          badmemoryaccess Yes

          EMS Settings

          identifier {emssettings}
          bootems Yes

          Debugger Settings

          identifier {dbgsettings}
          debugtype Serial
          debugport 1
          baudrate 115200

          RAM Defects

          identifier {badmemory}

          Global Settings

          identifier {globalsettings}
          inherit {dbgsettings}
          {emssettings}
          {badmemory}

          Boot Loader Settings

          identifier {bootloadersettings}
          inherit {globalsettings}
          {hypervisorsettings}

          Hypervisor Settings

          identifier {hypervisorsettings}
          hypervisordebugtype Serial
          hypervisordebugport 1
          hypervisorbaudrate 115200

          Resume Loader Settings

          identifier {resumeloadersettings}
          inherit {globalsettings}

          Device options

          identifier {d773e1b9-3100-11eb-925c-c8f93fef49ee}
          description Windows Recovery
          ramdisksdidevice unknown
          ramdisksdipath \Recovery\WindowsRE\boot.sdi

          Device options

          identifier {e3bdfdfc-ff9e-11f0-bbc4-a11e900eeb0f}
          description Windows Recovery
          ramdisksdidevice partition=\Device\HarddiskVolume1
          ramdisksdipath \Recovery\WindowsRE\boot.sdi

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

            @rniesen Your VM is missing Viridian extensions (Hyper-V-compatible VM enlightenments implemented by Xen). This is typically due to the wrong VM template being chosen at the time of creation; the built-in Windows template should be used for all Windows VMs. There's an issue with Server 2025 that causes it to not run well without these features enabled.

            Please power off your VM, run this command to add them back, then reboot:

            xe vm-param-set uuid=<vm-uuid> platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true
            R 1 Reply Last reply Reply Quote 1
            • R Offline
              rniesen @dinhngtu
              last edited by

              @dinhngtu

              Hello,

              I will change this.

              And will that cause some rare working of the VM's?

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

                @rniesen Do you mean occasional hangs? Yes, Server 2025 is known to hang if these options are not present.

                1 Reply Last reply Reply Quote 1
                • First post
                  Last post