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

    Recurring crashes on VM

    Scheduled Pinned Locked Moved XCP-ng
    3 Posts 2 Posters 257 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.
    • T Offline
      the_jest
      last edited by

      I'm not sure if this is specifically an XCP-ng issue, so forgive me if this isn't the right place for it. I'm also not sure what details would be most useful to share, but I can describe my setup further as necessary.

      I've been running XCP-ng for a few weeks, and for the most part everything has been going well. I have about 6 VMs running, all based on vanilla installs of Debian Bookworm. One of these VMs serves as a Docker host, without about a dozen containers running in it; this VM has more memory and CPUs dedicated to it than others, but still runs comfortably (i.e. it's not always at 100% CPU or running out of memory or anything). Every couple of days, this VM has crashed; this doesn't appear to be associated with anything that's actively happening (i.e. it doesn't seem to happen when I do something specific on a container, it just happens). I'm attaching the dmesg output of a crash, but it starts with a "general protection fault".

      What can I do to figure out what's going on?

      Thank you.

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Can you check on the host with xl dmesg if you can correlate?

        T 1 Reply Last reply Reply Quote 0
        • T Offline
          the_jest @olivierlambert
          last edited by

          @olivierlambert
          No, the only thing I get with xl dmesg on the host, for some time back, are random brief reports of individual CPUs running above temperature threshold and then being clocked down, and then resolving. Nothing else.

          1 Reply Last reply Reply Quote 0
          • T the_jest referenced this topic on
          • First post
            Last post