Re: 13.0 RC4 might be delayed

[Guido Falsi via freebsd-current]

On 29/03/21 16:28, Mario Lobo wrote:

[snip]
   Good point. Now the question is, what the default should be. Since the


correct aio configuration is in the pkg-message and easy to setup I'd go
for default to AIO turned on.
--
Guido Falsi 



+1

The way it is, is running smooth here on STABLE/13 and 14-CURRENT.



I've just committed the AIO option (enabled by default) in r569604.

BTW, since I'm going to sleep shortly, this will be my last commit to 
subversion. If I read correctly the migration schedule, subversion will 
be read only by the time I wake up.


Hope everything works out fine!

--
Guido Falsi 
___
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: 13.0 RC4 might be delayed

[Mario Lobo]

[snip]
  Good point. Now the question is, what the default should be. Since the

> correct aio configuration is in the pkg-message and easy to setup I'd go
> for default to AIO turned on.
> --
> Guido Falsi 
>

+1

The way it is, is running smooth here on STABLE/13 and 14-CURRENT.

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!]
___
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: 13.0 RC4 might be delayed

[Guido Falsi via freebsd-current]

On 29/03/21 06:26, Greg Rivers wrote:

On Sunday, 28 March 2021 20:37:13 CDT David G Lawrence via freebsd-current 
wrote:

On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:

On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
wrote:


On 26/03/2021 03:40, The Doctor via freebsd-current wrote:

??? if people are having issues with ports like ???


If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with
emulators/virtualbox-ose 6.1.18 as the host

* no such trouble with 12.0-RELEASE-p5 as a guest.

I hope to refine the bug report this weekend.



Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
That
was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
will try again shortly to see if it's any better.


Kevin,

?? Make sure you have these options in your /etc/sysctl.conf :

vfs.aio.max_buf_aio=8192
vfs.aio.max_aio_queue_per_proc=65536
vfs.aio.max_aio_per_proc=8192
vfs.aio.max_aio_queue=65536

?? ...otherwise the guest I/O will random hang in VirtualBox. This
issue was
mitigated in a late 5.x VirtualBox by patching to not use AIO, but the
issue
came back in 6.x when that patch wasn't carried forward.


Sorry I lost that patch. Can you point me to the patch? Maybe it can be
easily ported.



I found the relevant commit. Please give me some time for testing and
I'll put this patch back in the tree.


If you're going to put that patch back in, then AIO should probably be
made an option in the port config, as shutting AIO off by default will
have a significant performance impact. Without AIO, all guest IO will
be become synchronous.
Ideally, someone would fix the AIO case by either increasing the defaults
in FreeBSD to something reasonable, and/or properly handing the case when
an AIO limit is reached.


Agreed, it would be a shame to have AIO disabled by default. A one time update 
to sysctl.conf (per the existing pkg message!) is a small price to pay for much 
better performance.



Good point. Now the question is, what the default should be. Since the 
correct aio configuration is in the pkg-message and easy to setup I'd go 
for default to AIO turned on.


I Have a few things on he pope with ports, I will need some days to work 
this out.


--
Guido Falsi 
___
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: 13.0 RC4 might be delayed

[Kevin Oberman]

On Sun, Mar 28, 2021 at 9:36 PM Gleb Popov  wrote:

