On Fri, Jan 26, 2018 at 1:15 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:
>
> On Fri, Jan 26, 2018 at 12:56 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> I'm trying to update an environment from 4.1.7 to 4.1.9.
>>
>>
>
>> I don't see errors in vdsm logs of target host, but I do see this in
>> /var/log/messages of target host
>>
>> Jan 26 12:39:51 ov200 libvirtd: 2018-01-26 11:39:51.179+0000: 2588: error
>> : virCPUx86UpdateLive:2726 : operation failed: guest CPU doesn't match
>> specification: missing features: vmx
>>
>> Indeed dbatest3 VM has this "vmx=on" flag in qemu-kvm command line on
>> source host, even if I never configured it explicitly...:
>>
>>
It was my fault. Inside source host, I didn't enable "Nested
Virtualization" in Edit Host -> Kernel, but in the past I installed the
package vdsm-hook-nestedvt.
This package creates the file /etc/modprobe.d/vdsm-nestedvt.conf with
options kvm-intel nested=1
and so I have
# systool -a -v -m kvm_intel | grep nested
nested = "Y"
This apparently originates guests to be started with "vmx=on" even if you
don't enable nested virtualization at edit host level from oVirt.
In the mean time I installed the hook in the target host too and I was able
to live migrate the VM.
Gianluca
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
