XEN-Server - Histórico de revisão

Wiki: /* Solucionando problemas com devices em loop */

2017-06-07T02:51:51Z

Solucionando problemas com devices em loop

← Versão anterior		Edição de 02h51min de 7 de junho de 2017
Linha 4:		Linha 4:

	Xen: Failed to find an unused loop device		Xen: Failed to find an unused loop device
-	~~Yeri TieteWednesday, October 20, 2010Errors, Linux, Software, VMxenLeave a comment~~
-	~~I had to start a new Xen domU this afternoon,~~

-	xm create vm#.domain	+	xm create vm#.domain

	But this resulted in following error:		But this resulted in following error:
Linha 16:		Linha 14:
	Solution:		Solution:

-	Create /etc/modprobe.d/local-loop.conf with this content:	+	Create /etc/modprobe.d/local-loop.conf with this content:

	options loop max_loop=64		options loop max_loop=64

-	~~Turn off all DomUs, yes, bummer. You’ll need to reload the loop module which won’t work if Xen is still using them. xm list should only display Domain-0.~~

-	modprobe -r loop && modprobe loop	+	**** Turn off all DomUs, yes, bummer. You’ll need to reload the loop module which won’t work if Xen is still using them. xm list should only display Domain-0.
		+
		+	modprobe -r loop && modprobe loop
		+

	And restart all DomUs. You can now create 32 (64/2 ~= # of DomUs; increase if you need more) DomUs.		And restart all DomUs. You can now create 32 (64/2 ~= # of DomUs; increase if you need more) DomUs.

Wiki: /* XEN-SERVER (Citrix e XCP) */

2017-06-07T02:51:00Z

XEN-SERVER (Citrix e XCP)

← Versão anterior		Edição de 02h51min de 7 de junho de 2017
Linha 1:		Linha 1:
		+	= XEN-SREVER SOURCE + DEBIAN =
		+	==Solucionando problemas com devices em loop==
		+	<pre>
		+
		+	Xen: Failed to find an unused loop device
		+	Yeri TieteWednesday, October 20, 2010Errors, Linux, Software, VMxenLeave a comment
		+	I had to start a new Xen domU this afternoon,
		+
		+	xm create vm#.domain
		+
		+	But this resulted in following error:
		+
		+	Error: Device 5632 (vbd) could not be connected.
		+	Failed to find an unused loop device
		+
		+	Solution:
		+
		+	Create /etc/modprobe.d/local-loop.conf with this content:
		+
		+	options loop max_loop=64
		+
		+	Turn off all DomUs, yes, bummer. You’ll need to reload the loop module which won’t work if Xen is still using them. xm list should only display Domain-0.
		+
		+	modprobe -r loop && modprobe loop
		+
		+	And restart all DomUs. You can now create 32 (64/2 ~= # of DomUs; increase if you need more) DomUs.
		+
		+	You can check (before & after) the difference in loop back devices: ls -ls /dev \| grep loop \| wc -l
		+
		+	</pre>
		+
	= XEN-SERVER (Citrix e XCP) =		= XEN-SERVER (Citrix e XCP) =

Wiki: /* XEN-SERVER (Citrix e XCP) */

2017-02-20T18:03:45Z

XEN-SERVER (Citrix e XCP)

← Versão anterior		Edição de 18h03min de 20 de fevereiro de 2017
Linha 1:		Linha 1:
	= XEN-SERVER (Citrix e XCP) =		= XEN-SERVER (Citrix e XCP) =
		+
		+	==Renovando a licença do XENSERVER - CITRIX pela linha de comando==
		+
		+	''' Primeiro você deve solicitar uma nova licença [http://deliver.citrix.com/go/citrix/xenserver_renewalb AQUI]'''
		+
		+	'''Procedimento para renovação da licença por linha de comando:'''
		+
		+	<pre>
		+
		+	find / -iname \*license
		+	/etc/xensource/license
		+	cd /etc/xensource/
		+	mv license /home/lupa/licenca/BKP_`date +%d-%m-%Y`.license
		+	cp /home/lupa/license.xslic ./license
		+
		+	</pre>

	==Habilitar Repositorio no XENSERVER==		==Habilitar Repositorio no XENSERVER==

Wiki: /* MIGRAÇÃO VMS */

2016-04-26T03:07:53Z

MIGRAÇÃO VMS

← Versão anterior		Edição de 03h07min de 26 de abril de 2016
Linha 130:		Linha 130:

	==MIGRAÇÃO VMS==		==MIGRAÇÃO VMS==
		+
		+	===Exportando uma VM:===
		+
		+	<pre>
		+	xe vmexport vm=<novo_nome_vm> filename=/<diretorio_de_backup_nome-da-vm.xva
		+	</pre>
		+
		+
		+	===Importando uam VM:===
		+
		+	<pre>
		+	xe vm-import filename=/<diretorio_de_backup_nome-da-vm.xva
		+	</pre>

Wiki: /* XEN-SERVER (Citrix e XCP) */

2016-04-26T03:04:41Z

XEN-SERVER (Citrix e XCP)

← Versão anterior		Edição de 03h04min de 26 de abril de 2016
Linha 128:		Linha 128:
	service iptables restart		service iptables restart
	</pre>		</pre>
		+
		+	==MIGRAÇÃO VMS==

Wiki: /* XEN-SERVER (Citrix e XCP)c */

2014-10-02T17:56:00Z

XEN-SERVER (Citrix e XCP)c

← Versão anterior		Edição de 17h56min de 2 de outubro de 2014
Linha 1:		Linha 1:
-	= XEN-SERVER (Citrix e XCP)c =	+	= XEN-SERVER (Citrix e XCP) =

	==Habilitar Repositorio no XENSERVER==		==Habilitar Repositorio no XENSERVER==

Wiki em 17h55min de 2 de outubro de 2014

2014-10-02T17:55:50Z

← Versão anterior		Edição de 17h55min de 2 de outubro de 2014
Linha 1:		Linha 1:
-	~~h.1~~ XEN-SERVER (Citrix e XCP)	+	= XEN-SERVER (Citrix e XCP)c =

-	=SNMP=	+	==Habilitar Repositorio no XENSERVER==
		+
		+	<pre>
		+	yum repolist enabled
		+	</pre>
		+
		+	<pre>
		+	sed -i -e "s/enabled=0/enabled=1/" /etc/yum.repos.d/CentOS-Base.repo
		+	</pre>
		+
		+	==SNMP==

	'''Instalação'''		'''Instalação'''

Wiki: Criou página com 'h.1 XEN-SERVER (Citrix e XCP) =SNMP= '''Instalação'''

  yum install net-snmp

'''Arquivo conf'''

  #######################################################…'

2014-06-23T01:18:49Z

Criou página com 'h.1 XEN-SERVER (Citrix e XCP) =SNMP= '''Instalação''' <pre> yum install net-snmp </pre> '''Arquivo conf''' <pre> #######################################################…'

Nova página

h.1 XEN-SERVER (Citrix e XCP)

=SNMP=

'''Instalação'''

<pre>

yum install net-snmp

</pre>

'''Arquivo conf'''

<pre>

###########################################################################
#
# snmpd.conf
#
# - created by the snmpconf configuration program
#
###########################################################################
# SECTION: Access Control Setup
#
# This section defines who is allowed to talk to your running
# snmp agent.

# rocommunity: a SNMPv1/SNMPv2c read-only access community name
# arguments: community [default|hostname|network/bits] [oid]

rocommunity <EMPRESA>

# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
# arguments: community [default|hostname|network/bits] [oid]

rwcommunity <EMPRESA> 192.168.0.0/24
com2sec mynet 192.168.0.0/24 <EMPRESA>
com2sec lupa <Ip Liberado para consultar o SNMP> <EMPRESA>
com2sec local localhost <EMPRESA>

group MyROGroup v1 mynet
group MyROGroup v2c mynet
group MyROGroup usm mynet
group MyRWGroup v1 local
group MyRWGroup v2c local
group MyRWGroup usm local
group MyRWGroup v1 lupa
group MyRWGroup v2c lupa
group MyRWGroup usm lupa

access MyROSystem "" any noauth exact system none none
access MyROGroup "" any noauth exact all none none
access MyRWGroup "" any noauth exact all all none

###########################################################################
# SECTION: System Information Setup
#
# This section defines some of the information reported in
# the "system" mib group in the mibII tree.

# syslocation: The [typically physical] location of the system.
# Note that setting this value here means that when trying to
# perform an snmp SET operation to the sysLocation.0 variable will make
# the agent return the "notWritable" error code. IE, including
# this token in the snmpd.conf file will disable write access to
# the variable.
# arguments: location_string

syslocation <EMPRESA>

# syscontact: The contact information for the administrator
# Note that setting this value here means that when trying to
# perform an snmp SET operation to the sysContact.0 variable will make
# the agent return the "notWritable" error code. IE, including
# this token in the snmpd.conf file will disable write access to
# the variable.
# arguments: contact_string

syscontact nome@seudominio.com.br

# sysservices: The proper value for the sysServices object.
# arguments: sysservices_number

sysservices 76

view all included .1 80

proc mountd

proc ntalkd 4

proc sendmail 10 1

disk / 10000
disk /var 5%
includeAllDisks 10%

load 12 14 14
</pre>

'''Regras IPTABLES (Liberação da porta 161)'''

Arquivo:
<pre>
/etc/sysconfig/iptables
</pre>

Adicionar a regra:
<pre>
-A RH-Firewall-1-INPUT -p udp --dport 161 -j ACCEPT
</pre>

Execute o comando:
<pre>
service iptables restart
</pre>