On the libvirt side, reading the documentation again i bumped into this :
<vendor_id state='on' value='KVM Hv'/>
https://libvirt.org/formatdomain.html#elementsFeatures
Anybody knowing why we have to rely on qemu since apparently libvirt is
suppose to support this since 2012 ?
https://www.redhat.com/archives/libvir-list/2012-June/msg00917.html
I have to admit i'm curious.
2016-04-13 21:23 GMT+02:00 Alex Williamson <[email protected]>:
> On Wed, Apr 13, 2016 at 1:17 PM, thibaut noah <[email protected]>
> wrote:
>
>> The problem i have is i use libvirt, putting the flag on qemu-arg
>> requires to set cpu again.
>> As i have no idea which cpu setting will be used this doesn't seem like a
>> good idea, i saw that people use scripts apparently but i wonder if someone
>> figured out how to put this directly into libvirt
>>
>
> $ cat qemu-kvm-hv-vendor
> #!/bin/sh
> exec PATHTOYOURQEMUKVM \
> `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=KeenlyKVM|g'`
>
> $ chmod 755 qemu-kvm-hv-vendor
>
> $ virsh edit YOURVM
>
> Replace <emulator>PATHTOYOURQEMUKVM</emulator> with
> PATHTO/qemu-kvm-hv-vendor
>
_______________________________________________
vfio-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/vfio-users
