>>Why 3.0 now? I thought 2.12 fixes this?
theses flags exists since a long time (qemu 2.5), I think we didn't enabled it
on proxmox4 because of missin kernel support.
but as you said me that you are working on qemu 3.0, it was for enabled them by
default for this machine.
>>And does this work for win 7 now actually? The previous series was for
>>win 8 and up.
yes, win2008r2/win7
need to find the official crosoft link, but here a blog about it.
http://bigdata-guide.blogspot.com/2014/01/microsoft-hyper-v-hypervisor.html
- Mail original -
De: "Wolfgang Bumiller"
À: "aderumier"
Cc: "pve-devel"
Envoyé: Jeudi 13 Septembre 2018 11:13:41
Objet: Re: [pve-devel] [PATCH qemu-server] qemu 3.0 : add hv_synic && hv_stimer
hyperv enlightment
On Fri, Aug 31, 2018 at 03:43:01PM +0200, Alexandre Derumier wrote:
> This fix cpu bug on last win10 updates
> ---
> PVE/QemuServer.pm | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 9bfb4a1..52b0163 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -6700,6 +6700,11 @@ sub add_hyperv_enlightenments {
>
> if ($winversion >= 7) {
> push @$cpuFlags , 'hv_relaxed';
> +
> + if (qemu_machine_feature_enabled ($machine_type, $kvmver, 3, 0)) {
Why 3.0 now? I thought 2.12 fixes this?
And does this work for win 7 now actually? The previous series was for
win 8 and up.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
