Lab Virtual Machines - Revision history

Benrwong: /* Virtual Machine Backups */

2018-08-21T17:29:41Z

Virtual Machine Backups

← Older revision		Revision as of 17:29, 21 August 2018
Line 19:		Line 19:
	If you ever need to restore from these backups:		If you ever need to restore from these backups:

	1. scp /export/ex9/archive/libvirt/images/20180817-he-VM_images.tar & /export/ex9/archive/libvirt/xml/he_VM_xml.tar.gz back to he or any functioning hypervisor.		1. scp /export/ex9/archive/libvirt/images/20180817-he-VM_images.tar & /export/ex9/archive/libvirt/xml/he_VM_xml.tar.gz back to he or any functioning hypervisor. <br />
	2. Untar the contents somewhere safe. Don't untar in /var/lib/libvirt or /etc/libvirt/qemu. Tar defaults to overwrite existing files.		2. Untar the contents somewhere safe. Don't untar in /var/lib/libvirt or /etc/libvirt/qemu. Tar defaults to overwrite existing files. <br />
	3. images .tar captures the /var/lib/libvirt directory. Move everything below that directory to /var/lib/libvirt or copy the necessary contents to /var/lib/libvirt. For default hypervisor installations, images are stored in /var/lib/libvirt/images.		3. images .tar captures the /var/lib/libvirt directory. Move everything below that directory to /var/lib/libvirt or copy the necessary contents to /var/lib/libvirt. For default hypervisor installations, images are stored in /var/lib/libvirt/images. <br />
	4. For situations where you need VMs redeclared, you must move the .xml files from he_VM_xml.tar.gz to /etc/libvirt/qemu/. Define VMs with the command:		4. For situations where you need VMs redeclared, you must move the .xml files from he_VM_xml.tar.gz to /etc/libvirt/qemu/. Define VMs with the command:
	virsh define <location of VM.xml file>		virsh define <location of VM.xml file>
Line 41:		Line 41:

	5. If a VM is properly defined, you only need to do the following command to start the VM:		5. If a VM is properly defined, you only need to do the following command to start the VM:
	virsh start <VM_Name>		virsh start <VM_Name>



	==Cluster 0==		==Cluster 0==

Benrwong: added instructions for restoring from backup

2018-08-21T17:29:02Z

added instructions for restoring from backup

@@ Line 14: / Line 14: @@
    zeta                          psicquic server
    sigma                          not sure what this does but we can keep it off <br />
-  These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018.  The file format is a .tar.gz file.
+. scp /export/ex9/archive/libvirt/images/20180817-he-VM_images.tar & /export/ex9/archive/libvirt/xml/he_VM_xml.tar.gz back to he or any functioning hypervisor.
-   omega                     matt o'meara.   transportal.
 ==Cluster 0==

Frodo: /* Virtual Machine Backups */ asdf

2018-08-21T16:47:30Z

Virtual Machine Backups: asdf

← Older revision		Revision as of 16:47, 21 August 2018
Line 6:		Line 6:
	alpha DNS,DHCP,Puppet,Foreman		alpha DNS,DHCP,Puppet,Foreman
	beta Authentication server; openldap		beta Authentication server; openldap
	chi		chi ???
	epsilon public portal gateway to cluster		epsilon public portal gateway to cluster
	gamma Sun Grid Engine		gamma Sun Grid Engine
	phi for excipients website		phi for excipients website
	psi		psi pgf fortran compiler
	tau web server for zinc		tau web server for zinc
	zeta		zeta psicquic server
	sigma not sure what this does but we can keep it off <br />		sigma not sure what this does but we can keep it off <br />

	These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018. The file format is a .tar.gz file.		These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018. The file format is a .tar.gz file.

			omega matt o'meara. transportal.

	==Cluster 0==		==Cluster 0==

Benrwong: /* Virtual Machine Backups */

2018-08-21T16:18:13Z

Virtual Machine Backups

← Older revision		Revision as of 16:18, 21 August 2018
Line 14:		Line 14:
	zeta		zeta
	sigma not sure what this does but we can keep it off <br />		sigma not sure what this does but we can keep it off <br />
	These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018.		These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018. The file format is a .tar.gz file.

	==Cluster 0==		==Cluster 0==

Benrwong: listed virtual machines

2018-08-21T16:17:19Z

listed virtual machines

← Older revision		Revision as of 16:17, 21 August 2018
Line 1:		Line 1:
	There are important VMs on both Cluster 0 and Cluster 2. Cluster 0 uses VMware while Cluster 2 uses KVM/libvirt.		There are important VMs on both Cluster 0 and Cluster 2. Cluster 0 uses VMware while Cluster 2 uses KVM/libvirt.

			==Virtual Machine Backups==
			he is the main hypervisor of BKS. It holds the following VMs:

			alpha DNS,DHCP,Puppet,Foreman
			beta Authentication server; openldap
			chi
			epsilon public portal gateway to cluster
			gamma Sun Grid Engine
			phi for excipients website
			psi
			tau web server for zinc
			zeta
			sigma not sure what this does but we can keep it off <br />
			These VMs were backed up to qof:/export/ex9/archive/libvirt during the downtime of Aug 17,2018.

	==Cluster 0==		==Cluster 0==

Benrwong: /* kvm/libvirt commands */

2017-01-03T19:08:56Z

kvm/libvirt commands

← Older revision		Revision as of 19:08, 3 January 2017
Line 22:		Line 22:

	# to get list of VMs on hypervisor		# to get list of VMs on hypervisor
	virsh list --all		virsh list --all <br />
	# to start a VM		# to start a VM
	virsh start <VM-name or VMid>		virsh start <VM-name or VMid> <br />
	# to shutdown a VM		# to shutdown a VM
	virsh shutdown <VM-name or VMid>		virsh shutdown <VM-name or VMid> <br />
	# to force shutdown a VM (equivalent of pulling the plug on a computer)		# to force shutdown a VM (equivalent of pulling the plug on a computer)
	virsh destroy --graceful <VM-name or VMid>		virsh destroy --graceful <VM-name or VMid> <br />
	# to pause a VM		# to pause a VM
	virsh suspend <VM-name or VMid>		virsh suspend <VM-name or VMid> <br />
	# to unpause a VM		# to unpause a VM
	virsh resume <VM-name or VMid>		virsh resume <VM-name or VMid> <br />
	# get XML file contents of VM		# get XML file contents of VM
	virsh dumpxml <VM-name or VMid>		virsh dumpxml <VM-name or VMid>

Benrwong: /* kvm/libvirt commands */

2017-01-03T19:07:47Z

kvm/libvirt commands

← Older revision		Revision as of 19:07, 3 January 2017
Line 23:		Line 23:
	# to get list of VMs on hypervisor		# to get list of VMs on hypervisor
	virsh list --all		virsh list --all

	# to start a VM		# to start a VM
	virsh start <VM-name or VMid>		virsh start <VM-name or VMid>

	# to shutdown a VM		# to shutdown a VM
	virsh shutdown <VM-name or VMid>		virsh shutdown <VM-name or VMid>

	# to force shutdown a VM (equivalent of pulling the plug on a computer)		# to force shutdown a VM (equivalent of pulling the plug on a computer)
	virsh destroy --graceful <VM-name or VMid>		virsh destroy --graceful <VM-name or VMid>

	# to pause a VM		# to pause a VM
	virsh suspend <VM-name or VMid>		virsh suspend <VM-name or VMid>

	# to unpause a VM		# to unpause a VM
	virsh resume <VM-name or VMid>		virsh resume <VM-name or VMid>

	# get XML file contents of VM		# get XML file contents of VM
	virsh dumpxml <VM-name or VMid>		virsh dumpxml <VM-name or VMid>

Benrwong at 19:07, 3 January 2017

2017-01-03T19:07:26Z

← Older revision		Revision as of 19:07, 3 January 2017
Line 17:		Line 17:

	==Cluster 2==		==Cluster 2==

			===kvm/libvirt commands===
			In order for a user to issue KVM commands, the service libvirtd must be running. Check the status of libvirtd by issuing the command: service libvirtd status. If libvirtd is not running, then you may issue command: service libvirtd start.

			# to get list of VMs on hypervisor
			virsh list --all

			# to start a VM
			virsh start <VM-name or VMid>

			# to shutdown a VM
			virsh shutdown <VM-name or VMid>

			# to force shutdown a VM (equivalent of pulling the plug on a computer)
			virsh destroy --graceful <VM-name or VMid>

			# to pause a VM
			virsh suspend <VM-name or VMid>

			# to unpause a VM
			virsh resume <VM-name or VMid>

			# get XML file contents of VM
			virsh dumpxml <VM-name or VMid>

Benrwong: Created page with "There are important VMs on both Cluster 0 and Cluster 2. Cluster 0 uses VMware while Cluster 2 uses KVM/libvirt. ==Cluster 0== Significant hypervisors on Cluster 0: vmware..."

2017-01-03T18:29:53Z

Created page with "There are important VMs on both Cluster 0 and Cluster 2. Cluster 0 uses VMware while Cluster 2 uses KVM/libvirt. ==Cluster 0== Significant hypervisors on Cluster 0: vmware..."

New page

There are important VMs on both Cluster 0 and Cluster 2. Cluster 0 uses VMware while Cluster 2 uses KVM/libvirt.

==Cluster 0==
Significant hypervisors on Cluster 0: vmware1 (access via root with clust 0 formulax2)
===VMWare Commands===
Webpage that describes numerous VMware commands: http://www.doublecloud.org/2013/11/vmware-esxi-vim-cmd-command-a-quick-tutorial/

# To get a list of all VMs and obtain VMid
vim-cmd vmsvc/getallvms

# To shutdown a VM:
vim-cmd vmsvc/power.off <VMid>

# To turn on a VM:
vim-cmd vmsvc/power.on <VMid>

==Cluster 2==