Recently upgraded to r297351, once running iovctl -C -f /etc/iovctl.conf
everything appears to work as it should. The main network interface ramains
connected and pinging works fine.
iovctl.conf
PF {
device : ix1;
num_vfs : 31;
}
DEFAULT {
passthrough : true;
}
VF-0 {
I have been interested in this when I first read about it in 2012. =]
Can this be done in loader.conf? I have vmm_load="YES"
I'm not sure if the vf's are usable, I have not actually tested the vf's.
The parent ix1 still shows no response.
kldunload vmm
kenv hw.vmm.force_iommu=1
kldload vmm
io
I don't know if you're still interested in this, but did you do "kenv
hw.vmm.force_iommu=1" before loading the vmm module? I think that might be
necessary.
On Wed, Feb 24, 2016 at 5:12 PM Ultima wrote:
> Yeah, still getting the -100 error, I do have sendmail disabled. I just
> tested with sendm
Yeah, still getting the -100 error, I do have sendmail disabled. I just
tested with sendmail up and running then add the VF's and it still shows
the error message.
On Wed, Feb 24, 2016 at 8:04 PM, Eric Joyner wrote:
> Are you still getting the -100 errors when trying to load the VF driver?
>
>
Are you still getting the -100 errors when trying to load the VF driver?
I've tried SR-IOV on a system here, and I can confirm that traffic stops
passing on the PF interface when you create a VF interface. That didn't
used to happen, so I'm investigating why that is right now.
On Wed, Feb 24, 201
Decided to do some more tests, I actually have a second board with sr-iov
capabilities that I used for awhile with vmware esxi. I decided to test
this out and unfortunately it won't activate, it is giving the no space
left on device error message. I double checked bios and all VT-d related
options
Upgraded to r295920 and used generic kernel. Then rebooted and checked
bios thoroughly. I found 3, yes 3 different areas in the bios for enabling
sr-iov (some screen shots below). 2 are for vt-d(Forgot to take a
screenshot of the 2nt, all were enabled) and one for sr-iov(was disabled).
Unfortunate
I forgot to mention my kernel conf I'm not sure if it would cause this
issue, but I'll test again with GENERIC.
--- /usr/src/sys/amd64/conf/GENERIC 2016-02-22 21:05:37.152953000 -0500
+++ /root/MYKERNEL-11-CURRENT-AMD64 2015-12-28 19:18:22.893391452 -0500
@@ -91,6 +91,12 @@
options WITNESS_SK
I don't really have any ideas on the error -100. Error -100 means there was
a mailbox error, so something failed in the initial communications setup
between the PF and VF, but I don't know what exactly went wrong.
I'm grasping at straws, but try using a smaller number of VFs initially,
like 2? And
gt;>> From: owner-freebsd-curr...@freebsd.org [mailto:
>>> owner-freebsd-curr...@freebsd.org] On Behalf Of Ultima
>>> Sent: Monday, February 22, 2016 12:02 PM
>>> To: Eric Joyner
>>> Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org
>&g
have?
Jeff
-Original Message-
From: owner-freebsd-curr...@freebsd.org [mailto:
owner-freebsd-curr...@freebsd.org] On Behalf Of Ultima
Sent: Monday, February 22, 2016 12:02 PM
To: Eric Joyner
Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org
Subject: Re: sr-iov issues, reset_
bsd.org [mailto:
> owner-freebsd-curr...@freebsd.org] On Behalf Of Ultima
> Sent: Monday, February 22, 2016 12:02 PM
> To: Eric Joyner
> Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org
> Subject: Re: sr-iov issues, reset_hw() failed with error -100
>
> Aft
-virtualizat...@freebsd.org
Subject: Re: sr-iov issues, reset_hw() failed with error -100
After reboot...
ifconfig ix1 up
dhclient ix1
DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ix1 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound
Did you do an ifconfig up on ix1 before loading the VF driver?
On Sat, Feb 20, 2016 at 11:57 AM Ultima wrote:
> Decided to do some testing with iovctl to see how sr-iov is coming along.
> Currently when adding the vf's there are a couple errors, and the network
> no longer function after iovctl
After reboot...
ifconfig ix1 up
dhclient ix1
DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ix1 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.145 -- renewal in 21600 seconds.
ix0 down
ping 192.168.1.1
PING 192.168.1.1
15 matches
Mail list logo
