{"id":1395,"date":"2011-05-30T13:58:03","date_gmt":"2011-05-30T11:58:03","guid":{"rendered":"http:\/\/blog.unelink.es\/?p=1395"},"modified":"2019-05-16T10:44:44","modified_gmt":"2019-05-16T08:44:44","slug":"ver-lista-de-maquinas-virtuales-en-openvz-con-vzlist","status":"publish","type":"post","link":"https:\/\/hosting.airetech.es\/blog\/wiki\/ver-lista-de-maquinas-virtuales-en-openvz-con-vzlist\/","title":{"rendered":"Ver lista de m\u00e1quinas virtuales en OpenVZ con vzlist"},"content":{"rendered":"

En OpenVZ tenemos un comando muy \u00fatil para poder ver toda la informaci\u00f3n de un servidor virtual en tiempo real, si se sabe utilizar correctamente, podemos ver la mayor\u00eda de propiedades c\u00f3mo: ips, hostname, ctid, load average, etc.<\/p>\n

Si ponemos vzlist en nuestra linea de comandos sin ning\u00fan par\u00e1metro nos salen los fundamentales, ctid, numero de procesos, estado, ip principal y hostname.<\/p>\n

CTID\u00a0\u00a0\u00a0\u00a0\u00a0 NPROC STATUS\u00a0\u00a0\u00a0 IP_ADDR\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 HOSTNAME\r\n105\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 47 running\u00a0\u00a0 XX.XXX.XXX.XXX \u00a0\u00a0 test\r\n338\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 55 running\u00a0\u00a0 XXX.XXX.XXX.XX\u00a0\u00a0\u00a0 prueba<\/pre>\n
Ahora para mostrar solo las columnas que nos interesan vamos a utilizar el parametro \"-o\", por ejemplo queremos mostrar en nuestra lista el ctid, el estado y el load average de cada m\u00e1quina.<\/p>\n
vzlist -o ctid,status,laverage\r\n\r\nNos dar\u00e1 como resultado:\r\n\r\nCTID STATUS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LAVERAGE\r\n105 running\u00a0\u00a0 0.00\/0.00\/0.00\r\n338 running\u00a0\u00a0 0.00\/0.00\/0.00\r\n585 running\u00a0\u00a0 0.04\/0.04\/0.01\r\n10556 running\u00a0\u00a0 0.01\/0.08\/0.08\r\n20710 running\u00a0\u00a0 0.00\/0.00\/0.00\r\n380225 running\u00a0\u00a0 0.00\/0.00\/0.00<\/pre>\n
Aqu\u00ed teneis una lista de todas las posibles columnas que podeis utilizar extra\u00eddo de http:\/\/www.linuxcertif.com\/man\/8\/vzlist\/<\/a><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n
Parameter<\/p>\n<\/td>\n
\n
Possible Specifiers<\/p>\n<\/td>\n
\n
Output Column<\/p>\n<\/td>\n
\n
Description<\/p>\n<\/td>\n<\/tr>\n
\n
ctid<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
CTID<\/code><\/p>\n<\/td>\n
\n
The Container ID.<\/p>\n<\/td>\n<\/tr>\n
\n
hostname<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
HOSTNAME<\/code><\/p>\n<\/td>\n
\n
The Container hostname.<\/p>\n<\/td>\n<\/tr>\n
\n
ip<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
IP_ADDR<\/code><\/p>\n<\/td>\n
\n
The Container IP address.<\/p>\n<\/td>\n<\/tr>\n
\n
status<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
STATUS<\/code><\/p>\n<\/td>\n
\n
Specifies whether the Container is running or stopped.<\/p>\n<\/td>\n<\/tr>\n
\n
tm<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
TM<\/code><\/p>\n<\/td>\n
\n
Specifies the type of the OS template your Container is based on:<\/p>\n
    \n
  • ST<\/code> indicates that the Container is based on a standard OS template;<\/li>\n
  • EZ<\/code> indicates that the Container is based on an EZ OS template.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
\n
ostemplate<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
OSTEMPLATE<\/code><\/p>\n<\/td>\n
\n
Specifies the name of the OS template your Container is based on ( e.g. redhat-el5-x86<\/code>).<\/p>\n<\/td>\n<\/tr>\n
\n
kmemsize<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
KMEMSIZE<\/code><\/p>\n<\/td>\n
\n
The size of unswappable kernel memory (in bytes), allocated for internal kernel structures of the processes of a particular Container. Typical amounts of kernel memory are 16\u202650 Kb per process.<\/p>\n<\/td>\n<\/tr>\n
\n
lockedpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
LOCKEDP<\/code><\/p>\n<\/td>\n
\n
The amount of memory not allowed to be swapped out (locked with the mlock()<\/code> system call), in 4-Kb pages.<\/p>\n<\/td>\n<\/tr>\n
\n
privvmpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
PRIVVMP<\/code><\/p>\n<\/td>\n
\n
The size in 4 Kb pages of private (or potentially private) memory, allocated by Container applications. Memory that is always shared among different applications is not included in this resource parameter.<\/p>\n<\/td>\n<\/tr>\n
\n
shmpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
SHMP<\/code><\/p>\n<\/td>\n
\n
The total size of shared memory (including IPC, shared anonymous mappings and tmpfs<\/code> objects), allocated by processes of a particular Container, in 4 Kb pages.<\/p>\n<\/td>\n<\/tr>\n
\n
numproc<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NPROC<\/code><\/p>\n<\/td>\n
\n
The number of processes and threads allowed.<\/p>\n<\/td>\n<\/tr>\n
\n
physpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
PHYSP<\/code><\/p>\n<\/td>\n
\n
The total size of RAM used by processes. This is accounting-only parameter currently. It shows the usage of RAM by the Container. For memory pages used by several different Containers (mappings of shared libraries, for example), only a fraction of a page is charged to each Container. The sum of the physpages<\/code> usage for all Containers corresponds to the total number of pages used in the system by all accounted users.<\/p>\n<\/td>\n<\/tr>\n
\n
vmguarpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
VMGUARP<\/code><\/p>\n<\/td>\n
\n
The memory allocation guarantee, in pages (one page is 4 Kb). Applications are guaranteed to be able to allocate memory while the amount of memory accounted as privvmpages<\/code> does not exceed the configured barrier of the vmguarpages<\/code> parameter. Above the barrier, memory allocation may fail in case of overall memory shortage.<\/p>\n<\/td>\n<\/tr>\n
\n
oomguarpages<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
OOMGUARP<\/code><\/p>\n<\/td>\n
\n
The out-of-memory guarantee, in 4 Kb pages. Any Container process will not be killed even in case of heavy memory shortage if the current memory consumption (including both physical memory and swap) does not reach the oomguarpages<\/code> barrier.<\/p>\n<\/td>\n<\/tr>\n
\n
numtcpsock<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NTCPSOCK<\/code><\/p>\n<\/td>\n
\n
The number of TCP sockets (PF_INET<\/code> family, SOCK_STREAM<\/code> type). This parameter limits the number of TCP connections and, thus, the number of clients the server application can handle in parallel.<\/p>\n<\/td>\n<\/tr>\n
\n
numflock<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NFLOCK<\/code><\/p>\n<\/td>\n
\n
The number of file locks created by all Container processes.<\/p>\n<\/td>\n<\/tr>\n
\n
numpty<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NPTY<\/code><\/p>\n<\/td>\n
\n
The number of pseudo-terminals. For example, ssh<\/code> session, screen<\/code>, xterm<\/code> application consumes pseudo-terminal resource.<\/p>\n<\/td>\n<\/tr>\n
\n
numsiginfo<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NSIGINFO<\/code><\/p>\n<\/td>\n
\n
The number of siginfo<\/code> structures (essentially this parameter limits size of signal delivery queue).<\/p>\n<\/td>\n<\/tr>\n
\n
tcpsndbuf<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
TCPSNDB<\/code><\/p>\n<\/td>\n
\n
The total size (in bytes) of send buffers for TCP sockets \u2013 amount of kernel memory allocated for data sent from an application to a TCP socket, but not acknowledged by the remote side yet.<\/p>\n<\/td>\n<\/tr>\n
\n
tcprcvbuf<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
TCPRCVB<\/code><\/p>\n<\/td>\n
\n
The total size (in bytes) of receive buffers for TCP sockets. Amount of kernel memory received from the remote side but not read by the local application yet.<\/p>\n<\/td>\n<\/tr>\n
\n
othersockb<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
OTHSOCKB<\/code><\/p>\n<\/td>\n
\n
The total size in bytes of UNIX-domain socket buffers, UDP and other datagram protocol send buffers.<\/p>\n<\/td>\n<\/tr>\n
\n
dgramrcvbuf<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
DGRAMRCVB<\/code><\/p>\n<\/td>\n
\n
The total size in bytes of receive buffers of UDP and other datagram protocols.<\/p>\n<\/td>\n<\/tr>\n
\n
nothersock<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NOTHSOCK<\/code><\/p>\n<\/td>\n
\n
The number of socket other than TCP. Local (UNIX-domain) sockets are used for communications inside the system. UDP sockets are used for Domain Name Service (DNS) queries, for example.<\/p>\n<\/td>\n<\/tr>\n
\n
dcachesize<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
DCACHESIZE<\/code><\/p>\n<\/td>\n
\n
The total size in bytes of dentry<\/code> and inode<\/code> structures locked in memory. Exists  as a  separate parameter to impose a limit causing file operations to sense  memory  shortage  and return  an  error  to  applications, protecting from excessive consumption of memory due to intensive file system operations.<\/p>\n<\/td>\n<\/tr>\n
\n
numfile<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NFILE<\/code><\/p>\n<\/td>\n
\n
The number of files opened by all Container processes.<\/p>\n<\/td>\n<\/tr>\n
\n
numiptent<\/code><\/p>\n<\/td>\n
\n
.m, .b,<\/code><\/p>\n
.l, .f<\/code><\/p>\n<\/td>\n
\n
NIPTENT<\/code><\/p>\n<\/td>\n
\n
The number of IP packet filtering entries.<\/p>\n<\/td>\n<\/tr>\n
\n
diskspace<\/code><\/p>\n<\/td>\n
\n
.s, .h<\/code><\/p>\n<\/td>\n
\n
DQBLOCKS<\/code><\/p>\n<\/td>\n
\n
The total size of disk space consumed by the Container, in 1 Kb blocks. When the space used by a Container hits the barrier, the Container can allocate additional disk space up to the limit during grace period.<\/p>\n<\/td>\n<\/tr>\n
\n
diskinodes<\/code><\/p>\n<\/td>\n
\n
.s, .h<\/code><\/p>\n<\/td>\n
\n
DQINODES<\/code><\/p>\n<\/td>\n
\n
The total number of disk inodes (files, directories, symbolic links) a Container can allocate. When the number of inodes used by a Container hits the barrier, the Container can create additional file entries up to the limit during grace period.<\/p>\n<\/td>\n<\/tr>\n
\n
laverage<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
LAVERAGE<\/code><\/p>\n<\/td>\n
\n
The average number of processes ready to run during the last 1, 5 and 15 minutes.<\/p>\n<\/td>\n<\/tr>\n
\n
cpulimit<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
CPULIM<\/code><\/p>\n<\/td>\n
\n
This is a positive number indicating the CPU time in per cent the corresponding Container is not allowed to exceed.<\/p>\n<\/td>\n<\/tr>\n
\n
cpuunits<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
CPUUNI<\/code><\/p>\n<\/td>\n
\n
Allowed CPU power. This is a positive integer number, which determines the minimal guaranteed share of the CPU the Container will receive. You may estimate this share as ((Container CPUUNITS)\/(Sum of CPU UNITS across all busy Containers))*100%. The total CPU power depends on CPU and Virtuozzo reporting tools consider one 1\u00a0GHz PIII Intel processor to be equivalent to 50,000 CPU units.<\/p>\n<\/td>\n<\/tr>\n
\n
slmmode<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
SLMMOD<\/code><\/p>\n<\/td>\n
\n
The SLM mode defining the behaviour of the SLM and UBC parameters in respect of the given Container. It can be one of the following:<\/p>\n
    \n
  • ubc<\/code>: the SLM mode is disabled, which means that the slmmemorylimit<\/code> parameter is not supported and you can use only the UBC parameters to control the amount of memory which can be consumed by the Container.<\/li>\n
  • slm<\/code>: the SLM mode is enabled, which means that the slmmemorylimit<\/code> parameter is supported and can be used to manage the amount of memory which can be consumed by the Container.<\/li>\n
  • all<\/code>: both the slmmemorylimit<\/code> and UBC parameters are supported and can be used to manage the amount of memory which can be consumed by the Container.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
\n
slminst<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
SLMINST<\/code><\/p>\n<\/td>\n
\n
The instant memory usage limit set for the Container, in 4 KB pages.<\/p>\n<\/td>\n<\/tr>\n
\n
slmavg<\/code><\/p>\n<\/td>\n
\n
none<\/p>\n<\/td>\n
\n
SLMAVG<\/code><\/p>\n<\/td>\n
\n
The average memory usage limit set for the Container, in 4 KB pages.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"En OpenVZ tenemos un comando muy \u00fatil para poder ver toda la informaci\u00f3n de un servidor virtual en tiempo real, si se sabe utilizar correctamente, podemos ver la mayor\u00eda de propiedades c\u00f3mo: ips, hostname, ctid, load average, etc. Si ponemos vzlist en nuestra linea de comandos sin ning\u00fan par\u00e1metro nos salen los fundamentales, ctid, numero de procesos, estado, ip principal Seguir leyendo<\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[349,11,6],"tags":[],"class_list":["post-1395","post","type-post","status-publish","format-standard","hentry","category-ssh","category-virtualizacion","category-wiki","cat-349-id","cat-11-id","cat-6-id"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/posts\/1395","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/comments?post=1395"}],"version-history":[{"count":13,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/posts\/1395\/revisions"}],"predecessor-version":[{"id":8404,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/posts\/1395\/revisions\/8404"}],"wp:attachment":[{"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/media?parent=1395"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/categories?post=1395"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hosting.airetech.es\/blog\/wp-json\/wp\/v2\/tags?post=1395"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}