>>I think that this is impossible to implement, because users may have 
>>different hosts 
>>inside one cluster. So It is hard to tell what selection we should allow. 

Indeed, I have opteron and xeon mixed in same cluster.

improvement could be to check if flags are supported by host before starting or 
livemigrate.
I see a redhat bugzilla about this
https://bugzilla.redhat.com/show_bug.cgi?id=824987


But I think that enforce is enough for now,  the vm will stop when starting or 
the targetvm when we do live migration if flags are not supproted


----- Mail original ----- 

De: "Dietmar Maurer" <[email protected]> 
À: "Alexandre DERUMIER" <[email protected]>, "Daniel Hunsaker" 
<[email protected]> 
Cc: [email protected] 
Envoyé: Vendredi 28 Mars 2014 06:22:40 
Objet: RE: [pve-devel] [PATCH] enforce cpu check 

> >>but it would be nice to prevent selecting a non-functioning option in the 
> first place. 
> 
> Not sure it's easy to implement, we need to implemented same feature 
> than qemu code, checking host cpu flags and guest cpus flags (and maybe 
> some other tricky things). 
> Maybe can you create a promxox bugzilla? like this we don't forgot your 
> suggestion. 

I think that this is impossible to implement, because users may have different 
hosts 
inside one cluster. So It is hard to tell what selection we should allow. 
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to