[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up
On Mon, Sep 10, 2012 at 03:54:34PM +0530, Ashok Anand wrote: > Hi, > I am trying to use SRIOV, usnig xen 4.0 on debian. > On my dom0, xm pci-list-assignable-devices show that > 0000:0f:10.0 > 0000:0f:10.2 > 0000:0f:10.4 > 0000:0f:10.6 > 0000:0f:11.2 > 0000:0f:11.4 > 0000:0f:11.6 > these virtual interfaces correspond to eth2, > i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0 > on my dom0 machine, i can ping other machine using eth2, (implying PF on > eth2 is active) > on my domU machine, when i attach the virtual function, i get the > following messages > [1][ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mapped GSI0 to IRQ28 > [2][ 2282.688470] ixgbevf 0000:00:00.0: setting latency timer to 64 > [3][ 2282.690187] ixgbevf 0000:00:00.0: PF still in reset state, assigning > new address > while PF on eth2 is there and active, since i can ping other machine. > Now, when I try to bring up the VF interface on domU, > i get the following error > 2476.295582] Unable to start - perhaps the PF Driver isn't up yet > SIOCSIFFLAGS: Network is down > [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet > SIOCSIFFLAGS: Network is down > and on dmesg on domU, > [ 2476.295582] Unable to start - perhaps the PF Driver isn't up yet > [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet > Any thoughts on what could be wrong? I have been struggling with this for > quite some time > and would really appreciate your thoughts on it. > Did you do "ifconfig ethX up" in dom0? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |