Archive for the ‘Virtualização’ Category

Esxi – Listar os ips das VLANS que estão passando em cada vmnic

Comando para listar os ips das VLANS que estão passando em cada vmnic (exemplo: quero saber o que passa no TRUNK em cada vmnic).

Não saco muito de linux mas vou batendo cabeça e posso não conseguir o resultado da forma mais elegante, mas consigo o que preciso!

Caso alguém saiba de uma forma diferente coloca aê no comment.

esxcfg-info –network | grep -E -i “VmKernel Device Name|Network Hint”

Exemplo da saida:
[root@esx ~]# esxcfg-info –network | grep -E -i “VmKernel Device Name|Network Hint”
        |—-Network Hint……………………………………0 10.248.0.0/255.255.255.128
           |—-VmKernel Device Name………………………….vmnic0
        |—-Network Hint……………………………………0 10.69.16.0/255.255.240.0, 2006 10.69.20.192/255.255.255.224, 2001 10.69.0.250/255.255.255.255, 2008 10.69.29.200/255.255.255.254, 2004 10.69.12.31/255.255.255.255, 2002 10.69.4.200/255.255.255.255
           |—-VmKernel Device Name………………………….vmnic1
        |—-Network Hint……………………………………
           |—-VmKernel Device Name………………………….vmnic10
        |—-Network Hint……………………………………60 10.240.0.0/255.255.255.128, 55 172.28.0.0/255.255.255.128, 65 0.0.0.0/0.0.0.0, 6 201.62.35.136/255.255.255.248, 39 10.4.20.5/255.255.255.255, 8 10.4.2.0/255.255.255.192, 75 10.248.0.0/255.255.255.128, 50 192.168.1.2/255.255.255.255, 38 10.4.19.2/255.255.255.255, 7 10.4.0.0/255.255.255.248, 37 10.4.18.0/255.255.255.252, 5 201.62.35.210/255.255.255.254, 40 10.4.21.1/255.255.255.255, 42 10.4.23.1/255.255.255.255, 30 200.165.59.155/255.255.255.255, 35 10.4.15.1/255.255.255.255, 21 0.0.0.0/0.0.0.0
           |—-VmKernel Device Name………………………….vmnic11

fonte:
http://communities.vmware.com/thread/95395

Como ativar acesso SSH no ESX 4.0

Por padrão o esx 4.0 vem com o acesso de root via ssh desabilitado! veja como habilitar neste link em inglês!

http://www.vladan.fr/how-to-activate-root-ssh-access-in-esx-4/

01.) First you must login as a root at the console of your ESX 4 Server.

02.) Then you must navigate to the /etc/ssh directory. Just type in:  cd /etc/ssh

03.) Open nano (text editor, easy to use…) type: nano sshd_config

Navigate to the line saying PermitRootLogin no and change it to Yes.

04.) Type then CTRL+X to exit. On the prompt answer Y (as Yes to save the modified file).

05.) Then you’ll need to restart the sshd service typing: service sshd restart.

06.) While you are in the cosole just type in the following two commands to open firewall ports:

esxcfg-firewall -e sshServer
esxcfg-firewall -e sshClient

VirtualCenter Server service cannot be started

No connection could be made because the target machine actively refused it x.x.x.x:443

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003926

Hoje um amigo nos avisou que o vcenter não estava conseguindo se conectar.  No nosso caso era a base do sql estava full!

Troubleshooting the VMware VirtualCenter Server service when it does not start or fails

Symptoms

  • You cannot connect to VirtualCenter
  • If you try to connect to VirtualCenter, you see the error:

    Cannot connect to host <server>: No connection could be made because the target machine actively refused it.

  • If you try to start the VMware VirtualCenter Server service, you may see the errors:
    • Could not start the VMware VirtualCenter Server service on Local Computer.  Error 1067: The process terminated unexpectedly.
    • Could not start the VMware VirtualCenter Server service on Local Computer.  Error 1069: The service did not start due to a logon failure.
    • The VMware VirtualCenter Server Service on Local Computer started then stopped.  Some services stop automatically if they have no work to do, for example the Performance Logs and Alerts service.

Purpose

This article guides you through the process of troubleshooting VirtualCenter when it does not start. The article helps you eliminate common causes for your problem by verifying the configuration of your database, validating network connectivity, and verifying the configuration of the VirtualCenter Server service.

Resolution

Please validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document that helps eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
To troubleshoot the VMware VirtualCenter Server service when it does not start or fails:
Note: If you perform a corrective action in any of the following steps, attempt to restart the VMware VirtualCenter Server service.
  1. Verify that the VMware VirtualCenter Server service cannot be restarted.

    Open the Microsoft Services control panel and check the status of the service. For more information on starting the VirtualCenter service if it has stopped, see Stopping, starting or restarting vCenter services (1003895).

  2. Verify that the configuration of the ODBC Data Source (DSN) used for connection to the database for VirtualCenter is correct. For more information, see Troubleshooting the database data source used by vCenter Server (1003928).

    Note: Ensure that you are using SQL authentication if you are using a Microsoft SQL server. Windows NT authentication is not supported.

  3. Verify that ports 902, 80, and 443 are not being used by any other application. If another application, such as Microsoft Internet Information Server (IIS), is utilizing any of the ports, VirtualCenter cannot start. For more information, see Port already in use when installing VirtualCenter (4824652).

    If you see an error similar to the following when reviewing the logs, another application may be using the ports:

    • Failed to create http proxy: Resource is already in use: Listen socket: :<port>

      Or

    • proxy failed on port <port>: Only one usage of each socket address (protocol/network address/port) is normally permitted.

      For more information on checking ports, see Determining if a port is in use (1003971).

  4. Verify the health of the database server that is being used for VirtualCenter. If the hard drives are out of space, the database transaction logs are full, or if the database is heavily fragmented, VirtualCenter may not start. For more information, see Investigating the health of a VirtualCenter database server (1003979).
  5. Verify that the Microsoft Active Directory domain is not accessible. If the domain is not available and you have permissions assigned to users in the domain, VirtualCenter may fail or refuse to start completely. For more information, see Investigating Active Directory when it causes the VirtualCenter server to stop or fail to start (1003996).

    Note:  If you are using Active Directory, ensure that the VMware VirtualCenter Server service is running as the local system account and not a domain account.
  6. Verify the VMware VirtualCenter Service is running with the proper credentials. For more information, see VirtualCenter Server service cannot be started after installation (1004280).
  7. Verify that critical folders exist on the VirtualCenter Server host. For more information, see Missing folders prevent VirtualCenter Server service from starting (1005882).

Note: If your problem still exists after trying the steps in this article, please:

Additional Information

Reviewing the vpxd log files is another common method of diagnosing the VirtualCenter Server when it does not start. By reviewing the log files, you can quickly determine the cause of the problem based on the error message reported.
For VirtualCenter 2.5.x the log files are stored in the following directory by default:
c:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs
For VirtualCenter 2.0.x the log files are stored in the following directory by default:
c:\Windows\Temp\vpx
To review the logs, open the most recent log in an editor such as Notepad, and navigate to the bottom of the file. The file contains any errors that occurs during the startup of the VirtualCenter Server service.

Clonando máquinas virtuais utilizando ESXi

Clonando máquinas virtuais utilizando ESXi.

Caso alguém saiba o comando para adicionar máquinas ao inventário, e também o comando para gerar um novo UUID, me avise que eu atualizo o script para que faça automaticamente.

O script foi feito para ser executado no diretório raiz do seu volume de storage.

# chmod +x clone.sh

# ./clone.sh template novo

onde: template (nome da maquina virtual que se deseja clonar) novo (nome da nova maquina virtual)

#!/bin/bash

echo "Criando diretório para a vm $2"
mkdir $2
cd $2
echo "Copiando imagem de disco da vm $1 para vm $2"
cp ../$1/*.vmdk .
vmkfstools -E $1.vmdk $2.vmdk
echo "Criando a nova máquina $2"
cp ../$1/$1.nvram ./$2.nvram
cp ../$1/$1.vmsd ./$2.vmsd
cat ../$1/$1.vmxf | sed -e "s/$1/$2/g" > $2.vmxf
chmod 600 $2.vmxf
cat ../$1/$1.vmx | sed -e "s/$1/$2/g" > $2.vmx
chmod 755 $2.vmx

echo '

Criação concluída, para integrá-la ao servidor de VM, proceda com os passos abaixo:

-> Importar o "novo.vmx" para o inventario

1) Browse Storage no diretório "novo"
2) Procurar o arquivo "novo.vmx"
3) Clicar com o botao direito sobre o arquivo "novo.vmx"
4) Escolher "Add to inventory"

-> Criar novo UUID para a máquina

1) Ligar a nova VM
2) Clicar com o botao direito sobre a nova VM
3) Escolher "Answer Question"
4) Escolher "Create"
'

Be Happy !!!

By Kl0Nez

Bom video sobre Cloud Computing

Como criar uma maquina virtual a partir de um site.

Uma particularidade das maquinas virtuais vmware é que os arquivos de configuração  são todos texto, com isso consigo abrir com um editor de texo normal .

Até agora nada de novidade.

Mas se você tiver somente o vmplayer e aparecer a necessidade de criar uma vm, você pode usar os sites:

http://www.easyvmx.com/ e http://dcgrendel.thewaffleiron.net/vmbuilder/2.0/

Basta salvar os arquivos gerado em um local no seu HD e instalar o SO usando o vmplayer.

Muito legal a ideia.

Top Virtualization Security Links

Caras, uma ótima fonte de pesquisa é o forum de discussão da vmware. Pesquisando lá encontrei este exelente documento:

Top Virtualization Security Links

Link para o forum vmware: http://communities.vmware.com/index.jspa

Usando dispositivo USB no vmware esx

Caras, quem estiver planejando virtualizar seus servidores deve ficar atendo a servidores que dependem de dispositivos de hardlock para o seu funcionamento (ARC GIS é um deles). As maquinas virtuais não terão suporte a dispositivos USB.

A boa noticia é que existe um dispositivo desenvolvido pela DIGI chamado AnywhereUSB que resolve esta deficiência.

ESXServer_AnywhereUSB

capturar

Lista de hardware não homolodados, mas suportados pelo esx e esxi

Bem legal, para quem não tem grana e tá afim fazer lab que não seja virtual.

Veja link.

http://www.vm-help.com/esx/esx3.5/Whiteboxes_SATA_Controllers_for_ESX_3.5_3i.htm

VMware Releases Open Source Virtualization Client

Quem me mostrou foi o meu amigo Fred Tarzan!!!

Fontes: http://developers.slashdot.org/article.pl?sid=09/02/04/0219236

Download:

http://code.google.com/p/vmware-view-open-client/

Texto:

http://ostatic.com/blog/vmware-saw-the-threat-releases-open-source-virtualization-client

Last year, following a crash in its share price and the replacement of its CEO with a seasoned Microsoft executive, I wrote about the perils that virtualization titan VMware faces. The problems come from two trends: 1) open source virtualization offerings; and 2) free virtualization within operating systems. From the free virtualization project Xen to the virtualization that Microsoft, Sun, Red Hat and others offer in operating systems,VMware’s proprietary strategy looked mighty shaky. Today, VMware made what I consider the shrewdest move it could: launching an open source client for virtual desktops.

The CEO replacement who entered VMware last year was Paul Maritz, a long-time Microsoft executive with intimate familiarity with how Windows swallowed up entire categories of utility software as it grew up, by simply wrapping free utilities into the operating system. Paul knows about that, and he had to have seen last year the dual threats to VMware of open source virtualization offerings and virtualization on board in operating systems.

The VMware View Open Client allows businesses to host virtualized desktops in the data center, and users can access their desktops from any device. Going with an open source solution like this was VMware’s only choice, especially as Microsoft includes Hyper-V virtualization in Windows Server. I’m sure Maritz was very focused on the Microsoft threat, because he used to be behind similar threats. VMware can grab market share with this move, stave off Microsoft dominance, and offer support and services around its open source offering. The company will also get substantial good PR from the decision.

You can get VMware View Open Client here, licensed under the Lesser GPL. It’s essentially a bet that customized user desktops are hosted in data centers, and that businesses will take to the idea that they can save money by centralizing custom solutions in data centers for desktop users to take advantage of through virtualization.

I agree with Dana Blankenhorn that this could cause a big shakeup in the software world. “Imagine what the PC world would be like if enterprises are able to slow purchases regardless of head count,” he writes. “Imagine what Microsoft revenues might look like in that world.” Indeed.

Valeu Fred!