similar to: Problems creating DomUs with large memory system/PAE enabled

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

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

I have a single VM (of 11) that has a recurring problem. This image has moved from machine to machine, with the problem following it. This image has been rebuilt from scratch, and the problem recurred. It would appear that there is something in the behaviour of this VM which causes it to crash and causes Xend to become unhappy. The problem presents as: Domain crashes, becomes zombie. xm

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I followed the instructions here: http://nixcraft.com/file-servers/14803-how-centos-5-pxe-linux-installation-server.html, along with a few other sources that were less successful, and I finally got a pxe boot going. I'm using CentOS 5.3 x86_64 media as the source. The server boots, but keeps hanging. Here is my boot line:

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

OK, here's the info Bastian asked for. Transcript: rob at thismachine:~$ dmesg Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.18-5-amd64 (Debian 2.6.18.dfsg.1-13) (dannf at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu May 31 23:51:05 UTC 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009c800 (usable)

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important On a machine with 2 dual-core Opterons and 16GB of memory, only about 3GB is detected by the hypervisor. Transcript: root at thismachine:~# xm dmesg Xen version 3.0.3-1 (Debian 3.0.3-0-2) (ultrotter at debian.org) (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)) Fri Nov 3 00:21:27 CET 2006 Latest

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection

I''ve installed Xen kernel for dom0 on a CentOS 4.4 but when i reboot the kernel says: _/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xenmdev = 59.12 University of Cambridge Computer Laboratory6 Sep 26 01:52 qemu-dm.6463.log Xen version 3.0.3.0 (root@uk.xensource.com) (gcc version 3.4.6 20060404 (Red Hastart qemu- -rw-r--r-- 1 root root t 3.4.6-3)) Mon Oct

Hi, I'm geting this message from virt-manager. Server: SuperMicro X8SIL with INTEL X3440 Here is my logs /var/log/dmesg: Bootdata ok (command line is ro root=/dev/md2) Linux version 2.6.18-194.3.1.el5xen (mockbuild at builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:49:53 EDT 2010 BIOS-provided physical RAM map: Xen: 0000000000000000 -

Not sure if this is a Fedora Core 6 issue. I already post a message on their list but didn''t get an answer. So I am going to try here.. Does anyone has Windows Guest OS running successfully with the Dom0 has all the physical memory allocated? If I don''t lower the memory assign to Dom0 through grub, I will not be able to run a Windows Guest OS. This what I got Using

After a couple hours last night.... doing a "killall -SIGUSR1 cpuspeed" bumps up the /proc/cpuinfo information for cpu mhz to 2393 Mhz. I did notice a little increase after that. However, the machine is still sluggish. I did a "hdparm -c 1 /dev/hda" but really did not notice any difference. I tried to download fglrx64_6_8_0_8.16.20-1.x86_64.rpm from ati (also 8.20.8) and get

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important The amd64 Dom0 crashes in early boot-stage. For debugging purpose I logged Kernel-Dump with minicom over Serial Console: System is: Dell Poweredge R710 2x Intel XEON X5650 96GB RAM Perc H200 SAS Controller 3x SAS-Drive I see a possible conjunction with Bug #600241 but acpi=off doesn't solve this problem. Regards,

I do not seem to be able to get any where with the power management functions. I have had a look at the xenpm Wiki page, but it hasn''t helped. Its probably something completely obvious, but I can''t see it. I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is running the latest Centos 5.3 kernel. My xm

Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

Hi - Xen cannot detect a PATA drive connected to my on-board promise 20378 K8T Neon MSI mobo. When I boot using a non exen kernel, the PATA is dected accordingly. Any thoughts? Following is dmesg from a regular non-exen kernel #uname -a Linux localhost 2.6.17-gentoo-r8 #1 Sun Oct 29 14:58:57 EST 2006 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux #dmesg Bootdata ok (command

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-5.8 Severity: normal Tags: upstream *** Please type your report below this line *** -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8,

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro