VIOMB(4) BSD Kernel Interfaces Manual VIOMB(4)NAME
viomb -- VirtIO memory ballooning driver
SYNOPSIS
virtio* at pci? dev ? function ?
viomb* at virtio?
DESCRIPTION virtio(4) defines an interface for efficient, standard, and extensible I/O between the hypervisor and the virtual machine. The viomb driver
supports the virtio-compliant memory ballooning device.
Memory ballooning works as follows:
1. The host operator requests a guest to return some amount of memory to the host (via e.g. Qemu monitor balloon command).
2. The hypervisor sends the request via VirtIO memory ballooning device.
3. The guest viomb driver requests allocation of that amount of physical memory from the NetBSD memory management system.
4. The viomb device tells the hypervisor the guest physical memory address of the allocated memory via VirtIO memory ballooning device.
The sysctl node hw.viomb.npages shows the requested number of memory pages to return to the hypervisor, while hw.viomb.actual shows the
actual number of memory pages that are already returned to the hypervisor.
SEE ALSO virtio(4), sysctl(8)
Rusty Russell, IBM Corporation, Virtio PCI Card Specification, http://ozlabs.org/~rusty/virtio-spec/.
HISTORY
The viomb device driver appeared in NetBSD 6.0.
BUGS
The userland interface should be same as the Xen ballooning device.
BSD November 26, 2011 BSD
Check Out this Related Man Page
VIRTIO_BLK(4) BSD Kernel Interfaces Manual VIRTIO_BLK(4)NAME
virtio_blk -- VirtIO Block driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device virtio_blk
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
virtio_blk_load="YES"
DESCRIPTION
The virtio_blk device driver provides support for VirtIO block devices.
LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5).
hw.vtblk.no_ident
hw.vtblk.X.no_ident
These tunables disable retrieving the device identification string from the hypervisor either globally or per-device. The default
value is 0.
hw.vtblk.writecache_mode
hw.vtblk.X.writecache_mode
These tunables determine the write cache mode globally or per-device. The mode can changed only if the ConfigWCE feature is negoti-
ated. Set to 0 for writethrough mode, 1 for writeback mode, and -1 to leave it as-is. The default value is to leave as-is.
SYSCTL VARIABLES
The following variables are available as sysctl(8) variables.
dev.vtblk.X.writecache_mode
The write cache mode of the device can be either writethrough (0) or writeback (1). If the ConfigWCE feature is negotiated, the
write cache mode can be toggled between writethrough and writeback.
SEE ALSO virtio(4)HISTORY
The virtio_blk driver was written by Bryan Venteicher <bryanv@FreeBSD.org>. It first appeared in FreeBSD 9.0.
BSD July 2, 2013 BSD
There is problem in my system whenever i run a command lsattr -El mem0 it shows 3gb memory and when i run lscfg -vp | grep Size it shows 8 modules of 512 mb. it means it shows 4 gb how is it possible. (1 Reply)
Hi all,
I have a HP-UX Server with 4 gigabytes of physical RAM. When I use the 'Glance' utility to see what my memory utilization is, my memory usage shows up maxed out at 99%. I shut off all the known processes that I'm running on that box and the memory utilization is still at 78% (with Swap... (1 Reply)
Hi All,
I have linux installed on my PC and windows runs on it as a guest OS thru VMplayer. The hard drive space which was originally allocated for guest OS is around 15GB. Please let me know how do I change it to 20GB. I have more than 30 GB of free space available on my hard drive.
Thanks... (2 Replies)
Hi,
I am having memory problem. Whenever i run the Tivoli backup command from CLI "dsmc" my memory use is very high.
Topas shows the following output
Memory
Real, MB 35584
%Comp 17
%Noncomp 80.1
%Client 80.1
and "svmon" shows
Paging space has not been used
size ... (8 Replies)
Hi,
monitor memory usage on AIX machine on any day of the week from 3:00 PM ET to 5:00 PM ET -
Povide min and max memory consumption.
Determine if all of the available memory is visible to the operating system. If it is not, determine the amount of memory which may be allocated to the... (3 Replies)
I have a host os Windows 7 ultimate in place where virtual box is installed.
Now in virtual box I have installed solaris 10.
There is internet connection present in host windows 7 still I am not able to access internet in solaris 10.
Please help to configure solaris so that internet can be... (12 Replies)
IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Hi,
I upgraded the physical memory on my RHEL5 server (BL460cG7) from 32G to 128G. When I rebooted the box I can see from the "hpasmcli" that the 128G memory has installed correctly.
However when I run a "free" command I can only see 64G of physical RAM? Is there a restriction on the max... (2 Replies)
Greetings,
i'm wondering if there is a way to determine minimum memory requirement for AIX kernel and OS functions? We use memdetails script from perfpmr package to see actual memory allocation, for example like this:
===========================================================================... (5 Replies)
I can't check actual memory usage in the Redhat 5.5...
The used memory is 14214 Mb of Total 15919 by Free -m command.
I sum the RSS value on PS aux command result and the value is 5428.66Mb.
Yes It's quite different actual usage memory and RSS value.
So I added Shared memory value... (5 Replies)
It seems that multi queue virtio functionality is enabled in the Redhat System being used, but I need to confirm if this functionality is working appropriately:
cat /usr/include/linux/virtio_net.hstruct virtio_net_config
{ /* The config defining mac address (if VIRTIO_NET_F_MAC) */ __u8 mac;... (2 Replies)
I have a guest LDOM running Solaris 10U11 on a Sun T4-1 host running Solaris 11.4. The host has a disk named bkpool that I'd like to share with the LDOM so both can read and write it. The host is hemlock, the guest is sol10.
root@hemlock:~# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (3 Replies)