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

    Converting VMware VMs to KVM

    Scheduled Pinned Locked Moved IT Discussion
    p2vv2vvirtualizationvmware esxikvmfedorafedora 31
    15 Posts 7 Posters 1.7k Views
    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.
    • Emad RE
      Emad R @scottalanmiller
      last edited by Emad R

      @scottalanmiller

      qemu-img does this, i heard you can do it in virtualbox if your using windows or copy them to kvm host and use that, but the real question will they work after that and I cant answer you thing, it depends if qemu-img was tested on older virtual hard disks format, so newer ones might be hard.

      1 Reply Last reply Reply Quote 1
      • M
        marcinozga
        last edited by marcinozga

        Starwind has a free disk image converter. https://www.starwindsoftware.com/starwind-v2v-converter
        I used it to convert between ESXi and Hyper-V in the past.

        1 Reply Last reply Reply Quote 1
        • black3dynamiteB
          black3dynamite
          last edited by

          Use virt-v2v.
          http://www.libguestfs.org/virt-v2v.1.html

          1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller
            last edited by

            Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V 😉

            DustinB3403D 1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403 @scottalanmiller
              last edited by

              @scottalanmiller said in Converting VMware VMs to KVM:

              Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V 😉

              But an old version of Hyper-V . . .

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

                @DustinB3403 said in Converting VMware VMs to KVM:

                @scottalanmiller said in Converting VMware VMs to KVM:

                Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V 😉

                But an old version of Hyper-V . . .

                Yeah, I prefer the KVM approach.

                DashrenderD 1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender @scottalanmiller
                  last edited by

                  @scottalanmiller said in Converting VMware VMs to KVM:

                  @DustinB3403 said in Converting VMware VMs to KVM:

                  @scottalanmiller said in Converting VMware VMs to KVM:

                  Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V 😉

                  But an old version of Hyper-V . . .

                  Yeah, I prefer the KVM approach.

                  even so - why 2016 and now 2019?

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

                    @Dashrender said in Converting VMware VMs to KVM:

                    @scottalanmiller said in Converting VMware VMs to KVM:

                    @DustinB3403 said in Converting VMware VMs to KVM:

                    @scottalanmiller said in Converting VMware VMs to KVM:

                    Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V 😉

                    But an old version of Hyper-V . . .

                    Yeah, I prefer the KVM approach.

                    even so - why 2016 and now 2019?

                    It's what they are licensed for and they require remote GUI management.

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

                      Pretty much if you run Windows every decision is made around "what licensing you purchased." It makes no sense to question, as every Windows scenario always has the same answer. Yes, it's ridiculous to choose Windows and not choose a licensing approach that keeps you up to date. But generally the factors that lead you to Windows also lead you away from good licensing approaches. It is what it is.

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

                        @scottalanmiller said in Converting VMware VMs to KVM:

                        and they require remote GUI management

                        Moot I know but to get that you just install Windows 2019 Server with Desktop Experience. It's the LTSC release.

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

                          @Pete-S said in Converting VMware VMs to KVM:

                          @scottalanmiller said in Converting VMware VMs to KVM:

                          and they require remote GUI management

                          Moot I know but to get that you just install Windows 2019 Server with Desktop Experience. It's the LTSC release.

                          But you need a license for that. 2019 isn't the issue, lack of license is. We use 2019 when we control the client's licensing situation.

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

                            Ideally, we wanted 2019, but they don't have it. We could do it without the GUI (no license needed) but it's the GUI is why our customer uses Hyper-V. Without the GUI, KVM is needed because it has a GUI. It is what it is. I was hoping that they couldn't find their 2016 license (they almost didn't) because it would have meant KVM which is way, way better for us to manage.

                            black3dynamiteB 1 Reply Last reply Reply Quote 0
                            • black3dynamiteB
                              black3dynamite @scottalanmiller
                              last edited by

                              @scottalanmiller said in Converting VMware VMs to KVM:

                              Ideally, we wanted 2019, but they don't have it. We could do it without the GUI (no license needed) but it's the GUI is why our customer uses Hyper-V. Without the GUI, KVM is needed because it has a GUI. It is what it is. I was hoping that they couldn't find their 2016 license (they almost didn't) because it would have meant KVM which is way, way better for us to manage.

                              I haven't been keeping up with Windows Admin Center for awhile. Was that an option to manage Hyper-V?

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

                                @black3dynamite said in Converting VMware VMs to KVM:

                                I haven't been keeping up with Windows Admin Center for awhile. Was that an option to manage Hyper-V?

                                It will be, but I'm not sure that it is yet. We've tried and not been able to get it working even internally anywhere, let alone externally. Once they figure out stability and authentication, I assume that it will be great for that. Being that this is 2016, it's going to suck hard. And if there is a Hyper-V issue, WAC would be down which is a problem in a small environment like this.

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