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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team @Ultra2D
      last edited by

      @Ultra2D so you mean that installing the updated packages would "break" the first migration of such a VM unless it's been rebooted once? If that is so, then I'd advise to revert to the previous version (or to make sure not to attempt a migration without power cycling the VMs once). Else, your choice. If the updated packages bring a benefit to you, you can keep them, else revert to the previous ones.

      U 1 Reply Last reply Reply Quote 0
      • U Offline
        Ultra2D @stormi
        last edited by

        @stormi I only tested with one VM. It crashed a couple of times when the pool master had updates from xcp-ng-updates_testing and the slaves had the updates that were released yesterday. After updating the last remaining slave to updates from xcp-ng-updates_testing, moving the VM resulted in a stuck VM. So I don't think you can draw any conclusions from this, except maybe that you should install the same version on master and slaves.

        1 Reply Last reply Reply Quote 0
        • stormiS Offline
          stormi Vates 🪐 XCP-ng Team
          last edited by

          Xen security updates pushed to everyone (7.6 yesterday, 7.5 today).
          Blog post: https://xcp-ng.org/blog/2019/03/12/xcp-ng-security-bulletin-vulnerabilities-pv-guests/

          1 Reply Last reply Reply Quote 0
          • C Offline
            codedmind
            last edited by

            I'm getting an error

            
            Running transaction test
            
            
            Transaction check error:
              installing package xen-dom0-tools-4.7.6-6.4.1.xcpng.x86_64 needs 1 inodes on the /var/log filesystem
            
            
            stormiS 1 Reply Last reply Reply Quote 0
            • stormiS Offline
              stormi Vates 🪐 XCP-ng Team @codedmind
              last edited by

              @codedmind This is probably related to a bug in the openvswitch package and log rotation. We sent a newsletter about it a few days ago: https://mailchi.mp/7ed52f9a2151/important-noticeopenvswitch-issue

              1 Reply Last reply Reply Quote 0
              • C Offline
                codedmind
                last edited by

                Humm ok... but i cannot update... yes i have that version.. but as i cannot up date how can i solve it?

                stormiS 1 Reply Last reply Reply Quote 0
                • stormiS Offline
                  stormi Vates 🪐 XCP-ng Team @codedmind
                  last edited by stormi

                  @codedmind when it got to the point that you ran out of inodes in /var/log, you need to remove some files before you can update. find /var/log -name ovsdb-server.log.*.gz -delete should work (untested, try without -delete first). Else look at the other threads that covered the subject.

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    codedmind
                    last edited by

                    Ok thanks!

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      rechotech
                      last edited by rechotech

                      Does the openvswitch bug cause the local storage to fill up, or just the log file?
                      Would this openvwswitch potential lead our XCP server to crash?

                      1 Reply Last reply Reply Quote 0
                      • stormiS Offline
                        stormi Vates 🪐 XCP-ng Team
                        last edited by stormi

                        Local storage is not touched. Only the /var/log partition, or the / partition if you have no /var/log partition. In the latter case, I suppose this could hang or crash the server. In the former case, it prevents some new tasks to be performed, but we haven't had reports of crashing servers at this stage.

                        R 1 Reply Last reply Reply Quote 0
                        • R Offline
                          rechotech @stormi
                          last edited by

                          since this is unlikely the cause of our crash, where would you suggest we look to determine why our xcp servers crashed a few days ago?

                          1 Reply Last reply Reply Quote 0
                          • stormiS Offline
                            stormi Vates 🪐 XCP-ng Team
                            last edited by

                            I suggest opening a dedicated thread with as much information as possible.

                            1 Reply Last reply Reply Quote 0
                            • stormiS Offline
                              stormi Vates 🪐 XCP-ng Team
                              last edited by

                              As a starting point, see https://github.com/xcp-ng/xcp/wiki/Logfiles and look for whatever happened by the time of the crashes, if logging was still operational at that moment.

                              1 Reply Last reply Reply Quote 0
                              • stormiS Offline
                                stormi Vates 🪐 XCP-ng Team
                                last edited by

                                For XCP-ng 7.6 only

                                New security update for the latest Intel CPU vulnerabilities:

                                http://xenbits.xen.org/xsa/advisory-297.html

                                Install it with:

                                yum update --enablerepo='xcp-ng-updates_testing' microcode_ctl-2.1-26.xs5.x86_64 xen-dom0-libs-4.7.6-6.5.1.xcpng.x86_64 xen-dom0-tools-4.7.6-6.5.1.xcpng.x86_64 xen-hypervisor-4.7.6-6.5.1.xcpng.x86_64 xen-libs-4.7.6-6.5.1.xcpng.x86_64 xen-tools-4.7.6-6.5.1.xcpng.x86_64
                                

                                There's nothing fancy in the way the updates were built so no breakage is expected, but we still need feedback from early-adopters before we push them to everyone.

                                Reboot required.

                                Downgrade if needed with:

                                yum downgrade microcode_ctl xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools
                                

                                What to test:

                                • basic functions of the hypervisor, VMs...

                                Read the advisory carefully: installing the updates is not enough. There are other steps to be taken for complete protection.

                                Citrix announcement: https://support.citrix.com/article/CTX251995

                                M borzelB rizaemet 0R 3 Replies Last reply Reply Quote 0
                                • U Offline
                                  Ultra2D
                                  last edited by

                                  @stormi said in Updates announcements and testing:

                                  yum update --enablerepo='xcp-ng-updates_testing' microcode_ctl-2.1-26.xs5.x86_64 xen-dom0-libs-4.7.6-6.5.1.xcpng.x86_64 xen-dom0-tools-4.7.6-6.5.1.xcpng.x86_64 xen-hypervisor-4.7.6-6.5.1.xcpng.x86_64 xen-libs-4.7.6-6.5.1.xcpng.x86_64 xen-tools-4.7.6-6.5.1.xcpng.x86_64

                                  Should the pool master be updated first? Or it doesn't matter for there updates?

                                  stormiS 2 Replies Last reply Reply Quote 0
                                  • stormiS Offline
                                    stormi Vates 🪐 XCP-ng Team @Ultra2D
                                    last edited by stormi

                                    @Ultra2D Yes, always the pool master first.

                                    1 Reply Last reply Reply Quote 0
                                    • stormiS Offline
                                      stormi Vates 🪐 XCP-ng Team @Ultra2D
                                      last edited by

                                      @Ultra2D Technically, some updates could be installed in any order, but it's safer and simpler to consider that master is always updated first.

                                      U 1 Reply Last reply Reply Quote 0
                                      • U Offline
                                        Ultra2D @stormi
                                        last edited by

                                        @stormi Sure, but I'd rather test on a pool member first if trying as an early adopter 😉 .

                                        stormiS 1 Reply Last reply Reply Quote 0
                                        • stormiS Offline
                                          stormi Vates 🪐 XCP-ng Team @Ultra2D
                                          last edited by

                                          @Ultra2D For this update, I think you could try with a slave first, since it's only an update of xen (and microcode_ctl), so I don't expect incompatibilities in pool management. But I wouldn't guarantee that cross-host operations such as migrations would work fine.

                                          U 1 Reply Last reply Reply Quote 0
                                          • U Offline
                                            Ultra2D @stormi
                                            last edited by

                                            @stormi I'll try it on a master, no worries. But not on a Friday.

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