Comment # 41 on bug 976250 from Gary Ching-Pang Lin

(In reply to sd fs from comment #38)
> > The other two patches are for bsc#982193 to enable the file-based NvVar. I build an OVMF without those two patches in my branch(*).
> 
> Upgraded Dom0 to
> 
> 	rpm -qa | grep -i ovmf
> 		ovmf-2015+git1462940744.321151f-31.1.x86_64
> 		ovmf-tools-2015+git1462940744.321151f-31.1.x86_64
> 		qemu-ovmf-x86_64-2015+git1462940744.321151f-31.1.noarch
> 
> re-exec'd 
> 
> 	mkinitrd
> 	grub2-mkconfig -o /boot/grub2/grub.cfg
> 
> rebooted Dom0
> 
> Guest launch still fails.
> 
That's weird...
The only difference between the OVMF of comment#11 and the one in my branch is
a HTTP/TCP patch which your system will never execute.

> Here's the debug.log
> 
> 	http://pastebin.com/raw/7kYSMm7a
> 
> Notice still the references to file-based NvVar, e.g.
> 
> 	"Saved NV Variables to NvVars file"
> 
> 
> ?
It's because you were using the partition in a real disk, so OVMF can access it
without connecting the XenBus. This error still showed:

Variable Check ReadOnly variable fail Write Protected -
04B37FE8-F6AE-480B-BDD5-37D98C5E89AA:VarErrorFlag

so your system needs ovmf-bsc982193-dont-restore-readonly-var.patch to make
file-based NvVars really work.