Comment 16 for bug 116267

Revision history for this message
In , Calvin (calvin-redhat-bugs) wrote :

I'm still not getting any networking in the Xen kernel. I can't even ping the
local gateway.

I've disabled NetworkManager and left the other network settings as they were.

The IRQ assignments still don't look right to me. Here's how they differ in
"dmesg" between non-Xen (<) and Xen (>) kernel boots. At a glance, it looks like
the IRQ numbers are being truncated.

191c163
< ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
---
> ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
193c165
< ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169
---
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
195c167
< ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 177
---
> ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
197c169
< ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 185
---
> ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18

Is there some special procedure to make the virtual interfaces and bridge come
up correctly?

This was what I had to do to get QEMU bridging to work:

Rename a copy of ifcfg-eth0 to ifcfg-br0
Remove all the IP related entries from original ifcfg-eth0 but leave the HWADDR.
Set "dev.rtc.max-user-freq = 1024" in /etc/sysctl.conf
Load the "tun" module
Run this sequence of commands:

    ifdown eth0
    ifdown br0
    modprobe bridge
    brctl addbr br0
    brctl stp br0 off
    brctl setfd br0 1
    ifup eth0
    brctl addif br0 eth0

Do I need to do this same thing to get Xen kernel networking running?
It sure seems like it should be simpler than that.

I'd be grateful for some pointers. Maybe this is all covered somewhere in Xen
docs. I'm certainly not getting the "out-of-the-box" experience that the on-line
docs say "most" people are supposed to get.