Kvmtools - Revision history

Igraltist: /* Download */

2017-08-02T09:26:29Z

Download

← Older revision		Revision as of 05:26, 2 August 2017
Line 90:		Line 90:

	via Webbrowser:		via Webbrowser:
	~~http~~://hg.kasten-edv.de/kvm-tools (klick on bzip,gzip or zip link)		https://hg.kasten-edv.de/kvm-tools (klick on bzip,gzip or zip link)

	via mercurial:		via mercurial:
	hg clone ~~http~~://hg.kasten-edv.de/kvm-tools --insecure		hg clone https://hg.kasten-edv.de/kvm-tools --insecure

	= Installation =		= Installation =

Igraltist: /* Configuration File Format */

2017-07-31T15:25:08Z

Configuration File Format

← Older revision		Revision as of 11:25, 31 July 2017
Line 54:		Line 54:
	# have to set the path to qemu-kvm or name		# have to set the path to qemu-kvm or name
	# the script generate-kvm-option does update the path		# the script generate-kvm-option does update the path
	qemu-kvm = ~~kvm,~~ qemu-~~kvm~~		qemu-kvm = qemu-system-x86_x84

	daemonize = enabled		daemonize = enabled

Igraltist: /* kvm-admin */

2017-07-31T15:24:03Z

kvm-admin

← Older revision		Revision as of 11:24, 31 July 2017
Line 2:		Line 2:
	'''What it does?'''		'''What it does?'''

	It offer the possibility to manage a qemu~~-kvm domain~~ via commandline.		It offer the possibility to manage a qemu guest via commandline.

	The reason to build was to have a simple tool to manage my own qemu~~-kvm domains~~.		The reason to build was to have a simple tool to manage my own qemu guest.

	Just to use it for qemu~~-kvm domains~~ to connect to a bridged network.		Just to use it for qemu guest to connect to a bridged network.

	= Howto use it =		= Howto use it =

Igraltist at 15:18, 8 April 2012

2012-04-08T15:18:20Z

← Older revision		Revision as of 11:18, 8 April 2012
Line 5:		Line 5:

	The reason to build was to have a simple tool to manage my own qemu-kvm domains.		The reason to build was to have a simple tool to manage my own qemu-kvm domains.

			Just to use it for qemu-kvm domains to connect to a bridged network.

	= Howto use it =		= Howto use it =
Line 32:		Line 34:

	= Features =		= Features =
	It's add a bridge to a given bridge from ~~guest~~ configuration file.		It's add a bridge to a given bridge from qemu-kvm domain configuration file.

	The bridge(s) have to exists.		The bridge(s) have to exists.
	There can individual bridges on the system and each ~~guest~~ can assign to different bridge.		There can individual bridges on the system and each qemu-kvm domain can assign to different bridge.
	No need to add many script files and scriptdown files.		No need to add many script files and scriptdown files.
	This is set automaticly.		This is set automaticly.

Igraltist at 15:15, 8 April 2012

2012-04-08T15:15:24Z

← Older revision		Revision as of 11:15, 8 April 2012
Line 10:		Line 10:

	<code>		<code>
	kvm-admin boot ~~my_guest~~		kvm-admin boot domain_name
	</code>		</code>

	<code>		<code>
	kvm-admin status ~~my_guest~~		kvm-admin status domain_name
	</code>		</code>

Line 22:		Line 22:

	<code>		<code>
	kvm-admin monitor ~~my_domain~~		kvm-admin monitor domain_name
	</code>		</code>

	<code>		<code>
	kvm-admin show ~~my_guest~~		kvm-admin show domain_name
	</code>		</code>

Igraltist at 15:14, 8 April 2012

2012-04-08T15:14:09Z

← Older revision		Revision as of 11:14, 8 April 2012
Line 1:		Line 1:
	= kvm-admin =		= kvm-admin =
	'''What it does?'''		'''What it does?'''

	It offer the possibility to manage a qemu-kvm domain via commandline.		It offer the possibility to manage a qemu-kvm domain via commandline.

Line 19:		Line 20:
	kvm-admin status all		kvm-admin status all
	</code>		</code>

	<code>		<code>
	kvm-admin monitor my_domain		kvm-admin monitor my_domain

Igraltist at 15:13, 8 April 2012

