similar to: [PATCH 5/5] xen: reserve Xen start_info rather than e820 reserving

Problems start before any of the kaiser code executes, though it could still be related to CONFIG_KAISER since that has effects beyond kaiser.c. --- (early) Initializing cgroup subsys cpuset (early) Initializing cgroup subsys cpu (early) Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild at c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Thu Jan 4 17:31:22 UTC

A CentOS 6.9 domU with kernel 2.6.32-696.18.7.el6.x86_64 also fails to boot on a CentOS 6.9 dom0 with kernel 4.9.63-29.el6.x86_64 and xen 4.4.4-34.el6.x86_64 Xen logs lines like these (among others): /var/log/xen/xend.log:[2018-01-05 17:55:45 2357] WARNING (XendDomainInfo:583) Could not unpause blktap disk: ('unpause', '-p11520', '-m4') failed (5632 )

Hi, we''re using Xen 3.3.0 on Debian Etch with 2.6.18.8 kernel from xen.org on dom0. We have problems starting Intrepid domU (using Intrepid''s kernel 2.6.27-7-server) if we give more than 4GB of memory to this domain. Using memory = ''4096'' works perfectly, but changing it to ''4097'' already gives an error. Can anyone put some light on this?

I can confirm the issue with 2.6.32-696.18.7.el6.x86_64, but mine looks alittle different... Maybe because i'm using pvgrub. ============= Init TPM Front ================ Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT Tpmfront:Info Shutting down tpmfront close blk: backend=/local/domain/0/backend/vbd/14/51712 node=device/vbd/51712

Attached patch makes the balloon driver arch-neutral (compiles on ia64... look ma, no #ifdef''s!). Please apply to xen-unstable. One change should be eyeballed, line 257 in balloon.c, because phys_to_machine_mapping[pfn] is not identical to pfn_to_mfn (different by sign bit, should be OK?) Signed-off by: Dan Magenheimer <dan.magenheimer@hp.com> diff -r 0255f48b757f

Xen patchbot -unstable wrote: ># HG changeset patch ># User cl349@firebug.cl.cam.ac.uk ># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17 ># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a >New console transport and update xenconsoled. >Add a new console interface using a seperate shared page and event channel >instead of passing the console input/output over control

move e820 ACPI entries into RAM. ACPI RAM maybe used as RAM after ACPI data is parsed, but current e820 entries don''t comply to this. Signed-off-by: Xin Li <xin.b.li@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The following was just sent to me... since some people have experienced these kinds of problems and asked about them I thought I'd forward it. Please leave the discussion on the linux-kernel mailing list, however. -hpa -------------- next part -------------- An embedded message was scrubbed... From: achen at t-online.de (Alexander Achenbach) Subject: [PATCH] zero-size E820 memory (kernel

git://git.zytor.com/users/genec/syslinux.git Branch memdisk-maxmem-for-hpa The goal of the changes was to process a "mem=" parameter (ie "mem=128M" or "mem=134217728"; same value) and alter the memory map that MEMDISK returns in INT15h AXe820h by changing any type 1 (available) ranges above the "mem=" value to type 2 (reserved) and splitting a type 1 that

All, When attempting to pxeboot the latest Xen3.0 hypervisor/kernel it was failing with the following error: ------ \ \/ /___ _ __ |___ / / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \ |_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |____(_)___/ \__,_|_|

The changeset ''12803:df5fa63490f4da7b65c56087a68783dbcb7944f8'' added a new hypercall XENMEM_set_memory_map for specifying the e820 mapping. There was a small bug in the userspace side of this change though - the e820 mapping was specified based on the ''memory_static_min'' domain info parameter which means the memory map size is clamped to the value

I can''t find this patch on any mailing list to respond to so starting a new thread. In case I''ve not missed it but instead it really wasn''t posted -- in the future can we try and ensure that any patches have been posted at least once. Same for the pull request, it should go to a list. BTW the version in Konrad''s tree is Stefano''s 2.6.39-rc1-fixes

Subject: Obtain VESA capabilities and attributes of VESA mode Also, move some more common code to dom0_init_screen_info(). This was tested on 2.6.22.1, and only made apply to 2.6.18 without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-08-07/arch/i386/kernel/setup-xen.c =================================================================== ---

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

Hi, I am following http://xenbits.xen.org/docs/unstable/misc/vtpm.txt, but I''m having some problems when I try to start vtpmmgr-stubdom I''m using Xen 4.3 on Ubuntu 12.04 and I have a physical TPM. The config file for vTPM manager is: kernel="/usr/local/lib/xen/boot/vtpmmgr-stubdom.gz" memory=16 disk=["file:/var/vtpmmgr-stubdom.img,hda,w"]

Hi all. I am trying to debug a kernel that I built, and I hope I could see some debug info printing out via XENPRINTF. I use it in the source code of kernel like: XENPRINTF("nr_pages: %ld shared_info: 0x%lx flags: 0x%lx pt_base: 0x%lx " "mod_start: 0x%lx mod_len: 0x%lx\n", xen_start_info->nr_pages, xen_start_info->shared_info, xen_start_info->flags,

Hi all. I am trying to debug a kernel that I built, and I hope I could see some debug info printing out via XENPRINTF. I use it in the source code of kernel like: XENPRINTF("nr_pages: %ld shared_info: 0x%lx flags: 0x%lx pt_base: 0x%lx " "mod_start: 0x%lx mod_len: 0x%lx\n", xen_start_info->nr_pages, xen_start_info->shared_info, xen_start_info->flags,

arm: implement ARMv7 tlb ops. xen/arch/arm/xen/Makefile | 1 + xen/arch/arm/xen/cache-v7.S | 17 +++++------------ xen/arch/arm/xen/domain_build.c | 6 +++--- xen/arch/arm/xen/tlb-v7.S | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 60 insertions(+), 15 deletions(-) Signed-off-by: Jaemin Ryu <jm77.ryu@samsung.com> diff -r c6a412adfae7

Hi all, This is a trivial patch which adds the two fields to start_info_t for the shared page and event channel port for the share. Feel free to destroy this in any way. The python binding just fills zeros in for the moment, making it harmless. Mike Wray has a nicer version in his tree, but this is the minimal version. (Thanks to Mike for the .esp fix, too). Cheers, Rusty. diff -ur

E820 definitions copied from IntelFrameworkModulePkg/Csm/ LegacyBiosDxe/LegacyBiosInterface.h. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> --- OvmfPkg/Include/IndustryStandard/E820.h | 46 +++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode