similar to: Dom0 fails to boot CentOS 5.4

Hello list, when installing Dahdi, the following error comes up : You do not appear to have the sources for the 2.6.18-164.11.1.el5xen kernel installed. make[1]: *** [modules] Error 1 The running kernel version : -bash-3.2# uname -a Linux vds.hosting.net 2.6.18-164.11.1.el5xen #1 SMP Wed Jan 20 08:06:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux -bash-3.2# ls /usr/src/kernels/

Hi, I am using Centos 5.4 x86_64 with kernel 2.6.18-164.11.1.el5xen. I've installed a Centos 5.4 (64 bit too) DomU (paravirtualized), process was apparently with no problems, but DomU refuses to start, this the error: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. Today I went into the office on a Sunday to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync'd files from root partition of physical

Hi, This is the specifications dom0 -------- [root@server ]# uname -r 2.6.18-238.12.1.el5xen [root@server ]# uname -m x86_64 domu -------- root@test:~# uname -r 2.6.18-238.12.1.el5xen root@test:~# uname -m x86_64 My issue is like dom0 clock is moving too fast. Interestingly, it is affecting ubuntu & debian domU. centos domU is just working fine. Here is how I could recreate the problem.

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync''d files from root partition of

Hey, I was looking for step by step installation for RHEL5 as dom0 and RHEL5 as domU, but could not find it.I put some instructions, hope it will save some time for somebody. If you will find some errors please fix them :) I assume that you already have rhel 5 up and running (webserver as well).I will install guest system in paravirtualized mode (mine processor does not support full

Hello, I have installed rpm version of xen 3.4.3+ libvirt 0.7.0-6 on my server with Centos 5.4 (kernel 2.6.18-238.12.1.el5xen) When I run reboot a domU (para virtualized Linux) by command "virsh reboot [vm]", sometimes domU cannot be rebooted but sometimes can, pattern is random. Also sometimes when domU reboots by "virsh reboot [vm]" , my ssh connection to dom0

Hi, I've got a big problem with a cx88 DVB card. It is passed through to a CentOS 5.3 domU (dom0 is CentOS 5.3 as well), but when I shutdown the domU, this happens: cx88[0]: mpeg risc op code error cx88[0]: mpeg - dma channel status dump cx88[0]: cmds: initial risc: 0xffffffff cx88[0]: cmds: cdt base : 0xffffffff cx88[0]: cmds: cdt size : 0xffffffff cx88[0]: cmds: iq base

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

Dear experts, to monitor performance of applications on our private clouds I decided to use Xenoprof. For that, I installed patched OProfile 0.9.5 on Dom0 and DomU. Then, I started the daemon on Dom0 opcontrol --start-daemon --active-domains=1 --separate=library --event=LLC_MISSES:90000 and received the following error: /usr/local/bin/opcontrol: line 1171: echo write error: invalid

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

Hi all, I am in a bit of a fix here, I have several Guests paravirtualized running on a Dom0 that is currently running the 2.6.18-92.1.22.el5xen Kernel. All my guests (administered by different people) have subsequently been updated to later versions of the kernel (namely 2.6.18-164.el5xen or 2.6.18-128.4.1.el5xen). Ones that are still running are using the Kernel 2.6.18-128.4.1.el5xen while

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. At the weekend I went into the office to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

On Wed, 18 Jun 03 09:39:42 EDT, you wrote in message <200306181351.h5IDpEOC122970@northrelay03.pok.ibm.com>: >I have installed the binary of R-1.7.1 for Windows from CRAN. After >using the Cut or Paste buttons the R Console window does not respond >to keyboard input; the window can be reactivated by switching to another >window and back to the R console. Cutting and pasting

Hello all, I am trying to get an Ubuntu 8.04 image running on my CentOS 5.2 Dom0 which so far has only been running CentOS 5.2 DomUs. The image I am trying to run was fetched from jailtime.org (just so I didn't have to go through building an image for myself). The configuration of the DomU is based on what the guys at jailtime.org provided and its as follows name = "redgum"

Hello all, I am sort of new to XEN and I have a dedicated server that is hosted for me. This server is an intel single quad 4 with 4 gig of ram. The OS is Centos 5 completely updated. I have installed XEN from the add and remove applet within Centos. Here is my grub.conf: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.10.el5PAE)

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having some dom0 running 2.6.18-53.1.6.el5xen (x86_64). On the dom0 where the load is high (more than 70% of total system memory consumed by dom0 and domU) we have a lot of "memory squeeze ". The result is that the domU seems to be blocked (no network/no disk acces/ etc....). Looking for a solution in xen

Hi, on one of our systems I see that while the time on the Centos 5.4 Host is correct it lags behind on two of the 5.5 guests by almost 5 minutes but is correct for the third domU. From what I understand the clock of the system is controlled by the host and and guest cannot write to it (and because of that not change it). Does anyone now what the cause could be and how I can fix the time for

Hi, My storage admin just assigned a Lun (fibre) to my server. Then re scanned using echo "1" > /sys/class/fc_host/host5/issue_lip echo "1" > /sys/class/fc_host/host6/issue_lip I can see the scsi device using dmesg But mpath device are not created for this LUN Pleas see below. The last 4 should be active and I think this is the problem Kernel: