Is there any possibilities to limit disk IO for virtualization guest on
FreeBSD?
I would like to know, if it is possible to limit IOps for jails, or
Bhyve guest, or VirtualBox quests. There are ways to limit CPU or RAM
for them, but CPU and RAM are really huge these days. On the other hand,
On Thu, May 8, 2014 at 5:57 PM, Miroslav Lachman 000.f...@quip.cz wrote:
Is there any possibilities to limit disk IO for virtualization guest on
FreeBSD?
I would like to know, if it is possible to limit IOps for jails, or Bhyve
guest, or VirtualBox quests. There are ways to limit CPU or RAM
On Wednesday, May 07, 2014 7:15:43 pm John Nielsen wrote:
I am trying to solve a problem with amd64 FreeBSD virtual machines running on
a Linux+KVM hypervisor. To be honest I'm not sure if the problem is in
FreeBSD or
the hypervisor, but I'm trying to rule out the OS first.
The _second_
On May 8, 2014, at 11:03 AM, John Baldwin j...@freebsd.org wrote:
On Wednesday, May 07, 2014 7:15:43 pm John Nielsen wrote:
I am trying to solve a problem with amd64 FreeBSD virtual machines running
on a Linux+KVM hypervisor. To be honest I'm not sure if the problem is in
FreeBSD or
the
When I was doing some early work on some of the Octeon multi-core chips, I
encountered something similar. If I remember correctly, there was an issue in
the shutdown sequence that did not properly halt the cores and set up the
start jump vector. So the first core would start, and when it tried
Andreas Nilsson wrote:
On Thu, May 8, 2014 at 5:57 PM, Miroslav Lachman 000.f...@quip.cz
mailto:000.f...@quip.cz wrote:
Is there any possibilities to limit disk IO for virtualization guest
on FreeBSD?
I would like to know, if it is possible to limit IOps for jails, or
Bhyve
