XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • jgraftonJ

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

      Watching Ignoring Scheduled Pinned Locked Moved 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

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      25
      2
      0 Votes
      25 Posts
      664 Views
      henri9813H
      Hello, Thanks for all !
    • D

      Slow response between XCP-NG and cloud stack syncing

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      2
      0 Votes
      2 Posts
      55 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.
    • T

      Xen 8.2 isos

      Watching Ignoring Scheduled Pinned Locked Moved Off topic
      2
      0 Votes
      2 Posts
      36 Views
      TeddyAstieT
      @TrapoSAMA https://updates.xcp-ng.org/isos/8.2/ And https://updates.xcp-ng.org/8/8.2/ appears fine.
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      584
      1 Votes
      584 Posts
      294k Views
      rzrR
      New maintenance update candidates for XCP-ng 8.3 LTS This release batch contains mostly fixes, tools version update, a some improvements. Note: the previous batch of updates has not been released yet, so if you haven't tested it, you will see more updates than described here when you'll install the update candidates. Refer to the previous announcements. What changed Virtualization & System 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. grub: Sync with XenServer 8.4: Fix a rare out-of-memory error. dracut: Fixes Fix to force reboot/shutdown/halt. Fix issue where the omission of 'override' kernel modules from the initrd image could, in rare instances, prevent a freshly installed XCP-ng host from booting. Control Plane xapi: Update to 25.1.11, add fixes and improvements. Fixed an issue where a newly installed host wouldn't be able to join a pool due to incompatible features exposed by storage. Fix shutdown VMs not being migratable due to errors generated when the VM was running. Allow moving VMs back to DHCP from static IP with configure_ipv4/6. Network stunnel: Fixed stunnel only considering one of the self-signed certificates with the same DN. Tools xcp-ng-pv-tools: Update to XCP-ng Windows Guest Tools 9.1.200 (full changelog). Drivers mpi3mr-module: Update to version 8.17.1, adding newly supported SAS5116 devices. Optional: mellanox-mlnxen-alt: Fix build error with kernel 4.19.19-8.0.42.1+. Storage kmod-drbd: Update to 9.2.18 (full changelog) Improve XOSTOR stabilty when evacuating/evicting an host. xcp-ng-release-linstor: Relocate config file to v8.3-linstor repository. Versions dracut: 033-538.xcpng8.3 -> 033-539.1.xcpng8.3 gpumon: 24.1.0-84.1.xcpng8.3 -> 24.1.0-91.1.xcpng8.3 grub: 1:2.06-4.0.2.1.xcpng8.3 -> 1:2.06-4.0.5.1.xcpng8.3 mpi3mr-module: 8.6.1.0.0-1.xcpng8.3 -> 8.17.1.0.0-1.xcpng8.3 stunnel: 5.60-5.xcpng8.3 -> 5.60-6.1.xcpng8.3 xapi: 26.1.4-3.2.xcpng8.3 -> 26.1.11-1.1.xcpng8.3 xcp-featured: 1.2.1-1.xcpng8.3 -> 1.2.1-2.xcpng8.3 xcp-ng-pv-tools: 8.3-17.xcpng8.3 -> 8.3-18.xcpng8.3 xen: 4.17.6-9.1.xcpng8.3 -> 4.17.6-9.3.xcpng8.3 Optional packages: mellanox-mlnxen-alt: 5.4_1.0.3.0-2.xcpng8.3 -> 5.4_1.0.3.0-3.xcpng8.3 XOSTOR users: specific update procedure Some XOSTOR packages are provided in separate repository, and should be installed along xcp-ng regular packages, using the following commands: yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing reboot Note: linstor packages themselves have not been updated, only kmod-drbd and xcp-ng-release-linstor. Thus, this time it's not necessary to restart the satellites before rebooting. The following XOSTOR-specific package received updates (and must be updated in the same transaction, which the above update commands will do): xcp-ng-release-linstor: 1.4-2.xcpng8.3 -> 1.5-1.xcpng8.3 (from xcp-ng-testing repo) kmod-drbd: 9.2.16-1.0.xcpng8.3 -> 9.2.18-2.0.xcpng8.3 (from xcp-ng-linstor-testing repo) Test on XCP-ng 8.3 Warning: XOSTOR users should skip this part and follow the instructions of the previous section. yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot The usual update rules apply: pool coordinator first, etc. What to test As usual, normal use and anything else you want to test. Test window before official release of the updates ~2 days We would like to thank users who reported feedback since our last call for testing: @Andrew, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro, @jeffberntsen, @majorp93, @manilx, @marcoi, @ph7.
    • M

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

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      4
      0 Votes
      4 Posts
      145 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

      Watching Ignoring Scheduled Pinned Locked Moved 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)

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      16
      2
      0 Votes
      16 Posts
      480 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

      Watching Ignoring Scheduled Pinned Locked Moved 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.