We are trying to understand the memory allocation and usage for a KVM guest
using the libvirt java API version 0.5.0. A certain memoryStats(int) on the
Domain class allows you to fetch MemoryStatistic values.
Each of this statistic has a tag and a value. In our case, the values
returned were
[tag:
Changes from v1:
Switch over from implicit slave device path, i.e. guessing
from that the slave is '/dev/nmdm0B', to
explicit master and slave device specification using
.
Roman Bogorodskiy (1):
bhyve: add console support through nmdm device
src/bhyve/bhyve_command.c| 34 +
nmdm is a FreeBSD driver which allows to create a pair of tty
devices one of which is passed to the guest and second is used
by the client.
This patch adds new 'nmdm' character device type. Its definition
looks this way:
Master is passed to the hypervisior and slave is used for client
conne
We use virBhyveTapGetRealDeviceName() to map network interface name
to a real device path, trying to open possible devices and getting
names by ioctl.
Make it skip devices that fail to open with EBUSY because they're
most likely already used by other VMs.
---
src/bhyve/bhyve_command.c | 2 ++
1 f
From: David Shane Holden
Signed-off-by: Roman Bogorodskiy
---
src/bhyve/bhyve_driver.c | 135 ++-
src/bhyve/bhyve_utils.h | 5 ++
2 files changed, 139 insertions(+), 1 deletion(-)
diff --git a/src/bhyve/bhyve_driver.c b/src/bhyve/bhyve_driver.c
in
Re-submit patch provided by David back in February when bhyve driver was not
in the tree. I did some changes to the patch on the way:
- rebase to the current master
- add ACL checks
- use bhyveDomObjFromDomain() instead of custom virDomainObjListFindByUUID()
- fix problems reported by 'syntax-
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package installed in the
system. Currently, APIs defined in src/ don't know whether libvirtd
is being run from the build dir or the installed dir. The following
additions provide the fu
Michal Privoznik wrote:
> If this fails, we should kill the domain and return an error. It won't happen
> currently, as ret is equal to zero in this area of code (it's not visible in
> the context, but this whole block starts with 'if (ret == 0) {'). Moreover,
> the same bug is present a few
