On 05/04/17 16:50, Igor Mammedov wrote: > On Thu, 04 May 2017 16:41:00 +0200 > Gerd Hoffmann <[email protected]> wrote: > >> Hi, >> >>> There is another thing to consider here, when vm is migrated to newer >>> qemu(with newer firmware version) then it might not boot on the next >>> restart due to hitting old set limit. >> >> Firmware is part of the migration data, so you have the same version on >> both ends. > true, until VM is shut down. After that it loads new firmware > from target host. So user will have see error that tells what is wrong > and manually fix limit value if vm startup config to another value > that would work for this specific fw/config combo.
I've been generally promoting the idea that firmware logs should be captured by libvirt by default, and exposed to the user similarly to QEMU error messages / error logs... Some rate limiting and/or log rotation would be necessary, so that guest code cannot flood the host system with infinite logs, but that wouldn't prevent saving error messages from non-malicious firmware. Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
