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

    XCP-ng 8.2 updates announcements and testing

    Scheduled Pinned Locked Moved News
    703 Posts 67 Posters 1.1m Views 86 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.
    • J Offline
      jmccoy555
      last edited by jmccoy555

      Only updated one host in my pool so far, but it has my TrueNAS VM and network performance looks comparable ⭐

      edit:

      Actually quite an improvement in comparison to my results above

      root@FILE001:~ # iperf -c 10.10.1.126
      ------------------------------------------------------------
      Client connecting to 10.10.1.126, TCP port 5001
      TCP window size: 80.8 KByte (default)
      ------------------------------------------------------------
      [  3] local 10.10.1.125 port 35576 connected with 10.10.1.126 port 5001
      [ ID] Interval       Transfer     Bandwidth
      [  3]  0.0-10.1 sec  6.30 GBytes  5.36 Gbits/sec
      root@FILE001:~ # iperf -s
      ------------------------------------------------------------
      Server listening on TCP port 5001
      TCP window size: 64.0 KByte (default)
      ------------------------------------------------------------
      [  4] local 10.10.1.125 port 5001 connected with 10.10.1.126 port 54773
      [ ID] Interval       Transfer     Bandwidth
      [  4]  0.0-10.0 sec  3.57 GBytes  3.06 Gbits/sec
      
      

      Also done a VM reboot now and no passthrough issues πŸ˜„

      1 Reply Last reply Reply Quote 3
      • stormiS Offline
        stormi Vates πŸͺ XCP-ng Team
        last edited by

        Just in time πŸ™‚

        Updates now published: https://xcp-ng.org/blog/2021/04/01/april-2021-1st-security-bugfixe-update/

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jmccoy555 @stormi
          last edited by

          @stormi Security updates on April 1st 🀣

          stormiS 1 Reply Last reply Reply Quote 2
          • stormiS Offline
            stormi Vates πŸͺ XCP-ng Team @jmccoy555
            last edited by

            @jmccoy555 Yeah. Install them today and they'll turn your hosts into VMware.

            J 1 Reply Last reply Reply Quote 1
            • J Offline
              jmccoy555 @stormi
              last edited by

              @stormi Isn't that a virus, not a bug fix????

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates πŸͺ Co-Founder CEO
                last edited by

                πŸ˜†

                1 Reply Last reply Reply Quote 0
                • BenjiReisB Offline
                  BenjiReis Vates πŸͺ XCP-ng Team
                  last edited by BenjiReis

                  New xsconsole fix to test for 8.2

                  New update candidate are available for testing and due to be released as official updates.

                  Original topic:

                  • https://xcp-ng.org/forum/topic/3886/xcp-ng-8-2-dns-settings-gone-after-reboot
                  • https://xcp-ng.org/forum/topic/3277/dns-config-on-8-1-hosts-disappearing
                  yum clean metadata --enablerepo=xcp-ng-testing
                  yum update xsconsole --enablerepo=xcp-ng-testing
                  systemctl restart xsconsole.service 
                  

                  What to test

                  Changing the DNS settings from the XSConsole and the change is retain after a reboot.

                  stormiS 1 Reply Last reply Reply Quote 2
                  • stormiS Offline
                    stormi Vates πŸͺ XCP-ng Team @BenjiReis
                    last edited by

                    @benjireis said in Updates announcements and testing:

                    What to test

                    Changing the DNS settings from the XSConsole and the change is retain after a reboot.

                    And, of course, as usual, that you don't notice any obvious regression in XSConsole.

                    gskgerG 1 Reply Last reply Reply Quote 1
                    • gskgerG Offline
                      gskger Top contributor @stormi
                      last edited by gskger

                      @stormi Did not even know the problem existed πŸ˜‡ . Anyway, added a new (second) DNS server (9.9.9.9) to the DNS server list via xsconsole and rebooted the host (XCP-ng 8.2.0 fully patched).

                      Before update: DNS 9.9.9.9 did not persist, only the previous settings are shown
                      After update: DNS 9.9.9.9 did persist the reboot and is listed together with the previous settings

                      Deleting DNS 9.9.9.9 worked as well, so the xsconsole update worked for me.

                      BenjiReisB 1 Reply Last reply Reply Quote 4
                      • olivierlambertO Offline
                        olivierlambert Vates πŸͺ Co-Founder CEO
                        last edited by olivierlambert

                        IIRC, it's on old problem reported a long time ago to Citrix. But they never fixed it.

                        edit: and thanks again @gskger for your tests, it matters a lot!

                        gskgerG 1 Reply Last reply Reply Quote 2
                        • gskgerG Offline
                          gskger Top contributor @olivierlambert
                          last edited by

                          @olivierlambert as always, it is a pleasure to help and also easy to do and to contribute. Oh and @BenjiReis - sorry for not replying to your initial post.

                          1 Reply Last reply Reply Quote 1
                          • BenjiReisB Offline
                            BenjiReis Vates πŸͺ XCP-ng Team @gskger
                            last edited by

                            @gskger Thanks for the report! πŸ˜„

                            1 Reply Last reply Reply Quote 0
                            • BenjiReisB Offline
                              BenjiReis Vates πŸͺ XCP-ng Team
                              last edited by BenjiReis

                              Experimental feature: select a network to evacuate an host
                              A new feature is available in our testing repo: select a network for host evacuation, this would allow to evacuate an host on any (faster) given network instead of the management one.

                              To access the feature, on all your hosts (always starting with master when in a pool):
                              yum update --enablerepo=xcp-ng-testing xapi-core-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-xe-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-tests-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64
                              And restart your hosts.

                              WHAT TO TEST
                              Host evacuation not on the management network (probably a 10G storage network to go faster!)
                              You can run xe host-evacuate host=<host_uuid> network-uuid=<network_uuid>
                              Or a XAPI client can call host.evacuate with a network ref parameter.
                              Host evacuation without the optionnal new parameter should behave as before the update.

                              Please report here if anything goes wrong (or right hopefully πŸ™‚ ) and if you spot a regression as well.

                              Thanks!

                              Edit: there are no plans for now to add this feature in 8.2 LTS, the package will probably stay in the testing repo for 8.2 and will be available in 8.3. It means that the package would be erased at next xapi update.

                              gskgerG V 2 Replies Last reply Reply Quote 1
                              • stormiS Offline
                                stormi Vates πŸͺ XCP-ng Team
                                last edited by

                                Up! Poor @BenjiReis needs some feedback πŸ˜„

                                1 Reply Last reply Reply Quote 1
                                • gskgerG Offline
                                  gskger Top contributor @BenjiReis
                                  last edited by

                                  @benjireis Had some time for testing and installed the update on my two host playlab (DELL Optiplex 9010, XCP-ng 8.2.0 fully pathed). This are identical hosts with an onboard NIC (Intel 82579LM, eth0) and a dual port NIC (Intel 82571EB/82571GB, eth1 and eth2). Both are connected to a Synology as shared storage.

                                  • Starting with the master, both hosts updated and rebooted without an issue.
                                  • Live migration of Debian, Ubuntu, Centos and Windows 10 VMs works (with and without guest tools installed).
                                  • Host evacuation over eth0 (Management network) without the new network-uuid parameter works as before.
                                  • Host evacuation over eth1 (Storage network) with the new parametrer works at full gigabit speed.

                                  Still working on 10G in my playlab, so i only have 1G available, but host evacuation over a non- management network works with the new network-uuid parameter.

                                  BenjiReisB 1 Reply Last reply Reply Quote 2
                                  • BenjiReisB Offline
                                    BenjiReis Vates πŸͺ XCP-ng Team @gskger
                                    last edited by

                                    @gskger Thanks for the report! This is greatly appreciated! πŸ˜„

                                    1 Reply Last reply Reply Quote 0
                                    • stormiS Offline
                                      stormi Vates πŸͺ XCP-ng Team
                                      last edited by

                                      New update candidates for 8.2, including guest SecureBoot support

                                      Several update candidates are ready for testing.

                                      Description of the changes

                                      • The updated uefistored brings guest SecureBoot support. The number one priority it to check that UEFI VMs still work well in various situations (including backups, restore from older backups, fresh install after the update was installed...). For SecureBoot support itself, usage detailed at https://github.com/xcp-ng/xcp-ng-org/pull/85/files currently until we merge the instructions to the official docs. We'll create a dedicated thread to discuss this feature.
                                      • Updated XAPI brings the latest fixes from Citrix hotfix XS82E020.
                                      • Updated storage manager (sm) brings the latest fixes from Citrix hotfix XS82E023 as well as a fix for a minor regression this hotfix brought (detected by @ronan-a and reported upstream with a patch proposal), an experimental MooseFS driver contributed by the MooseFS developers (not enabled by default), and a fix for NFS SR creation with some QNAP devices (contributed upstream, to the sm project, but still waiting for review after ~4 months).
                                      • Updated xsconsole fixes DNS settings management: when changed from the text UI, DNS settings were not saved to the XAPI and were thus lost after a reboot (not contributed upstream], because there's no public git repository for XSConsole unfortunately).
                                      • Updated blktap fixes a rare crash in specific situations.
                                      • Updated guest tools ISO brings support for new OSes and versions, such as CentoS 8.3+ & Stream, AlmaLinux, Rocky Linux, fixed installation on FreePBX... Those have already been tested in this thread but more tests are always welcome.

                                      How to update (XCP-ng 8.2 only)

                                      yum update blktap forkexecd message-switch rrdd-plugins sm sm-rawhba uefistored xapi-core xapi-tests xapi-xe xcp-ng-pv-tools xcp-ng-release xcp-ng-release-config xcp-ng-release-presets xenopsd xenopsd-cli xenopsd-xc xsconsole --enablerepo=xcp-ng-testing
                                      

                                      What to test

                                      The main goal of the testing phase is to avoid regressions, so test whatever you want. The closer to your actual use of XCP-ng, the better.

                                      If interested, you can also test that what we claim we have fixed is actually fixed, and have a go at guest Secure Boot.

                                      beshleman opened this pull request in xcp-ng/xcp-ng-org

                                      closed Guest secure boot #85

                                      M gskgerG X 3 Replies Last reply Reply Quote 0
                                      • V Offline
                                        vmpr @BenjiReis
                                        last edited by

                                        @benjireis today I tested it but didn't reboot the host, was working after a toolstack restart. please integrate it into 8.2 LTS, a very useful feature, and we want to stay at 8.2 LTS. πŸ‘

                                        1 Reply Last reply Reply Quote 0
                                        • M Offline
                                          MartinB @stormi
                                          last edited by

                                          @stormi can you please tell us more about this moosefs driver?

                                          Regards,

                                          Martin

                                          1 Reply Last reply Reply Quote 0
                                          • stormiS Offline
                                            stormi Vates πŸͺ XCP-ng Team
                                            last edited by

                                            @martinb Not much. I'm waiting for the developers of MooseFS to contribute documentation about how to use it.

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