similar to: Re: [edk2] Passing Xen memory map and resource map to OVMF

Displaying 9 results from an estimated 9 matches similar to: "Re: [edk2] Passing Xen memory map and resource map to OVMF"

2013 Nov 17
6
Re: [edk2] [PATCH RFC 0/7] OvmfPkg: make OVMF fully working with Xen
On Sat, Nov 16, 2013 at 3:31 AM, Jordan Justen <jljusten@gmail.com> wrote: > When I try to boot this on qemu or kvm, it asserts because the video > framebuffer address is NULL. > That''s expected because of the hack. ;-) > On Fri, Nov 15, 2013 at 7:58 AM, Wei Liu <wei.liu2@citrix.com> wrote: >> This is a quick hack I pulled together last night to make OVMF
2012 Oct 21
0
chain.c32 for tianocore EDK2 DUET EFILDR
Just pushed a hacky commit[1] to an "efildr_hack" branch at git.zytor.com/users/sha0/syslinux.git The commit message goes: This introduces support for chaining to tianocore's EDK2's DUET's EFILDRs. You should use EFILDR for FAT12, EFILDR16 for FAT16, EFILDR32 or EFILDR64 (depending on the architecture) for FAT32. Usage: chain.c32 efildr=<filename> where
2018 Apr 20
1
[PATCH] uefi: remove last references to kraxel's old edk2 builds
Commit 889386f8c6088e57fd68f2bb6bf85f69ecfc6f6c removed most of them already, so remove the last ones, and the supporting code. --- generator/UEFI.ml | 6 ------ v2v/utils.ml | 1 - 2 files changed, 7 deletions(-) diff --git a/generator/UEFI.ml b/generator/UEFI.ml index 5161e28ee..1ff3f84d2 100644 --- a/generator/UEFI.ml +++ b/generator/UEFI.ml @@ -30,12 +30,6 @@ open Docstrings (* Order
2016 Mar 22
0
Re: uefi built from tiancore via edk2 can't persist boot changes
On Mon, 2016-03-21 at 13:53 -0500, jsl6uy js16uy wrote: > for this host....my nvram setting look like >   <os> >     <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> >     <loader readonly='yes' type='pflash'>/home/xyz/OVMF.fd</loader> >     <nvram
2013 Nov 25
0
Re: [edk2] [PATCH RFC v2 7/7] OvmfPkg: introduce XenMemMapInitialization
Regarding patches 5-7, it seems like the mem-map code flow could be more shared. It is a bit challenging to unravel things though. I guess the only specific thing I can really point out is that PcdPciAllowFullEnumeration should be initialized in a different patch, and not within the mem-map init path. -Jordan On Tue, Nov 19, 2013 at 12:38 PM, Wei Liu <wei.liu2@citrix.com> wrote: > This
2016 Mar 24
0
Re: uefi built from tiancore via edk2 can't persist boot changes
On 03/21/16 19:53, jsl6uy js16uy wrote: > Apologies if this has been gone over, but I believe I have checked the > intertubes more than a bit..... > > I am using libvirt and have vms booting under an OVMF.fd to use an efi > firmware. I can create vms, linux ubuntu, and they will boot up. > However, everytime I reboot am I dropped into the default efi shell > provide by the
2016 Apr 20
1
Re: uefi built from tiancore via edk2 can't persist boot changes
Thanks VERY MUCH for all the info and help! Apologies for the extreme delay. I got distracted by other threads that forced out this work to later date. Also some frustration as well. ;) I completely missed this update. Apologies and thanks Will be diving back into this shortly! On Thu, Mar 24, 2016 at 3:57 PM, Laszlo Ersek <lersek@redhat.com> wrote: > On 03/21/16 19:53, jsl6uy js16uy
2016 Mar 21
4
uefi built from tiancore via edk2 can't persist boot changes
Apologies if this has been gone over, but I believe I have checked the intertubes more than a bit..... I am using libvirt and have vms booting under an OVMF.fd to use an efi firmware. I can create vms, linux ubuntu, and they will boot up. However, everytime I reboot am I dropped into the default efi shell provide by the tianocore build. Then I must walk the FS to the booting efi app and run, in
2013 Nov 19
0
[PATCH RFC v2 0/7] Make OVMF fully working with Xen
Hi all Manage to pull together another prototype without any hack in it. The first patch adds PcdPciAllowFullEnumeration in MdeModulePkg, which short-cuts full enumeration if set to false. This one should be helpful to QEMU as well. This patch set should work with QEMU / KVM as well (read: doesn''t break). The code path is the same as before if Xen is not detected. Comments are