Diferencias

Muestra las diferencias entre dos versiones de la página.

--- unattended_installations:proxmox [2015/02/25 23:29] – creado jdzant
+++ unattended_installations:proxmox [2022/11/02 17:58] (actual) – editor externo 127.0.0.1
@@ Línea 1: / Línea 1: @@
-Introduction
+ Introduction
-This page lists the important Proxmox VE and Debian command line tools. All CLI tools have also manual pages.
-KVM specific
+This page lists the important Proxmox VE and Debian command line tools. All CLI tools have also manual pages.
-qm
+KVM specific
-qm - qemu/kvm manager - see Manual: qm and Qm manual
+qm
-OpenVZ specific
-vzps
+qm - qemu/kvm manager - see Manual: qm and Qm manual
-This utility program can be run on the Node just as the standard Linux ps. For information on the ps utility please consult the corresponding man page, vzps provides certain additional functionality related to monitoring separate Containers running on the Node.
+OpenVZ specific
-The vzps utility has the following functionality added:
+vzps
-•	The -E CT_ID command line switch can be used to show only the processes running inside the Container with the specified ID.
-pvectl
+This utility program can be run on the Node just as the standard Linux ps. For information on the ps utility please consult the corresponding man page, vzps provides certain additional functionality related to monitoring separate Containers running on the Node.
-pvectl - vzctl wrapper to manage OpenVZ containers - see Pvectl manual
-vzctl
+The vzps utility has the following functionality added:
-vzctl - utility to control an OpenVZ container - see Vzctl manual
-vztop
+    The -E CT_ID command line switch can be used to show only the processes running inside the Container with the specified ID.
-This utility program can be run on the Node just as the standard Linux top . For information on the top utility please consult the corresponding man page, vztop provides certain additional functionality related to monitoring separate Containers running on the Node.
-The vztop utility has the following functionality added:
+pvectl
-•	The -E CT_ID command line switch can be used to show only the processes running inside the Container with the ID specified. If -1 is specified as CT_ID, the processes of all running Containers are displayed.
-•	The e interactive command (the key pressed while top is running) can be used to show/hide the CTID column, which displays the Container where a particular process is running (0 stands for the Hardware Node itself).
+pvectl - vzctl wrapper to manage OpenVZ containers - see Pvectl manual
-•	The E interactive command can be used to select another Container the processes of which are to be shown. If -1 is specified, the processes of all running Containers are displayed.
+vzctl
-vztop - display top CPU processes
+vzctl - utility to control an OpenVZ container - see Vzctl manual
+vztop
+This utility program can be run on the Node just as the standard Linux top . For information on the top utility please consult the corresponding man page, vztop provides certain additional functionality related to monitoring separate Containers running on the Node.
+The vztop utility has the following functionality added:
+    The -E CT_ID command line switch can be used to show only the processes running inside the Container with the ID specified. If -1 is specified as CT_ID, the processes of all running Containers are displayed.
+    The e interactive command (the key pressed while top is running) can be used to show/hide the CTID column, which displays the Container where a particular process is running (0 stands for the Hardware Node itself).
+    The E interactive command can be used to select another Container the processes of which are to be shown. If -1 is specified, the processes of all running Containers are displayed.
+vztop - display top CPU processes
 :28:52  up 31 days, 11:18,  1 user,  load average: 0.07, 0.06, 0.02
 processes: 196 sleeping, 1 running, 0 zombie, 0 stopped
@@ Línea 51: / Línea 64: @@
 ..
 ..
-user_beancounters
-cat /proc/user_beancounters
+user_beancounters
+cat /proc/user_beancounters
 Version: 2.5
@@ Línea 105: / Línea 121: @@
             numiptent                      20                   20  9223372036854775807  9223372036854775807                    0
 vzlist
-example:
+    example:
 vzlist
       CTID      NPROC STATUS    IP_ADDR         HOSTNAME
@@ Línea 112: / Línea 130: @@
         121 running   10.100.100.18   mediawiki.fantinibakery.com
          49 running   -               fbc14.fantinibakery.com
-From PVE 3.0 onwards, the display will be:
+From PVE 3.0 onwards, the display will be:
 vzlist
       CTID      NPROC STATUS    IP_ADDR         HOSTNAME
@@ Línea 118: / Línea 138: @@
         121 running   10.100.100.18   mediawiki
          49 running   -               fbc14
