similar to: Bad FADT and timer going backwards

Displaying 6 results from an estimated 6 matches similar to: "Bad FADT and timer going backwards"

2005 Jun 15
2
x86_64 - Dom0 will not boot on EMT64
I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1
2004 Sep 23
16
network_alloc_rx_buffers panic
Some users are hitting this panic in network_alloc_rx_buffers() when running a big network intensive app: /* Check return status of HYPERVISOR_dom_mem_op(). */ if ( rx_mcl[nr_pfns].args[5] != nr_pfns ) panic("Unable to reduce memory reservation\n"); I''m not clear on what is happening here. Are the domains changing size? Which memory reservation is being
2005 May 24
28
Xen & Transmeta (from xen-users)
All- With suggestions from Ian and previous posts on this list, I''ve been investigating why Xen causes a Transmeta-based system to reboot immediately.. I''ve added instrumentation to xen/arch/x86/boot/x86_32.S (a collection of ''.asciz "foo"'' statements) hoping to locate a point of failure.. and it dies sometime before this code is run.. At what point
2009 Sep 30
3
Gathering information about RAM in sockets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have an IBM xseries 345, running CentOS 5.3, hosting a few Xen domUs. However, I need more RAM -- but cannot remember if all (four) RAM sockets are populated (which would mean to buy higher capacity modules) or if there are two slots left to use. However, I'd like (and think that it's possible, but don't remember how) to
2004 Oct 21
3
Problem booting Dom0
Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9
2009 Jan 29
0
[PATCH v2] txt: 2/5 - ACPI Generic Address Structure for tboot shutdown
New versions of tboot support ACPI GAS (Generic Address Structure) for handling sleep states. This required a change to the tboot_shared_t data structure that is not backwards compatible. This patch requires that new version makes use of GAS when invoking tboot on shutdown. Signed-off-by: Shane Wang <shane.wang@intel.com> Signed-off-by: Joseph Cihula <joseph.cihula@intel.com> diff