[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] PCI Passthrough problems (Cannot access network but e1000 loads fine)


  • To: "Andy Burns" <lists.xensource.com@xxxxxxxxxxxxxx>
  • From: Asim <linkasim@xxxxxxxxx>
  • Date: Fri, 8 Aug 2008 10:50:17 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 08 Aug 2008 08:50:56 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RG4Ckzxcp5Iy5aHf0kn0gyAqIGeCwuzKhrSXJvgA87zTvjZlYUY6LGNckcjmjs3amt YYjrfdxbvGbmdVy4vgxDBrVE/a1++E+dax3SXQ7u1SIJqsANGF7/GLMadCDrrJ8PnFJP aZQ+4RhoUidOKHE3gT1aAs03dXNY/nY9pTTac=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I do not get anything strange here. This is from the dmesg on domU

[339497.233655] Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
[339497.233657] Copyright (c) 1999-2006 Intel Corporation.
[339497.234124] e1000: In __devinit.
[339497.245661] PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
[339497.512872] e1000: 0000:00:00.0: e1000_probe: (PCI:33MHz:32-bit)
00:07:e9:39:07:e5
[339497.552859] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[339497.725307] Entered sys_init_module.
[339497.730044] device-mapper: ioctl: 4.7.0-ioctl (2006-06-24)
initialised: dm-devel@xxxxxxxxxx
[339498.000804] EXT3 FS on sda1, internal journal
[339498.269163] Adding 65528k swap on /dev/sda2.  Priority:-1
extents:1 across:65528k
[339499.153997] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
>From the prompt:
[root@fedora_pristine ~]# ping 128.105.104.101
PING 128.105.104.101 (128.105.104.101) 56(84) bytes of data.
>From 128.105.104.129 icmp_seq=1 Destination Host Unreachable
>From 128.105.104.129 icmp_seq=2 Destination Host Unreachable
>From 128.105.104.129 icmp_seq=3 Destination Host Unreachable


Is there anything special I need to do for /etc/network or
/etc/network-scripts/ifcfg-eth0 apart from what I did to get it
working for vif interface.

I used extra='noirqdebug' in my config file and my domU does not boot after :
[340110.616654] Entered sys_init_module.
[340110.621535] usbcore: registered new driver usbfs
[340110.621572] usbcore: registered new driver hub

I already have extra='xcons=tty' - does that get overidden?

Please help.

Regards,
Asim

On 8/8/08, Andy Burns <lists.xensource.com@xxxxxxxxxxxxxx> wrote:
> On 08/08/2008 04:31, Asim wrote:
>
>> I'm running a PV DomU on CentOS 4. I was able to successfulyl hide a
>> e1000 PCI card by appropriately modifying /etc/modprobe.conf. The
>> device is not configured as a eth device in my dom0. I was also able
>> to successfully load it in my domU and e1000 driver loads fine.
>> ifconfig shows correct configuration of IP address.
>>
>> However, I'm not able to access the network. The network was
>> accessible with the same IP using vif interface instead. Kindly help.
>
> Any ethernet or interrupt related messages in dmesg on dom0 or domU or
> from xm dmesg?
>
> Research the noirqdebug/pollirq/swiotlb settings and try some combinations
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.