Date: Sat, 02 May 2026 13:45:16 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "Miroslav Lachman" <000.fbsd@quip.cz>, "Sean Eric Fagan" <Sean.fagan@klarasystems.com>, freebsd-virtualization <freebsd-virtualization@freebsd.org>, "Chuck Tuffli" <chuck@freebsd.org> Cc: "Mark Johnston" <markj@freebsd.org> Subject: Re: bhyve and controlled errors Message-ID: <51b087ce-121a-4356-aba6-71ef1f0cad5c@app.fastmail.com> In-Reply-To: <4e4a795c-0dae-4e71-883a-0f3d45adb675@quip.cz> References: <F7A52994-0294-4C99-86F4-7204AE2D6CB9@klarasystems.com> <4e4a795c-0dae-4e71-883a-0f3d45adb675@quip.cz>
index | next in thread | previous in thread | raw e-mail
On Tue, 7 Apr 2026, at 10:32, Miroslav Lachman wrote: > On 26/03/2026 15:56, Sean Eric Fagan wrote: >> I’d asked Mark about this and he suggested I bring it up on the list: >> >> Has anyone thought about implementing controls / tunables to bhyve to introduce errors? I am, most specifically right now, thinking about causing disk I/O errors, or having requests dropped by the "hardware," to test error handling. >> >> Last time I looked at the bhyve source code, it scared me, so if someone else has looked at this, I’m love to know. > > I understand it would be nice to have it directly as a part of bhyve, > but if you need something right now, you can try "gnop". > See man gnop(8): > Its main purpose is testing other GEOM classes, as it allows > forced provider removal and I/O error simulation with a given > probability. > > Or maybe someone with skill can reuse its code for bhyve feature. > > Kind regards > Miroslav Lachman Chuck Tuffli already did some work in this area: https://papers.freebsd.org/2019/bsdcan/tuffli-frankensteins_disk_drive/ https://bhyvecon.org/bhyveconOttawa2019-Chuck.pdf You should be able to find the related videos for these. A+ Davehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51b087ce-121a-4356-aba6-71ef1f0cad5c>