similar to: x86_64 platform : addresses type

We found machines with >32 E820 memory map entries, where Xen fails to boot (but Linux does boot fine). The native Linux (both x86 and x86_86) already has: #define E820MAX 128 /* number of entries in E820MAP */ Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Jun --- Intel Open Source Technology Center -- diff -r 3bb1857981e6 -r 51e9c0c806b2 xen/include/asm-x86/e820.h ---

Hey guys, Here are my thoughts about current Xen boot infrastructure and some changes proposal. It is linked with EFI development but not only. Since the beginning Xen image and other needed stuff could be loaded into memory according to multiboot protocol. (e.g. implemented by GRUB). It means that current implementation of Xen takes info about current system config from multiboot_info_t

Hi Lin, In addition to bug 6541114... Bug ID 6541114 Synopsis GRUB/ZFS fails to load files from a default compressed (lzjb) root ... I found yet another way to get the "Error 16: Inconsistent filesystem structure" from GRUB. This time when trying to boot a Xen Dom0 from a zfs bootfs Synopsis: grub/zfs-root: cannot boot xen from a zfs root

flight 15155 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/15155/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 15130 build-i386-oldkern 4 xen-build fail REGR. vs. 15130 Tests which are failing intermittently

Hi, V6: The only change from V5 is in patch #6: - changed comment to reflect autoxlate - removed a redundant ASSERT - reworked logic a bit so that get_page_from_gfn() is called with NULL for p2m type as before. arm has ASSERT wanting it to be NULL. Tim: patch 4 needs your approval. Daniel: patch 5 needs your approval. These patches implement PVH dom0. Patches 1 and 2