similar to: [PATCH] move e820 ACPI entries into RAM

Two more observations: (adding to my previous below email) 1) Centos 5.6 also showing the same ACPI errors as in CentOS 5.5 2)BIOS-E820 map has a difference in the first line: (0000000000010000 instead of 0000000000000000) ================================ - Centos-5.3 BIOS-E820 memory map is: BIOS-e820: 0000000000000000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000

Hi, Am trying to build SMP kernel. Took kernel-2.6.18-194.src.rpm, extracted, rpmbuilded with SMP option. Successfully compile the new kernel and when using that kernel to boot up, following errors were shown up(highlighted in bold & red color): My kernel config file has ACPI and PCI configs enabled. Any pointers to what caused the problem are appreciated. ******************************

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: grave Hello, I am trying to install the XEN Hypervisor on a Debian Jessie Server. When I am booting without the Hypervisor, everything works fine, but when I am Booting WITH the XEN-Hypervisor, then System crashes / reboots after the "Scrubbing Free RAM" Message without any Error-message, just a blank screen.

Don''t compile HVM_DBG_LOG into xen by default. Signed-off-by: Xin Li <xin.b.li@intel.com> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Use reserve_early rather than e820 reservations for Xen start info and mfn->pfn table, so that the memory use is a bit more self-documenting. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> --- arch/x86/xen/setup.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 15c6c68..ad0047f 100644

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'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

Had to changed the Subject header because the mailing list software thought the previous one ("so old bootloader" ...) was suspicious. Just a backgrounder and a little more info I've gathered: Trying to install Fedora Core 3 via PXE using DHCP-TFTP. Kernel loads but initrd isn't used for rootfs. The machine's an AMD Athlon 64-based box with 512MB physical memory (one DDR

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

Hello, This is not a question directly related to asterisk. I am currently rinning ansterisk on a Debian server and i just upgraded my memory from 1GB to 2GB. However, my linux OS does not recognise the memory upgrade. The BIOS does, but the Debian Linux refuses to use the entier memory, currently, it registered only 900MB. Can anyone tell me why thi is and a solution to this?? My Debian version

when I run dmesg PE2950 Dell Server I see the following line Linux version 2.6.18-92.1.6.el5 (mockbuild at builder15.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed J un 25 13:45:47 EDT 2008 Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 -

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

[ 0.000000] microcode: CPU0 microcode updated early to revision 0x1b, date = 2014-05-29 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc3+ (airlied at crackbookpro) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #44 SMP Sat Dec 5 16:05:39 AEST 2015 [

Hi Jan Beulich, > changeset 15414: 3cf5052ba5e5 x86: machine check exception handling With the c/s, when creating HVM guest, I can only see a white Qemu window. :( Can you have a look? Thanks. PS: the serial log follows: (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f2000000 (XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c101 (XEN) HVM1: pci dev 03:0 bar 14 size 01000000:

Hello Ian, i?ve tried to install "xen-linux-system-amd64" on a VMware host again and everything went fine. The Installation completes and i can boot into Xen und boot up the Dom0. So, you were right. It seems to be a problem with the initscript, but as far as i can tell, only when running xen under xen. To me, this specific issue is resolved, since the meta-package seems to install

Hi Sydney, Thanks for all the info. I'd like to have the initscript work sensibly in this scenario at some point (not for Jessie though, it's too late now) so I think we may as well keep this bug around to track that since it already contains a bunch of useful information. Thanks, Ian. On Tue, 2014-12-30 at 00:39 +0100, Sydney Meyer wrote: > Hello Ian, > > i?ve tried to

> On 23 Dec 2014, at 12:59, Ian Campbell <ijc at debian.org> wrote: > > Control: reassign -1 xen-utils-common 4.4.1-6 > Control: retitle -1 /etc/init.d/xen fails when run in a guest, causing postinst to fail. > > Seems like this issue is in the Xen packages not in the xen-linux-system > metapackage, so reassigning. > > On Mon, 2014-12-22 at 23:01 +0100, Sydney

Steven, I found where the difference is, it may be my fault: My changeset number + 1 = your changeset number. My 11160 is your 11159, and my 11161 is your 11160. Attached please see those patches, Thanks, Winston, -----Original Message----- From: Steven Smith [mailto:sos22@hermes.cam.ac.uk] On Behalf Of Steven Smith Sent: Wednesday, October 11, 2006 10:33 AM To: Wang, Winston L Cc: Stefan Berger;