> On Mon, Mar 29, 2021 at 4:37 AM David G Lawrence via freebsd-current <
> freebsd-current@freebsd.org> wrote:
>
> > > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> > > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin <
> > grahamper...@gmail.com>
> > > >>> wrote:
> > > >>>
> > >  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > > ??? if people are having issues with ports like ???
> > > 
> > >  If I'm not mistaken:
> > > 
> > >  * 13.0-RC3 seems to be troublesome, as a guest machine, with
> > >  emulators/virtualbox-ose 6.1.18 as the host
> > > 
> > >  * no such trouble with 12.0-RELEASE-p5 as a guest.
> > > 
> > >  I hope to refine the bug report this weekend.
> > > 
> > > >>>
> > > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7
> > system.
> > > >>> That
> > > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5)
> > and
> > > >>> will try again shortly to see if it's any better.
> > > >>
> > > >> Kevin,
> > > >>
> > > >> ?? Make sure you have these options in your /etc/sysctl.conf :
> > > >>
> > > >> vfs.aio.max_buf_aio=8192
> > > >> vfs.aio.max_aio_queue_per_proc=65536
> > > >> vfs.aio.max_aio_per_proc=8192
> > > >> vfs.aio.max_aio_queue=65536
> > > >>
> > > >> ?? ...otherwise the guest I/O will random hang in VirtualBox.
> > This
> > > >> issue was
> > > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but
> > the
> > > >> issue
> > > >> came back in 6.x when that patch wasn't carried forward.
> > > >
> > > > Sorry I lost that patch. Can you point me to the patch? Maybe it can
> > be
> > > > easily ported.
> > > >
> > >
> > > I found the relevant commit. Please give me some time for testing and
> > > I'll put this patch back in the tree.
> >
> >If you're going to put that patch back in, then AIO should probably be
> > made an option in the port config, as shutting AIO off by default will
> > have a significant performance impact. Without AIO, all guest IO will
> > be become synchronous.
> >
>
> Are you sure about that? Without AIO, VBox uses a generic POSIX backend,
> which is based on pthread, I think.
>
At least VirtualBax without AIO has some serious performance issues without
AIO. At least a Win7 guest does on certain operations. I would really
prefer better aio values. I don't recall who suggested those to me, but I
took them and made them more reasonable, but I am sure they are not close
to optimal and I don't understand their use well enough to get them right.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: 13.0 RC4 might be delayed

[Alan Somers]

On Sun, Mar 28, 2021 at 10:36 PM Gleb Popov  wrote:

> On Mon, Mar 29, 2021 at 4:37 AM David G Lawrence via freebsd-current <
> freebsd-current@freebsd.org> wrote:
>
> > > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> > > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin <
> > grahamper...@gmail.com>
> > > >>> wrote:
> > > >>>
> > >  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > > ??? if people are having issues with ports like ???
> > > 
> > >  If I'm not mistaken:
> > > 
> > >  * 13.0-RC3 seems to be troublesome, as a guest machine, with
> > >  emulators/virtualbox-ose 6.1.18 as the host
> > > 
> > >  * no such trouble with 12.0-RELEASE-p5 as a guest.
> > > 
> > >  I hope to refine the bug report this weekend.
> > > 
> > > >>>
> > > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7
> > system.
> > > >>> That
> > > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5)
> > and
> > > >>> will try again shortly to see if it's any better.
> > > >>
> > > >> Kevin,
> > > >>
> > > >> ?? Make sure you have these options in your /etc/sysctl.conf :
> > > >>
> > > >> vfs.aio.max_buf_aio=8192
> > > >> vfs.aio.max_aio_queue_per_proc=65536
> > > >> vfs.aio.max_aio_per_proc=8192
> > > >> vfs.aio.max_aio_queue=65536
> > > >>
> > > >> ?? ...otherwise the guest I/O will random hang in VirtualBox.
> > This
> > > >> issue was
> > > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but
> > the
> > > >> issue
> > > >> came back in 6.x when that patch wasn't carried forward.
> > > >
> > > > Sorry I lost that patch. Can you point me to the patch? Maybe it can
> > be
> > > > easily ported.
> > > >
> > >
> > > I found the relevant commit. Please give me some time for testing and
> > > I'll put this patch back in the tree.
> >
> >If you're going to put that patch back in, then AIO should probably be
> > made an option in the port config, as shutting AIO off by default will
> > have a significant performance impact. Without AIO, all guest IO will
> > be become synchronous.
> >
>
> Are you sure about that? Without AIO, VBox uses a generic POSIX backend,
> which is based on pthread, I think.
>

We should also consider changing the defaults.

