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

    Best practice partition & LVM for KVM

    IT Discussion
    9
    69
    7.4k
    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.
    • travisdh1T
      travisdh1 @kuyaz
      last edited by

      @kuyaz said in Best practice partition & LVM for KVM:

      Hi all,

      If I have :

      • raid 1 4TB Sata 7200 rpm
      • raid 1 1TB SSD

      What is the best practice partition and mount point for above configuration?
      I want to utilize ssd for VM that required high IOPs and the rest will be on SATA.

      Is it ok if i do like this :

      LVG : vg_ssd_critical_vm
      /vm (ssd)

      LVG : vg_sata_non_critical_vm
      /boot 2GB
      /bootBIOS 1GB
      /root (ALL remaining space)
      /swap (32GB)

      I like to make root it's own smallish partition when talking large amounts of storage. It shouldn't require all that much space. I like 50GB, but that's more than is really required often times.

      /biosBOOT should be MB, not GB.

      I plan to install centos with KVM and ovirt on Sata Raid. Should i also separate the host on different partition / LV?

      Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

      Do I need to spare some free space for LVM snapshot?

      If you want to take a snapshot of one of the LVMs, then yes.

      All guru please advise... thanks

      ObsolesceO 1 Reply Last reply Reply Quote 0
      • ObsolesceO
        Obsolesce @travisdh1
        last edited by

        @travisdh1 said in Best practice partition & LVM for KVM:

        Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

        Because oVirt will be installed on it, and it requires CentOS.

        scottalanmillerS travisdh1T 2 Replies Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @Obsolesce
          last edited by

          @tim_g said in Best practice partition & LVM for KVM:

          @travisdh1 said in Best practice partition & LVM for KVM:

          Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

          Because oVirt will be installed on it, and it requires CentOS.

          Fedora has been supported at least as recently as Fed 24.

          ObsolesceO 1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce @scottalanmiller
            last edited by

            @scottalanmiller said in Best practice partition & LVM for KVM:

            @tim_g said in Best practice partition & LVM for KVM:

            @travisdh1 said in Best practice partition & LVM for KVM:

            Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

            Because oVirt will be installed on it, and it requires CentOS.

            Fedora has been supported at least as recently as Fed 24.

            As a node, yes.

            But for oVirt Engine, he'll need to use CentOS.

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @Obsolesce
              last edited by

              @tim_g said in Best practice partition & LVM for KVM:

              @travisdh1 said in Best practice partition & LVM for KVM:

              Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

              Because oVirt will be installed on it, and it requires CentOS.

              That looks like a decent web-based management tool. Does it need installed on the host tho?

              ObsolesceO 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @Obsolesce
                last edited by

                @tim_g said in Best practice partition & LVM for KVM:

                @scottalanmiller said in Best practice partition & LVM for KVM:

                @tim_g said in Best practice partition & LVM for KVM:

                @travisdh1 said in Best practice partition & LVM for KVM:

                Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

                Because oVirt will be installed on it, and it requires CentOS.

                Fedora has been supported at least as recently as Fed 24.

                As a node, yes.

                But for oVirt Engine, he'll need to use CentOS.

                No, as the engine. The client goes on all Fedora.

                ObsolesceO 1 Reply Last reply Reply Quote 1
                • ObsolesceO
                  Obsolesce @travisdh1
                  last edited by

                  @travisdh1 said in Best practice partition & LVM for KVM:

                  @tim_g said in Best practice partition & LVM for KVM:

                  @travisdh1 said in Best practice partition & LVM for KVM:

                  Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

                  Because oVirt will be installed on it, and it requires CentOS.

                  That looks like a decent web-based management tool. Does it need installed on the host tho?

                  No, but you can (known as self-hosted). You can also make the oVirt Engine HA between two hosts.

                  The other way is to run the oVirt Engine as a VM on another host, and connect the nodes to it.

                  1 Reply Last reply Reply Quote 0
                  • ObsolesceO
                    Obsolesce @scottalanmiller
                    last edited by Obsolesce

                    @scottalanmiller said in Best practice partition & LVM for KVM:

                    @tim_g said in Best practice partition & LVM for KVM:

                    @scottalanmiller said in Best practice partition & LVM for KVM:

                    @tim_g said in Best practice partition & LVM for KVM:

                    @travisdh1 said in Best practice partition & LVM for KVM:

                    Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

                    Because oVirt will be installed on it, and it requires CentOS.

                    Fedora has been supported at least as recently as Fed 24.

                    As a node, yes.

                    But for oVirt Engine, he'll need to use CentOS.

                    No, as the engine. The client goes on all Fedora.

                    I know for a 100% fact you cannot use the oVirt Engine on Fedora. It does not work. I tried that first, even though Fedora is not listed as a supported OS for the oVirt Engine.

                    But you can run oVirt nodes on Fedora.

                    scottalanmillerS 1 Reply Last reply Reply Quote 1
                    • ObsolesceO
                      Obsolesce @kuyaz
                      last edited by

                      @kuyaz said in Best practice partition & LVM for KVM:

                      LVG : vg_ssd_critical_vm
                      /vm (ssd)
                      LVG : vg_sata_non_critical_vm
                      /boot 2GB
                      /bootBIOS 1GB
                      /root (ALL remaining space)
                      /swap (32GB)

                      I'd use XFS. Don't use EXT4. You're correct with using LVM.

                      I'd go like this:

                      LVG : vg_ssd_critical_vm
                      /DATAssd

                      LVG : vg_sata_non_critical_vm
                      /DATAhdd (xfs)
                      /boot 2GB (xfs)
                      /bootBIOS 1GB
                      /root 50GB (xfs)
                      /swap 32GB (swap)
                      /home whatever (xfs)

                      As @travisdh1 said, you'll need space for snapshots of the LVMs, but don't do it for the VMs. Use VM snapshots for those instead.

                      You're VMs should be RAW (.img) for better performance.

                      K 1 Reply Last reply Reply Quote 2
                      • scottalanmillerS
                        scottalanmiller @Obsolesce
                        last edited by

                        @tim_g said in Best practice partition & LVM for KVM:

                        @scottalanmiller said in Best practice partition & LVM for KVM:

                        @tim_g said in Best practice partition & LVM for KVM:

                        @scottalanmiller said in Best practice partition & LVM for KVM:

                        @tim_g said in Best practice partition & LVM for KVM:

                        @travisdh1 said in Best practice partition & LVM for KVM:

                        Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

                        Because oVirt will be installed on it, and it requires CentOS.

                        Fedora has been supported at least as recently as Fed 24.

                        As a node, yes.

                        But for oVirt Engine, he'll need to use CentOS.

                        No, as the engine. The client goes on all Fedora.

                        I know for a 100% fact you cannot use the oVirt Engine on Fedora. It does not work. I tried that first, even though Fedora is not listed as a supported OS for the oVirt Engine.

                        But you can run oVirt nodes on Fedora.

                        They had it listed as working on the oVirt site, that's where I looked it up.

                        ObsolesceO 1 Reply Last reply Reply Quote 0
                        • ObsolesceO
                          Obsolesce @scottalanmiller
                          last edited by Obsolesce

                          @scottalanmiller said in Best practice partition & LVM for KVM:

                          @tim_g said in Best practice partition & LVM for KVM:

                          @scottalanmiller said in Best practice partition & LVM for KVM:

                          @tim_g said in Best practice partition & LVM for KVM:

                          @scottalanmiller said in Best practice partition & LVM for KVM:

                          @tim_g said in Best practice partition & LVM for KVM:

                          @travisdh1 said in Best practice partition & LVM for KVM:

                          Why CentOS instead of Fedora Server? It's a relatively recent change in recommendation around here, but most of us prefer Fedora Server over CentOS. CentOS packages are just getting old and untenable for anything other than legacy software.

                          Because oVirt will be installed on it, and it requires CentOS.

                          Fedora has been supported at least as recently as Fed 24.

                          As a node, yes.

                          But for oVirt Engine, he'll need to use CentOS.

                          No, as the engine. The client goes on all Fedora.

                          I know for a 100% fact you cannot use the oVirt Engine on Fedora. It does not work. I tried that first, even though Fedora is not listed as a supported OS for the oVirt Engine.

                          But you can run oVirt nodes on Fedora.

                          They had it listed as working on the oVirt site, that's where I looked it up.

                          It wouldn't install for me, unless I just couldn't find the correct repo... but I tried.

                          https://www.ovirt.org/download/

                          0_1510290171734_Untitled.png

                          1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce
                            last edited by

                            I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce
                              last edited by

                              The only recent fedora repos I see are for ovirt-node, not the engine.

                              1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @Obsolesce
                                last edited by

                                @tim_g said in Best practice partition & LVM for KVM:

                                I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                FC24 repos for 4.1

                                ObsolesceO 1 Reply Last reply Reply Quote 0
                                • ObsolesceO
                                  Obsolesce @scottalanmiller
                                  last edited by

                                  @scottalanmiller said in Best practice partition & LVM for KVM:

                                  @tim_g said in Best practice partition & LVM for KVM:

                                  I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                  FC24 repos for 4.1

                                  Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                  But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                  scottalanmillerS K 2 Replies Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller @Obsolesce
                                    last edited by

                                    @tim_g said in Best practice partition & LVM for KVM:

                                    @scottalanmiller said in Best practice partition & LVM for KVM:

                                    @tim_g said in Best practice partition & LVM for KVM:

                                    I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                    FC24 repos for 4.1

                                    Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                    But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                    no, but it's clearly been on Fedora from time to time. I wonder why they are doing it like that.

                                    ObsolesceO 1 Reply Last reply Reply Quote 0
                                    • ObsolesceO
                                      Obsolesce @scottalanmiller
                                      last edited by

                                      @scottalanmiller said in Best practice partition & LVM for KVM:

                                      @tim_g said in Best practice partition & LVM for KVM:

                                      @scottalanmiller said in Best practice partition & LVM for KVM:

                                      @tim_g said in Best practice partition & LVM for KVM:

                                      I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                      FC24 repos for 4.1

                                      Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                      But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                      no, but it's clearly been on Fedora from time to time. I wonder why they are doing it like that.

                                      No idea... you know I'd much rather use Fedora. But having to start with FC24 reminds me of technical debt in a way.

                                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @Obsolesce
                                        last edited by

                                        @tim_g said in Best practice partition & LVM for KVM:

                                        @scottalanmiller said in Best practice partition & LVM for KVM:

                                        @tim_g said in Best practice partition & LVM for KVM:

                                        @scottalanmiller said in Best practice partition & LVM for KVM:

                                        @tim_g said in Best practice partition & LVM for KVM:

                                        I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                        FC24 repos for 4.1

                                        Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                        But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                        no, but it's clearly been on Fedora from time to time. I wonder why they are doing it like that.

                                        No idea... you know I'd much rather use Fedora. But having to start with FC24 reminds me of technical debt in a way.

                                        It is, but having oVirt only on CentOS 7 feels like that, too 🙂

                                        ObsolesceO 1 Reply Last reply Reply Quote 0
                                        • ObsolesceO
                                          Obsolesce @scottalanmiller
                                          last edited by

                                          @scottalanmiller said in Best practice partition & LVM for KVM:

                                          @tim_g said in Best practice partition & LVM for KVM:

                                          @scottalanmiller said in Best practice partition & LVM for KVM:

                                          @tim_g said in Best practice partition & LVM for KVM:

                                          @scottalanmiller said in Best practice partition & LVM for KVM:

                                          @tim_g said in Best practice partition & LVM for KVM:

                                          I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                          FC24 repos for 4.1

                                          Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                          But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                          no, but it's clearly been on Fedora from time to time. I wonder why they are doing it like that.

                                          No idea... you know I'd much rather use Fedora. But having to start with FC24 reminds me of technical debt in a way.

                                          It is, but having oVirt only on CentOS 7 feels like that, too 🙂

                                          Not 7.0... CentOS 7 or 7.x

                                          scottalanmillerS 1 Reply Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @Obsolesce
                                            last edited by

                                            @tim_g said in Best practice partition & LVM for KVM:

                                            @scottalanmiller said in Best practice partition & LVM for KVM:

                                            @tim_g said in Best practice partition & LVM for KVM:

                                            @scottalanmiller said in Best practice partition & LVM for KVM:

                                            @tim_g said in Best practice partition & LVM for KVM:

                                            @scottalanmiller said in Best practice partition & LVM for KVM:

                                            @tim_g said in Best practice partition & LVM for KVM:

                                            I seen an FC22 repo, but that's using oVirt 3.6 and is way old.

                                            FC24 repos for 4.1

                                            Missed that... would you use FC24 to control your datacenter, and for how long? I'd rather use something I know will stay supported or at least stay current. It seems it only is with CentOS/RHEL. So I'd use CentOS for the oVirt Engine and Fedora for each oVirt Node.

                                            But that's not what the OP is doing. It looks like he's going to do a self-hosted install of oVirt Engine, if that's the case, I'd go with the most recent most stably supported way, and that happens to be CentOS or RHEL.

                                            no, but it's clearly been on Fedora from time to time. I wonder why they are doing it like that.

                                            No idea... you know I'd much rather use Fedora. But having to start with FC24 reminds me of technical debt in a way.

                                            It is, but having oVirt only on CentOS 7 feels like that, too 🙂

                                            Not 7.0... CentOS 7 or 7.x

                                            Patched, but still old. Not something I want as my hypervisor base.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 1 / 4
                                            • First post
                                              Last post