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

    Mouse stops responding in XO console (XCP-ng 8.3, Win11 24H2)

    Scheduled Pinned Locked Moved XCP-ng
    xcp-ng 8.3windows 11 24h2xo consolexenorchestra
    25 Posts 8 Posters 705 Views
    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.
    • M Offline
      mrchip
      last edited by mrchip

      It's happening to me right now in a debian vm. If I can help let me know what steps you would like me to take. I just noticed my ram has peaked and currently maxing out (8GB)

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

        @mrchip Could you post a kernel log?

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mrchip @dinhngtu
          last edited by

          @dinhngtu Hope this is what you r looking for. In the debian machine I did a sudo cat /var/log/kern.log If you need more pls let me know....glad to help (i feel like I can actually do something to help rather than just always ask)

          /var/log/kern.log
          Jan 26 00:00:10 Server1 kernel: [2365430.803316] audit: type=1400 audit(1737878410.115:54): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=2235578 comm="cups-browsed" capability=23 capname="sys_nice"
          Jan 28 00:00:41 Server1 kernel: [2538262.338725] audit: type=1400 audit(1738051241.138:55): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3011151 comm="cupsd" capability=12 capname="net_admin"
          Jan 28 00:00:41 Server1 kernel: [2538262.472961] audit: type=1400 audit(1738051241.270:56): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=3011153 comm="cups-browsed" capability=23 capname="sys_nice"
          Jan 29 00:00:06 Server1 kernel: [2624628.082358] audit: type=1400 audit(1738137606.613:57): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=3398507 comm="cupsd" capability=12 capname="net_admin"
          Jan 29 00:00:06 Server1 kernel: [2624628.223119] audit: type=1400 audit(1738137606.753:58): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=3398509 comm="cups-browsed" capability=23 capname="sys_nice"
          Jan 29 11:04:11 Server1 kernel: [2664473.087788] vethf832f9f: renamed from eth0
          Jan 29 11:04:11 Server1 kernel: [2664473.103008] br-edbd4014078c: port 5(veth86cb043) entered disabled state
          Jan 29 11:04:11 Server1 kernel: [2664473.183494] br-edbd4014078c: port 5(veth86cb043) entered disabled state
          Jan 29 11:04:11 Server1 kernel: [2664473.186667] device veth86cb043 left promiscuous mode
          Jan 29 11:04:11 Server1 kernel: [2664473.186681] br-edbd4014078c: port 5(veth86cb043) entered disabled state
          Jan 29 11:04:12 Server1 kernel: [2664474.427682] br-edbd4014078c: port 3(vethf4ee1d4) entered disabled state
          Jan 29 11:04:12 Server1 kernel: [2664474.427918] veth86a96c5: renamed from eth0
          Jan 29 11:04:12 Server1 kernel: [2664474.477396] br-edbd4014078c: port 2(veth39cf04c) entered disabled state
          Jan 29 11:04:12 Server1 kernel: [2664474.477874] vethf309b04: renamed from eth0
          Jan 29 11:04:13 Server1 kernel: [2664474.545685] br-edbd4014078c: port 3(vethf4ee1d4) entered disabled state
          Jan 29 11:04:13 Server1 kernel: [2664474.551561] device vethf4ee1d4 left promiscuous mode
          Jan 29 11:04:13 Server1 kernel: [2664474.551576] br-edbd4014078c: port 3(vethf4ee1d4) entered disabled state
          Jan 29 11:04:13 Server1 kernel: [2664474.595118] br-edbd4014078c: port 2(veth39cf04c) entered disabled state
          Jan 29 11:04:13 Server1 kernel: [2664474.596504] device veth39cf04c left promiscuous mode
          Jan 29 11:04:13 Server1 kernel: [2664474.596516] br-edbd4014078c: port 2(veth39cf04c) entered disabled state
          Jan 29 11:04:14 Server1 kernel: [2664475.911158] br-edbd4014078c: port 1(veth6b48fa5) entered disabled state
          Jan 29 11:04:14 Server1 kernel: [2664475.911674] veth5cbeb55: renamed from eth0
          Jan 29 11:04:14 Server1 kernel: [2664475.960704] br-edbd4014078c: port 1(veth6b48fa5) entered disabled state
          Jan 29 11:04:14 Server1 kernel: [2664475.966880] device veth6b48fa5 left promiscuous mode
          Jan 29 11:04:14 Server1 kernel: [2664475.966895] br-edbd4014078c: port 1(veth6b48fa5) entered disabled state
          Jan 29 11:04:22 Server1 kernel: [2664484.107936] br-edbd4014078c: port 4(veth683c2f5) entered disabled state
          Jan 29 11:04:22 Server1 kernel: [2664484.108374] vethf5cbea0: renamed from eth0
          Jan 29 11:04:22 Server1 kernel: [2664484.157546] br-edbd4014078c: port 4(veth683c2f5) entered disabled state
          Jan 29 11:04:22 Server1 kernel: [2664484.160841] device veth683c2f5 left promiscuous mode
          Jan 29 11:04:22 Server1 kernel: [2664484.160854] br-edbd4014078c: port 4(veth683c2f5) entered disabled state
          Jan 29 11:22:29 Server1 kernel: [2665571.445517] br-edbd4014078c: port 1(veth4aec386) entered blocking state
          Jan 29 11:22:29 Server1 kernel: [2665571.445527] br-edbd4014078c: port 1(veth4aec386) entered disabled state
          Jan 29 11:22:29 Server1 kernel: [2665571.445770] device veth4aec386 entered promiscuous mode
          Jan 29 11:22:29 Server1 kernel: [2665571.505153] br-edbd4014078c: port 2(veth2a255f6) entered blocking state
          Jan 29 11:22:29 Server1 kernel: [2665571.505162] br-edbd4014078c: port 2(veth2a255f6) entered disabled state
          Jan 29 11:22:29 Server1 kernel: [2665571.505790] device veth2a255f6 entered promiscuous mode
          Jan 29 11:22:29 Server1 kernel: [2665571.518601] br-edbd4014078c: port 2(veth2a255f6) entered blocking state
          Jan 29 11:22:29 Server1 kernel: [2665571.518609] br-edbd4014078c: port 2(veth2a255f6) entered forwarding state
          Jan 29 11:22:29 Server1 kernel: [2665571.518998] br-edbd4014078c: port 2(veth2a255f6) entered disabled state
          Jan 29 11:22:29 Server1 kernel: [2665571.552743] br-edbd4014078c: port 3(vethaf13886) entered blocking state
          Jan 29 11:22:29 Server1 kernel: [2665571.552752] br-edbd4014078c: port 3(vethaf13886) entered disabled state
          Jan 29 11:22:29 Server1 kernel: [2665571.554815] device vethaf13886 entered promiscuous mode
          Jan 29 11:22:29 Server1 kernel: [2665571.555131] br-edbd4014078c: port 3(vethaf13886) entered blocking state
          Jan 29 11:22:29 Server1 kernel: [2665571.555137] br-edbd4014078c: port 3(vethaf13886) entered forwarding state
          Jan 29 11:22:29 Server1 kernel: [2665571.555590] br-edbd4014078c: port 3(vethaf13886) entered disabled state
          Jan 29 11:22:30 Server1 kernel: [2665571.606822] br-edbd4014078c: port 4(veth2223bee) entered blocking state
          Jan 29 11:22:30 Server1 kernel: [2665571.606831] br-edbd4014078c: port 4(veth2223bee) entered disabled state
          Jan 29 11:22:30 Server1 kernel: [2665571.607027] device veth2223bee entered promiscuous mode
          Jan 29 11:22:30 Server1 kernel: [2665571.607342] br-edbd4014078c: port 4(veth2223bee) entered blocking state
          Jan 29 11:22:30 Server1 kernel: [2665571.607347] br-edbd4014078c: port 4(veth2223bee) entered forwarding state
          Jan 29 11:22:30 Server1 kernel: [2665572.455928] br-edbd4014078c: port 4(veth2223bee) entered disabled state
          Jan 29 11:22:32 Server1 kernel: [2665573.589693] eth0: renamed from vethf5e03fb
          Jan 29 11:22:32 Server1 kernel: [2665573.649374] eth0: renamed from vethf0c6038
          Jan 29 11:22:32 Server1 kernel: [2665573.667658] eth0: renamed from veth1995f96
          Jan 29 11:22:32 Server1 kernel: [2665573.712825] IPv6: ADDRCONF(NETDEV_CHANGE): veth2223bee: link becomes ready
          Jan 29 11:22:32 Server1 kernel: [2665573.713118] br-edbd4014078c: port 4(veth2223bee) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665573.713124] br-edbd4014078c: port 4(veth2223bee) entered forwarding state
          Jan 29 11:22:32 Server1 kernel: [2665573.714903] IPv6: ADDRCONF(NETDEV_CHANGE): vethaf13886: link becomes ready
          Jan 29 11:22:32 Server1 kernel: [2665573.715122] br-edbd4014078c: port 3(vethaf13886) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665573.715129] br-edbd4014078c: port 3(vethaf13886) entered forwarding state
          Jan 29 11:22:32 Server1 kernel: [2665573.716337] IPv6: ADDRCONF(NETDEV_CHANGE): veth2a255f6: link becomes ready
          Jan 29 11:22:32 Server1 kernel: [2665573.716774] br-edbd4014078c: port 2(veth2a255f6) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665573.716782] br-edbd4014078c: port 2(veth2a255f6) entered forwarding state
          Jan 29 11:22:32 Server1 kernel: [2665573.717541] eth0: renamed from veth558de09
          Jan 29 11:22:32 Server1 kernel: [2665573.741959] IPv6: ADDRCONF(NETDEV_CHANGE): veth4aec386: link becomes ready
          Jan 29 11:22:32 Server1 kernel: [2665573.742249] br-edbd4014078c: port 1(veth4aec386) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665573.742260] br-edbd4014078c: port 1(veth4aec386) entered forwarding state
          Jan 29 11:22:32 Server1 kernel: [2665574.169423] br-edbd4014078c: port 5(vethffa23f9) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665574.169432] br-edbd4014078c: port 5(vethffa23f9) entered disabled state
          Jan 29 11:22:32 Server1 kernel: [2665574.173953] device vethffa23f9 entered promiscuous mode
          Jan 29 11:22:32 Server1 kernel: [2665574.174386] br-edbd4014078c: port 5(vethffa23f9) entered blocking state
          Jan 29 11:22:32 Server1 kernel: [2665574.174392] br-edbd4014078c: port 5(vethffa23f9) entered forwarding state
          Jan 29 11:22:32 Server1 kernel: [2665574.502871] br-edbd4014078c: port 5(vethffa23f9) entered disabled state
          Jan 29 11:22:33 Server1 kernel: [2665575.448654] eth0: renamed from veth45947d1
          Jan 29 11:22:33 Server1 kernel: [2665575.479261] IPv6: ADDRCONF(NETDEV_CHANGE): vethffa23f9: link becomes ready
          Jan 29 11:22:33 Server1 kernel: [2665575.479584] br-edbd4014078c: port 5(vethffa23f9) entered blocking state
          Jan 29 11:22:33 Server1 kernel: [2665575.479591] br-edbd4014078c: port 5(vethffa23f9) entered forwarding state
          Jan 29 22:26:04 Server1 kernel: [2705386.167132] uhci_hcd 0000:00:01.2: host controller halted, very bad!
          Jan 29 22:26:04 Server1 kernel: [2705386.168306] uhci_hcd 0000:00:01.2: HC died; cleaning up
          Jan 29 22:26:04 Server1 kernel: [2705386.168843] usb 1-2: USB disconnect, device number 2
          Jan 30 00:00:35 Server1 kernel: [2711057.357727] audit: type=1400 audit(1738224035.619:59): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4011142 comm="cupsd" capability=12 capname="net_admin"
          Jan 30 00:00:35 Server1 kernel: [2711057.537107] audit: type=1400 audit(1738224035.795:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=4011144 comm="cups-browsed" capability=23 capname="sys_nice"

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

            @mrchip Could you post the contents of /var/log/{xensource,daemon}.log on the host (as well as their .1 version) as well? They're pretty big, so you'll have to upload them somewhere.

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              mrchip @dinhngtu
              last edited by

              @dinhngtu sent u a dm with a link to the files

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