vfs.aio.max_buf_aio: this is the maximum number of buffered AIO requests
per process.  Buffered AIO requests are only used when directing AIO to
device nodes, not files, and only for devices that don't support unmapped
I/O.  Most devices do support unmapped I/O, including all GEOM devices.
For devices that do support unmapped I/O, the number of AIO requests per
process is unlimited.  So this knob isn't very important.  However, it is
more important on powerpc and mips, where unmapped I/O isn't always
possible.  16 is probably pretty reasonable for mips.

vfs.aio.max_aio_queue_per_proc: this is the maximum queued aio requests per
process.  This applies to all AIO requests, whether to files or devices.
So it ought to be large.  If your program is too unsophisticated to handle
EAGAIN, then it must be very large.  Otherwise, a few multiples of
max(vfs.aio.max_aio_per_proc, your SSD's queue depth) is probably
sufficient.

vfs.aio.max_aio_per_proc: this is the max number of active aio requests in
the slow path (for I/O to files, or other cases like misaligned I/O to
disks).  Setting this too low won't cause programs to fail, but it could
hurt performance.  Setting it higher than vfs.aio.max_aio_procs probably
won't have any benefit.

vfs.aio.max_aio_queue: like max_aio_per_proc, but global instead of
per-process.  Doesn't need to be more than a few multiples of
max_aio_per_proc.

Finally, I see that emulators/virtualbox-ose's pkg-message advises checking
for the AIO kernel module.  That advice is obsolete.  AIO is nowadays
builtin to the kernel and always enabled.  There is no kernel module any
longer.

Actually, the defaults don't look unreasonable to me, for an amd64 system
with disk, file, or zvol-backed VMs.  Does virtualbox properly handle
EAGAIN as returned by aio_write, aio_read, and lio_listio?  If not, raising
these limits is a poor substitute for fixing virtualbox.  If so, then I'm
really curious.  If anybody could tell me which limit actually solves the
problem, I would like to know.

-Alan
___
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: 13.0 RC4 might be delayed

[David G Lawrence via freebsd-current]

> On Mon, Mar 29, 2021 at 4:37 AM David G Lawrence via freebsd-current <
> freebsd-current@freebsd.org> wrote:
> 
> > > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> > > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin <
> > grahamper...@gmail.com>
> > > >>> wrote:
> > > >>>
> > >  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > > ??? if people are having issues with ports like ???
> > > 
> > >  If I'm not mistaken:
> > > 
> > >  * 13.0-RC3 seems to be troublesome, as a guest machine, with
> > >  emulators/virtualbox-ose 6.1.18 as the host
> > > 
> > >  * no such trouble with 12.0-RELEASE-p5 as a guest.
> > > 
> > >  I hope to refine the bug report this weekend.
> > > 
> > > >>>
> > > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7
> > system.
> > > >>> That
> > > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5)
> > and
> > > >>> will try again shortly to see if it's any better.
> > > >>
> > > >> Kevin,
> > > >>
> > > >> ?? Make sure you have these options in your /etc/sysctl.conf :
> > > >>
> > > >> vfs.aio.max_buf_aio=8192
> > > >> vfs.aio.max_aio_queue_per_proc=65536
> > > >> vfs.aio.max_aio_per_proc=8192
> > > >> vfs.aio.max_aio_queue=65536
> > > >>
> > > >> ?? ...otherwise the guest I/O will random hang in VirtualBox.
> > This
> > > >> issue was
> > > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but
> > the
> > > >> issue
> > > >> came back in 6.x when that patch wasn't carried forward.
> > > >
> > > > Sorry I lost that patch. Can you point me to the patch? Maybe it can
> > be
> > > > easily ported.
> > > >
> > >
> > > I found the relevant commit. Please give me some time for testing and
> > > I'll put this patch back in the tree.
> >
> >If you're going to put that patch back in, then AIO should probably be
> > made an option in the port config, as shutting AIO off by default will
> > have a significant performance impact. Without AIO, all guest IO will
> > be become synchronous.
> >
> 
> Are you sure about that? Without AIO, VBox uses a generic POSIX backend,
> which is based on pthread, I think.

   No, I'm not sure - I haven't looked at the code. My comment is based on
some comments that a VirtualBox developer made in a forum 3-4 years ago
where he said that the "generic POSIX" IO was very simple and never
intended to be used in production - only as a placeholder when developing
for a new host platform.

   Are you sure that it does multi-threaded IO?

-DG
___
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: 13.0 RC4 might be delayed

[Gleb Popov]

On Mon, Mar 29, 2021 at 4:37 AM David G Lawrence via freebsd-current <
freebsd-current@freebsd.org> wrote:

> > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin <
> grahamper...@gmail.com>
> > >>> wrote:
> > >>>
> >  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > ??? if people are having issues with ports like ???
> > 
> >  If I'm not mistaken:
> > 
> >  * 13.0-RC3 seems to be troublesome, as a guest machine, with
> >  emulators/virtualbox-ose 6.1.18 as the host
> > 
> >  * no such trouble with 12.0-RELEASE-p5 as a guest.
> > 
> >  I hope to refine the bug report this weekend.
> > 
> > >>>
> > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7
> system.
> > >>> That
> > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5)
> and
> > >>> will try again shortly to see if it's any better.
> > >>
> > >> Kevin,
> > >>
> > >> ?? Make sure you have these options in your /etc/sysctl.conf :
> > >>
> > >> vfs.aio.max_buf_aio=8192
> > >> vfs.aio.max_aio_queue_per_proc=65536
> > >> vfs.aio.max_aio_per_proc=8192
> > >> vfs.aio.max_aio_queue=65536
> > >>
> > >> ?? ...otherwise the guest I/O will random hang in VirtualBox.
> This
> > >> issue was
> > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but
> the
> > >> issue
> > >> came back in 6.x when that patch wasn't carried forward.
> > >
> > > Sorry I lost that patch. Can you point me to the patch? Maybe it can
> be
> > > easily ported.
> > >
> >
> > I found the relevant commit. Please give me some time for testing and
> > I'll put this patch back in the tree.
>
>If you're going to put that patch back in, then AIO should probably be
> made an option in the port config, as shutting AIO off by default will
> have a significant performance impact. Without AIO, all guest IO will
> be become synchronous.
>

Are you sure about that? Without AIO, VBox uses a generic POSIX backend,
which is based on pthread, I think.
___
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: 13.0 RC4 might be delayed

[Greg Rivers via freebsd-current]

On Sunday, 28 March 2021 20:37:13 CDT David G Lawrence via freebsd-current 
wrote:
> > > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> > >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
> > >>> wrote:
> > >>>
> >  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > ??? if people are having issues with ports like ???
> > 
> >  If I'm not mistaken:
> > 
> >  * 13.0-RC3 seems to be troublesome, as a guest machine, with
> >  emulators/virtualbox-ose 6.1.18 as the host
> > 
> >  * no such trouble with 12.0-RELEASE-p5 as a guest.
> > 
> >  I hope to refine the bug report this weekend.
> > 
> > >>>
> > >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. 
> > >>> That
> > >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
> > >>> will try again shortly to see if it's any better.
> > >>
> > >> Kevin,
> > >>
> > >> ?? Make sure you have these options in your /etc/sysctl.conf :
> > >>
> > >> vfs.aio.max_buf_aio=8192
> > >> vfs.aio.max_aio_queue_per_proc=65536
> > >> vfs.aio.max_aio_per_proc=8192
> > >> vfs.aio.max_aio_queue=65536
> > >>
> > >> ?? ...otherwise the guest I/O will random hang in VirtualBox. This 
> > >> issue was
> > >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but the 
> > >> issue
> > >> came back in 6.x when that patch wasn't carried forward.
> > > 
> > > Sorry I lost that patch. Can you point me to the patch? Maybe it can be 
> > > easily ported.
> > > 
> > 
> > I found the relevant commit. Please give me some time for testing and 
> > I'll put this patch back in the tree.
> 
>If you're going to put that patch back in, then AIO should probably be
> made an option in the port config, as shutting AIO off by default will
> have a significant performance impact. Without AIO, all guest IO will
> be become synchronous.
>Ideally, someone would fix the AIO case by either increasing the defaults
> in FreeBSD to something reasonable, and/or properly handing the case when
> an AIO limit is reached.
> 
Agreed, it would be a shame to have AIO disabled by default. A one time update 
to sysctl.conf (per the existing pkg message!) is a small price to pay for much 
better performance.

-- 
Greg


___
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: 13.0 RC4 might be delayed

[David G Lawrence via freebsd-current]

> > On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:
> >>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
> >>> wrote:
> >>>
>  On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > ??? if people are having issues with ports like ???
> 
>  If I'm not mistaken:
> 
>  * 13.0-RC3 seems to be troublesome, as a guest machine, with
>  emulators/virtualbox-ose 6.1.18 as the host
> 
>  * no such trouble with 12.0-RELEASE-p5 as a guest.
> 
>  I hope to refine the bug report this weekend.
> 
> >>>
> >>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. 
> >>> That
> >>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
> >>> will try again shortly to see if it's any better.
> >>
> >> Kevin,
> >>
> >> ?? Make sure you have these options in your /etc/sysctl.conf :
> >>
> >> vfs.aio.max_buf_aio=8192
> >> vfs.aio.max_aio_queue_per_proc=65536
> >> vfs.aio.max_aio_per_proc=8192
> >> vfs.aio.max_aio_queue=65536
> >>
> >> ?? ...otherwise the guest I/O will random hang in VirtualBox. This 
> >> issue was
> >> mitigated in a late 5.x VirtualBox by patching to not use AIO, but the 
> >> issue
> >> came back in 6.x when that patch wasn't carried forward.
> > 
> > Sorry I lost that patch. Can you point me to the patch? Maybe it can be 
> > easily ported.
> > 
> 
> I found the relevant commit. Please give me some time for testing and 
> I'll put this patch back in the tree.

   If you're going to put that patch back in, then AIO should probably be
made an option in the port config, as shutting AIO off by default will
have a significant performance impact. Without AIO, all guest IO will
be become synchronous.
   Ideally, someone would fix the AIO case by either increasing the defaults
in FreeBSD to something reasonable, and/or properly handing the case when
an AIO limit is reached.

-DG
___
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: 13.0 RC4 might be delayed

[Guido Falsi via freebsd-current]

On 28/03/21 22:34, Guido Falsi via freebsd-current wrote:

On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:

On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
wrote:


On 26/03/2021 03:40, The Doctor via freebsd-current wrote:

??? if people are having issues with ports like ???


If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with
emulators/virtualbox-ose 6.1.18 as the host

* no such trouble with 12.0-RELEASE-p5 as a guest.

I hope to refine the bug report this weekend.



Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. 
That

was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
will try again shortly to see if it's any better.


Kevin,

    Make sure you have these options in your /etc/sysctl.conf :

vfs.aio.max_buf_aio=8192
vfs.aio.max_aio_queue_per_proc=65536
vfs.aio.max_aio_per_proc=8192
vfs.aio.max_aio_queue=65536

    ...otherwise the guest I/O will random hang in VirtualBox. This 
issue was
mitigated in a late 5.x VirtualBox by patching to not use AIO, but the 
issue

came back in 6.x when that patch wasn't carried forward.


Sorry I lost that patch. Can you point me to the patch? Maybe it can be 
easily ported.




I found the relevant commit. Please give me some time for testing and 
I'll put this patch back in the tree.


--
Guido Falsi 
___
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: 13.0 RC4 might be delayed

[Guido Falsi via freebsd-current]

On 27/03/21 06:04, David G Lawrence via freebsd-current wrote:

On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
wrote:


On 26/03/2021 03:40, The Doctor via freebsd-current wrote:

??? if people are having issues with ports like ???


If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with
emulators/virtualbox-ose 6.1.18 as the host

* no such trouble with 12.0-RELEASE-p5 as a guest.

I hope to refine the bug report this weekend.



Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. That
was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
will try again shortly to see if it's any better.


Kevin,

Make sure you have these options in your /etc/sysctl.conf :

