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

    Control domain of Xcp-ng

    Scheduled Pinned Locked Moved Xen Orchestra
    16 Posts 4 Posters 1.6k Views 3 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.
    • S Offline
      sumansaha
      last edited by

      Would be great to know the purpose of the control domain.It looks its related to the snapshot. Want to know more details on this . Screenshot 2022-12-21 at 12.30.07 AM.png

      DarkbeldinD 1 Reply Last reply Reply Quote 0
      • DarkbeldinD Offline
        Darkbeldin Vates 🪐 Pro Support Team @sumansaha
        last edited by

        @sumansaha When you do a backup the snapshot needs to be downloaded by Xen orchestra, for that this snapshot is first exposed by your dom0 through an http link, that's what's VDI attached to the control domain means. They are snapshot attached to your dom0 VM to be exposed through http.

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sumansaha @Darkbeldin
          last edited by sumansaha

          @Darkbeldin is it safe to forget the control domain from
          Dashboard-> Health->VDIs attached to Control Domain

          DarkbeldinD 1 Reply Last reply Reply Quote 0
          • DarkbeldinD Offline
            Darkbeldin Vates 🪐 Pro Support Team @sumansaha
            last edited by

            @sumansaha Not forget the control domain but yes you can remove the VDI attached to it.

            1 Reply Last reply Reply Quote 0
            • S Offline
              sumansahabd
              last edited by

              @Darkbeldin There is no other to remove VDI. Do you mean to remove the VM.

              DarkbeldinD 1 Reply Last reply Reply Quote 0
              • DarkbeldinD Offline
                Darkbeldin Vates 🪐 Pro Support Team @sumansahabd
                last edited by

                @sumansahabd No what you are seeing in Dashboard > Health are VDI attached to your dom0 not dom0 himself so yes click on the item there and remove them it's ok.

                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  sumansaha @Darkbeldin
                  last edited by

                  @Darkbeldin Screenshot 2023-01-05 at 1.48.36 AM.png
                  Screenshot 2023-01-05 at 1.56.20 AM.png

                  Actually I didn't get you . But the two control domain snapshot has two base copies and consumed storage space. Please suggest how we can remove the control domain snapshots.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    It's not a control domain snapshot, it's a VM snapshot (Porta web) MOUNTED on the dom0.

                    Having a snap mounted to the dom0 is OK during the backup phase, but if it's still attached after, it's not normal.

                    So if it's outside a backup, you can disconnected the snapshots from the control domain, remove the VM snapshot, and then it should be coalesced automatically 🙂

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      sumansaha @olivierlambert
                      last edited by

                      @olivierlambert Screenshot 2023-01-05 at 2.02.59 AM.png

                      I've disconnected the snapshots and after that should I go for to Destroy VDI' .

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by olivierlambert

                        Check if your VM with porta web doesn't have a snapshot, that will automatically remove all the snapshot disks 🙂

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          sumansaha @olivierlambert
                          last edited by

                          @olivierlambert Screenshot 2023-01-05 at 2.16.07 AM.png

                          There is no snapshot actually. Should I run "Destroy VDI" on the snapshots from the disk.

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO Offline
                            olivierlambert Vates 🪐 Co-Founder CEO
                            last edited by

                            Yes, destroy the VDI snapshot in the SR/disk view

                            S 1 Reply Last reply Reply Quote 0
                            • S Offline
                              sumansaha @olivierlambert
                              last edited by sumansaha

                              @olivierlambert
                              Screenshot 2023-01-05 at 11.46.17 AM.png

                              Thanks for your response.After 'Destory VDI' from Disk currently there is only one base copy. And no coalesced process running now. Is there any way to remove current base copy.

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Offline
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by

                                No. If it's not coalesced automatically, there's a reason 🙂

                                S 1 Reply Last reply Reply Quote 0
                                • S Offline
                                  sumansaha @olivierlambert
                                  last edited by

                                  @olivierlambert How we can troubleshoot that.

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO Offline
                                    olivierlambert Vates 🪐 Co-Founder CEO
                                    last edited by

                                    https://xcp-ng.org/docs/troubleshooting.html is a good start to read.

                                    In your case, it's likely inside /var/log/SMlog

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