XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    XCP-ng 7.5.0 final is here

    Development
    15
    74
    19318
    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.
    • sriccio
      sriccio @stormi last edited by

      @stormi Okay, crystal clear thanks.

      1 Reply Last reply Reply Quote 0
      • txsastre
        txsastre last edited by

        Thanks.

        Gonna install it from scratch on the 3 develop servers.

        1 Reply Last reply Reply Quote 0
        • D
          dsiminiuk last edited by

          Used Rufus to install the ISO to USB.
          Booted, upgraded pool master from 7.4.
          Tried to migrate all running VMs from the 2nd host (server1) to the pool master (server2) to apply the upgrade to server1.
          2 VMs wouldn't migrate. Forcibly shutdown, now they are stuck as "Starting VM on server2..." not completing.
          1 VM can't start "The operation cannot be performed because the specified virtual disk could not be found."

          Upgrading from Xenserver 7.3 to XCP-ng 7.4 was cleaner.

          F 1 Reply Last reply Reply Quote 0
          • olivierlambert
            olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

            Double check your shared SR is connected on all host.

            D 1 Reply Last reply Reply Quote 0
            • D
              dsiminiuk @olivierlambert last edited by

              @olivierlambert It is. Reconnecting all the SRs was the first thing you're presented with after the upgrade. Even the local filesystem and DVD needed to be repaired.

              After a reboot and a "PANIC on CPU 0", I did a cold shutdown. All VMs start now except the one that can't find the VDI, yet I can detach and reattach the VDI in XCP-ng Center.

              1 Reply Last reply Reply Quote 0
              • olivierlambert
                olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

                😨 that's… strange. Could it be a hardware issue? Panic on a CPU is not commong.

                D 1 Reply Last reply Reply Quote 0
                • G
                  GregW last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • D
                    dsiminiuk @olivierlambert last edited by

                    @olivierlambert The VDIs are over shared ISCSI on FreeNAS VDEVs. There are other VMs with VDIs on the same RAID10 LUN that are running fine.

                    It's actually 2 VDIs and I moved both (boot and swap) of the failed VM to an alternate RAID5 LUN and it made no difference.

                    Is there a log I should be looking in to see more detail?

                    1 Reply Last reply Reply Quote 0
                    • olivierlambert
                      olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

                      Check the /var/log/xensource.log and SMlog about this VDI error.

                      Again, a PANIC on CPU 0 isn't a good news regarding your hardware.

                      1 Reply Last reply Reply Quote 0
                      • txsastre
                        txsastre last edited by

                        well installed from scratch on my 3 servers
                        everything fine, but, when trying to activate HA it gives me an error. The same when I upgraded 7.4.1 to 7.5 RC.

                        3 hosts are connected via HBA to a one Storage on a fibre channel.

                        tried to connect only 2 hosts with a few combinations (host1 and host2, host1 and host3, host2 and host3), also trying to configure HA with one host (yep little strange) it gave me the same error.

                        0_1533928426464_SelecciΓ³_006.jpg

                        1 Reply Last reply Reply Quote 0
                        • olivierlambert
                          olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

                          Please provide real logs and not just a XCP-ng screenshot πŸ™‚

                          How did you enable HA by the way?

                          txsastre 1 Reply Last reply Reply Quote 0
                          • D
                            dsiminiuk last edited by

                            The CPU PANIC was on server1 (not pool master) so I've shut it down and I'll do a fresh install there later. It won't even show me the NICs that I know are there. Might be a hardware problem indeed.

                            I left all VMs powered down and tried to capture SMlog and xensource.log for the duration of the startup failure event.

                            I see "Raised Server_error(SESSION_INVALID," but have no idea if this is related to the error.
                            I don't have privs to upload the files.

                            1 Reply Last reply Reply Quote 0
                            • olivierlambert
                              olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

                              Use pastebin or hastebin to put your logs there πŸ™‚

                              SESSION INVALID is not related

                              1 Reply Last reply Reply Quote 0
                              • D
                                dsiminiuk last edited by

                                xensource.log https://cloud.k5rwk.org/index.php/s/BjJBBFxcg9EkknP
                                SMlog https://cloud.k5rwk.org/index.php/s/YxCYjAKRgcYgmKn

                                1 Reply Last reply Reply Quote 0
                                • borzel
                                  borzel XCP-ng Center Team 🏚️ last edited by borzel

                                  😞 VDI_MISSING

                                  xensource.log:500

                                  Aug 10 14:58:43 xs2 xenopsd-xc: [error|xs2|15 |Parallel:task=50.atoms=1.(VBD.plug RO vm=67bd9da9-9cb7-1882-9ad4-68e65e6095a2)|xenops] Re-raising exception VDI_MISSING: OpaqueRef:fa60f4c9-7095-35d7-6c91-2436713508a0; OpaqueRef:e08c2398-4e43-4cdd-af5b-41926a5f9d76
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dsiminiuk last edited by

                                    Well, I detached the VDIs, deleted the VM, created a new one, attached the VDIs and it booted up. This is solved for me, but I don't know the root cause.

                                    1 Reply Last reply Reply Quote 0
                                    • borzel
                                      borzel XCP-ng Center Team 🏚️ last edited by

                                      Yehaa! πŸ™‚
                                      I hope you had a backup if it had not worked πŸ”™ πŸ†™

                                      1 Reply Last reply Reply Quote 0
                                      • txsastre
                                        txsastre @olivierlambert last edited by

                                        @olivierlambert sorry. Where can i get them from?
                                        I tried to enable HA as always using xcp-ng center.

                                        1 Reply Last reply Reply Quote 0
                                        • olivierlambert
                                          olivierlambert Vates πŸͺ Admin πŸ§‘β€πŸ’» last edited by

                                          Same as @dsiminiuk xensource and SMlog πŸ™‚

                                          txsastre 1 Reply Last reply Reply Quote 0
                                          • D
                                            dsiminiuk last edited by

                                            I've installed from CDROM a new clean install of 7.5 and had all my VMs running. I added the 2nd host to the pool and migrated some of the VMs from the pool master to the 2nd server fine. One however, abended with a XenOpts error (don't have the details now). And the VM that was powered off while transferring and now it won't start. Status is "Starting VM..." for 10+ minutes now.
                                            Something's not quite right here.

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