2012-04-08T15:13:11Z

← Older revision		Revision as of 11:13, 8 April 2012
Line 2:		Line 2:
	'''What it does?'''		'''What it does?'''
	It offer the possibility to manage a qemu-kvm domain via commandline.		It offer the possibility to manage a qemu-kvm domain via commandline.

			The reason to build was to have a simple tool to manage my own qemu-kvm domains.

	= Howto use it =		= Howto use it =
	~~Example, to get monitor's help~~:		Examples:

	<code>		<code>
	kvm-admin ~~monitor my_domain~~		kvm-admin boot my_guest
	</code>		</code>

	~~To get the command printed:~~		<code>
			kvm-admin status my_guest
			</code>

	<code>		<code>
	kvm-admin ~~show my_guest~~		kvm-admin status all
			</code>
			<code>
			kvm-admin monitor my_domain
	</code>		</code>

	~~Boot a guest:~~

	<code>		<code>
	kvm-admin ~~boot~~ my_guest		kvm-admin show my_guest
	</code>		</code>

Igraltist at 14:55, 8 April 2012

2012-04-08T14:55:18Z

← Older revision		Revision as of 10:55, 8 April 2012
Line 1:		Line 1:
	= kvm-admin =		= kvm-admin =
	'''What it does?'''		'''What it does?'''
	It ~~can do~~ the ~~following actions: show, boot, shutdown, status and monitor~~.		It offer the possibility to manage a qemu-kvm domain via commandline.

	= Howto use it =		= Howto use it =
Line 7:		Line 7:

	<code>		<code>
	kvm-admin ~~my_guest~~ monitor ~~help~~		kvm-admin monitor my_domain
	</code>		</code>

Line 13:		Line 13:

	<code>		<code>
	kvm-admin my_guest ~~show~~		kvm-admin show my_guest
	</code>		</code>

Line 19:		Line 19:

	<code>		<code>
	kvm-admin my_guest ~~boot~~		kvm-admin boot my_guest
	</code>		</code>

Line 32:		Line 32:

	= Configuration File Format =		= Configuration File Format =
	The ~~guest~~ configuration file ~~has to be~~ placed in the directory 'domains'.		The qemu-kvm domain configuration file are placed in the directory 'domains'.
	The format is taken 1:1 from the command line.		The format is taken 1:1 from the command line but separated by new line

	To use an qemu-kvm option which doesn't have a parameter, have to use:		To use an qemu-kvm option which doesn't have a parameter you have to use:
	variable = enabled		variable = enabled

	Global configuration variabales, which all ~~guest~~ should effected,		Global configuration variabales which all qemu-kvm domains should effected,
	can write in 'config/kvm.cfg' file.		can write in 'config/kvm.cfg' file.

	~~Exampe~~:		Example:
	# have to set the path to qemu-kvm ~~executable~~		# have to set the path to qemu-kvm or name
	qemu-kvm = ~~/usr/bin/~~kvm		# the script generate-kvm-option does update the path
			qemu-kvm = kvm, qemu-kvm

	daemonize = enabled		daemonize = enabled
Line 49:		Line 50:


	Example ~~format~~:		Example output for a qemu-kvm domain:
			# if name is not set it will use the filename as name
	name = my_guest		name = my_guest
	smp = 2		smp = 2
Line 69:		Line 71:
	# first network interface		# first network interface
	net = nic,[and other options]		net = nic,[and other options]
	net = tap~~,ifname=my_iface_one~~,bridge=br0		net = tap,bridge=br0
	# second network interface		# second network interface
	net = nic,[and other options]		net = nic,[and other options]
	net = tap~~,ifname=my_iface_two~~,bridge=br1		net = tap,bridge=br1

	= Download =		= Download =
Line 81:		Line 83:

	via mercurial:		via mercurial:
	hg clone http://hg.kasten-edv.de/kvm-tools		hg clone http://hg.kasten-edv.de/kvm-tools --insecure

	= Installation =		= Installation =
Line 89:		Line 91:
	To run the kvm process under a unprivileged user.		To run the kvm process under a unprivileged user.

	Add an user 'kvm' ~~for example~~ and add this in the ~~guest~~ configuration file.		Add an user 'kvm' and add this in to the qemu-kvm domain configuration file.
	runas = kvm		runas = kvm

	For each ~~guest~~ can assign an individual user.		For each qemu-kvm domain you can assign an individual user.

	When all ~~guests~~ should run as the user 'kvm' then add this in the global configurations file 'config/kvm.cfg'		When all qemu-kvm domains should run as the user 'kvm' then add this in the global configurations file 'config/kvm.cfg'
	runas = kvm		runas = kvm

	When is set in 'config/kvm.cfg' the ~~guest~~ configuration file ~~does~~ override		When is set in 'config/kvm.cfg' the qemu-kvm domain configuration file can override it.
	it~~, when there also is set~~.
	~~runas = kvm_one~~

	~~Then this process is running as user 'kvm_one'~~


	= ToDo =		= ToDo =
			* extend the installer script
	* build a init script		* build a init script
	* build an installation routine		* build an installation routine

Whit: fixed some grammar and spelling

2011-06-22T23:45:32Z

fixed some grammar and spelling

← Older revision		Revision as of 19:45, 22 June 2011
Line 1:		Line 1:
	= kvm-admin =		= kvm-admin =
	'''What it does?'''		'''What it does?'''
	It can do the ~~follow action~~: show, boot, shutdown, status and monitor.		It can do the following actions: show, boot, shutdown, status and monitor.

	= Howto use it =		= Howto use it =
Line 23:		Line 23:


	= ~~Featurs~~ =		= Features =
	It's add a bridge to a given bridge from guest configuration file.		It's add a bridge to a given bridge from guest configuration file.

Line 29:		Line 29:
	There can individual bridges on the system and each guest can assign to different bridge.		There can individual bridges on the system and each guest can assign to different bridge.
	No need to add many script files and scriptdown files.		No need to add many script files and scriptdown files.
	This is set ~~automatic~~.		This is set automaticly.

	= Configuration File Format =		= Configuration File Format =
	The guest configuration file ~~have~~ to placed in the directory 'domains'.		The guest configuration file has to be placed in the directory 'domains'.
	The format is taken 1:1 from the command line.		The format is taken 1:1 from the command line.

	To use an qemu-kvm option which ~~don~~'t have a parameter, have to use:		To use an qemu-kvm option which doesn't have a parameter, have to use:
	variable = enabled		variable = enabled

	Global configuration ~~varibales~~, which all guest should effected,		Global configuration variabales, which all guest should effected,
	can write in 'config/kvm.cfg' file.		can write in 'config/kvm.cfg' file.

Line 45:		Line 45:
	qemu-kvm = /usr/bin/kvm		qemu-kvm = /usr/bin/kvm

	~~dammonize~~ = enabled		daemonize = enabled
	localtime = enabled		localtime = enabled

Line 61:		Line 61:
	localtime = enabled		localtime = enabled

	Only one exception ~~exist~~.		Only one exception exists.
	This is only for the '-net tap' option.		This is only for the '-net tap' option.
	There have to add an option for the bridge.		There have to add an option for the bridge.
Line 75:		Line 75:

	= Download =		= Download =
	It can ~~dowloaded~~ on the mercurial repository on:		It can be downloaded on the mercurial repository on:

	via Webbrowser:		via Webbrowser:
Line 94:		Line 94:
	For each guest can assign an individual user.		For each guest can assign an individual user.

	When all ~~guest~~ should run as the user 'kvm' then add this in the global configurations file 'config/kvm.cfg'		When all guests should run as the user 'kvm' then add this in the global configurations file 'config/kvm.cfg'
	runas = kvm		runas = kvm

Igraltist at 22:17, 9 December 2010

2010-12-09T22:17:27Z

← Older revision		Revision as of 18:17, 9 December 2010
Line 82:		Line 82:
	via mercurial:		via mercurial:
	hg clone http://hg.kasten-edv.de/kvm-tools		hg clone http://hg.kasten-edv.de/kvm-tools
	~~hg branches (to get a list)~~
	~~hg update branch_nummer_to_latest_version~~

	= Installation =		= Installation =
Line 105:		Line 103:
	Then this process is running as user 'kvm_one'		Then this process is running as user 'kvm_one'


			= ToDo =
			* build a init script
			* build an installation routine
			* add possibility to automatic create and delete guest

	= Fixes =		= Fixes =
	The ordinary fixes :)		The ordinary fixes :)