vfs.aio.max_buf_aio=8192
vfs.aio.max_aio_queue_per_proc=65536
vfs.aio.max_aio_per_proc=8192
vfs.aio.max_aio_queue=65536

...otherwise the guest I/O will random hang in VirtualBox. This issue was
mitigated in a late 5.x VirtualBox by patching to not use AIO, but the issue
came back in 6.x when that patch wasn't carried forward.


Sorry I lost that patch. Can you point me to the patch? Maybe it can be 
easily ported.


--
Guido Falsi 
___
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: 13.0 RC4 might be delayed

[Kevin Oberman]

On Sat, Mar 27, 2021 at 5:07 AM dmilith .  wrote:

> It may not only be Virtualbox, but also happens under Vmware VMs.
>
> I use Vmware Fusion 7 pro as my software build-host on top of my Mac
> Pro for years now, but I can't build much with 13.0 cause regular
> build processes (like sed, awk, grep, zsh) turn into zombies randomly.
> Example shot from my private CI from yesterday:
> http://s.verknowsys.com/12f14b0350ee3baeb8f153cd48764bc8.png
>
> The issue doesn't happen on 12.2, 12.1, 12.0 or older releases.
>
> I reported this issue (I'm testing it since 13-alpha) here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253718
>
> In RC3 it feels it got even worse and happens even more often… It's a
> critical release blocker if you ask me…
>
> kind regards
> Daniel
>
> On 27/03/2021, David G Lawrence via freebsd-current
>  wrote:
> >> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
> >> wrote:
> >>
> >> > On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> >> > > ??? if people are having issues with ports like ???
> >> >
> >> > If I'm not mistaken:
> >> >
> >> > * 13.0-RC3 seems to be troublesome, as a guest machine, with
> >> > emulators/virtualbox-ose 6.1.18 as the host
> >> >
> >> > * no such trouble with 12.0-RELEASE-p5 as a guest.
> >> >
> >> > I hope to refine the bug report this weekend.
> >> >
> >>
> >> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
> >> That
> >> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
> >> will try again shortly to see if it's any better.
> >
> > Kevin,
> >
> >Make sure you have these options in your /etc/sysctl.conf :
> >
> > vfs.aio.max_buf_aio=8192
> > vfs.aio.max_aio_queue_per_proc=65536
> > vfs.aio.max_aio_per_proc=8192
> > vfs.aio.max_aio_queue=65536
> >
> >...otherwise the guest I/O will random hang in VirtualBox. This issue
> > was
> > mitigated in a late 5.x VirtualBox by patching to not use AIO, but the
> > issue
> > came back in 6.x when that patch wasn't carried forward.
> >
> > -DG
> > ___
> > 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"
> >
>
>
> --
> --
> Daniel Dettlaff
> Versatile Knowledge Systems
> verknowsys.com
>

My problem was resolved when I spent the time to read the pkg-message in
the port. It is running just fine, now. Somehow I missed David's message,
as well.  Not good. Unfortunate that the patches to turn off AIO did not
make it into V6.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

[Kevin Oberman]

Host is FreeBSD 13-STABLE.Guest is Win 7 which I depend on for Quicken. I
also use it to access a bank account at a bank that refuses access from any
OS other than Windows or MacOS. I managed to access it for about a year by
having Firefox lie and claim to be Windows, but that stopped working. They
make the almost humorous claim that only Windows and MacOS are adequately
secure.

At this point I have no idea if the issue is with VirtualBx or FreeBSD,
but, after seeing more details of your problem, I doubt mine is related. I
really suspect it's VirtualBox, so I will drop out of this discussion as it
appears that I don't have an issue with it. After some more work on it,
I'll open a ticket with emulators@.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Fri, Mar 26, 2021 at 7:23 PM Graham Perrin 
wrote:

> On 26/03/2021 21:55, Kevin Oberman wrote:
> > On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin  > > wrote:
> >
> >
> > If I'm not mistaken:
> >
> > …
> >
> > Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
> > That was right after 6.1.18 was put into ports. Fell back to legacy
> > (v5) and will try again shortly to see if it's any better.
>
> Windows 7 guest or host?
>
> For me, Windows 10 20H2 guest is rock solid.
>
> % pkg info -x virtualbox
> virtualbox-ose-6.1.18
> virtualbox-ose-kmod-6.1.18_1
> % freebsd-version -kru
> 14.0-CURRENT
> 14.0-CURRENT
> 14.0-CURRENT
> % uname -a
> FreeBSD mowa219-gjp4-8570p 14.0-CURRENT FreeBSD 14.0-CURRENT #90
> main-n245648-66f138563be: Thu Mar 25 08:00:54 GMT 2021
> root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
> %
>
>
___
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: 13.0 RC4 might be delayed

[dmilith .]

It may not only be Virtualbox, but also happens under Vmware VMs.

I use Vmware Fusion 7 pro as my software build-host on top of my Mac
Pro for years now, but I can't build much with 13.0 cause regular
build processes (like sed, awk, grep, zsh) turn into zombies randomly.
Example shot from my private CI from yesterday:
http://s.verknowsys.com/12f14b0350ee3baeb8f153cd48764bc8.png

The issue doesn't happen on 12.2, 12.1, 12.0 or older releases.

I reported this issue (I'm testing it since 13-alpha) here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253718

In RC3 it feels it got even worse and happens even more often… It's a
critical release blocker if you ask me…

kind regards
Daniel

On 27/03/2021, David G Lawrence via freebsd-current
 wrote:
>> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
>> wrote:
>>
>> > On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
>> > > ??? if people are having issues with ports like ???
>> >
>> > If I'm not mistaken:
>> >
>> > * 13.0-RC3 seems to be troublesome, as a guest machine, with
>> > emulators/virtualbox-ose 6.1.18 as the host
>> >
>> > * no such trouble with 12.0-RELEASE-p5 as a guest.
>> >
>> > I hope to refine the bug report this weekend.
>> >
>>
>> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
>> That
>> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
>> will try again shortly to see if it's any better.
>
> Kevin,
>
>Make sure you have these options in your /etc/sysctl.conf :
>
> vfs.aio.max_buf_aio=8192
> vfs.aio.max_aio_queue_per_proc=65536
> vfs.aio.max_aio_per_proc=8192
> vfs.aio.max_aio_queue=65536
>
>...otherwise the guest I/O will random hang in VirtualBox. This issue
> was
> mitigated in a late 5.x VirtualBox by patching to not use AIO, but the
> issue
> came back in 6.x when that patch wasn't carried forward.
>
> -DG
> ___
> 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"
>


-- 
--
Daniel Dettlaff
Versatile Knowledge Systems
verknowsys.com
___
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: 13.0 RC4 might be delayed

[David G Lawrence via freebsd-current]

> On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
> wrote:
> 
> > On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > > ??? if people are having issues with ports like ???
> >
> > If I'm not mistaken:
> >
> > * 13.0-RC3 seems to be troublesome, as a guest machine, with
> > emulators/virtualbox-ose 6.1.18 as the host
> >
> > * no such trouble with 12.0-RELEASE-p5 as a guest.
> >
> > I hope to refine the bug report this weekend.
> >
> 
> Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. That
> was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
> will try again shortly to see if it's any better.

Kevin,

   Make sure you have these options in your /etc/sysctl.conf :

vfs.aio.max_buf_aio=8192
vfs.aio.max_aio_queue_per_proc=65536
vfs.aio.max_aio_per_proc=8192
vfs.aio.max_aio_queue=65536

   ...otherwise the guest I/O will random hang in VirtualBox. This issue was
mitigated in a late 5.x VirtualBox by patching to not use AIO, but the issue
came back in 6.x when that patch wasn't carried forward.

-DG
___
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"

VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

[Graham Perrin]

On 26/03/2021 21:55, Kevin Oberman wrote:
On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin > wrote:



If I'm not mistaken:

…

Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. 
That was right after 6.1.18 was put into ports. Fell back to legacy 
(v5) and will try again shortly to see if it's any better.


Windows 7 guest or host?

For me, Windows 10 20H2 guest is rock solid.

% pkg info -x virtualbox
virtualbox-ose-6.1.18
virtualbox-ose-kmod-6.1.18_1
% freebsd-version -kru
14.0-CURRENT
14.0-CURRENT
14.0-CURRENT
% uname -a
FreeBSD mowa219-gjp4-8570p 14.0-CURRENT FreeBSD 14.0-CURRENT #90 
main-n245648-66f138563be: Thu Mar 25 08:00:54 GMT 2021 
root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 
amd64

%

___
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: 13.0 RC4 might be delayed

[Kevin Oberman]

On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin 
wrote:

> On 26/03/2021 03:40, The Doctor via freebsd-current wrote:
> > … if people are having issues with ports like …
>
> If I'm not mistaken:
>
> * 13.0-RC3 seems to be troublesome, as a guest machine, with
> emulators/virtualbox-ose 6.1.18 as the host
>
> * no such trouble with 12.0-RELEASE-p5 as a guest.
>
> I hope to refine the bug report this weekend.
>

Had nothing but frequent guest lockups on 6.1.18 with my Win7 system. That
was right after 6.1.18 was put into ports. Fell back to legacy (v5) and
will try again shortly to see if it's any better.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"

12.2-RELEASE-p4 versus VirtualBox (was: 13.0 RC4 might be delayed)

[Graham Perrin]

On 26/03/2021 20:01, Graham Perrin wrote:

If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with 
emulators/virtualbox-ose 6.1.18 as the host


* no such trouble with 12.0-RELEASE-p5 as a guest.


On closer inspection: the problem is not limited 13.0-RC3.

If I save the state of a guest whilst 12.2-RELEASE-p3 runs:

* no problem after starting from the saved state.

If I upgrade to 12.2-RELEASE-p4, restart the guest then save the state, 
I can start from the saved state, however:


* no response to keyboard input

* ACPI shutdown does not begin a shutdown routine.

___
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: 13.0 RC4 might be delayed

[Graham Perrin]

On 26/03/2021 03:40, The Doctor via freebsd-current wrote:

… if people are having issues with ports like …


If I'm not mistaken:

* 13.0-RC3 seems to be troublesome, as a guest machine, with 
emulators/virtualbox-ose 6.1.18 as the host


* no such trouble with 12.0-RELEASE-p5 as a guest.

I hope to refine the bug report this weekend.

___
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: 13.0 RC4 might be delayed

[Michael Gmelin]

> On 26. Mar 2021, at 04:30, Scott Long  wrote:
> 
> Hi everyone,
> 
> Speaking on behalf of Core, i wanted to let you know that 13.0 RC4 might be 
> delayed.  Glen has an emergency to attend to, and might be unavailable or 
> slow to respond for a few more days.

Fingers crossed, whatever it may be.

Best,
Michael


___
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: 13.0 RC4 might be delayed

[The Doctor via freebsd-current]

On Thu, Mar 25, 2021 at 09:29:27PM -0600, Scott Long wrote:
> Hi everyone,
> 
> Speaking on behalf of Core, i wanted to let you know that 13.0 RC4 might be 
> delayed.  Glen has an emergency to attend to, and might be unavailable or 
> slow to respond for a few more days.  You???re still encouraged to email re@ 
> with requests and questions.  Anything urgent can be directed to core@ if 
> necessary.
>

HJust wondering if people are having issues with ports like VLC

or Web Browsers?

> Thanks,
> Scott
> ___
> 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"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b  
Without discipline, there's no life at all.  -Katharine Hepburn
___
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"

13.0 RC4 might be delayed

[Scott Long]

Hi everyone,

Speaking on behalf of Core, i wanted to let you know that 13.0 RC4 might be 
delayed.  Glen has an emergency to attend to, and might be unavailable or slow 
to respond for a few more days.  You’re still encouraged to email re@ with 
requests and questions.  Anything urgent can be directed to core@ if necessary.

Thanks,
Scott
___
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"