Another way could be to use add romfile option to netX in vmid.conf,
and update it at vm_start if a new rom version is available (use glob on rom 
directory, take rom with biggest number suffix)



----- Mail original -----
De: "aderumier" <[email protected]>
À: "dietmar" <[email protected]>
Cc: "pve-devel" <[email protected]>
Envoyé: Jeudi 22 Octobre 2015 20:38:04
Objet: Re: [pve-devel] disable-efi-enable-pxe-roms.patch break livemigration 
from old qemu guest without pxe

>>I doubt we can fix this cleanly - what if we need to update the bios file 
>>again 
>>because of a bug? Wait every time for the next major release? 

It's possible also to use qmp "info qtree", to retrieve current rom filenames, 
on source vm. 
(we could keep roms with version suffix for examples) 







----- Mail original ----- 
De: "dietmar" <[email protected]> 
À: "aderumier" <[email protected]> 
Cc: "pve-devel" <[email protected]> 
Envoyé: Jeudi 22 Octobre 2015 19:08:42 
Objet: Re: [pve-devel] disable-efi-enable-pxe-roms.patch break livemigration 
from old qemu guest without pxe 

> I don't known if it's critical, 
> 
> but we could also add a rom option to vmid.conf, to netX: , to choose pxe or 
> efi. 
> 
> Then when next qemu machine version (2.5) will be release, we could enable it 
> by default. 

I doubt we can fix this cleanly - what if we need to update the bios file again 
because of a bug? Wait every time for the next major release? 
_______________________________________________ 
pve-devel mailing list 
[email protected] 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to