Converting VMware VMs to KVM
-
Use
virt-v2v.
http://www.libguestfs.org/virt-v2v.1.html -
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
-
@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 . . .
-
@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.
-
@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?
-
@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.
-
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.
-
@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.
-
@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.
-
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.
-
@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?
-
@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.
