Re: Attn: CI/Jenkins people; Run bhyve instance for testing pf

[Nikos Vassiliadis]

On 07/18/2017 02:55 AM, Panagiotes Mousikides wrote:

Den 2017-07-16 kl. 21:11, skrev Alan Somers:

On Sun, Jul 16, 2017 at 2:44 PM, Panagiotes Mousikides
 wrote:

Hello everybody!

I am working on adding tests to the FreeBSD test suite for testing 
pf, the

network packet filter.

These tests need at least two machines running and connected to each 
other,

with one machine generating network traffic and the other running pf and
filtering the traffic.  I am looking for a way to fire off a bhyve 
instance

to serve as the second machine, the first being the actual machine I am
running the tests on. This should be done completely automatically, with
scripts to configure all network interfaces and to preferably also 
set up an

SSH server on the bhyve instance.

This bhyve instance could start off as running the latest stable 
version of

FreeBSD, or it could be configured to run a snapshot of the development
tree.  The aim is to have the desired version of FreeBSD that we want to
test running on it.  Ideally this would be done in such a way that we 
can
reuse the machine for further tests, instead of rebuilding everything 
from

scratch for each test.

What I am looking for is the best way to do this, preferably so that 
it can
be easily integrated into the CI work being done at Jenkins.  What do 
you

think?  Any input is welcome!

All the best,
Panagiotes

It's possible to setup CI systems that involve multiple machines
networked together.  I've done it.  But it's complicated, fragile, and
slow.  I advise you to consider very carefully whether you truly need
multiple VMs.  What about creating an epair(4)?  You could run pf on
epair0b and generate traffic from epair0a.  That would be faster than
spinning up VMs, and would be very easy to integrate into any other CI
system.  Would that work?

-Alan


Hi Alan!

Thank you for the tip about epair(4), it sounds really like an 
interesting approach to my problem.  I will look into it!


Best regards,
Panagiotes


Hi,

It would be great if you use vnet jails for that. I am not
sure regarding the per-vnet pf functionality but I have seen
many bug fixes hitting the tree since last year. You can ask
on freebsd-virtualizat...@freebsd.org or freebsd...@freebsd.org
to learn more about it.

Pf within a jail should behave more or less like the "normal" one.
Plus you will be testing per-vnet functionality, which the project
needs anyhow, in one go.

Best regards,
Nikos




___
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: strange buildworld failure

[Nikos Vassiliadis]

On 11/24/2012 1:45 PM, Dimitry Andric wrote:

On 2012-11-24 03:38, Benjamin Kaduk wrote:

On Fri, 23 Nov 2012, Nikos Vassiliadis wrote:

On 11/23/2012 1:34 PM, Sergey Kandaurov wrote:

Also, my src.conf had WITHOUT_CLANG but I deleted it and then I
also deleted /usr/obj when it failed for the first time. But that
didn't work. I am building with -j3.


Does it always fail there at usr.bin/ypwhich?
It's likely that -j3 is the culprit of why you do not see the actual build
error because it might be lost off the screen. Try to restart without -jN.



Thanks, that worked.


Hmm, buildworld is supposed to be parallel-make-safe.
Perhaps a full log of the failing buildworld (e.g., with script(1)) could
be posted for analysis?


Well, either a full log, or the tail of the log, as long as it contains
the actual command(s) that failed.  Sometimes it can help to search
backwards with less, or your favorite editor, for the string error:,
or if there is no such string, searching for other problem indicators.

Also, copies of make.conf and src.conf are often essential in finding
the cause of the problem.  Many build issues are caused by erroneous
settings. :)


I installed world after the successful build, so now it probably is
too late to get a more useful problem report:(

By the way, I tried to add some debugging info with the help of make -d A
or -d g2 but the amount of logging was excessive(the build was ran in a tmux
terminal and the tmux process was using more CPU time than the build itself,
so I canceled). What should I use with make -d in order to get some basic
debugging? Or is there another way?

Thanks in advance, Nikos
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

strange buildworld failure

[Nikos Vassiliadis]

Hi,

I am trying to buildworld but it fails here:

=== usr.bin/ypwhich (all)
cc -O2 -pipe  -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -Wno-uninitialized -
Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare 
-Wno-unused-value -Wno-parentheses-equality -Wno-
unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -c 
/usr/src/usr.bin/ypwhich/ypwhich.c
gzip -cn /usr/src/usr.bin/ypwhich/ypwhich.1  ypwhich.1.gz
cc -O2 -pipe  -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -Wno-uninitialized -
Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare 
-Wno-unused-value -Wno-parentheses-equality -Wno-
unused-function -Wno-conversion -Wno-switch -Wno-switch-enum  -o ypwhich 
ypwhich.o
1 error
*** [everything] Error code 2
1 error
*** [buildworld] Error code 2
1 error


My make.conf has these:
WITHOUT_X11=1
MALLOC_PRODUCTION=1
NO_CLEAN=1

Also, my src.conf had WITHOUT_CLANG but I deleted it and then I
also deleted /usr/obj when it failed for the first time. But that
didn't work. I am building with -j3.

Thanks for any ideas/pointers, Nikos

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

Re: strange buildworld failure

[Nikos Vassiliadis]

On 11/23/2012 1:34 PM, Sergey Kandaurov wrote:

Also, my src.conf had WITHOUT_CLANG but I deleted it and then I
also deleted /usr/obj when it failed for the first time. But that
didn't work. I am building with -j3.


Does it always fail there at usr.bin/ypwhich?
It's likely that -j3 is the culprit of why you do not see the actual build
error because it might be lost off the screen. Try to restart without -jN.



Thanks, that worked.

Nikos

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

Re: em problem in virtualbox since the weekend

[Nikos Vassiliadis]

On 7/20/2011 5:35 AM, Steve Wills wrote:

While testing some other things, I found -CURRENT from yesterday doesn't
work with the em0 in my VirtualBox 4.0.8 (a little out of date
admittedly). It worked Friday or Saturday I think. Anyone else seen this


I also see this on a 4.0.4something installation.


em0: Unable to allocate bus resource: memory
em0: Allocation of PCI resources failed


So, you're not alone:)

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