1. Home
  2. Popular
Log in to post
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    588
    1 Votes
    588 Posts
    295k Views
    acebmxerA
    @TeddyAstie said: @acebmxer said: @rzr Just installed updates on host 1. Once host rebooted it took an extra min or two to reconnect to xo, but did finally connect. Applying updates on host 2 now. Update - host2 no issues. Once reboot complete it connected to xo as expected without delay. I see these updates include - xen: Add support for xenpm get-core-temp to query CPU temperature on Intel platforms. Use xenpm get-core-temp to get the temperature on Intel's CPU, to fallback unsupported coretemp. Doc update being reviewed . My host are AMD so can verify these. I might be able to deploy a Intel host later tonight. Will this come to AMD later? AMD rely on a different method to expose the temperature, that don't require this xenpm-based approach. In principle, it should already work with plain sensors (through k10temp), but our driver may not be up to date for recent AMD CPUs. From AMD 7950x [17:51 xcp-ng-haznrrtw ~]# xenpm get-core-temp [Package0] Unable to fetch temperature (61 - No data available) [CPU0] Unable to fetch temperature (61 - No data available) [CPU2] Unable to fetch temperature (61 - No data available) [CPU4] Unable to fetch temperature (61 - No data available) [CPU6] Unable to fetch temperature (61 - No data available) [CPU8] Unable to fetch temperature (61 - No data available) [CPU10] Unable to fetch temperature (61 - No data available) [CPU12] Unable to fetch temperature (61 - No data available) [CPU14] Unable to fetch temperature (61 - No data available) [CPU16] Unable to fetch temperature (61 - No data available) [CPU18] Unable to fetch temperature (61 - No data available) [CPU20] Unable to fetch temperature (61 - No data available) [CPU22] Unable to fetch temperature (61 - No data available) [CPU24] Unable to fetch temperature (61 - No data available) [CPU26] Unable to fetch temperature (61 - No data available) [CPU28] Unable to fetch temperature (61 - No data available) [CPU30] Unable to fetch temperature (61 - No data available) Intel 13700k [17:50 xcp-ng-kulwlwbp ~]# xenpm get-core-temp Package0: 28°C CPU0: 26°C CPU2: 23°C CPU4: 23°C CPU6: 25°C CPU8: 25°C CPU10: 24°C CPU12: 23°C CPU14: 25°C CPU16: 24°C CPU18: 24°C CPU20: 28°C CPU22: 28°C
  • jgraftonJ

    CPU pegged at 100% in several Rocky Linux 8 VMs without workload in guest

    Compute
    28
    0 Votes
    28 Posts
    4k Views
    jgraftonJ
    @laszlobortel Hehe yeah, those are pretty old kernels. I'd say there's a good chance kernel upgrades will go a long way to alleviating the CPU hangs. I can't say it's exclusively a problem with lvmohba storage, that's just what we use because of our previous VMware infrastructure was block storage over fiber channel. We knew a physical infra overhaul wasn't in the cards for us for this migration so we stayed with our existing storage system. This bug bit us half way through the migration until we figured out upgrading the kernel generally fixed it.
  • henri9813H

    Slow boot on rocky linux 10 latest kernel

    Compute
    25
    2
    0 Votes
    25 Posts
    684 Views
    henri9813H
    Hello, Thanks for all !
  • D

    Slow response between XCP-NG and cloud stack syncing

    Compute
    2
    0 Votes
    2 Posts
    60 Views
    olivierlambertO
    Hi, XCP-ng got an event system that will propagate things like this instantly, at least that's the way it works normally Do you have the same behaviour in Xen Orchestra? Have you reported the issue to CloudStack? If you have an XCP-ng support subscription, you can also open a ticket so we can take a look on XCP-ng status to catch any obvious issue.
  • M

    xe sr-create ignores other-config:auto-scan=true during SR creation

    Compute
    4
    0 Votes
    4 Posts
    147 Views
    M
    @psafont Thanks for the quick response and clarification. I appreciate you opening a work item for this. Looking forward to seeing this improvement in a future release.
  • H

    Performing automated shutdown during a power failure using a USB-UPS with NUT - XCP-ng 8.2

    Compute
    33
    0 Votes
    33 Posts
    28k Views
    S
    For people running XCP-ng, wanting to use NUT client to power down gracefully during longer power outages, it could be interesting to note that Unifi now has two very affordable UPS models that feature a built in NUT server. So no need to run your own NUT server.
  • itservicesI

    XO Backup Error: VDI_IN_USE(OpaqueRef:.., destroy)

    Backup
    16
    2
    0 Votes
    16 Posts
    490 Views
    itservicesI
    Quick Update: Was looking good with commit cf26d. After the transfer completed the VDI of that particular VM was still in use, according to XO. So still failure on the job. Regards, Marc
  • E

    TrueNAS VM failing to start

    Compute
    22
    0 Votes
    22 Posts
    2k Views
    E
    Wearing my best Lazarus cosplay outfit, I'll apologise for the resurrection. Today I had an issue with my UPS which caused me to reboot XCP a few times. During those reboots I had at least 2, maybe 3, re-occurrences of this where when TrueNAS was booting, XCP would lock up. Most of the time, after a power cycle of the server, the next boot would start TRUENAS cleanly. One time it took 2 power cycles before success. Unfortunately only one of the crashes resulted in a /var/crash report, but that did have the same symptoms as my original report: (XEN) [ 81.101362] Non-responding CPUs: {24-47} (XEN) [ 81.101363] (XEN) [ 81.101364] **************************************** (XEN) [ 81.101365] Panic on CPU 5: (XEN) [ 81.101366] FATAL TRAP: vec 2, NMI[0000] IN INTERRUPT CONTEXT (XEN) [ 81.101366] **************************************** (XEN) [ 81.101367] (XEN) [ 81.101368] Reboot in five seconds... (XEN) [ 81.101369] Executing kexec image on cpu5 (XEN) [ 82.101441] Failed to shoot down CPUs {24-47} Between my original report and today, I have rebooted other times, following updates, when this issue has not surfaced. Does anyone think this could be hardware related, despite all the memory testing and stress testing I did when I built the server and again after the original issue, all with no faults. Or have I just got an unlucky set of circumstances with some sort of race condition.