Date: Fri, 10 May 2019 08:54:10 +0100 From: Jonathan Rowley <jonathans.email@icloud.com> To: freebsd-virtualization@freebsd.org Subject: Unsubscribe Message-ID: <8520A110-26D2-4F0C-B81B-F1D984A8C906@icloud.com>
next in thread | raw e-mail | index | archive | help
> On 9 May 2019, at 13:00, freebsd-virtualization-request@freebsd.org wrote:= >=20 > Send freebsd-virtualization mailing list submissions to > freebsd-virtualization@freebsd.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > or, via email, send a message with subject or body 'help' to > freebsd-virtualization-request@freebsd.org >=20 > You can reach the person managing the list at > freebsd-virtualization-owner@freebsd.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-virtualization digest..." >=20 >=20 > Today's Topics: >=20 > 1. [Bug 237636] bhyve guest ZFS filesystem freezes in > zcw->zcw_cv state (bugzilla-noreply@freebsd.org) > 2. [maybe OT] Strange behaviour when connecting to serial port > of a FreeBSD inside a VM (Joachim Durchholz) > 3. [Bug 231117] bhyve: I/O lockups inside guests > (bugzilla-noreply@freebsd.org) > 4. [Bug 231117] bhyve: I/O lockups inside guests > (bugzilla-noreply@freebsd.org) >=20 >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Thu, 09 May 2019 01:53:57 +0000 > From: bugzilla-noreply@freebsd.org > To: virtualization@FreeBSD.org > Subject: [Bug 237636] bhyve guest ZFS filesystem freezes in > zcw->zcw_cv state > Message-ID: > <bug-237636-27103-uuAaoXGoqC@https.bugs.freebsd.org/bugzilla/> > Content-Type: text/plain; charset=3D"UTF-8" >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237636 >=20 > Mark Linimon <linimon@FreeBSD.org> changed: >=20 > What |Removed |Added > --------------------------------------------------------------------------= -- > Assignee|bugs@FreeBSD.org |virtualization@FreeBSD.org= >=20 > --=20 > You are receiving this mail because: > You are the assignee for the bug. >=20 > ------------------------------ >=20 > Message: 2 > Date: Thu, 9 May 2019 08:52:42 +0200 > From: Joachim Durchholz <jo@durchholz.org> > To: freebsd-virtualization@freebsd.org > Subject: [maybe OT] Strange behaviour when connecting to serial port > of a FreeBSD inside a VM > Message-ID: <2c875da4-741b-3601-dd38-b191450497d7@durchholz.org> > Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed >=20 > Sorry if this off-topic, please direct me to the correct list. >=20 > I have FreeBSD running inside a VirtualBox VM, and while FreeBSD boots=20 > and works fine and I could successfully hook up a host's domain socket,=20= > I don't see output on the socket. > SOMETHING is working: Some boot messages are redirected, though to a=20 > place that I do not see. >=20 > I have a shell script that recreates the entire situation from scratch,=20= > I can describe everything in excruciating detail - where do I start? >=20 > Regards, > Jo >=20 >=20 > ------------------------------ >=20 > Message: 3 > Date: Thu, 09 May 2019 07:31:01 +0000 > From: bugzilla-noreply@freebsd.org > To: virtualization@FreeBSD.org > Subject: [Bug 231117] bhyve: I/O lockups inside guests > Message-ID: > <bug-231117-27103-uQWDRhbVjX@https.bugs.freebsd.org/bugzilla/> > Content-Type: text/plain; charset=3D"UTF-8" >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231117 >=20 > --- Comment #24 from Mateusz Kwiatkowski <kwiat3k@panic.pl> --- > (In reply to Rodney W. Grimes from comment #23) >=20 > Rodney, many thanks for your engagement in this matter. It seems that you w= ere > right suspecting that arc_max is the culprit. After reducing its size virt= ual > machines are working stable for over a day. So, instead of stability issue= this > was more like user experience issue. As you see we both were tricked by to= p(1) > output which looked fine and didn't indicate problem. Is it possible to ha= ve a > notice printed in dmesg that happens (as we have for other kernel limits)?= >=20 > --=20 > You are receiving this mail because: > You are the assignee for the bug. >=20 > ------------------------------ >=20 > Message: 4 > Date: Thu, 09 May 2019 09:58:01 +0000 > From: bugzilla-noreply@freebsd.org > To: virtualization@FreeBSD.org > Subject: [Bug 231117] bhyve: I/O lockups inside guests > Message-ID: > <bug-231117-27103-mkuJ13R4sx@https.bugs.freebsd.org/bugzilla/> > Content-Type: text/plain; charset=3D"UTF-8" >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231117 >=20 > --- Comment #25 from Mateusz Kwiatkowski <kwiat3k@panic.pl> --- > (In reply to Mateusz Kwiatkowski from comment #24) > I'm afraid I celebrated too soon. I/O in VM locked up - it just took more t= ime. >=20 > Memory stats: > Mem: 3846M Active, 4806M Inact, 26G Wired, 27G Free > ARC: 7755M Total, 2419M MFU, 4208M MRU, 14M Anon, 478M Header, 635M Other > 6145M Compressed, 10G Uncompressed, 1.68:1 Ratio=20 >=20 > I'll now test patch with virtio barriers. >=20 > --=20 > You are receiving this mail because: > You are the assignee for the bug. >=20 > ------------------------------ >=20 > Subject: Digest Footer >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freeb= sd.org" >=20 >=20 > ------------------------------ >=20 > End of freebsd-virtualization Digest, Vol 441, Issue 4 > ******************************************************
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8520A110-26D2-4F0C-B81B-F1D984A8C906>