On Wed, Mar 16, 2016 at 07:35:09PM +0100, Laszlo Ersek wrote: > OVMF uses this feature for a few flags. They are all called > "opt/ovmf/...". I followed the advice in "docs/specs/fw_cfg.txt" (which > shouldn't be surprising since I seem to have reviewed every patch for > that file):
Wait a second. You are saying upsteam OVMF puts files there. If users add their own flags that happen to be in opt/ovmf/ then what happens? And how do they *know* they should avoid that? There's no warning, guest just breaks in various ways. This is exactly the kind of mess I was worried about. We have a global namespace with no way to control what goes where. opt/ was for end users not firmware. The right thing to do would be for ovmf to reserve itself a directory under root. This really needs more thought. For now I'd suggest we drop the whole interface from 2.6 and come back to it after 2.6. -- MST