-•	The fields for (-o option) selective display are: ctid, nproc, status, ip, hostname.
-•	All are case sensitive and are used with the options -H (no header) and -o [field1, field2, ...]
+    The fields for (-o option) selective display are: ctid, nproc, status, ip, hostname.
-•	The binary is at: /usr/sbin/vzlist
+    All are case sensitive and are used with the options -H (no header) and -o [field1, field2, ...]
-•	by default, vzlist lists only RUNNING CTs, stopped ones won't appear in its output (qm list for VMs, instead, lists also stopped ones)
+    The binary is at: /usr/sbin/vzlist
-USAGE
+    by default, vzlist lists only RUNNING CTs, stopped ones won't appear in its output (qm list for VMs, instead, lists also stopped ones)
+USAGE
 Usage: vzlist [-a | -S] [-n] [-H] [-o field[,field...] | -1] [-s [-]field]
         [-h pattern] [-N pattern] [-d pattern] [CTID [CTID ...]]
@@ Línea 142: / Línea 165: @@
  -d, --description filter CTs by description pattern
  -L, --list   get possible field names
-Backup
-vzdump
-vzdump - backup utility for virtual machine - see Vzdump manual
-vzrestore
-vzrestore - restore OpenVZ vzdump backups - see Vzrestore manual
-qmrestore
-qmrestore - restore KVM vzdump backups - see Qmrestore manual
-Cluster management
-pveca
-PVE Cluster Administration Toolkit
-USAGE
-•	pveca -l # show cluster status
-•	pveca -c # create new cluster with localhost as master
-•	pveca -s [-h IP] # sync cluster configuration from master (or IP)
-•	pveca -d ID # delete a node
-•	pveca -a [-h IP] # add new node to cluster
-•	pveca -m # force local node to become master
-•	pveca -i # print node info (CID NAME IP ROLE)
-Software version check
-pveversion
-Proxmox VE version info - Print version information for Proxmox VE packages.
-USAGE
-pveversion [--verbose]
-•	without any argument shows the version of pve-manager, something like:
-pve-manager/1.5/4660
-or
-pve-manager/3.0/957f0862
-•	with -v argument it shows a list of programs versions related to pve, like:
-pve-manager: 1.5-7 (pve-manager/1.5/4660)
-running kernel: 2.6.18-2-pve
-proxmox-ve-2.6.18: 1.5-5
-pve-kernel-2.6.18-2-pve: 2.6.18-5
-pve-kernel-2.6.18-1-pve: 2.6.18-4
-qemu-server: 1.1-11
-pve-firmware: 1.0-3
-libpve-storage-perl: 1.0-10
-vncterm: 0.9-2
-vzctl: 3.0.23-1pve8
-vzdump: 1.2-5
-vzprocps: 2.0.11-1dso2
-vzquota: 3.0.11-1
-pve-qemu-kvm-2.6.18: 0.9.1-5
-or
-pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
-running kernel: 2.6.32-20-pve
-proxmox-ve-2.6.32: 3.0-100
-pve-kernel-2.6.32-20-pve: 2.6.32-100
-lvm2: 2.02.95-pve3
-clvm: 2.02.95-pve3
-corosync-pve: 1.4.5-1
-openais-pve: 1.1.4-3
-libqb0: 0.11.1-2
-redhat-cluster-pve: 3.2.0-2
-resource-agents-pve: 3.9.2-4
-fence-agents-pve: 4.0.0-1
-pve-cluster: 3.0-4
-qemu-server: 3.0-20
-pve-firmware: 1.0-22
-libpve-common-perl: 3.0-4
-libpve-access-control: 3.0-4
-libpve-storage-perl: 3.0-8
-vncterm: 1.1-4
-vzctl: 4.0-1pve3
-vzprocps: 2.0.11-2
-vzquota: 3.1-2
-pve-qemu-kvm: 1.4-13
-ksm-control-daemon: 1.1-1
-aptitude
-Standard Debian package update tool
-LVM
-Most of the commands in LVM are very similar to each other. Each valid command is preceded by one of the following:
-•	Physical Volume = pv
-•	Volume Group = vg
-•	Logical Volume = lv
-USAGE
-		Physical Volume 	Volume Group 	Logical Volume
-	LVM 	PV 	VG 	LV
-s 	No 	Yes 	Yes 	Yes
-display 	No 	Yes 	Yes 	Yes
-create 	No 	Yes 	Yes 	Yes
-rename 	No 	No 	Yes 	Yes
-change 	Yes 	Yes 	Yes 	Yes
-move 	No 	Yes 	Yes 	No
-extend 	No 	No 	Yes 	Yes
-reduce 	No 	No 	Yes 	Yes
-resize 	No 	Yes 	No 	Yes
-split 	No 	No 	Yes 	No
-merge 	No 	No 	Yes 	No
-convert 	No 	No 	Yes 	Yes
-import 	No 	No 	Yes 	No
-export 	No 	No 	Yes 	No
-importclone 	No 	No 	Yes 	No
-cfgbackup 	No 	No 	Yes 	No
-cfgrestore 	No 	No 	Yes 	No
-ck 	No 	Yes 	Yes 	No
-scan 	diskscan 	Yes 	Yes 	Yes
-mknodes 	No 	No 	Yes 	No
-remove 	No 	Yes 	Yes 	Yes
-dump 	Yes 	No 	No 	No
-iSCSI
+Backup
-DRBD
+vzdump
-See DRBD
-Debian Appliance Builder
+vzdump - backup utility for virtual machine - see Vzdump manual
-dab
+vzrestore
-See Debian Appliance Builder
-Other useful tools
+vzrestore - restore OpenVZ vzdump backups - see Vzrestore manual
-pveperf
+qmrestore
-Simple host performance test.
-(from man page)
+qmrestore - restore KVM vzdump backups - see Qmrestore manual
-USAGE
+Cluster management
-pveperf [PATH]
+pveca
-DESCRIPTION
-Tries to gather some CPU/Hardisk performance data on the hardisk mounted at PATH (/ is used as default)
+PVE Cluster Administration Toolkit
-It dumps on the terminal:
+USAGE
-•	CPU BOGOMIPS: bogomips sum of all CPUs
-•	REGEX/SECOND: regular expressions per second (perl performance test), should be above 300000
+    pveca -l # show cluster status
-•	HD SIZE: harddisk size
+    pveca -c # create new cluster with localhost as master
-•	BUFFERED READS: simple HD read test. Modern HDs should reach at least 40 MB/sec
+    pveca -s [-h IP] # sync cluster configuration from master (or IP)
-•	AVERAGE SEEK TIME: tests average seek time. Fast SCSI HDs reach values < 8 milliseconds. Common IDE/SATA disks get values from 15 to 20 ms.
+    pveca -d ID # delete a node
-•	FSYNCS/SECOND: value should be greater than 200 (you should enable "write back" cache mode on you RAID controller - needs a battery backed cache (BBWC)).
+    pveca -a [-h IP] # add new node to cluster
-•	DNS EXT: average time to resolve an external DNS name
+    pveca -m # force local node to become master
-•	DNS INT: average time to resolve a local DNS name
+    pveca -i # print node info (CID NAME IP ROLE)
-Note: this command may require root privileges (or sudo) to run, otherwise you get an error after "HD SIZE" value, like: <<sh: /proc/sys/vm/drop_caches: Permission denied unable to open HD at /usr/bin/pveperf line 149.>>
-Example output
+Software version check
+pveversion
+Proxmox VE version info - Print version information for Proxmox VE packages.
+USAGE
+pveversion [--verbose]
+    without any argument shows the version of pve-manager, something like:
+    pve-manager/1.5/4660
+or
+    pve-manager/3.0/957f0862
+    with -v argument it shows a list of programs versions related to pve, like:
+    pve-manager: 1.5-7 (pve-manager/1.5/4660)
+    running kernel: 2.6.18-2-pve
+    proxmox-ve-2.6.18: 1.5-5
+    pve-kernel-2.6.18-2-pve: 2.6.18-5
+    pve-kernel-2.6.18-1-pve: 2.6.18-4
+    qemu-server: 1.1-11
+    pve-firmware: 1.0-3
+    libpve-storage-perl: 1.0-10
+    vncterm: 0.9-2
+    vzctl: 3.0.23-1pve8
+    vzdump: 1.2-5
+    vzprocps: 2.0.11-1dso2
+    vzquota: 3.0.11-1
+    pve-qemu-kvm-2.6.18: 0.9.1-5
+or
+    pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
+    running kernel: 2.6.32-20-pve
+    proxmox-ve-2.6.32: 3.0-100
+    pve-kernel-2.6.32-20-pve: 2.6.32-100
+    lvm2: 2.02.95-pve3
+    clvm: 2.02.95-pve3
+    corosync-pve: 1.4.5-1
+    openais-pve: 1.1.4-3
+    libqb0: 0.11.1-2
+    redhat-cluster-pve: 3.2.0-2
+    resource-agents-pve: 3.9.2-4
+    fence-agents-pve: 4.0.0-1
+    pve-cluster: 3.0-4
+    qemu-server: 3.0-20
+    pve-firmware: 1.0-22
+    libpve-common-perl: 3.0-4
+    libpve-access-control: 3.0-4
+    libpve-storage-perl: 3.0-8
+    vncterm: 1.1-4
+    vzctl: 4.0-1pve3
+    vzprocps: 2.0.11-2
+    vzquota: 3.1-2
+    pve-qemu-kvm: 1.4-13
+    ksm-control-daemon: 1.1-1
+aptitude
+Standard Debian package update tool
+LVM
+Most of the commands in LVM are very similar to each other. Each valid command is preceded by one of the following:
+    Physical Volume = pv
+    Volume Group = vg
+    Logical Volume = lv
+USAGE
+		Physical Volume 	Volume Group 	Logical Volume
+	LVM 	PV 	VG 	LV
+s 	No 	Yes
+Yes
+	Yes
+display 	No 	Yes 	Yes 	Yes
+create 	No 	Yes 	Yes 	Yes
+rename 	No 	No 	Yes 	Yes
+change 	Yes 	Yes 	Yes 	Yes
+move 	No 	Yes 	Yes 	No
+extend 	No 	No 	Yes 	Yes
+reduce 	No 	No 	Yes 	Yes
+resize 	No 	Yes 	No 	Yes
+split 	No 	No 	Yes 	No
+merge 	No 	No 	Yes 	No
+convert 	No 	No 	Yes 	Yes
+import 	No 	No 	Yes 	No
+export 	No 	No 	Yes 	No
+importclone 	No 	No 	Yes 	No
+cfgbackup 	No 	No 	Yes 	No
+cfgrestore 	No 	No 	Yes 	No
+ck 	No 	Yes 	Yes 	No
+scan 	diskscan 	Yes 	Yes 	Yes
+mknodes 	No 	No 	Yes 	No
+remove 	No 	Yes 	Yes 	Yes
+dump 	Yes 	No 	No 	No
+iSCSI
+DRBD
+See DRBD
+Debian Appliance Builder
+dab
+See Debian Appliance Builder
+Other useful tools
+pveperf
+Simple host performance test.
+(from man page)
+USAGE
+    pveperf [PATH]
+DESCRIPTION
+    Tries to gather some CPU/Hardisk performance data on the hardisk mounted at PATH (/ is used as default)
+It dumps on the terminal:
+    CPU BOGOMIPS: bogomips sum of all CPUs
+    REGEX/SECOND: regular expressions per second (perl performance test), should be above 300000
+    HD SIZE: harddisk size
+    BUFFERED READS: simple HD read test. Modern HDs should reach at least 40 MB/sec
+    AVERAGE SEEK TIME: tests average seek time. Fast SCSI HDs reach values < 8 milliseconds. Common IDE/SATA disks get values from 15 to 20 ms.
+    FSYNCS/SECOND: value should be greater than 200 (you should enable "write back" cache mode on you RAID controller - needs a battery backed cache (BBWC)).
+    DNS EXT: average time to resolve an external DNS name
+    DNS INT: average time to resolve a local DNS name
+Note: this command may require root privileges (or sudo) to run, otherwise you get an error after "HD SIZE" value, like: <<sh: /proc/sys/vm/drop_caches: Permission denied unable to open HD at /usr/bin/pveperf line 149.>>
+Example output
 CPU BOGOMIPS:      26341.80
 REGEX/SECOND:      1554770
@@ Línea 275: / Línea 336: @@
 DNS EXT:           314.58 ms
 DNS INT:           236.94 ms (mypve.com)
-pvesubscription
-For managing a node's subscription key
+pvesubscription
-Usage
-To set the key use:
+For managing a node's subscription key
-•	pvesubscription set <key>
+Usage
-The following updates the subscription status
-•	pvesubscription update -force
+To set the key use:
-To print subscription status use
-•	pvesubscription get
+    pvesubscription set <key>
+The following updates the subscription status
+    pvesubscription update -force
+To print subscription status use
+    pvesubscription get
 USAGE: pvesubscription <COMMAND> [ARGS] [OPTIONS]
        pvesubscription get