similar to: Dom0 running on Centos

Hi, I have an issue with my XEN servers, in that when I do a yum upgrade, it upgrades the kernels, and then updates the grub.conf file to boot with the normal Linux kernel, and not the XEN kernel - and I tend to forget to update the grub.conf, until I reboot and see XEN isn't running. So, is it safe to remove the normal kernel & kernel-development, and only run the XEN kernel? This is

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 Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial

Hi list! Now when Fedora 10 is out, I thought of writing here what's needed to run Fedora 10 Xen domUs on CentOS 5 dom0. Fedora 10 does not have separate kernel-xen, but instead Xen domU support is included in the normal kernel-PAE.i686 and kernel.x86_64 (based on the pv_ops Xen support included in the mainline/vanilla Linux kernels). RHEL 5.3 beta (and final obviously too) includes

-----Original Message----- From: xen-users-bounces@lists.xensource.com <xen-users-bounces@lists.xensource.com> Sent: Thursday, 24 September 2009 3:09 AM To: xen-users@lists.xensource.com <xen-users@lists.xensource.com> Subject: [Xen-users] Manually create Fedora domU on CentOS 5.3 dom0 I am trying to setup a Fedora 11 domU on my CentOS 5.3 dom0 installation. I want it to use a dom0

I've been going along not noticing things happening right under my nose. so imagine my surprise when I discovered last night that my Centos 5 box has installed multiple new kernels over the last few months, as updates come out, and IT IS NOT BOOTING THE NEWST ONE. grub.conf says to boot kernel 0, and 0 is the newest one. but the one it actually boots is 6 or 8 down the list (clearly I've

I've recently upgraded a Centos 5.3 machine to Centos 5.5. The hardware isn't HVM capabile so I'm only running para-virt guests. Using a vanilla i386 kernel boots without, but the newer kernel-xen locks up the Dom0 after a couple of minute. I'm only booting into single user mode for these tests so no VMs are active. *kernel-xen-2.6.18-128.1.10.el5 - no issues

Hello, We have default xen 3.1.2 on centOS 5.5. We now want to upgrade xen 3.1.2 to xen 4.0.1 while using the existing dom0 kernel (2.6.18). I followed the instructions on http://wiki.xensource.com/xenwiki/Xen4.0 hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg cd xen-4.0-testing.hg make xen make tools make stubdom make install-xen make install-tools make install-stubdom And

Hey everyone, I was hoping you all could help me with a problem. I''m trying to run the xen kernel 2.6.18-164.11.1.el5xen on CentOS 5.4 X86_64. The dom0 machine boots the 2.6.18-164.11.1.el5 kernel without an issue, so I can get into it and get any information you might need, however the issue I''m having is that once I select the xen option from my grub menu, it will go into the

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Hello everyone. I've stumbled upon a strange networking issue with multiple interfaces on CentOS 5. The network setup is just like the diagram in http://lartc.org/howto/lartc.rpdb.multiple-links.html It looks like linux is not routing correctly outgoing packets on interfaces different from the one of the default gateway, but instead broadcasts an ARP request on the link, looking for the

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

CentOS Errata and Security Advisory 2010:0504 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0504.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: d6fec8de3caea170a9476788898bb003 kernel-2.6.18-194.8.1.el5.i686.rpm d62a5f48eeb9e575ca6382d4d3045d14 kernel-debug-2.6.18-194.8.1.el5.i686.rpm

Hello. Yesterday I tried installing Fedora 10 and Fedora 11 i386 Xen domUs/guests using virt-install and/or virt-manager on CentOS 5.3 Xen x86_64 dom0/host. It doesn't work. The guest kernel crashes early and the graphical VNC console newer shows up. Installing x86_64 domU on x86_64 dom0 work well. 32-on-32 works aswell. So it's a 32-on-64 bug. CentOS 5.3 32b guest on x86_64 host

CentOS Errata and Security Advisory 2010:0504 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0504.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: fe40a3e75db98a5aeae19a238727d3a7 kernel-2.6.18-194.8.1.el5.x86_64.rpm 7c15e699d45a5407be36da78fe2cb1e4 kernel-debug-2.6.18-194.8.1.el5.x86_64.rpm

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

Hi, We''re trying to run Xen on a Debian "Etch" base system (kernel 2.6.18-6-xen-amd64), but have come across a strange networking error whenever bridging (vif-bridge/network-bridge) is in operation. The symptom is that the dom0 base system loses all network connectivity to the outside world while the two guest instances function perfectly well. As far as we can tell, we

S pozdravem Stan.M. On 25.5.2010, at 18:00, centos-virt-request at centos.org wrote: > Send CentOS-virt mailing list submissions to > centos-virt at centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a message with subject or body 'help' to >

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, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed