Re: bhyve with vlans - host and vm can't pass traffic

Thanks for your reply, Matthew. See results below: On 4/22/2015 4:17 PM, Matthew Grooms wrote: On 4/22/2015 11:02 AM, Scott O'Connell wrote: I'm very new to bhyve and am having an issue. I'm trying to get VM's and VLAN's working. I'm able to get VLAN's working in a VM, but the VM and the VMH

Re: bhyve with vlans - host and vm can't pass traffic

On 4/22/2015 11:02 AM, Scott O'Connell wrote: I'm very new to bhyve and am having an issue. I'm trying to get VM's and VLAN's working. I'm able to get VLAN's working in a VM, but the VM and the VMHOST, can't communicate with each other on the same vlan. Using 10.1-RELEASE-p9 for both VMHOST0

Re: panic: SACK scoreboard must not be empty

On 04/22/15 19:19, Peter Holm wrote: > On Wed, Apr 22, 2015 at 11:45:21AM +1000, Lawrence Stewart wrote: >> Hi Peter, >> >> On 04/15/15 21:04, Peter Holm wrote: >>> Seen during i386 stress tests. >>> >>> db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at >>> db_trace_self_wrapper+0x2a/

Re: moving struct bpf_if to bpf.c

On Saturday 18 April 2015 14:08:56 Mark Johnston wrote: > Hello, > > At the moment, bpf.h defines struct bpf_if differently depending on > whether BPF_INTERNAL is #defined. This causes problems with CTF, as it > results in a sort of bifurcation within the type graph: CTF sees two > different struc

bhyve with vlans - host and vm can't pass traffic

I'm very new to bhyve and am having an issue. I'm trying to get VM's and VLAN's working. I'm able to get VLAN's working in a VM, but the VM and the VMHOST, can't communicate with each other on the same vlan. Using 10.1-RELEASE-p9 for both VMHOST01 and DEV. Upstream from the VMHOST on lagg0 i

Re: panic: SACK scoreboard must not be empty

On Wed, Apr 22, 2015 at 11:45:21AM +1000, Lawrence Stewart wrote: > Hi Peter, > > On 04/15/15 21:04, Peter Holm wrote: > > Seen during i386 stress tests. > > > > db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at > > db_trace_self_wrapper+0x2a/frame 0xe47578b0 > > kdb_backtrace(c139e

Re: Intel em (82574L and 82573L) problems: stopping on high network and cpu load (Watchdog timeout)

On Tue, 14-Apr-2015 at 10:01:16 -0400, Mike Tancsa wrote: > On 4/14/2015 1:54 AM, Andre Albsmeier wrote: > > > > Is this an em specific issue or should one avoid TSO generally > > at the moment? That is, should I disable it on machines with > > msk (and maybe other) interfaces as well? > > em spec