similar to: latest kernel

Hi Yum has just updated 5 of my Linux boxes running CentOS 4.3 to the 2.6.9-42 kernel. All is well on four of the boxes, but on the fifth the network card (eth0) will not work. I've downgraded the kernel to the previous version and the network card works fine again. I've tried removing and re-installing the new kernel, but the network card won't work with it. The details of the

Hi list, I've recently managed to install CentOS 4.4 on an Apple Mac Pro. Functionality-wise everything works great, but when trying to benchmark the system, I don't get stable runtimes, they differ by more than 30%. For example a benchmark run with our PDE solving code takes between 500 and 800 s on the completely unloaded machine. Suspicious kernel output (complete output attached):

Hi, I using asterisk 1.2.4 on a CentOS with Linux 2.6.9-22.0.2.ELsmp kernel. I've two x100p cards connected, only one card is reconigzed by asterisk. 02:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface 02:02.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31) 02:03.0 Communication controller: Tiger Jet

Hi, I have CentOS4.1 up to date and I get on boot: ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection divert: allocating divert_blk for eth1 ipw2200: ipw-2.2-boot.fw load failed: Reason -2 ipw2200: Unable to load firmware: 0xFFFFFFFE divert: freeing divert_blk for eth1 ipw2200: failed to register network device ipw2200: probe of 0000:03:03.0 failed with error -5 My understanding

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

Hi All, The only Internet connection our LAN have is via a proxy server (remotely located) which is in ZONE is defined as prox and in HOSTS defined as prox eth0:<proxy_ip> Local Area Network is defined in ZONE as net and HOSTS defined as eth0:<ip_subnet> Is it possible for shorewall to be a proxy server of the local area network (net)? and shorewall will then get the connection

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

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

Hello, Marvel Yukon Gigabit Ethernet is supported by CentOS ? -- -- Devel in Precio http://www.pas-world.com

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops

A gentle reminder on this issue Please can any one help on this problem? ________________________________ From: Manyam, Ramesh Sent: Wednesday, November 19, 2008 7:46 PM To: xen-devel@lists.xensource.com Subject: megaraid sas driver failing in Xen-3.4 unstable version On Xen-3.4 (unstable version), I have created CentOS HVM guest & WS2K8 HVM guest and dedicated MegaRAID SAS controller but

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 all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

Hello, I originally posted this to xen-users, but someone suggested I post it here. I am having ACPI problems on a PenguinComputing Altus1600 system. It has 2x dual core Opteron 2210 processors. The system boots with a standard Debian or Ubuntu SMP kernel, with ACPI enabled. However the xen live cd, binary xen install, as well as my own custom compile of xen 3.0.4 from source will not boot.

PV on HVM guests map GSIs into event channels; at restore time the event channels are resumed by restore_pirqs. Device drivers might try to register the same GSI again through ACPI at restore time, but the GSI has already been mapped and bound by restore_pirqs. This patch detects these situations and avoid mapping the same GSI multiple times. Signed-off-by: Stefano Stabellini

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello all I tried to enable PCI Passthrough in my Debian Squeeze installation. Unfortunately, it didnt work. The following bug showed up (excerpt from dmesg): [ 10.148612] uhci_hcd 0000:00:14.2: PCI INT D -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 4.678352] Failed to setup GSI :11, err_code:-22 [ 4.678480] dmfe 0000:00:0e.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low)