>>Or would your patch become included in the regular proxmox..?

Yes. I have sent a patch this morning on the pve-devel mailing list.
Waiting for review.

----- Mail original -----
De: "lists" <li...@merit.unu.edu>
À: "proxmoxve" <pve-user@pve.proxmox.com>
Envoyé: Mardi 8 Novembre 2016 10:44:07
Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM

Hi Alexandre, 

That would be super, i guess! (although you'd have to tell me also how 
to apply the patch to our proxmox....) 

Or would your patch become included in the regular proxmox..? 

The latter seems appropriate, since from what I understand, this is 
something that also virt-manager does automatically. 
(https://github.com/virt-manager/virt-manager/commit/cbba1c4dd381) 

Anyway: much appreciated, thanks! 

MJ 

On 8-11-2016 0:42, Alexandre DERUMIER wrote: 
> I can make a patch for this. 
> 
> 
> ----- Mail original ----- 
> De: "lists" <li...@merit.unu.edu> 
> À: "proxmoxve" <pve-user@pve.proxmox.com> 
> Envoyé: Lundi 7 Novembre 2016 20:36:35 
> Objet: Re: [PVE-User] disable HyperV enlightments for win7 uefi VM 
> 
> Just to add to my own question: 
> 
> To disable HyperV enlightments you have to make sure that these options 
> are NOT set: 
> 
> "hv_time,hv_relaxed,hv_spinlocks=0x2000" 
> 
> Can anyone tell me how to do / where to check that in proxmox? 
> 
> MJ 
> 
> On 7-11-2016 18:50, lists wrote: 
>> Hi, 
>> 
>> We are trying to migrate a win7 uefi machine into proxmox, and so far 
>> we're failing. Done a lot of reading, and what seems to be the problem: 
>> 
>> https://bugs.launchpad.net/qemu/+bug/1593605 
>> 
>> My conclusion ius that we should be able to run win7/uefi on qemu, but 
>> we need to disable the disable HyperV enlightments. 
>> 
>> And this is where we're stuck now, google tells me numerous to ENABLE 
>> them, for example: 
>> 
>>> virt-xml $VMNAME --edit --features 
>>> hyperv_relaxed=on,hyperv_vapic=on,hyperv_spinlocks=on,hyperv_spinlocks_retries=8191
>>>  
>>> 
>> 
>> But proxmox does not know virt-xml, and we need to DISABLE them, using 
>> (what we understand) cpu flags. 
>> 
>> Could someone help us in the right direction? 
>> 
>> MJ 
>> _______________________________________________ 
>> pve-user mailing list 
>> pve-user@pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> _______________________________________________ 
> pve-user mailing list 
> pve-user@pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> 
> _______________________________________________ 
> pve-user mailing list 
> pve-user@pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
> 
_______________________________________________ 
pve-user mailing list 
pve-user@pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 

_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Reply via email to