similar to: Xen pci passthru problems with kernel -164.6.1

Hi all, I am running CentOS 5.3 under xen on a VPS machine (so I have a limited control on the machine) I am playing with openswan and KLIPS and I need to build the ipsec.ko kernel module. I would need to download kernel source but I am really confused about what source I have to get. uname -r tells: 2.6.18-128.7.1.el5xen ls /lib/modules tells: ls /lib/modules 2.6.18-128.7.1.el5xen

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

Hi all, After rebooting my CentOS 5.5 server, i have the following message: ================================== Red Hat nash version 5.1.19.6 starting EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: invalid argument setuproot: moving /root failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting

Hi guys! I am new here on the list , and this is my first question, and i want to say tanks to you all for the help that i will get from you all. Ok there is my problem. I rent a virtual machine ( Server ) here in South Africa and this server is a Centos running ou top of a Xen server. The machine works 100% no problems , but wend i try to compile the dahdi-linux-complete-2.2.1+2.2.1 i got

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

Hi, I updated a server yesterday from "kernel 2.6.18-128.7.1.el5xen" to "kernel 2.6.18-164.el5xen" After rebooting, my message log is flooded every second or so with this error messages: Oct 6 14:52:20 xenserver1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": NON-FATAL recoverable (Branch=0 DRAM-Bank=0 Buffer ID = 0 RDWR=Read RAS=0 CAS=0

I previously reported this on the centos mailing list: http://lists.centos.org/pipermail/centos/2009-November/085672.html And I've found out that Red Hat has backported the VT-d support from Xen 3.3 to RHEL 5.4. http://lists.centos.org/pipermail/centos/2009-November/085677.html It seams to me that the "classic" Xen pci-passthru (up to Xen 3.2) works only on some minor cases as

Setup: RedHat/Centos/Sci. Linux 5 update 3, Dom0: kernel-xen-2.6.18-164.10.1.el5xen 64-bit (on Dell Poweredge 2950 dual quad-core). DomU: kernel-xen-2.6.18-164.10.1.el5xen 32-bit, 1 vcpu 6 domU''s per dom0. We have also seen the same problem with 2.6.18-164.9.1 and 2.6.18-164.6.1 kernels on this branch. Symptom: On 32-bit domU only (we have never seen 64-bit domU be affected), we observe

After many moons I have revisited this problem and found a solution that moves the problem further up the stack. I will post my new problem separately but just for completeness here is the solution. Original problem: trying to build kmod-dahdi-linux for out of date PAE kernel. Errors: rpmbuild --bb ~/localrpms/SPECS/dahdi-linux-kmod.spec --target=i686 --define "kversion `uname -r`" +

On 12/16/18 4:59 PM, Marc Haber wrote: > Hi, > > I would like to run a network firewall as a VM on a KVM host. There are > ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP > or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs > 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. > > To save

i followed readme as below #make world #uname -a 2.6.18-128.7.1.el5xen #make install # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.18- xen.img 2.6.18-xen i updated menu.lst title Xen 3.4 / XenLinux 2.6 kernel /boot/xen-3.4.gz console=vga module /boot/vmlinuz-2.6.18.8-xen root=<root-dev> ro console=tty0 module

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal File: pygrub pygrub error when trying to run a image created by xen-create-image with partitions option. ---------------------------------------------------------------------------------------------------------------------------------------- [2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm',

Hi, I'm having a linux box running with Centos 5.3 x86 (kernel 2.6.18-128.7.1.el5xen) which is freezing time to time and can't login neither trough console. The only thing what I can do, to pass the situation is to power off/on the pc. The pc is used only as a torrent server running with transmission 1.74. There are days when 400GB data traffic goes through the pc, and there

From: Mikhail Gordeev <obirvalger@altlinux.org> --- v2v/convert_linux.ml | 49 +++++++++++++++++++++++++++++++++++++++++++ v2v/convert_linux.mli | 2 +- 2 files changed, 50 insertions(+), 1 deletion(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index a871d754f4..5ae83a2f66 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -52,6 +52,7 @@ let convert (g :

Having problems compiling Broadcom netxtreme2-7.6.62 drivers using the Xen4CentOS (http://wiki.centos.org/QaWiki/Xen4) kernel: CentOS release 6.4 (Final) 3.4.61-9.el6.centos.alt.x86_64 I had to modify the Makefile's a little to get to pass the validation since it was referring to kernel 3.0 and 3.5 but not 3.4. But after doing this I still had the following problem: # make make -C bnx2/src

Greetings, I?m new to xen virtualization on CentOS, but I have been unable to find the answer to this problem I?m experiencing. My setup: AMD quad core (64bit), 8Gb ram. CentOS 5.3 dom0, CentOS 5.3 domU?s (paravirtualized). Dom0 is set up with two NIC?s, the built-in and a PCI card, and I set up xen bridging on both interfaces. My domU?s seem to boot up fine, run fine, and

Doing a kickstart install of Fedora 12 results in a non-bootable image. >From a virt-maanger instance, the error produced when trying to run the domU is: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire