On Sun, Feb 11, 2018 at 9:33 AM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Sat, Feb 10, 2018 at 8:41 PM, Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
On Fri, Feb 9, 2018 at 4:32 PM, Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
If I edit the VM, in general settings I see "Other OS" as operating system. In General subtab after selecting the VM in "Virtual Machines" tab I again see "Other OS" in "Operating System" and the field "Origin" filled with the value "VMware"
During virt-v2v it seems it was recognized as Windows 2008 though...
libguestfs: trace: v2v: hivex_value_utf8 = "Windows Server 2008 R2 Enterprise" libguestfs: trace: v2v: hivex_value_key 11809408
I can send all the log if it can help. Thanks, Gianluca
So it seems it has been a problem with virt-v2v conversion, because if I shutdown the VM and set it to Windows 2008 R2 x86_64 and optimized for server and I run it, I get this flag for the cpu:
A new virt-v2v was just released, worth testing it. It has some nice features, and perhaps fixes the above too. For example: Virt-v2v now installs Windows 10 / Windows Server 2016 virtio block drivers correctly (Pavel Butsykin, Kun Wei).
Virt-v2v now installs virtio-rng, balloon and pvpanic drivers, and correctly sets this in the target hypervisor metadata for hypervisors which support that (Tomáš Golembiovský).
Virt-v2v now installs both legacy and modern virtio keys in the Windows registry (Ladi Prosek).
Thanks for the info. In the mean time after installing virtio-win on proxy host I retried with the same version of virt-v2v provided with 4.1.9: virt-v2v-1.36.3-6.el7_4.3.x86_64 and then selecting and injecting it in the import window and the VM correctly starts with virtio drivers (version 61.74.104.14100) after a reboot requested (first starts remains in black window for a couple of minutes and then asks to restart) It also has qxl drivers (6.1.0.1024) But the VM remains as "Other OS" and obviously has no hv_ optimization. I'm going to try the new version as you suggested. It would be nice also to have virtio-scsi option and not only the virtio option directly in import function.... BTW: I see that in case a target VM with the same name of source exists, I'm given an error and I can't change the VM name on destination.... This seems to me a big limitation, because forces to rename the source VM or rename a pre-existing VM at destination with the same name....
-cpu Westmere,vmx=on,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff
BTW: what are the other flags for:
hv_spinlocks=0x1fff hv_relaxed hv_vapic ?
These are the enlightenment that allow Windows guests to run faster (hv = hyper-v). See[1] Y.
[1] http://blog.wikichoon.com/2014/07/enabling-hyper-v- enlightenments-with-kvm.html
Thanks for the Cole link Gianluca