similar to: need to load uhci_hcd with acpi=off

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

Does anybody please have any experience with the following CentOS 6 warnings in logwatch? WARNING: Kernel Errors Present ACPI Error (psargs-0359): [ ...: 1 Time(s) pci 0000:00:01.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.5: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.6: PCIe errors

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround

Dear CentOS users, I run a small Facebook game at a CentOS 6.3 machine with PostgreSQL 8.4.3 + few PHP scripts + 1 Perl daemon and even though the server worked ok, I've suggested my users to double up the RAM to 32 GB and they have collected money for that. Now my problem is that I don't know, which knob to turn and how to really use the additional memory. Below is my top output at the

Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t

I'm trying to figure out why 2 machines have a "hard I/O lock" on the HDD when running EL6. I have 4 identical machines, all were stable with EL5. 2 work great with EL6, 2 do not. I've checked momtherboard BIOS versions and settings, SAS controller BIOS versions and settings, they are the same between the working and non- working systems. When booting a non-working system,

@@ -491,16 +512,15 @@ int pirq_guest_bind(struct vcpu *v, int int rc = 0; cpumask_t cpumask = CPU_MASK_NONE; + WARN_ON(!spin_is_locked(&v->domain->evtchn_lock)); I find this WARN_ON() is triggered harmlessly when I assign device to HVM guest. The call trace is XEN_DOMCTL_bind_pt_irq -> pt_irq_create_bind_vtd() -> pirq_guest_bind(). Should we

... rather than __assign_irq_vector(), to ensure desc->affinity gets initialized properly. This at once eliminates the need to forward-declare the latter function. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/irq.c +++ b/xen/arch/x86/irq.c @@ -25,7 +25,6 @@ #include <public/physdev.h> static void parse_irq_vector_map_param(char *s); -static int

Ok im trying to play Counter Strike 1.6, but it crashes when i join a server. The Video is set to OpenGL and when i set it to "Software" it started working (but the quality was really shitty so i want OpenGL). I have this video card VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] And when the game crashed i got this error: Code: Allocating

Hi I just upgraded my domU kernel from 2.6.29-gentoo-r5 to 2.6.30-gentoo-r4 and was not able to boot successful. Only after disabling the xen frame buffer I was able to boot my domU kernel. Did I mis configure something or has the xen framebuffer fallen into the hands of the bitrot monster? No obvious hinds or messages on the (text) console or on xm dmesg. The output stops just before the

Hi list, I installed 2 HB8 cards each of them with a Quad Bri modules in a HP 360 G6 running Debian Squeeze. Here is an output of dmesg wafter server has booted: [ 9.784123] wctdm24xxp 0000:0b:08.0: PCI INT A -> GSI 31 (level, low) -> IRQ 31 [ 11.847073] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex [ 11.847600] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

Happy New Year. Finally got my fw and tc rules down pat for the bridge, now interested in introducing a third nic to have nat on the box as well. Does anyone have a idea of a good place to start reading up on the subject, mainly interested in how to setup the flow direction to start with as to get a overall understanding of the flow, found that help best. Internet --- eth0 --- eth1 ---

Trying to debug a database server getting cpu softlocks causing SSHD to hang and not let anybody log in. Figured that a good first step would be to get some kernel dumps when the problem occurs. According to what I read at the following web site, I can get dumps for softlock problems too. Here's the site: http://blog.kreyolys.com/2011/03/17/no-panic-its-just-a-kernel-panic/ Using a

A note to confirm that "-m physdev --physdev-is-bridged" in the iptables command does enable iptables to work in a bridged environment. I was fighting the same problem and this indeed solved it. Below is my test script running on a two NIC Debian 3.1 266MHz bridge. Before adding the physdev flag, only the "tc filter" commands worked but now the iptables commands also

Hello List, i am running Debian Squeeze and i installed DRBD, 3.2.0-0.bpo.4-amd64 and Xen4.0 from the Backports. Sometimes i get such ugly Kernel message: [257318.441757] BUG: unable to handle kernel paging request at ffff880025f19000 Log: [256820.643918] xen-blkback:ring-ref 772, event-channel 16, protocol 1 (x86_64-abi) [256830.802492] vif86.0: no IPv6 routers present [256835.674481]

I recently encountered this in the logs of a new Debian Xen Dom0, and having now spent the better part of a day researching and testing, I've come to the conclusion that this is not a bug in xen-utils-common or even iptables; it's merely the consequence of structural changes to the core netfilter code starting in the 2.6.20 kernel. This is rather long, but the issue is complicated. Please

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,

I just kickstarted a new machine with the latest CentOS 6.2 files, including kernel 2.6.32-220.13.1.el6.x86_64. It came up without network interfaces. dmesg says: bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011) alloc irq_desc for 36 on node -1 alloc kstat_irqs on node -1 bnx2 0000:01:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 bnx2 0000:01:00.0:

Hi all, I have Xen 3.2 newly installed on Lenny with network bridging configured. When I built my first VM, I found it couldn''t connect to the Internet. This turned out to be because my dom0''s iptables was configured to DROP all packets on the FORWARD chain (when I removed that, it started working). The "Xen Networking" page on the wiki describes this exact situation