On Mon, 2017-08-28 at 15:19 -0700, California Sullivan wrote: > Note that these tests can be quite time consuming, as we have to wait > for the first two tests to timeout, and the timeout values have to be > somewhat high as it sometimes takes a while for the ovmf firmware to > come up.
I think this needs to be addressed by making the runqemu support classes more flexible: instead of waiting for some hard-coded login prompt that one never gets, the code should be configurable enough to also enter commands into the UEFI shell and/or return as soon as a certain well-known string (like the "Security Violation" is printed). I have https://bugzilla.yoctoproject.org/show_bug.cgi?id=11438 open as a stretch goal for 2.4 around that, but haven't had time to actually do anything. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
