background preloader

ESXI

Facebook Twitter

TUTO: NAS SYNOLOGY DSM 5 SUR SERVEUR HP N54L. Vous cherchez un NAS pour stocker vos données en réseau, vous devez installer plusieurs disques durs dedans ou vous avez besoin d’une solution évolutive.

TUTO: NAS SYNOLOGY DSM 5 SUR SERVEUR HP N54L

Les NAS Synology, dont la réputation n’est plus à faire, s’avèrent rapidement onéreux, dès lors qu’ils possèdent plusieurs baies de stockage. La solution proposée ici se révèle assez économique. En effet, HP propose un produit très complet, à prix compétitif, le presque célèbre serveur HP N54L , dont la référence complète est « HP ProLiant MicroServer G7 N54L 1P 2GB-U Non-hot Plug SATA 250GB 150W PS Server« ESXi 5.1: Using Raw Device Mappings (RDM) on an HP Microserver. Having some spare time on my hands I decided to investigate the performance differences between presenting local storage as a Raw Device Mapping (RDM) and as a VMFS formatted datastore on my testbed server at home.

ESXi 5.1: Using Raw Device Mappings (RDM) on an HP Microserver

The server and disk specifications are as follows: HP Microserver N36L8GB RAM1 x 250GB HDD, 2 x 1TB HDD in use within VMFS5 formatted datastoresAn HP 500GB 7200RPM SATA Disk mounted in slot 4 of the Microserver.WHS 2011 as the only virtual machine installed.vSphere Hypervisor 5.1 (free) Creating the RDM passthrough for unsupported hardware/scenarios required a bit of a hack using the command line. Here’s how I did it (using this article from David Warburton as a guide. Thanks David!) Utiliser un disque en Raw Device Mapping (RDM) pour Xpenology.

Suite à mon dernier article sur l’installation des VmWare tools sur la VM Xpenology, un lecteur m’a rapporté en commentaire quelques soucis pour intégrer un disque en RDM.

Utiliser un disque en Raw Device Mapping (RDM) pour Xpenology

Comme je ne m’étais pas fait de doc, c’est l’occasion de me rappeler la procédure. Le fait d’intégrer des disques en RDM permet d’obtenir les performances maximales sur les disques attachés à une VM Pour rappel, voici ma configuration : V-Front VIBSDepot Wiki. Creating RDMs on SATA drives. [Home] [Forum] ESXi provides the ability to use raw device mapping (RDM) as a method to provide a VM with direct access to a LUN on a Fibre CHannel or iSCSI storage device.

Creating RDMs on SATA drives

RDMs are useful should you have to share a LUN with a physical server or have SAN utilities running in the VM that will be able to access the LUN directly. You can also use a RDM to provide a VM direct access to a local SATA drive that is connected a SATA controller. This method was first posted by Mário Simões in the forums here as a method to run RAID 5 in a VM on a SATA controller that did not support RAID.

This method would also be useful for importing data from existing servers, but one should note that this is not officially supported. 1) The first step of the process is to determine the disk that you'll want to use for the RDM. . ~ # fdisk -l Device Boot Start End Blocks Id System 2) The next step is to run the command ls /dev/disks/ -l. 3) To create the RDM you'll use the command vmkfstools. Practical ways to deal with VMware ESXi 5.0′s 2TB virtual disk size limitation. Recently ruderthanyou posted some intriguing comments: on The reasoning behind vZilla’s storage configuration yesterday:I have a ESXi 5 whitebox build very similar to yours.

Practical ways to deal with VMware ESXi 5.0′s 2TB virtual disk size limitation

I’ve recently run into this 2TB limit for vmdk’s and this post interested me greatly. I have 5x3TB Hitachi Coolspins in an 11TB array. I wanted to present a 8TB vmdk to my sbs2011e guest.. Took me a few times reading this post to understand, but it doesn’t appear that you’re presenting any of the 7TB vmfs as a >2TB vmdk to your guest OS. I’m glad I potentially helped your marriage, who’d think storage talk could possibly do such a thing ;-). Hopefully a picture really is worth a thousand words. Soon, I’d like to do a deeper drive article on RDM mappings, similar to the recent post about configuring USB 3.0 passthrough at tinkertry.com/usb3passthru. Can vCenter’s Storage Migration actually work with such RDMs? Jan 07 2012 Update: It works! ESXi 5.1: Using Raw Device Mappings (RDM) on an HP Microserver. Virtual Datacenter with vSphere 5.1. Part 1: Install and configure the ESXi Host(s)-1533 - Xylos.

Installer VMware vSphere ESXi 5.1 sur serveur HP ProLiant N54L et créer une VM Synology (DSM 4.2) avec XPenology. En ce moment (24/01/2014), Super bon plan: Micro Serveur HP Proliant G7 N54L à 159€ ttcPlus d'informations sur dealabs.com Tuto : Installation VMware vSphere ESXi 5.1 sur serveur HP ProLiant N54L et création d'une machine virtuelle : Serveur Synology (DSM 4.2 et 4.3) avec distrib XPenology Pré-requis - Mémoire: Le serveur HP Proliant N54L est vendu avec une RAM de 2Go que l'on doit étendre 4 Go ou plus pour faire tourner ESXi et ses machines virtuelles. - Une clé USB 2.0 d'au moins 2Go - Créer un compte sur le site de WMware pour obtenir une licence gratuite d'essai à 60 jours , puis après installation de ESXi , faire une demande de licence définitive à vie - licence sans support bien sûre !

Installer VMware vSphere ESXi 5.1 sur serveur HP ProLiant N54L et créer une VM Synology (DSM 4.2) avec XPenology

Sinon c'est payant ... tarifs ici : Restriction de la licence gratuite : - Votre système hôte doit avoir 32go de ram physique au maximum - Cette licence ne donne pas accès au support Vmware - Cette licence comprend donc uniquement l’hyperviseur en lui-même. Puis cliquez sur Modifier ... VMware Front Experience: How to make your unsupported SATA AHCI Controller work with ESXi 5.5. In ESXi 5.5 VMware removed driver support not only for some commodity network cards, but also for lots of SATA controllers that have never been on the HCL, but worked fine with the generic ahci driver of ESXi 5.0 and 5.1 (provided that they support and are configured for AHCI mode).

VMware Front Experience: How to make your unsupported SATA AHCI Controller work with ESXi 5.5

For the NICs the problem could easily be solved by using the old ESXi 5.1 drivers with ESXi 5.5, but - until recently - I had no idea how to fix the issue for the SATA controllers. I always thought that whenever an ESXi driver is loaded then it would detect and configure any PCI devices that it supports, but the ahci driver of ESXi 5.5 behaves differently: Even if manually loaded (with vmkload_mod ahci) it will only configure the devices that are explicitly listed with their PCI IDs in its map file (/etc/vmware/driver.map.d/ahci.map).

But once you realize this it is easy to add support for other SATA AHCI controllers that are not listed there. Then reboot the host to make the change effective. ESXi 5.5 – Installing with less than 4Gib RAM. (ESX MEMORY_SIZE ERROR during install) Many of us use ESXi for both work and home labs.

ESXi 5.5 – Installing with less than 4Gib RAM. (ESX MEMORY_SIZE ERROR during install)

However, not all of us have the 4+ GB of ram in our servers, well, because we don’t need it. I for one, have 3GB of ram in my server, and it run 3 Centos 6.5 Servers (Web Server, Plex Server, and Dev Server) and a Windows XP SP3 VM without any issues what so ever.