Re: [ovirt-users] Info about windows guest performance

2018-02-12 Thread Gianluca Cecchi
On Sun, Feb 11, 2018 at 9:33 AM, Yaniv Kaul  wrote:

>
>
> On Sat, Feb 10, 2018 at 8:41 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Fri, Feb 9, 2018 at 4:32 PM, Gianluca Cecchi <
>> gianluca.cec...@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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Info about windows guest performance

2018-02-11 Thread Yaniv Kaul
On Sat, Feb 10, 2018 at 8:41 PM, Gianluca Cecchi 
wrote:

> On Fri, Feb 9, 2018 at 4:32 PM, Gianluca Cecchi  > 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).



>
> -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



> Complete command is:
>
> /usr/libexec/qemu-kvm
> -name guest=testmig,debug-threads=on
> -S
> -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/
> qemu/domain-15-testmig/master-key.aes
> -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off
> -cpu Westmere,vmx=on,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff
> -m size=4194304k,slots=16,maxmem=16777216k
> -realtime mlock=off
> -smp 2,maxcpus=16,sockets=16,cores=1,threads=1
> -numa node,nodeid=0,cpus=0-1,mem=4096
> -uuid XXX
> -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-4.1708.el7.
> centos,serial=XXX,uuid=YYY
> -no-user-config
> -nodefaults
> -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-
> 15-testmig/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control
> -rtc base=2018-02-10T18:32:22,driftfix=slew
> -global kvm-pit.lost_tick_policy=delay
> -no-hpet
> -no-shutdown
> -boot strict=on
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
> -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5
> -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.
> 0,addr=0x4
> -drive if=none,id=drive-ide0-1-0,readonly=on
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
> -drive file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-
> 9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/
> 2de93ee3-7d6e-4a10-88c4-abc7a11fb687/a9f4e35b-4aa0-
> 45e8-b775-1a046d1851aa,format=qcow2,if=none,id=drive-scsi0-
> 0-0-1,serial=2de93ee3-7d6e-4a10-88c4-abc7a11fb687,cache=
> none,werror=stop,rerror=stop,aio=native
> -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-
> scsi0-0-0-1,id=scsi0-0-0-1,bootindex=1
> -drive file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-
> 9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/
> f821da0a-cec7-457c-88a4-f83f33404e65/0d0c4244-f184-
> 4eaa-b5bf-8dc65c7069bb,format=raw,if=none,id=drive-scsi0-0-
> 0-0,serial=f821da0a-cec7-457c-88a4-f83f33404e65,cache=none,
> werror=stop,rerror=stop,aio=native
> -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-
> scsi0-0-0-0,id=scsi0-0-0-0
> -netdev tap,fd=30,id=hostnet0
> -device e1000,netdev=hostnet0,id=net0,mac=00:50:56:9d:c9:29,bus=pci.
> 0,addr=0x3
> -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/
> 421d6f1b-58e3-54a4-802f-fb52f7831369.com.redhat.rhevm.vdsm,server,nowait
> -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=
> charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/
> 421d6f1b-58e3-54a4-802f-fb52f7831369.org.qemu.guest_agent.0,server,nowait
> -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=
> charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent
> -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=
> charchannel2,id=channel2,name=com.redhat.spice.0
> -spice tls-port=5900,addr=10.4.192.32,x509-dir=/etc/pki/vdsm/
> libvirt-spice,tls-channel=default,tls-channel=main,tls-
> channel=display,tls-channel=inputs,tls-channel=cursor,tls-
> 

Re: [ovirt-users] Info about windows guest performance

2018-02-10 Thread Gianluca Cecchi
On Fri, Feb 9, 2018 at 4:32 PM, Gianluca Cecchi 
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:

-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
?

Complete command is:

/usr/libexec/qemu-kvm
-name guest=testmig,debug-threads=on
-S
-object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-testmig/master-key.aes
-machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off
-cpu Westmere,vmx=on,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff
-m size=4194304k,slots=16,maxmem=16777216k
-realtime mlock=off
-smp 2,maxcpus=16,sockets=16,cores=1,threads=1
-numa node,nodeid=0,cpus=0-1,mem=4096
-uuid XXX
-smbios type=1,manufacturer=oVirt,product=oVirt
Node,version=7-4.1708.el7.centos,serial=XXX,uuid=YYY
-no-user-config
-nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-testmig/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control
-rtc base=2018-02-10T18:32:22,driftfix=slew
-global kvm-pit.lost_tick_policy=delay
-no-hpet
-no-shutdown
-boot strict=on
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5
-device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4
-drive if=none,id=drive-ide0-1-0,readonly=on
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-drive
file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/2de93ee3-7d6e-4a10-88c4-abc7a11fb687/a9f4e35b-4aa0-45e8-b775-1a046d1851aa,format=qcow2,if=none,id=drive-scsi0-0-0-1,serial=2de93ee3-7d6e-4a10-88c4-abc7a11fb687,cache=none,werror=stop,rerror=stop,aio=native
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1,bootindex=1
-drive
file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/f821da0a-cec7-457c-88a4-f83f33404e65/0d0c4244-f184-4eaa-b5bf-8dc65c7069bb,format=raw,if=none,id=drive-scsi0-0-0-0,serial=f821da0a-cec7-457c-88a4-f83f33404e65,cache=none,werror=stop,rerror=stop,aio=native
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0
-netdev tap,fd=30,id=hostnet0
-device
e1000,netdev=hostnet0,id=net0,mac=00:50:56:9d:c9:29,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel2,name=vdagent
-device
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
-spice
tls-port=5900,addr=10.4.192.32,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
-device
qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
-msg timestamp=on

Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Info about windows guest performance

2018-02-09 Thread Gianluca Cecchi
On Fri, Feb 9, 2018 at 4:25 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
> Analyzing my command line I see the "-no-hpet" but I dont see the "hv_time"
>
> See below full comand.
>
> Any hints?
>
>
> What OS type do you have set for that VM? Make sure it matches the Windows
> version. That enables the hyperv enlightenments settings
>
> Thanks,
> michal
>

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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Info about windows guest performance

2018-02-09 Thread Michal Skrivanek


> On 9 Feb 2018, at 14:04, Gianluca Cecchi  wrote:
> 
> Hello,
> while in my activities to accomplish migration of a Windows 2008 R2 VM (with 
> an Oracle RDBMS inside) from vSphere to oVirt, I'm going to check performance 
> related things.
> 
> Up to now I only ran Windows guests inside my laptops and not inside an oVirt 
> infrastructure.
> 
> Now I successfully migrated this kind of VM to oVirt 4.1.9.
> The guest had an LSI logic sas controller. Inside the oVirt host that I used 
> as proxy (for VMware virt-v2v) I initially didn't have the virtio-win rpm.
> I presume that has been for this reason that the oVirt guest has been 
> configured with IDE disks…

yes
you won’t get any decent performance unless you use virtio drivers. Either 
virtio-block or virtio-scsi

> Can you confirm?
> 
> For this test I started with ide, then added a virtio-scsi disk and then 
> changed also the boot disk to virtio-scsi and all now goes well, with also 
> ovirt-guest-tools-iso-4.1-3 provided iso used to install qxl and so on...
> 
> So far so good.
> I found this bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=1277353 
> 
> 
> where it seems that 
> 
> "
> For optimum I/O performance it's critical to make sure that Windows guests 
> use the Hyper-V reference counter feature. QEMU command line should include
> 
> -cpu ...,hv_time
> 
> and
> 
> -no-hpet
> "
> Analyzing my command line I see the "-no-hpet" but I dont see the "hv_time"
> See below full comand.
> Any hints?

What OS type do you have set for that VM? Make sure it matches the Windows 
version. That enables the hyperv enlightenments settings

Thanks,
michal
> Thanks,
> Gianluca
> 
> /usr/libexec/qemu-kvm
> -name guest=testmig,debug-threads=on
> -S
> -object 
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-12-testmig/master-key.aes
> -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off
> -cpu Westmere,vmx=on
> -m size=4194304k,slots=16,maxmem=16777216k
> -realtime mlock=off
> -smp 2,maxcpus=16,sockets=16,cores=1,threads=1
> -numa node,nodeid=0,cpus=0-1,mem=4096
> -uuid x-y-z-x-y
> -smbios type=1,manufacturer=oVirt,product=oVirt
> Node,version=7-4.1708.el7.centos,serial=xx,uuid=yy
> -no-user-config
> -nodefaults
> -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-12-testmig/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control
> -rtc base=2018-02-09T12:41:41,driftfix=slew
> -global kvm-pit.lost_tick_policy=delay
> -no-hpet
> -no-shutdown
> -boot strict=on
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
> -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5
> -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4
> -drive if=none,id=drive-ide0-1-0,readonly=on
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
> -drive 
> file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/2de93ee3-7d6e-4a10-88c4-abc7a11fb687/a9f4e35b-4aa0-45e8-b775-1a046d1851aa,format=qcow2,if=none,id=drive-scsi0-0-0-1,serial=2de93ee3-7d6e-4a10-88c4-abc7a11fb687,cache=none,werror=stop,rerror=stop,aio=native
> -device 
> scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1,bootindex=1
> -drive 
> file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/f821da0a-cec7-457c-88a4-f83f33404e65/0d0c4244-f184-4eaa-b5bf-8dc65c7069bb,format=raw,if=none,id=drive-scsi0-0-0-0,serial=f821da0a-cec7-457c-88a4-f83f33404e65,cache=none,werror=stop,rerror=stop,aio=native
> -device 
> scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0
> -netdev tap,fd=30,id=hostnet0
> -device e1000,netdev=hostnet0,id=net0,mac=00:50:56:9d:c9:29,bus=pci.0,addr=0x3
> -chardev 
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.com.redhat.rhevm.vdsm,server,nowait
> -device 
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev 
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.org.qemu.guest_agent.0,server,nowait
> -device 
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent
> -device 
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -spice 
> tls-port=5900,addr=10.4.192.32,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
> -device 
> qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
> -msg timestamp=on
> 
> 

[ovirt-users] Info about windows guest performance

2018-02-09 Thread Gianluca Cecchi
Hello,
while in my activities to accomplish migration of a Windows 2008 R2 VM
(with an Oracle RDBMS inside) from vSphere to oVirt, I'm going to check
performance related things.

Up to now I only ran Windows guests inside my laptops and not inside an
oVirt infrastructure.

Now I successfully migrated this kind of VM to oVirt 4.1.9.
The guest had an LSI logic sas controller. Inside the oVirt host that I
used as proxy (for VMware virt-v2v) I initially didn't have the virtio-win
rpm.
I presume that has been for this reason that the oVirt guest has been
configured with IDE disks...
Can you confirm?

For this test I started with ide, then added a virtio-scsi disk and then
changed also the boot disk to virtio-scsi and all now goes well, with also
ovirt-guest-tools-iso-4.1-3 provided iso used to install qxl and so on...

So far so good.
I found this bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1277353

where it seems that

"

For optimum I/O performance it's critical to make sure that Windows
guests use the Hyper-V reference counter feature. QEMU command line
should include

-cpu ...,hv_time

and

-no-hpet

"

Analyzing my command line I see the "-no-hpet" but I dont see the "hv_time"

See below full comand.

Any hints?

Thanks,

Gianluca


/usr/libexec/qemu-kvm
-name guest=testmig,debug-threads=on
-S
-object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-12-testmig/master-key.aes
-machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off
-cpu Westmere,vmx=on
-m size=4194304k,slots=16,maxmem=16777216k
-realtime mlock=off
-smp 2,maxcpus=16,sockets=16,cores=1,threads=1
-numa node,nodeid=0,cpus=0-1,mem=4096
-uuid x-y-z-x-y
-smbios type=1,manufacturer=oVirt,product=oVirt
Node,version=7-4.1708.el7.centos,serial=xx,uuid=yy
-no-user-config
-nodefaults
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-12-testmig/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control
-rtc base=2018-02-09T12:41:41,driftfix=slew
-global kvm-pit.lost_tick_policy=delay
-no-hpet
-no-shutdown
-boot strict=on
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5
-device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4
-drive if=none,id=drive-ide0-1-0,readonly=on
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-drive 
file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/2de93ee3-7d6e-4a10-88c4-abc7a11fb687/a9f4e35b-4aa0-45e8-b775-1a046d1851aa,format=qcow2,if=none,id=drive-scsi0-0-0-1,serial=2de93ee3-7d6e-4a10-88c4-abc7a11fb687,cache=none,werror=stop,rerror=stop,aio=native
-device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1,bootindex=1
-drive 
file=/rhev/data-center/ef17cad6-7724-4cd8-96e3-9af6e529db51/fa33df49-b09d-4f86-9719-ede649542c21/images/f821da0a-cec7-457c-88a4-f83f33404e65/0d0c4244-f184-4eaa-b5bf-8dc65c7069bb,format=raw,if=none,id=drive-scsi0-0-0-0,serial=f821da0a-cec7-457c-88a4-f83f33404e65,cache=none,werror=stop,rerror=stop,aio=native
-device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0
-netdev tap,fd=30,id=hostnet0
-device e1000,netdev=hostnet0,id=net0,mac=00:50:56:9d:c9:29,bus=pci.0,addr=0x3
-chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.com.redhat.rhevm.vdsm,server,nowait
-device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev 
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/421d6f1b-58e3-54a4-802f-fb52f7831369.org.qemu.guest_agent.0,server,nowait
-device 
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel2,name=vdagent
-device 
virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
-spice 
tls-port=5900,addr=10.4.192.32,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
-device 
qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
-msg timestamp=on
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users