similar to: WG: Dom0 kernel crashes when dom0_mem= is used!

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,

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 -

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

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

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

I''ve a problem with managing power consumption on Intel Nehalem CPU. I''ve installed Xen 3.4 on our Dell PowerEdge T610 system on a Ubuntu 9.04 distribution. I recompiled the kernel 2.6.30rc5. Now I can see the c-states of the CPUs but no access to P-states information and the frequency scaling does not work. By the way, if I run the kernel 2.6.28.13 which is the last one

Hi all, I''ve successfully installed xen3.3.0 on Linux ubuntu 2.6.27.5 #1 SMP i686 GNU/Linux. I built xen with the requisite XSM_ENABLE=y, ACM_SECURITY=y and believe I have the correct config parameters in the 2.6.27.5 kernel. Boot goes smoothly, set to automatically create 2 domUs. All appears okay with XSM/ACM... root@ubuntu:~# xm dmesg | grep -i xsm (XEN) XSM Framework v1.0.0

Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal My 32Bit Dom0-crashes with error "Out of SW-IOMMU space for 65536 bytes" after doing moderate I/O on the local storage, which is a software-raid1 over 3 harddrives, connected to the builtin Perc H200 controller with ext3-fs. The error is reproduceable with "dd if=/dev/zero of=bigfile bs=1024 count=1000000"

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

Hi there We have a pair of servers running FreeBSD 9.1-RC3 that act as transparent layer 7 loadbalancer (relayd) and pop/imap proxy (dovecot). Only one of them is active at a given time, it's a failover setup. From time to time the active one gets in a state in which the 'thread taskq' thread uses up 100% of one cpu on its own, like here: ---- PID USERNAME PRI NICE SIZE

Hello, Since FreeBSD 9.1 I have strange problems with the distribution. Some servers are rebooting without any kernel panic, instanly. First i thought it's a problem with my KVM system, but one of my FreeBSD under a Dell R210 have the same problem. The servers concerned are now: - Monitoring server - LDAP test server - Some other servers, randomly (not in production). First i thought it's

Hello everybody, we recently got three Dell PowerEdge servers equipped with Qlogic QLE2462 cards (dual FC 4Gbps ports) and an EMC CLARiiON CX3-40 SAN. The servers with the FC cards were successfully and extensively tested with an older SUN StorEdge T3 SAN. However, when we connect them to the CX3-40, create and mount a new partition and then do something as simple as "tar -C /san -xf

The redbuild boxes for redports are doing a very good and reliable job getting kernel panics out of 10.0: http://people.freebsd.org/~sbruno/redbuild_panic.txt Pretty frequent and pretty nasty. Happening on multiple machines under load. sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc:

Hi All. I have a server which hanged two times because we could not connect to the box, it was not responding. In /var/log/messages I saw: Apr 11 10:13:29 server kernel: INFO: task imap:5855 blocked for more than 120 seconds. Apr 11 10:13:29 server kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 11 10:13:29 server kernel: imap D

It's hard to tell without full logs but since this is a Dell 410 there is a possibility that this is the same bug as #603632. Please test with kernel 2.6.32-29 when it is uploaded (which should be later this week). If this does not help then please provide a full log of the boot. Ian. -- Ian Campbell Current Noise: Witchery - The God Who Fell From Earth I give you the man who -- the man