Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Aug 2019 18:56:16 +0000 (UTC)
From:      Edward Tomasz Napierala <trasz@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r53319 - head/en_US.ISO8859-1/htdocs/news/status
Message-ID:  <201908241856.x7OIuG03049044@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: trasz
Date: Sat Aug 24 18:56:16 2019
New Revision: 53319
URL: https://svnweb.freebsd.org/changeset/doc/53319

Log:
  Add Quarterly Status Report for 2019Q2.
  
  Reviewed by:	bcr (earlier version)
  Differential Revision:	https://reviews.freebsd.org/D21381

Added:
  head/en_US.ISO8859-1/htdocs/news/status/report-2019-04-2019-06.xml   (contents, props changed)
Modified:
  head/en_US.ISO8859-1/htdocs/news/status/Makefile

Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/Makefile	Sat Aug 24 17:03:34 2019	(r53318)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile	Sat Aug 24 18:56:16 2019	(r53319)
@@ -83,6 +83,7 @@ XMLDOCS+=	report-2017-10-2017-12
 XMLDOCS+=	report-2018-01-2018-09
 XMLDOCS+=	report-2018-09-2018-12
 XMLDOCS+=	report-2019-01-2019-03
+XMLDOCS+=	report-2019-04-2019-06
 
 XSLT.DEFAULT=	report.xsl
 

