Date: Tue, 07 May 2019 19:50:40 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 231117] bhyve: I/O lockups inside guests Message-ID: <bug-231117-27103-HBVx1OJvfN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231117-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-231117-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231117 --- Comment #23 from Rodney W. Grimes <rgrimes@FreeBSD.org> --- (In reply to Mateusz Kwiatkowski from comment #22) > VMs may use 8GBs of RAM in total. Hypervisor has 64GB in total. So VMs an= d ARC could create OOM condition but the statistics I provided were taken a= t themoment when one of the VMs hang. I'll reduce arc_max anyway to 8GB to = make sure this isn't the cause. Not sure you need to cut arc_max to 8GB, but just make sure that arc_max + total(all VM's) + host usage is < than 64GB. I have been pointed at: If the guest(s) are using virtio-block, it might be interesting to check the status of the IO queues for those devices. The reported issues could be a case of https://smartos.org/bugview/OS-7613. (Posted as https://reviews.freebsd.org/D19501) I have pinged the D19501 review and it looks like some forward motion has happened there. You *may* if you can want to try the patch that is there n= ow, knowing that it is about to be revised. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231117-27103-HBVx1OJvfN>