Jenkins build is still unstable: FreeBSD_HEAD #496

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

Re: bhyve with lagg failover doesn't work on wifi

I have similar problem with bridging tap0 and lagg0 (lacp). Problem I think is beetween lagg0 and tap0. I can see ICMP traffic from guest to host on bridge0 interface (ping), but no tcp (ssh). Tcpdump on host on tap0: host: 192.168.22.19 guest: 192.168.22.135 tcpdump: listening on tap0, link-typ

Jenkins build is still unstable: FreeBSD_HEAD #497

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

Jenkins build is still unstable: FreeBSD_HEAD #498

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

Re: Call for testing on vagrant-bhyve

Hi, thanks for your work! Regarding the conversion process described in the README, you might also want to look into / patch vagrant-mutate: https://github.com/sciurus/vagrant-mutate People use it to convert from VirtualBox to libvirt on Linux. -- Christian Schwarz

Re: Call for testing on vagrant-bhyve

Hello, Thanks for your reply. One of my mentor, Steve Wills, has started working on adding support to vagrant-mutate. https://github.com/swills/vagrant-mutate/tree/bhyve But now it's limited to FreeBSD boxes, Linux boxes are more complicated, we are trying to find better ways. Now we have to con

CURRENT: memory leak?

I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD 12.0-CURRENT #16 r303470: Fri Jul 29 05:58:42 CEST 2016 ). Swap space gets eaten up while building world/kernel and/or ports very quickly. I see this phenomenon on different CURRENT systems with different RAM (but all ZFS!). No

Jenkins build is still unstable: FreeBSD_HEAD #499

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

Re: CURRENT: memory leak?

On 2016-07-29 14:04, O. Hartmann wrote: I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD 12.0-CURRENT #16 r303470: Fri Jul 29 05:58:42 CEST 2016 ). Swap space gets eaten up while building world/kernel and/or ports very quickly. I see this phenomenon on different CURRENT syste

Re: bhyve with lagg failover doesn't work on wifi

Generally speaking, you can't bridge the station side of a wireless link. The access point will only accept frames with the station's MAC address. So what you are seeing is expected, unfortunately. Your best bet is probably to do NAT. Take lagg0 out of the bridge and use it as your "public" int

Re: CURRENT: memory leak?

Am Fri, 29 Jul 2016 15:03:04 -0400 Allan Jude schrieb: > On 2016-07-29 14:04, O. Hartmann wrote: > > > > I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD > > 12.0-CURRENT #16 > > r303470: Fri Jul 29 05:58:42 CEST 2016 ). Swap space gets eaten up while > > building > > world/ker

Re: CURRENT: memory leak?

On Fri, Jul 29, 2016 at 12:03 PM, Allan Jude wrote: > On 2016-07-29 14:04, O. Hartmann wrote: >> >> I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD >> 12.0-CURRENT #16 >> r303470: Fri Jul 29 05:58:42 CEST 2016 ). Swap space gets eaten up while >> building >> world/kernel and/or p

Re: CURRENT: memory leak?

Am Fri, 29 Jul 2016 12:41:17 -0700 Ngie Cooper schrieb: > On Fri, Jul 29, 2016 at 12:03 PM, Allan Jude wrote: > > On 2016-07-29 14:04, O. Hartmann wrote: > >> > >> I realise an exorbitant memory usage of FreeBSD CURRENT ( FreeBSD > >> 12.0-CURRENT #16 > >> r303470: Fri Jul 29 05:58:42 CEST 201

Re: CURRENT: memory leak?

On Fri, Jul 29, 2016 at 12:52 PM, O. Hartmann wrote: ... > This is after starting VBox and a Win 7 pro guest (just started, no login) > with 3572 MB > memory reserved and 4 logical CPUs (VBox 5.0.26): > > root@localhost: [ports] vmstat -Hm | sort -rnk 2,3 | head -n 10 > solaris 53030 6208

Re: EARLY_AP_STARTUP hangs during boot

On Thursday, July 28, 2016 12:31:31 AM Gary Jennejohn wrote: > Well, now I know that ULE is a prerequiste for EARLY_AP_STARTUP! I > wasn't aware of that. I prefer BSD and that's the scheduler I did > the first tests with. > > But with the ULE scheduler the system comes up all the way. > > It wo

Jenkins build is still unstable: FreeBSD_HEAD #500

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

Jenkins build is still unstable: FreeBSD_HEAD #501

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

Re: bhyve with lagg failover doesn't work on wifi

On Fri, Jul 29, 2016 at 01:06:52PM -0600, John Nielsen wrote: > Generally speaking, you can't bridge the station side of a wireless link. The > access point will only accept frames with the station's MAC address. So what > you are seeing is expected, unfortunately. > > Your best bet is probably

Jenkins build is still unstable: FreeBSD_HEAD #502

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

FreeBSD_HEAD_i386 - Build #3721 - Failure

FreeBSD_HEAD_i386 - Build #3721 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3721/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3721/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3721/console Change summaries: 3

Build failed in Jenkins: FreeBSD_HEAD #503

See -- [...truncated 77974 lines...] cc -O2 -pipe -I. -I/builds/workspace/FreeBSD_HEAD/src/lib/libprocstat -D_KVM_VNODE -DLIBPROCSTAT_ZFS -MD -MF.depend.udf.o -MTudf.o -std=gnu99 -fstack-protector-st

FreeBSD_HEAD_i386 - Build #3722 - Still Failing

FreeBSD_HEAD_i386 - Build #3722 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3722/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3722/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3722/console Change summari