Added: head/en_US.ISO8859-1/htdocs/news/status/report-2019-04-2019-06.xml
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2019-04-2019-06.xml	Sat Aug 24 18:56:16 2019	(r53319)
@@ -0,0 +1,2458 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
+  Status Report//EN"
+  "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
+
+<!-- $FreeBSD$ -->
+<!-- This file was generated with https://github.com/trasz/md2docbook -->
+<!--
+     Variables to replace:
+     %%START%%     - report month start
+     %%STOP%%      - report month end
+     %%YEAR%%      - report year
+     %%NUM%%       - report issue (first, second, third, fourth)
+     %%STARTNEXT%% - report month start
+     %%STOPNEXT%%  - report month end
+     %%YEARNEXT%%  - next report due year (if different than %%YEAR%%)
+     %%DUENEXT%%   - next report due date (i.e., June 6)
+-->
+
+<report>
+  <date>
+    <month>April-June</month>
+
+    <year>2019</year>
+  </date>
+
+  <section>
+    <title>Introduction</title>
+
+    <p>This quarter our report includes
+    some interesting topics easily accessible to anyone, even if
+    you are not a programmer: we report the link to a presentation
+    of the 2019 FreeBSD survey results at BSDCan 2019 and describe
+    an interesting experience of a 3-person hackaton, which might
+    encourage you to host one yourself, possibly with more participants.
+    We also provide some up to date information about the status
+    of our IRC channels.</p>
+
+  <p>For those who have some more technical skills, we give some
+      news about the role of git in the FreeBSD project, describe
+      the status of some tools to hunt bugs or enhance security and
+      announce a clone of sysctl.</p>
+
+    <p>Finally, those who are more experienced with programming will
+      probably be interested in the great work that has been done
+      with drivers: in particular, an aknowledgement is due to Alan
+      Somers for having started to bring up to date our FUSE
+      implementation, which was about 11 years behind. Other important
+      improvements include a more user-friendly experience with
+      trackpoints and touchpads enabled by default, much low level
+      work on graphics, many new bhyve features, updates to the
+      linux compatibility layer, various kernel improvements.</p>
+
+    <p>Have a nice read!<br/>
+      
+      -- Lorenzo Salvadore</p>
+  </section>
+
+  <category>
+    <name>team</name>
+
+    <description>&os; Team Reports</description>
+
+    <p>Entries from the various official and semi-official teams,
+      as found in the <a href="&enbase;/administration.html">Administration
+        Page</a>.</p>
+  </category>
+
+  <category>
+    <name>proj</name>
+
+    <description>Projects</description>
+
+    <p>Projects that span multiple categories, from the kernel and userspace
+      to the Ports Collection or external projects.</p>
+  </category>
+
+  <category>
+    <name>kern</name>
+
+    <description>Kernel</description>
+
+    <p>Updates to kernel subsystems/features, driver support,
+      filesystems, and more.</p>
+  </category>
+
+  <category>
+    <name>arch</name>
+
+    <description>Architectures</description>
+
+    <p>Updating platform-specific features and bringing in support
+      for new hardware platforms.</p>.
+  </category>
+
+  <category>
+    <name>bin</name>
+
+    <description>Userland Programs</description>
+
+    <p>Changes affecting the base system and programs in it.</p>
+  </category>
+
+  <category>
+    <name>ports</name>
+
+    <description>Ports</description>
+
+    <p>Changes affecting the Ports Collection, whether sweeping
+      changes that touch most of the tree, or individual ports
+      themselves.</p>
+  </category>
+
+  <category>
+    <name>doc</name>
+
+    <description>Documentation</description>
+
+    <p>Noteworthy changes in the documentation tree or new external
+      books/documents.</p>
+  </category>
+
+  <category>
+    <name>misc</name>
+
+    <description>Miscellaneous</description>
+
+    <p>Objects that defy categorization.</p>
+  </category>
+
+  <category>
+    <name>third</name>
+
+    <description>Third-Party Projects</description>
+
+    <p>Many projects build upon &os; or incorporate components of
+      &os; into their project.  As these projects may be of interest
+      to the broader &os; community, we sometimes include brief
+      updates submitted by these projects in our quarterly report.
+      The &os; project makes no representation as to the accuracy or
+      veracity of any claims in these submissions.</p>
+  </category>
+
+  <project cat='team'>
+    <title>Release Engineering Team</title>
+
+    <contact>
+      <person>
+	<name>FreeBSD Release Engineering Team</name>
+	<email>re@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://www.freebsd.org/releases/11.3R/schedule.html">FreeBSD 11.3-RELEASE schedule</url>
+      <url href="https://www.freebsd.org/releases/11.3R/announce.html">FreeBSD 11.3-RELEASE announcement</url>
+      <url href="https://www.freebsd.org/releases/12.1R/schedule.html">FreeBSD 12.1-RELEASE schedule</url>
+      <url href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</url>
+    </links>
+
+    <body>
+      <p>The FreeBSD Release Engineering Team is responsible for
+	setting
+	and publishing release schedules for official project
+	releases
+	of FreeBSD, announcing code freezes and maintaining the
+	respective branches, among other things.</p>
+
+      <p>During the second quarter of 2019, the FreeBSD Release
+	Engineering team
+	started the 11.3-RELEASE cycle, with the code slush
+	starting May 3rd.
+	Throughout the cycle, there were three BETA builds and
+	three RC builds,
+	all of which in line with the originally-published
+	schedule. The final RC
+	build started June 28th, with the final release build
+	targeted for July 5th.</p>
+
+      <p>FreeBSD 11.3-RELEASE will be the fourth release from the
+	<tt>stable/11</tt>
+	branch, building on the stability and reliability of
+	11.2-RELEASE.</p>
+
+      <p>The FreeBSD Release Engineering Team also published the
+	schedule for the
+	12.1-RELEASE, targeted to start September 6th. One
+	important thing to note
+	regarding the published schedule is it excludes a hard
+	freeze on the
+	<tt>stable/12</tt> branch, as a test run for eliminating
+	code freezes entirely during
+	a release cycle. Commits to what will be the
+	<tt>releng/12.1</tt> branch will still
+	require explicit approval from the Release Engineering
+	Team, however.</p>
+
+      <p>Additionally throughout the quarter, several development
+	snapshots builds
+	were released for the <tt>head</tt>, <tt>stable/12</tt>,
+	and <tt>stable/11</tt> branches.</p>
+
+      <p>Much of this work was sponsored by the FreeBSD Foundation
+	and Rubicon
+	Communications, LLC (Netgate).</p>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>Ports Collection</title>
+
+    <contact>
+      <person>
+	<name>René Ladan</name>
+	<email>portmgr-secretary@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>FreeBSD Ports Management Team</name>
+	<email>portmgr@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://www.FreeBSD.org/ports/">About FreeBSD Ports</url>
+      <url href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</url>
+      <url href="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</url>
+      <url href="https://www.freebsd.org/portmgr/index.html">Ports Management Team">Ports Management Team</url>
+    </links>
+
+    <body>
+      <p>The following was done during the last quarter by portmgr
+	to keep things in
+	the Ports Tree going:</p>
+
+      <p>During the last quarter the number of ports rose to just
+	under 37,000. At the
+	end of the quarter, there were 2146 open PRs and 7837
+	commits (excluding 499 on
+	the quarterly branch) from 172 committers. This shows a
+	slight decrease in
+	activity compared to previous quarter.</p>
+
+      <p>People come and go, last quarter we welcomed Pedro Giffuni
+	(pfg@), Piotr Kubaj
+	(pkubaj@) and Hans Petter Selasky (hselasky@). Pedro and
+	Hans Petter were
+	already active as src committers. We said goodbye to
+	gordon@, kan@, tobez@,
+	and wosch@.</p>
+
+      <p>On the infrastructure side, a new USES=cabal was
+	introduced and various default
+	versions were updated: MySQL to 5.7, Python to 3.6, Ruby
+	to 2.5, Samba to 4.8
+	and Julia gained a default version of 1.0. The web
+	browsers were also updated:
+	Firefox to 68.0 and Chromium to 75.0.3770.100</p>
+
+      <p>During the last quarter, antoine@ ran a total of 41
+	exp-runs to test various
+	package updates, bump the stack protector level to
+	"strong", switch the default
+	Python version to 3.6 as opposed to 2.7, remove sys/dir.h
+	from base which has
+	been deprecated for over 20 years, and convert all Go
+	ports to USES=go.</p>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Core Team</title>
+
+    <contact>
+      <person>
+	<name>FreeBSD Core Team</name>
+	<email>core@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
+
+      <ul>
+	<li>Core approved source commit bits for Doug Moore (dougm),
+	Chuck Silvers
+	(chs), Brandon Bergren (bdragon), and a vendor commit bit
+	for Scott
+	Phillips (scottph).</li>
+      </ul>
+
+      <ul>
+	<li>The annual developer survey closed on 2019-04-02. Of the
+	397
+	developers, 243 took the survey with an average completion
+	time of 12
+	minutes. The public survey closed on 2019-05-13. It was
+	taken by
+	3637 users and had a 79% completion rate.
+	<a
+	href="https://www.youtube.com/watch?v=9nc8N6GtAPg&amp;t=549">A
+	presentation of the survey results</a>
+	took place at BSDCan 2019.</li>
+      </ul>
+
+      <ul>
+	<li>The core team voted to appoint a working group to explore
+	transitioning our source code 'source of truth' from
+	Subversion to
+	Git. Core asked Ed Maste to chair the group as Ed has been
+	researching this topic for some time. For example, Ed gave
+	<a href="https://www.youtube.com/watch?v=G8wQ88d85s4">a
+	MeetBSD 2018 talk on the topic</a>.</li>
+      </ul>
+
+      <p>
+	There is a variety of viewpoints within core regarding
+	where and how
+	to host a Git repository, however core feels that Git is
+	the prudent
+	path forward.</p>
+
+      <ul>
+	<li>The project received many Season of Docs submissions and
+	picked a top
+	candidate. Google will announce the accepted technical
+	writer
+	projects on 2019-08-06. We are hoping for lots of new and
+	refreshed
+	man pages.</li>
+      </ul>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>Continuous Integration</title>
+
+    <contact>
+      <person>
+	<name>Jenkins Admin</name>
+	<email>jenkins-admin@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>Li-Wen Hsu</name>
+	<email>lwhsu@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</url>
+      <url href="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</url>
+      <url href="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</url>
+      <url href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</url>
+      <url href="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</url>
+      <url href="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</url>
+      <url href="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</url>
+      <url href="https://hackfoldr.org/freebsd-ci-report/">FreeBSD CI weekly report</url>
+    </links>
+
+    <body>
+      <p>The FreeBSD CI team maintains continuous integration
+	system and related tasks
+	for the FreeBSD project. The CI system regularly checks
+	the committed changes
+	can be successfully built, then performs various tests and
+	analysis of the
+	results. The results from build jobs are archived in an
+	artifact server, for
+	the further testing and debugging needs. The CI team
+	members examine the
+	failing builds and unstable tests, and work with the
+	experts in that area to
+	fix the code or adjust test infrastructure. The details
+	are of these efforts
+	are available in the weekly CI reports.</p>
+
+      <p>The
+	<a
+	href="https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md">FCP
+	for CI policy</a>
+	is in "feedback" state, please provide any comments to
+	freebsd-testing@ or
+	other suitable lists.</p>
+
+      <p>We had a testing working group in <a
+	href="https://wiki.freebsd.org/DevSummit/201905/TestingCI">201905
+	DevSummit</a></p>
+
+      <p>Please see freebsd-testing@ related tickets for more
+	information.</p>
+
+      <p>Work in progress:</p>
+
+      <ul>
+	<li>Fixing the failing test cases and builds</li>
+
+	<li>Adding drm ports building test against -CURRENT</li>
+
+	<li>Adding powerpc64 tests job: <a
+	href="https://github.com/freebsd/freebsd-ci/pull/33">https://github.com/freebsd/freebsd-ci/pull/33</a></li>;
+
+	<li>Implementing automatic tests on bare metal hardware</li>
+
+	<li>Extending and publishing the embedded testbed</li>
+
+	<li>Planning for running ztest and network stack tests</li>
+
+	<li>Help more 3rd software get CI on FreeBSD through a hosted
+	CI solution</li>
+      </ul>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Graphics Team status report</title>
+
+    <contact>
+      <person>
+	<name>FreeBSD Graphics Team</name>
+	<email>x11@freebsd.org</email>
+      </person>
+      <person>
+	<name>Niclas Zeising</name>
+	<email>zeising@freebsd.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://github.com/FreeBSDDesktop">Project GitHub page</url>
+    </links>
+
+    <body>
+      <p>The FreeBSD X11/Graphics team maintains the lower levels
+	of the FreeBSD graphics
+	stack.
+	This includes graphics drivers, graphics libraries such as
+	the
+	MESA OpenGL implementation, the X.org xserver with related
+	libraries and
+	applications, and Wayland with related libraries and
+	applications.</p>
+
+      <p>In the last report, half a year ago, several updates and
+	changes had been made
+	to the FreeBSD graphics stack.</p>
+
+      <p>To further improve the user experience, and to improve
+	input device handling,
+	evdev was enabled in the default configuration in late
+	2018. Building on that,
+	we have enabled IBM/Lenovo trackpoints and elantech and
+	synaptics touchpads by
+	default as well.</p>
+
+      <p>The input device library libinput has been updated as the
+	last in a series of
+	updates bringing the userland input stack up to date.
+	This is work that was started in 2018.</p>
+
+      <p>We have made several improvements to the drm kernel
+	drivers.
+	A long-standing memory leak in the Intel (i915) driver has
+	been fixed, and
+	several other updates and improvements have been made to
+	the various drm
+	kernel driver components.</p>
+
+      <p>A port of the drm kernel drivers using the 5.0 Linux
+	kernel sources has been
+	created and committed to FreeBSD ports as
+	<tt>graphics/drm-devel-kmod</tt>.
+	This driver requires a recent Linux KPI and is only
+	available on recent
+	versions of FreeBSD CURRENT.</p>
+
+      <p>This version of the driver contains several development
+	improvements.
+	The generic drm (drm.ko) driver as well as the i915
+	(i915kms.ko) driver
+	can now be unloaded and reloaded to ease in development
+	and testing.
+	This causes issues with the virtual consoles, however, so
+	an SSH connection is
+	recommended.
+	To aid debugging <tt>i915kms.ko</tt> use of debugfs has
+	been improved, but there are
+	still limitations preventing it from being fully
+	functional.
+	Since debugfs is based on pseudofs it is possible that
+	this will prevent a fully
+	functional debugfs in its current state, so we might have
+	to look into adding
+	the required functionality to pseudofs or use another
+	framework.</p>
+
+      <p>The new in-kernel drm driver for VirtualBox,
+	<tt>vboxvideo.ko</tt> has been ported from
+	Linux.
+	Support is currently an experimental work in progress.
+	For example the virtual console won't update after loading
+	the driver, but X-
+	and Wayland-based compositors are working.</p>
+
+      <p>Mesa has been updated to 18.3.2 and switched from using
+	<tt>devel/llvm60</tt> to use
+	the Ports default version of llvm, currently
+	<tt>devel/llvm80</tt>.</p>
+
+      <p>Several userland Xorg drivers, applications, and libraries
+	have been updated,
+	and other improvements to the various userland components
+	that make up the
+	Graphics Stack have been made.</p>
+
+      <p>We have also continued our regularly scheduled bi-weekly
+	meetings, although work
+	remains in sending out timely meeting minutes afterwards.</p>
+
+      <p>People who are interested in helping out can find us on
+	the x11@FreeBSD.org
+	mailing list, or on our gitter chat: <a
+	href="https://gitter.im/FreeBSDDesktop/Lobby">https://gitter.im/FreeBSDDesktop/Lobby</a>.
+	We are also available in #freebsd-xorg on EFNet.</p>
+
+      <p>We also have a team area on GitHub where our work
+	repositories can be found:
+	<a
+	href="https://github.com/FreeBSDDesktop">https://github.com/FreeBSDDesktop</a></p>;
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>IRC Admin</title>
+
+    <contact>
+      <person>
+	<name>IRC Admin</name>
+	<email>irc@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>The FreeBSD IRC Admin team manages the FreeBSD Project's
+	presence
+	and activity on the freenode IRC network, looking after:</p>
+
+      <ul>
+	<li>Registration and management of channels within the
+	official namespace (#freebsd*)</li>
+
+	<li>Channel moderation</li>
+
+	<li>Liaising with freenode staff</li>
+
+	<li>Allocating <tt>freebsd/*</tt> hostmask cloaks for users</li>
+
+	<li>General user support relating to channel management</li>
+      </ul>
+
+      <p>
+	While the FreeBSD Project does not _currently_ endorse IRC
+	as an
+	official support channel [1][2], as it has not been able
+	to guarantee
+	a consistent or positive user experience, IRC Admin has
+	been working
+	toward creating a high quality experience, by
+	standardising channel
+	administration and moderation expectations, and ensuring
+	the projects
+	ability to manage all channels within its namespace.</p>
+
+      <p>In the last quarter, IRC Admin:</p>
+
+      <ul>
+	<li>Cleaned up (deregistered) registrations for channels that
+	were defunct,
+	stale, out of date, or had founders that were inactive
+	(not seen for &gt; 1
+	year). Channels that were found to be otherwise active
+	have been retained.
+	FreeBSD now has ~40 channels registered from a previous
+	total of over 150.</li>
+
+	<li>Documented baseline configuration settings in the Wiki for
+	channels,
+	including ChanServ settings, channel modes, registration
+	policy, etc.</li>
+
+	<li>Established multiple documented methods for reporting user
+	abuse
+	or other channel issues to IRC Admin for resolution</li>
+      </ul>
+
+      <p>
+	Upcoming changes:</p>
+
+      <ul>
+	<li>Work with existing <tt>#freebsd*</tt> channels to
+	standardise channel management,
+	settings and access.</li>
+
+	<li>Migrate, forward and/or consolidate existing or duplicate
+	<tt>#freebsd*</tt>
+	channels to channels with a standard naming convention.</li>
+
+	<li>Work with unofficial <tt>##freebsd*</tt> channels to
+	migrate them to the official
+	<tt>#freebsd*</tt> channels if suitable</li>
+
+	<li>Update existing IRC-related website and documentation
+	sources the describe
+	the official state of project managed IRC presence on
+	freenode.</li>
+      </ul>
+
+      <p>
+	Lastly, and to repeat a previous call, while the vast
+	majority of
+	the broader user community interacts on the freenode IRC
+	network,
+	the FreeBSD developer presence still needs to be
+	significantly
+	improved on freenode.</p>
+
+      <p>There are many opportunities to be had by increasing the
+	amount and
+	quality of interaction between FreeBSD users and
+	developers, both
+	in terms of developers keeping their finger on the pulse
+	of the
+	community and in encouraging and cultivating greater
+	contributions
+	to the Project over the long term.</p>
+
+      <p>It is critical to have a strong developer presence amongst
+	users,
+	and IRC Admin would like again to call on all developers
+	to join
+	the FreeBSD freenode channels to increase that presence.</p>
+
+      <p>Users are invited to <tt>/join #freebsd-irc</tt> on the
+	freenode IRC network
+	if they have questions, ideas, constructive criticism, and
+	feedback
+	on how the FreeBSD Project can improve the service and
+	experience
+	it provides to the community on IRC.</p>
+
+      <p>[1] https://www.freebsd.org/community/irc.html
+	[2]
+	https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/support.html#irc</p>;
+
+    </body>
+
+  </project>
+
+  <project cat='proj'>
+    <title>bhyve - Live Migration</title>
+
+    <contact>
+      <person>
+	<name>Elena Mihailescu</name>
+	<email>elenamihailescu22@gmail.com</email>
+      </person>
+      <person>
+	<name>Darius Mihai</name>
+	<email>dariusmihaim@gmail.com</email>
+      </person>
+      <person>
+	<name>Mihai Carabas</name>
+	<email>mihai@freebsd.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve">Github wiki - How to Live and Warm Migrate a bhyve guest</url>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github - Warm Migration branch</url>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev">Github - Live Migration branch</url>
+    </links>
+
+    <body>
+      <p>The Migration feature uses the Save/Restore feature to
+	migrate a bhyve guest
+	from a FreeBSD host to another FreeBSD host. To migrate a
+	bhyve guest,
+	one needs to start an empty guest on the destination host
+	from a shared guest
+	image using the bhyve tool with the <tt>-R</tt> option
+	followed by the source host
+	IP and the port to listen to migration request. On the
+	source host, the
+	migration is started by executing the bhyvectl command
+	with the <tt>--migrate</tt>
+	or <tt>--migrate-live</tt> option, followed by the
+	destination host IP and the
+	port to send to the messages.</p>
+
+      <p>New features added:</p>
+
+      <ul>
+	<li>Clear the dirty bit after each migration round</li>
+
+	<li>Extend live migration to highmem segment</li>
+      </ul>
+
+      <p>
+	Future tasks:</p>
+
+      <ul>
+	<li>Refactor live migration branch</li>
+
+	<li>Rebase live migration</li>
+
+	<li>Extend live migration to unwired memory</li>
+      </ul>
+
+    </body>
+
+    <sponsor>
+      Matthew Grooms
+    </sponsor>
+
+  </project>
+
+  <project cat='proj'>
+    <title>bhyve - Save/Restore</title>
+
+    <contact>
+      <person>
+	<name>Elena Mihailescu</name>
+	<email>elenamihailescu22@gmail.com</email>
+      </person>
+      <person>
+	<name>Darius Mihai</name>
+	<email>dariusmihaim@gmail.com</email>
+      </person>
+      <person>
+	<name>Mihai Carabas</name>
+	<email>mihai@freebsd.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_snapshot">Github repository for the snapshot feature for bhyve</url>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve">Github wiki - How to Save and Restore a bhyve guest</url>
+      <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix">Github wiki - Suspend/resume test matrix</url>
+      <url href="https://reviews.freebsd.org/D19495">Phabricator review - bhyve Snapshot Save and Restore</url>
+    </links>
+
+    <body>
+      <p>The Save/Restore for bhyve feature is a suspend and resume
+	facility added to the
+	FreeBSD/amd64's hypervisor, bhyve. The bhyvectl tool is
+	used to save the guest
+	state in three files (a file for the guest memory, a file
+	for the states of
+	various devices and the state of the CPU, and another one
+	for some metadata that
+	is used in the restore process).
+	To suspend a bhyve guest, the bhyvectl tool must be run
+	with the <tt>--suspend
+	&lt;state_file_name&gt;</tt>
+	option followed by the guest name.</p>
+
+      <p>To restore a bhyve guest from a checkpoint, one simply has
+	to add the <tt>-r</tt> option
+	followed by the main state file (the same file that was
+	given to the <tt>--suspend</tt>
+	option for bhyvectl) when starting the VM.</p>
+
+      <p>New features added:</p>
+
+      <ul>
+	<li>Open ticket on Phabricator</li>
+
+	<li>Apply feedback received from community</li>
+      </ul>
+
+      <p>
+	Future tasks:</p>
+
+      <ul>
+	<li>Add suspend/resume support for nvme</li>
+
+	<li>Add suspend/resume support for virtio-console</li>
+
+	<li>Add suspend/resume support for virtio-scsi</li>
+
+	<li>Add TSC offsetting for restore for AMD CPUs</li>
+      </ul>
+
+    </body>
+
+    <sponsor>
+      Matthew Grooms
+    </sponsor>
+
+  </project>
+
+  <project cat='proj'>
+    <title>ENA FreeBSD Driver Update</title>
+
+    <contact>
+      <person>
+	<name>Michal Krawczyk</name>
+	<email>mk@semihalf.com</email>
+      </person>
+      <person>
+	<name>Maciej Bielski</name>
+	<email>mba@semihalf.com</email>
+      </person>
+      <person>
+	<name>Marcin Wojtas</name>
+	<email>mw@semihalf.com</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</url>
+    </links>
+
+    <body>
+      <p>ENA (Elastic Network Adapter) is the smart NIC available
+	in the
+	virtualized environment of Amazon Web Services (AWS). The
+	ENA
+	driver supports multiple transmit and receive queues and
+	can handle
+	up to 100 Gb/s of network traffic, depending on the
+	instance type
+	on which it is used.</p>
+
+      <p>ENAv2 has been under development for FreeBSD, similar to
+	Linux
+	and DPDK. Since the last update internal review and
+	improvements
+	of the patches were done, followed by validation on
+	various AWS
+	instances.</p>
+
+      <p>Completed since the last update:</p>
+
+      <ul>
+	<li>Upstream of the ENAv2 patches - revisions
+	<a
+	href="https://svnweb.freebsd.org/base?view=revision&amp;revision=348383">r348383</a>;
+	-
+	<a
+	href="https://svnweb.freebsd.org/base?view=revision&amp;revision=348416">r348416</a>;
+	introduce a major driver upgrade to version v2.0.0. Along
+	with various fixes
+	and improvements, the most significant features are LLQ
+	(Low Latency Queues)
+	and independent queues reconfiguration using sysctl
+	commands.</li>
+
+	<li>Implement NETMAP support for ENA</li>
+      </ul>
+
+      <p>
+	Todo:</p>
+
+      <ul>
+	<li>Internal review and upstream of NETMAP support</li>
+      </ul>
+
+    </body>
+
+    <sponsor>
+      Amazon.com Inc
+    </sponsor>
+
+  </project>
+
+  <project cat='proj'>
+    <title>FUSE</title>
+
+    <contact>
+      <person>
+	<name>Alan Somers</name>
+	<email>asomers@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>FUSE (File system in USErspace) allows a userspace program
+	to
+	implement a file system. It is widely used to support
+	out-of-tree file
+	systems like NTFS, as well as for exotic pseudo file
+	systems like
+	sshfs. FreeBSD's fuse driver was added as a GSoC project
+	in 2012.
+	Since that time, it has been largely neglected. The FUSE
+	software is
+	<a
+	href="https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&amp;known_name=fusefs&amp;list_id=289348&amp;query_based_on=fusefs&amp;query_format=advanced&amp;short_desc=%5Bfusefs%5D%20sysutils%2Ffusefs-&amp;short_desc_type=anywordssubstr">buggy</a>;
+	and out-of-date. Our implementation is about 11 years
+	behind.</p>
+
+      <p>During Q2 I nearly finished the FUSE overhaul that I
+	begain in Q1. I raised
+	the protocol level from 7.8 to 7.23, fixed many bugs (see
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199934">199934</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216391">216391</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233783">233783</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234581">234581</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235773">235773</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235774">235774</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235775">235775</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236226">236226</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236231">236231</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236236">236236</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239291">239291</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236329">236329</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236379">236379</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236381">236381</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236405">236405</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236327">236327</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236466">236466</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236472">236472</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236473">236473</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236474">236474</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236530">236530</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236557">236557</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236560">236560</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236647">236647</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236844">236844</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237052">237052</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237181">237181</a>,
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237588">237588</a>,
+	and
+	<a
+	href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238565">238565</a>),
+	and added
+	the following features:</p>
+
+      <ul>
+	<li>Optional kernel-side permissions checks (`-o
+	default_permissions`)</li>
+
+	<li>Implement <tt>VOP_MKNOD</tt>, <tt>VOP_BMAP</tt>, and
+	<tt>VOP_ADVLOCK</tt></li>
+
+	<li>Allow interrupting FUSE operations</li>
+
+	<li>Support named pipes and unix-domain sockets in fusefs file
+	systems</li>
+

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201908241856.x7OIuG03049044>