tag:blogger.com,1999:blog-6557344978890249612024-02-21T06:01:33.248+01:00gVirtual BlogGilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-655734497889024961.post-8606495716459780202011-12-27T16:26:00.001+01:002011-12-27T16:28:38.433+01:00Changer l'emplacement de création des snapshotsCe paramètre est à configurer au niveau de la VM. Vous devez pour cela modifier le fichier vmx en ajoutant/modifiant le propriété workingDir.<br />
<br />
Vous devrez arrêter la VM pour réaliser l'opération et prendre en charge la modification<br />
<br />
Exemple:<br />
<br />
workingDir="/vmfs/volumes/4b7d3e11-5ef2ab42-5169-11aef34d5f63/"<br />
<br />
Les autres fichiers (vmdk, vmx, vswap, ...) ne changeront pas d'emplacement, seulement l'emplacement des fichiers de snapshots utiliseront ce paramètre.<br />
<br />
Pour ma part, ce paramètre m'a permis de pouvoir réaliser la maintenance d'un serveur qui se trouvait sur un datastore quasi full. J'avais besoin de créer un snapshot pour pouvoir faire un retour arrière rapide et de ne pas risquer de stopper la VM pendant la maintenance si le snapshot remplissait le datastore.Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-47695350216753299712011-12-27T16:09:00.006+01:002011-12-27T16:28:14.360+01:00ESXi command line<div style="background-color: white; font-family: arial, sans-serif; font-size: 13px;">Ci-dessous une liste des commandes que j'utilise couramment pour faire des manipulations sur les machines virtuelles :</div><ul style="background-color: white; font-family: arial, sans-serif; font-size: 13px;"><li>Lister les machines virtuelles enregistrées sur cet hôte (<u>vous permet d'obtenir le vmid</u> qui sera nécessaire pour les autres commandes)<br />
<code style="font-size: 11px;">vim-cmd /vmsvc/getallvms</code></li>
<li>Désenregistrer une VM<br />
<code style="font-size: 11px;">vim-cmd /vmsvc/unregister [vmid]<vmid></vmid></code></li>
<li>Enregistrer une VM<br />
<code style="font-size: 11px;">vim-cmd /solo/register [/path/to/file.vmx]</code></li>
<li>Obtenir l'état d'une VM<br />
<code style="font-size: 11px;">vim-cmd /vmsvc/power.getstate</code> <code style="font-size: 11px;">[</code><span style="font-family: monospace; font-size: 11px;">vmid]</span></li>
<li>Arrêter une VM<br />
<code style="font-size: 11px;">vim-cmd /vmsvc/power.off <code>[</code>vmid] </code><span style="font-family: monospace; font-size: 11px;"><b><vmid></vmid></b></span></li>
<li>Démarrer une VM<br />
<code style="font-size: 11px;">vim-cmd /vmsvc/power.on <code>[</code>vmid] </code><span style="font-family: monospace; font-size: 11px;"><b><vmid></vmid></b></span></li>
</ul>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-62506593713361213832010-02-14T15:38:00.011+01:002011-11-28T17:37:05.111+01:00Problème P2V Windows NT4<span style="font-family: verdana; font-size: 85%;">Lors de la migration d’une VM sous VMware Server vers un ESXi 4, la VM consommée 100 % du CPU ce qui entrainait une alerte.<br />
<br />
Après quelques recherches, VMware ne supporte pas le SMP sur les machines virtuelles Windows NT 4.<br />
La VM avait 2 vCPU mais le passage à 1 vCPU ne résout pas pour autant le problème.<br />
<br />
J’ai appris qu’il y avait plusieurs versions de HAL (Hardware Abstraction Layer) et que la VM en question n’utilisé pas la bonne.<br />
<br />
Sur les communautés VMware, il est conseillé de charger la DLL <span style="font-weight: bold;">halapic.dll</span> qui se trouve dans le SP6a de Windows NT4 ainsi que le Kernel <span style="font-weight: bold;">ntoskrnl.exe</span>.<br />
<br />
Après avoir récupérés et copiés ces fichiers dans le répertoire system32 (<span style="font-weight: bold;">ntoskrnl.exe</span> existe peut-être déjà, renommé le fichier copier en<span style="font-weight: bold;"> ntkrnl.exe</span> par ex.), modifier à présent le fichier<span style="font-weight: bold;"> boot.ini</span>.<br />
<br />
Rajouter la ligne en gras :<br />
<br />
[boot loader]<br />
timeout=5<br />
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT<br />
[operating systems]<span style="font-weight: bold;"><br />
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00 VM" /HAL=halapic.dll /KERNEL=ntkrnl.exe /NUMPROC=1</span><br />
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00"<br />
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00 [VGA mode]" /basevideo /sos<br />
<br />
Redémarrer la machine et constater le changement.<span style="font-weight: bold;"><br />
<br />
Sources :</span><br />
<a href="http://communities.vmware.com/thread/37856">http://communities.vmware.com/thread/37856</a><br />
<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;156358&sd=tech">http://support.microsoft.com/default.aspx?scid=kb;en-us;156358&sd=tech</a><br />
<br />
</span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-11765059924388795792009-12-21T10:08:00.030+01:002009-12-21T11:49:02.773+01:00Configuration JumboFrames & Multipathing sur ESXi 4<span style=";font-family:verdana;font-size:85%;" >Et oui, le jumbo frame est supporté sur VMware ESXi 4 pour les VMKernel. Il s'agit d'une bonne nouvelle pour ceux qui ont une baie SAN iSCSI supportant ce type de trame.<br /></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" >Jusqu'à présent le doute régné sur le support ou non de cette techno sur la version all</span><span style=";font-family:verdana;font-size:85%;" >é</span><span style=";font-family:verdana;font-size:85%;" >gée de l'hyperviseur, j'ai retrouvé ce weekend sur un blog des communities VMware l'info qui affirme que c'est possible et supporté contrairement à ce qu'affirme la doc. (<a href="http://blogs.vmware.com/esxi/2009/12/esxi-40-supports-jumbo-frames.html">http://blogs.vmware.com/esxi/2009/12/esxi-40-supports-jumbo-frames.html</a>)</span><span style=";font-family:verdana;font-size:85%;" >.</span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" >Bonne nouvelle, donc, à présent passons à la configuration...</span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" >Pour commencer, il vous faudra VMware vSphere CLI pour pouvoir réaliser la configuration réseau. Oui, la configuration se fait encore en ligne de commande puisque le jumbo frame (MTU 9000) n'est pas configurable via l'interface graphique.</span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><br /><br />IP du serveur ESXi : <span style="font-weight: bold;">192.168.1.10</span></span><span style=";font-family:verdana;font-size:85%;" ><br /><br />Lancer vSphere CLI.<br /><br />Création d'un vSwitch : </span><span style=";font-family:verdana;font-size:85%;" > <span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -a vSwitch1</span></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><br />Activation des jumbo frames sur le switch : <span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -m 9000 vSwitch1</span></span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><br />Affecter les cartes réseaux physiques au vSwitch :</span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -L vmnic4<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -L vmnic5<br /><br /></span></span><span style=";font-family:verdana;font-size:85%;" >Création d'un port group : </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN1" vSwitch1<br /></span><br />Configuration du VMkernel<span style="font-weight: bold;"> </span>(IP + Jumbo Frames): </span><span style="font-weight: bold;font-family:verdana;font-size:85%;" ><br />\bin\esxcfg-v</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >m</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.10 -n 255.255.255.0 -m 9000 "VMkernel SAN1"<br /><br /></span>A l'aide des 2 dernières commande, recréer d'autre VMkernel po</span><span style=";font-family:verdana;font-size:85%;" >ur la gestion du traffic SAN. J'ai 2 cartes Gigabit dédié pour le SAN et je crée en général 6 VMkerne</span><span style=";font-family:verdana;font-size:85%;" >l sur lequel je configure le multipathing. Voici ce que cela donne au niveau networking :</span><span style=";font-family:verdana;font-size:85%;" ><br /><br /></span><span style=";font-family:verdana;font-size:85%;" ><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfDEuLvzOsGmpyNJHjgu5FSLmzwxZWUlOyr8rpmVpc0HytDmMD9YUREye8YAga7HvfJe_PoT6szu-3S3_FGrp575jai14qEoXHFK6V8e_1Duddry1PpXiif25Ed7_N5NDgLehY_IR7p-0W/s1600-h/conf-san.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 172px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfDEuLvzOsGmpyNJHjgu5FSLmzwxZWUlOyr8rpmVpc0HytDmMD9YUREye8YAga7HvfJe_PoT6szu-3S3_FGrp575jai14qEoXHFK6V8e_1Duddry1PpXiif25Ed7_N5NDgLehY_IR7p-0W/s320/conf-san.jpg" alt="" id="BLOGGER_PHOTO_ID_5417620672392951826" border="0" /></a></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN2" vSwitch1</span></span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN3" vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN4" vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN5" vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -A "VMkernel SAN6" vSwitch1</span></span><span style="font-weight: bold;"><br /><br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.11 -n 255.255.255.0 -m 9000 "VMkernel SAN2"</span></span><span style=";font-family:verdana;font-size:85%;" > </span> <span style="font-weight: bold;font-family:verdana;font-size:85%;" ><br />\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.12 -n 255.255.255.0 -m 9000 "VMkernel SAN3"</span></span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.13 -n 2</span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">55.255.255.0 -m 9000 "VMkernel SAN4"</span></span><span style=";font-family:verdana;font-size:85%;" > </span> <span style="font-weight: bold;font-family:verdana;font-size:85%;" ><br />\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.14 -n 255.255.255.0 -m 9000 "VMkernel SAN5"</span></span><span style=";font-family:verdana;font-size:85%;" > </span> <span style="font-weight: bold;font-family:verdana;font-size:85%;" ><br />\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-a -i 10.1.2.15 -n 255.255.255.0 -m 9000 "VMkernel SAN6"</span></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;"><br /></span></span><span style=";font-family:verdana;font-size:85%;" ><br />Ensuite, je désactive une des cartes physiques sur 3 VMkernel et l'autre carte sur les 3 autres</span><span style=";font-family:verdana;font-size:85%;" >.<br />Pour cela : </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;"><br />\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN1" -N vmnic5 vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN2" -N vmnic5 vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN3" -N vmnic5 vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN4" -N vmnic4 vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN5" -N vmnic4 vSwitch1<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -p "VMkernel SAN6" -N vmnic4 vSwitch1</span></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;"><br /></span><span><br />Voici le résultat de la commande : pour le VMkernel SAN1,</span></span><span style=";font-family:verdana;font-size:85%;" ><span> la carte vmnic5 e</span></span><span style=";font-family:verdana;font-size:85%;" ><span>st désactivé.</span></span><span style=";font-family:verdana;font-size:85%;" ><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWg0Yt_mfZ_vRHfY-TRyrZ_fxAbEZ8yV7oFo0_UeNO8AipvARsBk-OOSI3hqBqxISSktV7LINy4kAw9TrWfBpRu9ZhqQrbOYWi8t2HUvS3oox6EMccx8ZWt7p759ZRjhfKosEDpN8eKOFO/s1600-h/conf-san1.jpg"><span style="font-weight: bold;"></span><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 259px; height: 320px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWg0Yt_mfZ_vRHfY-TRyrZ_fxAbEZ8yV7oFo0_UeNO8AipvARsBk-OOSI3hqBqxISSktV7LINy4kAw9TrWfBpRu9ZhqQrbOYWi8t2HUvS3oox6EMccx8ZWt7p759ZRjhfKosEDpN8eKOFO/s320/conf-san1.jpg" alt="" id="BLOGGER_PHOTO_ID_5417630378239659458" border="0" /></a></span><br /><span style=";font-family:verdana;font-size:85%;" > Ensuite on réalise un bind des VMkernel sur l'iSCSI initiator :<br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk2 -d vmhba33</span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk3 -d vmhba33<br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk4 -d vmhba33<br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk5 -d vmhba33<br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk6 -d vmhba33<br /></span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcli.exe --server 192.168.1.10 swiscsi nic add -n vmk7 -d vmhba33</span><br /><br /><span style=";font-family:verdana;font-size:85%;" ><span>Vous retrouverez les infos concernant l'ID du VMkernel et de l'iSCSI initiator via le client v</span></span><span style=";font-family:verdana;font-size:85%;" ><span>Sphere.</span></span><span style=";font-family:verdana;font-size:85%;" ><br /></span><span style=";font-family:verdana;font-size:85%;" ><span><br /></span></span><span style=";font-family:verdana;font-size:85%;" ><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijEmRMDp8eB6xap0NaguswNK7vOIsoevltbX_U2haLl_61j33lq0vIduVRqcTOr7nmm0TcbrokEJv9eV2Er5_2ooe8LYdt6ZFsgL73x3vxAAzzr4byl1mgg0KBaIhBQSHZEIy118HoVGxb/s1600-h/vmkernel.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 125px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijEmRMDp8eB6xap0NaguswNK7vOIsoevltbX_U2haLl_61j33lq0vIduVRqcTOr7nmm0TcbrokEJv9eV2Er5_2ooe8LYdt6ZFsgL73x3vxAAzzr4byl1mgg0KBaIhBQSHZEIy118HoVGxb/s320/vmkernel.jpg" alt="" id="BLOGGER_PHOTO_ID_5417633198471938274" border="0" /></a></span><span style=";font-family:verdana;font-size:85%;" > <a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1lTPwMDobmL00OboFQB-UCM-Sm4H1aqiWPFrRUDyqvVdMzX0wfEWDctkUYOnw4Qm8OS1SPK5FHbjNVL-4yvb8RaSpknNgbXSOAZuGvHIEeojE1B8QjBnfXBQPIEh_H9roCSvLURXYz4mq/s1600-h/iSCSI_init.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 88px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1lTPwMDobmL00OboFQB-UCM-Sm4H1aqiWPFrRUDyqvVdMzX0wfEWDctkUYOnw4Qm8OS1SPK5FHbjNVL-4yvb8RaSpknNgbXSOAZuGvHIEeojE1B8QjBnfXBQPIEh_H9roCSvLURXYz4mq/s320/iSCSI_init.jpg" alt="" id="BLOGGER_PHOTO_ID_5417633993783979458" border="0" /></a></span><span style=";font-family:verdana;font-size:85%;" > Aprés ces opérations, vous pouvez vérifier la configuration à l'aide des commandes suivantes :<br />Pour vérifier le vSwitch : </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">\bin\esxcfg-vswitch.pl --server 192.168.1.10 -l</span></span><span style=";font-family:verdana;font-size:85%;" ><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBJ5mlVJVouqaYSTtu1A8HxG-ATALsA7fAQwsIV4-CnSTquN2PaoJHqsccJTZioBJlSbZr6iTTVGjpSvdM3We8H3WuJK5bCVyQ9yJVpDtB52cxHcSrYKVZjuw3xKrnlCL-9UEQPGNcRU6y/s1600-h/conf-vswitch.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 258px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjBJ5mlVJVouqaYSTtu1A8HxG-ATALsA7fAQwsIV4-CnSTquN2PaoJHqsccJTZioBJlSbZr6iTTVGjpSvdM3We8H3WuJK5bCVyQ9yJVpDtB52cxHcSrYKVZjuw3xKrnlCL-9UEQPGNcRU6y/s320/conf-vswitch.jpg" alt="" id="BLOGGER_PHOTO_ID_5417636740723747730" border="0" /></a><br /></span><span style=";font-family:verdana;font-size:85%;" > Pour vérifier les VMkernel : </span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >\bin\esxcfg-vm</span><span style="font-weight: bold;font-family:verdana;font-size:85%;" >knic.pl --server 192.168.1.10 </span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">-l</span></span><span style=";font-family:verdana;font-size:85%;" ><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi38duUS4LtiwCcmNmqG2X6UXM1aOnHbC0mA39OTG3U_e3jauROgnSavHul5NJymeYrkXul6CZ4AZ549glCVupWNhUXCACOrz5VFd0eJCQuDyW8w1mCYnKxiekVSWrcfgHBWR-Pz0ZpAg_o/s1600-h/conf-vmkernel.png"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 177px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi38duUS4LtiwCcmNmqG2X6UXM1aOnHbC0mA39OTG3U_e3jauROgnSavHul5NJymeYrkXul6CZ4AZ549glCVupWNhUXCACOrz5VFd0eJCQuDyW8w1mCYnKxiekVSWrcfgHBWR-Pz0ZpAg_o/s320/conf-vmkernel.png" alt="" id="BLOGGER_PHOTO_ID_5417637073133009090" border="0" /></a><br /></span><span style=";font-family:verdana;font-size:85%;" ><span>Il ne reste plus qu'à configurer l'iSCSI initiator pour l'accès à la baie SAN.<br /></span></span><span style=";font-family:verdana;font-size:85%;" ><img src="file:///C:/Users/NS-GDA/AppData/Local/Temp/moz-screenshot.png" alt="" /><img src="file:///C:/Users/NS-GDA/AppData/Local/Temp/moz-screenshot-1.png" alt="" /></span> <span style=";font-family:verdana;font-size:85%;" > </span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-63633894375851788722009-03-21T21:31:00.007+01:002009-05-10T12:21:21.493+02:00Alignement de blocS'il y a une opération à réaliser sur vos machines virtuelles afin d'accroitre les performances en I/O c'est bien l'alignement de bloc.<br /><br />En effet, l'alignement de bloc permet d'économiser quelques étapes de lecture/écriture de données sur le disques.<br /><br />Je vous propose deux sites, bien détaillé ou vous trouvez les explications sur le pourquoi faut-il faire ces modifications et le comment.<br /><br />Site 1 : <a href="http://www.boche.net/blog/index.php/2009/03/20/storage-block-size-and-alignment/">Jason Boche</a><br />Site 2 : <a href="http://viops.vmware.com/home/docs/DOC-1407">Viops</a><br /><br />Pour ceux qui tenterai d'aligner les partitions de ces VMs, il n'est possible de réaliser ceci que sur un disque vierge (enfin vous perdrez les infos qui sont dessus) et pour faire cela sur un disque système, il faut le faire avant l'installation de l'OS. Pour cela j'utilise un CD winpe qui me permet d'exécuter diskpart sur la partition avant l'installation de mon OS ou vous pouvez rattacher votre futur disque système à une VM Windows et faire les opérations.Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-86549875275282181312009-03-20T09:02:00.007+01:002009-03-21T21:28:48.205+01:00Installer VMware Tools - Windows 2008 R2<span style="font-family: verdana;font-size:180%;" ><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOcBqTizSnUWMQ3Sq1O8nJb4kII4x8d5IthdktoqmvTGyx5W4Q_3wnj4y2Q2xPbQ5dnwqMEiNev6_JWCTI9x1BJx6HCmwUySrVuSOyaIT5QlPQTh5g6rEsN9DTdokHDmQBZEdn7WHcSPi2/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5315739011777169122" border="0" /></a><br /></span><div style="font-family: verdana;font-family:verdana;" class="entry-body"><div><div class="item-body"><div><pre style="font-family:verdana;"><span style="font-size:180%;"><br /><br /></span><span style="font-family: verdana;font-size:85%;" ><span style="font-weight: bold; font-style: italic;"><br /></span></span><span style="font-family: verdana;font-size:85%;" ><span><span><span style="">En mode Core, WoW64 (Windows over Windows) est devenu une option, cette fonctionnalité n'est plus installé par défaut.<br />Elle permet le support des applications 32 bits sous les OS 64 bits.<br /><br />Pour installer WoW64 :<br /></span></span></span></span><span style="font-family: verdana;font-size:85%;" ><br /></span><span style="font-family: verdana;font-size:85%;" ><span style="font-weight: bold; font-style: italic;">C:\Users\Administrator>start /w ocsetup ServerCore-WOW64<br /></span><br /></span><span style="font-family: verdana;font-size:85%;" >Vous devez redémarrer le système pour activer la fonctionnalité.<br /></span><span style="font-family: verdana;font-size:85%;" >Après le redémarrage, vous pourrez installer VMware Tools sans problème.</span><span style="font-size:180%;"><br /></span></pre><span style="font-size:180%;"></span></div></div></div></div>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-74572767528412457362009-03-19T17:16:00.012+01:002009-03-21T21:29:14.936+01:00Mise à jour serveur ESXi - Retour en arrière<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlzgI4H7mPELP7srGY1NW8qoTupfIVayWCODw9Q0RwsBDgqTxDVzEd7lUcfpju_CtXBPACsevFNcWdB1AhvJa6Fpc6ma1nu7ClaM9FAQq54rmFtGdBIWuJSzX8XmKVMSAw7ey08y1477dA/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5315735312249130962" border="0" /></a><span style="font-size:85%;"><span style="font-family:verdana;"><br />La mise à jour d'un serveur peut, dans certains cas, apporter son lot de problème.<br /><br />Si cela vous arrive, vous pouvez toujours revenir à la v</span></span><span style="font-size:85%;"><span style="font-family:verdana;">ersion précédent l'application du patch.<br /><br />Pour revenir en arrière, vous devez redémarrer la machine. Quand la barre blanche de chargement apparait appuyer sur les touches <span style="font-weight: bold;">SHIFT+R</span>.<br /><br /></span></span><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyaEv7gMlunxw9lQoPNeNWNFQ3bBMPi052T2wt9foz0ApVPTH2HI1K0OhLY2aXlIv-WcpJQh534T95efjFi2DjzGlrQEoEwpUyVO5LgseRM5d2TRt0r9em3tAeLe2unuOTp_B6YzhJ5Xo-/s1600-h/searchVMware_siebert_ESXi_12.png"><img style="cursor: pointer; width: 320px; height: 200px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiyaEv7gMlunxw9lQoPNeNWNFQ3bBMPi052T2wt9foz0ApVPTH2HI1K0OhLY2aXlIv-WcpJQh534T95efjFi2DjzGlrQEoEwpUyVO5LgseRM5d2TRt0r9em3tAeLe2unuOTp_B6YzhJ5Xo-/s320/searchVMware_siebert_ESXi_12.png" alt="" id="BLOGGER_PHOTO_ID_5315734922738875170" border="0" /></a><br /><br /><span style="font-size:85%;"><span style="font-family:verdana;">Un message d'avertissement apparait, vous prévenant que vous allez remplacer votre version par une version plus ancienne. Appuyer sur la touche </span><span style="font-weight: bold;font-family:verdana;" >Y</span><span style="font-family:verdana;"> pour accepter.</span></span><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjypdCeNHv1zoiOFL81nguVA5a5tPAK5bXPcYVQXulpkZdaxxzfy2NR0R0gwAcoxSfoSQ9iBlfnvVXiktYyUKyxcaA2ZdgKHrUuMSHwfEem5YJ-ajcbfg4xfTH_TJgFF4JDy-7u5roIomQz/s1600-h/searchVMware_siebert_ESXi_13.png"><img style="cursor: pointer; width: 320px; height: 200px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjypdCeNHv1zoiOFL81nguVA5a5tPAK5bXPcYVQXulpkZdaxxzfy2NR0R0gwAcoxSfoSQ9iBlfnvVXiktYyUKyxcaA2ZdgKHrUuMSHwfEem5YJ-ajcbfg4xfTH_TJgFF4JDy-7u5roIomQz/s320/searchVMware_siebert_ESXi_13.png" alt="" id="BLOGGER_PHOTO_ID_5315734987156350210" border="0" /></a><br /><br /><span style="font-size:85%;"><span style="font-family:verdana;">Appuyer sur la touche </span><span style="font-weight: bold;font-family:verdana;" >Entrée</span><span style="font-family:verdana;">.</span></span><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhR6jpgkNMEB0gvOS75xWHF5pEBIm2lfZ1j8QzQVoUlU9BIk4EkyjNix27O3tkBnNnmxIT4XjCCcX-b9PMG52KoAlDzkFx59QsaREh1Q1pnCbBpNVCIc0b1Xjw5GNc65ajeMjey-ni-ffHx/s1600-h/searchVMware_siebert_ESXi_14.png"><img style="cursor: pointer; width: 320px; height: 200px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhR6jpgkNMEB0gvOS75xWHF5pEBIm2lfZ1j8QzQVoUlU9BIk4EkyjNix27O3tkBnNnmxIT4XjCCcX-b9PMG52KoAlDzkFx59QsaREh1Q1pnCbBpNVCIc0b1Xjw5GNc65ajeMjey-ni-ffHx/s320/searchVMware_siebert_ESXi_14.png" alt="" id="BLOGGER_PHOTO_ID_5315735035490140530" border="0" /></a><br /><br /><span style=";font-family:verdana;font-size:85%;" >Voila votre serveur ESXi tourne avec la version antérieur à la mise à jour.<br /></span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-81974727281370830712009-03-19T14:15:00.022+01:002009-03-23T08:53:09.373+01:00Mise à jour serveur ESXi<span style=";font-family:verdana;font-size:85%;" ><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNwOK3jbbjmqgO2k3fcU6DDdq6vtApzvQWexHnhGF0YzCrtZRDJKWAUdYglxzULLwt9l7iwhNHqDA2NNXjBsJxWWXpYvQ8t2zMkM6UUuimI3Iy6QsoTOkZBDTrcDxSig2ms9zZd5Ocbrgy/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5314887122614432146" border="0" /></a><br /><br />Voici les différentes étapes pour mettre à jour votre serveur VMware ESXi.<br /></span><br /><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;"><br />1ere étape - RCLI</span><br />Il vous faut <span style="font-weight: bold;">VMware Remote Client (RCLI)</span> sur votre machine.<br />Vous pouvez le télécharger <a href="http://www.vmware.com/download/download.do?downloadGroup=VI-RCLI-U2">ici</a> et la documentation <a href="http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf">ici</a>.<br /></span><br /><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">2eme étape - Download</span></span><br /><span style=";font-family:verdana;font-size:85%;" >Récupérer les derniers updates pour votre serveur <a href="http://support.vmware.com/selfsupport/download/">ici</a>.<br /><br /><span style="font-weight: bold;">3eme étape - Update</span></span><br /><span style=";font-family:verdana;font-size:85%;" ><br />Lancer la <span style="font-weight: bold;">console RCLI</span> ou dans un invite de commande taper : <span style="font-weight: bold;">cd "C:\Program Files\VMware\VMware VI Remote CLI"</span>. (Répertoire d'installation par défaut)</span><span style=";font-family:verdana;font-size:85%;" ><br /><br />Aller dans le répertoire <span style="font-weight: bold;">bin.</span><br /><br /></span><a style="font-family: verdana;" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhar276HVBcTs6zVnWRar2MjafgjEz4Dq-xXUAkSm605qf-AsiWnZwo8WoShuoWeGSk4fwRENiAfHwvVc485Abtpu6OkHpYNRKv3Qjti5GdGLKCdfT4S7GlUxxREW0jTSZt7rqw9utoLa_x/s1600-h/screen1.png"><img style="cursor: pointer; width: 320px; height: 165px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhar276HVBcTs6zVnWRar2MjafgjEz4Dq-xXUAkSm605qf-AsiWnZwo8WoShuoWeGSk4fwRENiAfHwvVc485Abtpu6OkHpYNRKv3Qjti5GdGLKCdfT4S7GlUxxREW0jTSZt7rqw9utoLa_x/s320/screen1.png" alt="" id="BLOGGER_PHOTO_ID_5314917694123653570" border="0" /></a><br /><br /><span style=";font-family:verdana;font-size:85%;" >Lancer la commande <span style="font-weight: bold;">vihostupdate.pl</span>...<br /><span style="font-family:verdana;">Syntax :</span></span><span style=";font-family:verdana;font-size:85%;" > </span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span class="a3"><pre>vihostupdate.pl –server [serveur name or ip] <server>-username [username]<root> -password <user>[password] -i –b [filename]<update></update></user></root></server></pre></span><server name="" or="" ip=""><servername or="" ip=""><root or="" other="" user=""><username><user password=""><password><filename></filename></password></user></username></root></servername></server><server name="" or="" ip=""><servername or="" ip=""><root or="" other="" user=""><username><user password=""><password><filename></filename></password></user><span style="font-family:verdana;"><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiY9A2MJHU8LSPZuqmXD09x5Jh0IeYwtO8wg-hZ1Mv7D_-mnNYOqo6gtsyl3wWvaDHrekW5nbIT0w79XCIn3vB66PEVqGvbdkcV2WJsyf4EzwcZgVuWPFK_TkHWfJ635I6Kms4sq3w7CR9u/s1600-h/screen2.png"><img style="cursor: pointer; width: 320px; height: 165px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiY9A2MJHU8LSPZuqmXD09x5Jh0IeYwtO8wg-hZ1Mv7D_-mnNYOqo6gtsyl3wWvaDHrekW5nbIT0w79XCIn3vB66PEVqGvbdkcV2WJsyf4EzwcZgVuWPFK_TkHWfJ635I6Kms4sq3w7CR9u/s320/screen2.png" alt="" id="BLOGGER_PHOTO_ID_5314919330626502834" border="0" /></a></pre></span></span></span></span></pre></span></span></span></span></pre></span></span></span>Le script va décompresser le fichier ZIP, le copier sur le serveur, l'installer et enfin redémarrer le serveur.<br />Une fois la mise à jour terminée, on vous invite à redémarrer le serveur ESXi. Pour cela taper <span style="font-weight: bold; font-style: italic;">yes</span>.<br /></span></username></root></servername></server><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span style="font-family:verdana;"><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjpf0960LVzC6XWDn1fFvjnb1MsPrfE7jpLYJDEQ2qRUytLCvZG9YT9kJizatgipP1toaxPmk6BoDlyhOF-RFPxBt-QO41ZGBHmMir3yBM7__B6ckZbH9CWFCHs3dul8CFzpmRXfXKpvKoS/s1600-h/screen3.png"><img style="cursor: pointer; width: 320px; height: 182px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjpf0960LVzC6XWDn1fFvjnb1MsPrfE7jpLYJDEQ2qRUytLCvZG9YT9kJizatgipP1toaxPmk6BoDlyhOF-RFPxBt-QO41ZGBHmMir3yBM7__B6ckZbH9CWFCHs3dul8CFzpmRXfXKpvKoS/s320/screen3.png" alt="" id="BLOGGER_PHOTO_ID_5314920280532649810" border="0" /></a></pre></span></span></span></span></pre></span></span></span></span></pre></span></span></span></span></pre></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span><span style=";font-family:verdana;font-size:85%;" ><span style="font-weight: bold;">4eme étape - Vérification</span></span><br /><server name="" or="" ip=""><servername or="" ip=""><root or="" other="" user=""><username><span style="font-family:verdana;"><br />Vérifier la versio</span><span style="font-family:verdana;">n du patch installé...<br />Syntax :<br /></span></username></root></servername></server><span class="a3"><pre>vihostupdate.pl –server [serveur name or ip]<server> -username [username]<root></root></server><server> -password [password] –q<br /></server></pre></span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span><span><span><span><span><span><span><span><span><span><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span style="font-family:verdana;"><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><span class="a3"><pre><pre><span><span><span style=";font-family:verdana;font-size:100%;" ><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPWtaGP89cTEqKvu5EUeIXmnFWdjWID7927F_VXD9fD_qHERBEmex7YOXzQnTWxLMxJCcYeCF8uGQW9DzoYmBAR6IAuaWXq7etCF8wDsOhGQsiTsxCv6xMwZZkLlsxBfPZ37dwegoNK1VB/s1600-h/screen4.png"><span class="a3"><img style="cursor: pointer; width: 320px; height: 182px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPWtaGP89cTEqKvu5EUeIXmnFWdjWID7927F_VXD9fD_qHERBEmex7YOXzQnTWxLMxJCcYeCF8uGQW9DzoYmBAR6IAuaWXq7etCF8wDsOhGQsiTsxCv6xMwZZkLlsxBfPZ37dwegoNK1VB/s320/screen4.png" alt="" id="BLOGGER_PHOTO_ID_5314920521852067778" border="0" /></span></a><br /><span style="font-size:85%;"><br />Voila, le serveur ESXi est maintenant à jour.<br /><br /></span></span></span></span></pre></pre></span></span></span></span></pre></span></span></span></span></pre></span></span></span></span></pre></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></pre></span></span></pre></span></span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-51809443400450424532009-03-19T09:25:00.019+01:002009-03-21T21:46:47.848+01:00Activer SSH sur VMware ESXi<a><span style="font-size:85%;"></span></a><span style="font-size:85%;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBpsgzu9Xyac-Sip9XRAriQ6tzifur8M9WXpSMoRfpg5bUo9H0O2guXprbLg7gFnQRXd2sKjJifgKHoGzGm8cvek2qJT1Xzv0P3vhFi7iLolSmrsSmUt35VkSE8PiqVajOe7I5geeElKUU/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5314812585628259058" border="0" /></a> </span><span style=";font-family:verdana;font-size:85%;" ><br />J'ai vu pas mal de chose à ce sujet sur d'autres blogs ou forum mais je trouve que leurs explications ne sont pas clair ou alors il y a des étapes inutiles.</span><br /><span style=";font-family:verdana;font-size:85%;" ><br /><br />Pour ma part, j'ai réalisé les actions suivantes sur un serveur ESXi Update 3 :</span><span style=";font-family:verdana;font-size:85%;" ><br /></span><ul style="font-family:verdana;"><li><span style="font-size:85%;">Sur le serveur ESXi, taper <span style="font-style: italic; font-weight: bold;">Alt+F1</span>.</span></li><li><span style="font-size:85%;">Taper <span style="font-style: italic; font-weight: bold;">unsupported</span> dans la console.</span></li><li><span style="font-size:85%;">Au prompt saisir le <span style="font-weight: bold; font-style: italic;">mot de passe root</span> du serveur.</span></li><li><span style="font-size:85%;">Ensuite taper la </span><span style="font-size:85%;">commande suivante : <span style="font-weight: bold; font-style: italic;">vi /etc/inetd.conf</span></span></li><li><span style="font-size:85%;">Rechercher la ligne dans le fichier commençant par <span style="font-weight: bold; font-style: italic;">#ssh</span> ; Pour cela taper <span style="font-weight: bold; font-style: italic;">/ssh</span> puis <span style="font-weight: bold; font-style: italic;">Entrée</span>.</span></li><li><span style="font-size:85%;">Appuyer sur la touche <span style="font-weight: bold; font-style: italic;">Inser</span> et supprimer le caractère <span style="font-style: italic; font-weight: bold;">#</span>.</span></li><li><span style="font-size:85%;">Pour quitter <span style="font-weight: bold; font-style: italic;">vi</span>, appuyer sur <span style="font-weight: bold; font-style: italic;">Echap</span> et taper <span style="font-style: italic; font-weight: bold;">:wq!</span>.</span></li><li><span style="font-size:85%;">Maintenant il faut redémarrer le service <span style="font-weight: bold; font-style: italic;">inetd</span>. Pour cela taper <span style="font-weight: bold; font-style: italic;">/etc/services.sh restart inetd</span></span></li></ul><span style="font-size:85%;"><span style="font-family:verdana;">Voila, à présent vous pouvez vous connecter à votre serveur ESXi en SSH. </span> <span style="font-family:verdana;"> <span style="font-family:verdana;"><br />Autre chose, si vous n'arrivez pas à rentrer dans le mode <span style="font-weight: bold; font-style: italic;">unsupported</span>, vous devez réaliser les étapes suivantes pour que cela fonctionne.</span> </span></span><ul style="font-family:verdana;"><li><span style="font-size:85%;">Connecter vous au serveur ESXi avec <span style="font-style: italic; font-weight: bold;">VI Client</span>.</span></li><li><span style="font-size:85%;">Cliquer sur le serveur ESXi et cliquer ensuite sur l'onglet <span style="font-style: italic; font-weight: bold;">Configuration</span>.</span></li><li><span style="font-size:85%;">Ensuite dans l'encadrer S</span><span style="font-size:85%;">oftware cliquer sur <span style="font-style: italic; font-weight: bold;">Advanced Settings</span>.</span></li><li><span style="font-size:85%;">Dans <span style="font-style: italic; font-weight: bold;">VMkernel</span> cocher la case <span style="font-style: italic; font-weight: bold;">VMkernel.boot.techSupportMod</span></span><span style="font-size:85%;"><span style="font-style: italic; font-weight: bold;">e</span>.</span></li><li><span style="font-size:85%;">Rédémarrer le serveur ESXi.</span></li></ul><span style="font-size:85%;"><span style="font-family:verdana;"><span style="font-weight: bold;"><br /></span></span></span><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoFFJKFoDFcqQVKh-wpi9iNdLp6onKGqubxiuuRonx6NZeKTV3QD6ZcTlH4dglHtpKL_15H4oXvPWWCHaqD2xNUERh-K37PiJ0JYm61BMV7kLV1FdTYl6Ja3-a023buvrLHUPZvsXVlX_y/s1600-h/Screenshot+-+19_03_2009+,+13_28_49.jpg"><img style="cursor: pointer; width: 320px; height: 260px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoFFJKFoDFcqQVKh-wpi9iNdLp6onKGqubxiuuRonx6NZeKTV3QD6ZcTlH4dglHtpKL_15H4oXvPWWCHaqD2xNUERh-K37PiJ0JYm61BMV7kLV1FdTYl6Ja3-a023buvrLHUPZvsXVlX_y/s320/Screenshot+-+19_03_2009+,+13_28_49.jpg" alt="" id="BLOGGER_PHOTO_ID_5314875680067312210" border="0" /></a> <a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizlQbhT0ig5WwqkSwXFGTcFyh97e5YsGFo2xD7-nnvQ-RNMi3-vduv7p2DB9NMYTOoSVm76uPK-u_u6_ZxSGIuDeVjAgvSPIKtuGSicwBSTTXms6hnD4iKv-cZe_NxT5oVB2X6TTdvNLww/s1600-h/Screenshot+-+19_03_2009+,+13_31_11.jpg"><img style="cursor: pointer; width: 320px; height: 213px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEizlQbhT0ig5WwqkSwXFGTcFyh97e5YsGFo2xD7-nnvQ-RNMi3-vduv7p2DB9NMYTOoSVm76uPK-u_u6_ZxSGIuDeVjAgvSPIKtuGSicwBSTTXms6hnD4iKv-cZe_NxT5oVB2X6TTdvNLww/s320/Screenshot+-+19_03_2009+,+13_31_11.jpg" alt="" id="BLOGGER_PHOTO_ID_5314875829655631634" border="0" /></a><br /><span style="font-size:85%;"><span style="font-family:verdana;"><span style="font-weight: bold;"><br />Remarque</span> : Avant d'arrêter le serveur ESXi, n'oubliez pas d'éteindre les machines virtuelles qui tournent dessus.<br /><br /></span></span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-24242629228676572522009-03-16T12:59:00.009+01:002009-03-21T21:47:05.008+01:00VMware vLaunchPad<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgpYa3pRb7sOhI-3x9LwmAUHm6wd4wG8fhDvlPpft69Y5XbtjyoeldfksCGoPp6IVc9G7h_5-3NcFDcezDbQ6p2Oun1MliP6iMUpoD16zxdAw3TwYPsAnO5Q5cqbrzqVszZbnwaLiMIthRR/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5313775345562342498" border="0" /></a><br /><span style="text-decoration: underline;"><span style="font-size:85%;"><span style="font-family:verdana;"><span style="font-weight: bold;"></span></span></span></span><br /><br /><br /><br /><br /><a href="http://www.vmware-land.com/">Eric Sieberg</a> à mis en ligne un nouveau vLaunchPad. Très pratique, il regroupe différents liens vers des sites de la communauté VMware.<br />C'est par ici :<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://vlp.vmware-land.com/"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 28px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhogdguVTqGvWuNfz5q_sv4ykViBGB0MMnGFzAo2nkuenLN9z45KzH53g1GEIuy92NXAMGNOGmSJtAuNovfbSzmjYDcCekhpk3quSywaq3Cx-V_9sbUWpVw6vyRJkhs-kyXWbDIxl9CUD4h/s320/screenshot.jpg" alt="" id="BLOGGER_PHOTO_ID_5313754246547350306" border="0" /></a>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-76508967392609955062009-03-11T09:36:00.010+01:002009-03-21T21:47:20.799+01:00Différence entre VMFS et RDM<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.vmware.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYpP-1hu-2HrtO69XPVz6ndUyQibYb4bCUSJptS2lrq25fkxj1coHEITU6fH-xxsgA_sP__VPw3nOcrbZZNDAzoTUZb_nMzqUkTCQewX90jz5qmDYjXAvDa_LmKW4BX35_uhF-R5OUpysn/s320/vmware.gif" alt="" id="BLOGGER_PHOTO_ID_5311850278485524578" border="0" /></a><br /><div class="entry-body"><div><div class="item-body"><div><p style="font-family:verdana;"><span style="font-size:85%;"><br /></span></p><p style="font-family:verdana;"><span style="font-size:85%;"><br /></span></p><p style="font-family:verdana;"><span style="font-size:85%;">Le système de virtualisation VMware ESX permet l’utilisation de plusieurs types de stockage en environnement SAN basé sur le protocole Fiber Channel ou iSCSI:</span></p> <ul style="font-family:verdana;"><li><span style="font-size:85%;"><span style="font-weight: bold;">V</span>irtual <span style="font-weight: bold;">M</span>achine <span style="font-weight: bold;">F</span>ile <span style="font-weight: bold;">S</span>ystem :<br /></span></li></ul> <blockquote style="font-family:verdana;"><p><span style="font-size:85%;">C’est un système de fichiers spécifique permettant de stocker des fichiers pour les machines virtuelles. VMFS est optimisé afin de pouvoir gérer l’exécution de plusieurs machines virtuelles en une seule charge de travail. Il fournit aussi une gestion distribuée des verrouillages de fichiers afin de permettre à plusieurs hôtes VMware ESX de partager des LUNs sur un SAN. Un volume VMFS peut être étendu sur 32 extensions de stockage d’un même type. Il est possible d’étendre un volume VMFS lorsque des machines virtuelles sont en cours d’exécution sur ce même volume. Dans une configuration simple, les disques des machines virtuelles sont stockés sous forme de fichiers VMDK dans un datastore VMFS.</span></p></blockquote> <ul style="font-family:verdana;"><li><span style="font-size:85%;"><span style="font-weight: bold;">R</span>aw <span style="font-weight: bold;">D</span>evice <span style="font-weight: bold;">M</span>apping :<br /></span></li></ul> <blockquote style="font-family:verdana;"><p><span style="font-size:85%;">Un RDM est un fichier spécial dans un volume VMFS qui intervient comme un proxy pour un “RAW device” (portion de disque ne contenant pas de système de fichier). Les RDMs fournissent certains des avantages des disques virtuels stockés dans un volume VMFS tout en conservant certains avantages de l’accès direct au disque physique. De manière générale, l’utilisation de RDM est recommandée quand une machine virtuelle doit interagir directement avec un disque physique sur le SAN.</span></p></blockquote></div></div></div></div>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0tag:blogger.com,1999:blog-655734497889024961.post-7242883119519901432009-03-11T09:21:00.009+01:002009-03-11T09:56:54.109+01:00Veeam FastSCP 3.0<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.veeam.com/"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 190px; height: 70px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirHxtbq-LHq-EVLUabnKvUNqiEISWHteqichFMOh-txBE3VJM0pRC4Vh0QJrq8nuMz7KaB0GGZLcuK52_ZjVF1_i0m-0IBUZkvCJKvdFmZkeZVtLqD0Bo3AdpNk9vtakgGv-I33oSLFGAP/s320/veeam.gif" alt="" id="BLOGGER_PHOTO_ID_5311842815901083554" border="0" /></a><br /><span style="font-size:85%;"><span style="font-family:verdana;">Au début du mois, Veeam à sortie la 3eme version de son logiciel FastSCP qui supporte enfin l'hyperviseur gratuit de VMware... ESXi.<br /><br />Ce logiciel permet de copier des fichiers de son poste vers un datastore de l'hôte ou d'un serveur hôte vers un autre.</span> <span style="font-family:verdana;">Vous aller me dire que cela était déjà possible auparavant et sans produit. Mais FastSCP permet de transfèrer plus rapidement que via le SCP de ESX.<br />Autre avantage, le schedule des copies de fichier est possible.</span><span style="font-family:verdana;"><br /><br />Il supporte également Virtual Center ce qui facilite le paramétrage du logiciel pour l'ajout des serveurs.<br /><br /></span></span><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXZSNrIsXPYJ1Omiaez4V9GnzD15B0DNNMGteUqqqChml0GwX5zlJrgCZGRFY85z9pgF9a7MyLfUn4ttxf6T0fsTmajLpxeULc4eT3zdyeX7blP9AXLlhJtuAAXAAwHIslD7hnvgwZfvSm/s1600-h/screenshot_fastscp2.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 218px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXZSNrIsXPYJ1Omiaez4V9GnzD15B0DNNMGteUqqqChml0GwX5zlJrgCZGRFY85z9pgF9a7MyLfUn4ttxf6T0fsTmajLpxeULc4eT3zdyeX7blP9AXLlhJtuAAXAAwHIslD7hnvgwZfvSm/s320/screenshot_fastscp2.jpg" alt="" id="BLOGGER_PHOTO_ID_5311845758821066658" border="0" /></a><br /><span style="font-size:85%;"><span style="font-family:verdana;"> </span> <span style="font-family:verdana;">Ce produit est gratuit et disponible en téléchargement </span><a style="font-family: verdana;" href="http://www.veeam.com/esx-fastscp.html">ici</a><span style="font-family:verdana;">.</span></span>Gilbert De Almeidahttp://www.blogger.com/profile/05001597602296686483noreply@blogger.com0