After looking at the kernel source, I see that the device ID for the i217 chip is missing from the 3.4.50 kernel, but is present in the 2.6.32 kernel. Looks like I need to open a bug report to have this backported.
Mark
Mark
On Tue, Jul 16, 2013 at 7:41 AM, Mark Nejedlo <nejedlo@xxxxxxxxx> wrote:
There is only one physical ethernet interface; no ethX is found under Xen. The MAC in ifcfg-eth0 is correct since it works just fine in the 2.6.32 kernel.Mark
On Tue, Jul 16, 2013 at 1:19 AM, Gene <gh5046@xxxxxxxxx> wrote:Is it finding any other eth devices? (eth1, eth2, etc)On Mon, Jul 15, 2013 at 8:50 PM, Mark Nejedlo <nejedlo@xxxxxxxxx> wrote:
> I've just installed CentOS 6.4 an Xen on a new system, and eth0 is not found
> on dom0 when booting into Xen. When I boot into the 2.6.32 kernel outside
> Xen my network interface is found, using the e1000e driver. If I boot into
> Xen eth0 is not found, even if I modprobe the e1000e driver by hand. My NIC
> is an Intel I217-V.
>
> Any suggestions for things I can do to get my network working inside Xen?
Verify the MAC address in the
/etc/sysconfig/network-scripts/ifcfg-eth0 file matches what you have
in the Xen configuration (xm list -l <hostname>). If not then remove
it.
> Thanks,
> Mark
-Gene
_______________________________________________
CentOS-virt mailing list
CentOS-virt@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos-virt
_______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
