Re: Heads up

2016-04-24 Thread Warner Losh 
I'll try virtualbox again, but it booted fine when I tried it before.
I'll give bhyve a sping. I haven't tried it in quite some time, but
it worked about 9 months ago.

But since I don't even know what the errors you are seeing are,
I can't tell you that it is similar to some other error reports or
something completely new.

Warner


On Sun, Apr 24, 2016 at 11:49 AM, Ivan Klymenko  wrote:

> On Fri, 15 Apr 2016 11:44:43 +0300
> Ivan Klymenko  wrote:
>
> > On Thu, 14 Apr 2016 16:42:33 -0600
> > Warner Losh  wrote:
> >
> > > The CAM I/O scheduler has been committed to current. This work is
> > > described in
> > > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the
> > > default scheduler doesn't change the default (old) behavior.
> > >
> > > One possible issue, however, is that it also enables NCQ Trims on
> > > ada SSDs. There are a few rogue drives that claim support for this
> > > feature, but actually implement data corrupt instead of queued
> > > trims. The list of known rogues is believed to be complete, but
> > > some caution is in order.
> > >
> > > Warner
> >
> > Hi.
> > Thanks for you work.
> > But i have problem with VirtualBox if i use the kernel with option
> > CAM_NETFLIX_IOSCHED
> > http://imgur.com/JpcfW1h
>
> This problem is not over.
> After the update on other hardware from r296979 to r298512 (!!! without
> option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual
> machine to a virtual disk I lost completely virtual machine with
> permanent damage to the integrity of the file system in the inside of
> the virtual machine.
>
> This is a serious bug!
>
> Who cares not to fall into the same situation - is testing yourself
> and needed more testers.
> Because there is a suspicion that the problem is also relevant for
> bhyve VM.
> With me on this no more neither the strength nor the desire nor
> time.
>
> Thanks.
>
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

ixv device_attach: ixv0 attach returned 5 (was sr-iov issues, reset_hw() failed with error -100)

2016-04-24 Thread Ultima 
 The sr-iov vf driver is failing to attach.


# pciconf -lv: (filtered to only relevant output)
ix0@pci0:129:0:0: class=0x02 card=0x1458 chip=0x15288086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Controller 10-Gigabit X540-AT2'
class  = network
subclass   = ethernet
ix1@pci0:129:0:1: class=0x02 card=0x1458 chip=0x15288086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Controller 10-Gigabit X540-AT2'
class  = network
subclass   = ethernet
none155@pci0:129:0:129: class=0x02 card=0x1458 chip=0x15158086
rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'X540 Ethernet Controller Virtual Function'
class  = network
subclass   = ethernet
none156@pci0:129:0:131: class=0x02 card=0x1458 chip=0x15158086
rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'X540 Ethernet Controller Virtual Function'
class  = network
subclass   = ethernet

# devctl attach pci0:129:0:129
devctl: Failed to attach pci0:129:0:129: Input/output error

# dmesg
ixv0:  at device 0.129 numa-domain 1 on pci12
ixv0: Using MSIX interrupts with 2 vectors
ixv0: ixgbe_reset_hw() failed with error -100
device_attach: ixv0 attach returned 5

# cat /etc/iovctl.conf
PF {
device : ix1;
num_vfs : 31;
}

DEFAULT {
passthrough : true;
}
VF-0 {
passthrough : false;
}
VF-1 {
passthrough : false;
}


Any ideas?

Ultima
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Problem reports for freebsd-virtualization@FreeBSD.org that need special attention

2016-04-24 Thread bugzilla-noreply 
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |202321 | [bhyve,patch] More verbose error reporting in bhy 
New |202322 | [bhyve,patch] add option to have bhyve write its  

2 problems total for which you should take action.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: pptdevs option crashes system

2016-04-24 Thread David Ehrmann 
It sounds like the bug I reported a while ago, but on a different chip
family:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207602

On Sunday, April 24, 2016, Vesselin Mirewski  wrote:

> Hi,
> I'm trying to bring up an excellent PCIe Fusion board which has no driver
> for FreeBSD. I used bhyve to bring up an ubuntu server ( which has an
> original driver by the manufacturer )
> All went just fine, till I tried to pass through the board to the linux.
> My CPUs support all that's needed by bhyve: Xeon X5675.
>
> The board ( pciconf -lv ) :
>
> none3@pci0:11:0:0: class=0x018000 card=0x178d103c chip=0x10051aed rev=0x01
> hdr=0x00
> vendor = 'Fusion-io'
> device = 'ioDimm3'
> class  = mass storage
> none4@pci0:12:0:0: class=0x018000 card=0x178d103c chip=0x10051aed rev=0x01
> hdr=0x00
> vendor = 'Fusion-io'
> device = 'ioDimm3'
> class  = mass storage
>
> my /boot/loader.conf has ( bhyve part ):
> vmm_load="YES"
> nmdm_load="YES"
>
> *pptdevs="11/0/0 12/0/0"*
>
> The last line crashes the system - "Interrupt trap" and the system starts
> to shutdown the cpus ( which gets an ugly loop till it finally reboots )
>
> Then single user,  set pptdevs="" , boot and everything is fine again.
>
> The board is an HP accelerator board with 2x160GB SLC SSDs with ( according
> to specifications ) 150PB lifetime and the amazing 230,000 IOPs - I'm dying
> to do some benchmarks with PostgreSQL ...
>
> Any advice will be highly appreciated. Thanks in advance for your time.
>
> --
> --
> В. Миревски
> +359 884 63 74 64
> ___
> freebsd-virtualization@freebsd.org  mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscr...@freebsd.org "
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

pptdevs option crashes system

2016-04-24 Thread Vesselin Mirewski 
Hi,
I'm trying to bring up an excellent PCIe Fusion board which has no driver
for FreeBSD. I used bhyve to bring up an ubuntu server ( which has an
original driver by the manufacturer )
All went just fine, till I tried to pass through the board to the linux.
My CPUs support all that's needed by bhyve: Xeon X5675.

The board ( pciconf -lv ) :

none3@pci0:11:0:0: class=0x018000 card=0x178d103c chip=0x10051aed rev=0x01
hdr=0x00
vendor = 'Fusion-io'
device = 'ioDimm3'
class  = mass storage
none4@pci0:12:0:0: class=0x018000 card=0x178d103c chip=0x10051aed rev=0x01
hdr=0x00
vendor = 'Fusion-io'
device = 'ioDimm3'
class  = mass storage

my /boot/loader.conf has ( bhyve part ):
vmm_load="YES"
nmdm_load="YES"

*pptdevs="11/0/0 12/0/0"*

The last line crashes the system - "Interrupt trap" and the system starts
to shutdown the cpus ( which gets an ugly loop till it finally reboots )

Then single user,  set pptdevs="" , boot and everything is fine again.

The board is an HP accelerator board with 2x160GB SLC SSDs with ( according
to specifications ) 150PB lifetime and the amazing 230,000 IOPs - I'm dying
to do some benchmarks with PostgreSQL ...

Any advice will be highly appreciated. Thanks in advance for your time.

-- 
--
В. Миревски
+359 884 63 74 64
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

[Differential] D1944: PF and VIMAGE fixes

2016-04-24 Thread kristof (Kristof Provost) 
kristof added inline comments.

INLINE COMMENTS
  sys/netpfil/pf/pf_if.c:130 I don't understand why this is required. Surely if 
an ifnet lives in V_ifnet (so, lives in the current vnet) ifp->if_vnet is 
always going to be curvnet?
  sys/netpfil/pf/pf_if.c:141 Why add curvnet here?
  pfi_attach_ifnet_event doesn't use its argument.
  sys/netpfil/pf/pf_if.c:143 Same as above.
  sys/netpfil/pf/pf_if.c:151 Same as above.
  sys/netpfil/pf/pf_if.c:814 I believe this is correct, but should probably 
include adding an __unused annotation to arg, and removing the 'curvnet' 
argument from the EVENTHANDLER_REGISTER() call.

REVISION DETAIL
  https://reviews.freebsd.org/D1944

EMAIL PREFERENCES
  https://reviews.freebsd.org/settings/panel/emailpreferences/

To: nvass-gmx.com, bz, trociny, kristof, gnn, zec, rodrigc, glebius, eri
Cc: ryan_timewasted.me, mmoll, javier_ovi_yahoo.com, farrokhi, julian, robak, 
freebsd-virtualization-list, freebsd-pf-list, freebsd-net-list
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"