Nested ESXi hosts and iSCSI POC

Similar Questions

• Unable to start x 64 VMs on nested ESXi host

  Hi gurus,

  I would ask your expertise on the question with my ESXi nested 5.1 checking. I managed to install the nested ESXi host, but I can't start a x 64 VMs. I continue to ask me what follows:

  
  Intel Core i7-3770 CPU @ 3.40 GHz
  DH77EB
  EBH7710H.86A.0100.2013.0312.1351
  Virtualization / VT - x is already enabled in the BIOS.
  Turn off the Bit is also activated.
  verified the host physical and NestedHVSupported set to TRUE
  added vhv.enable = "true" on the physics of the host \etc\vmware\config
  created nested ESXi VM
  original operating system is any other 64 bit
  Once the virtual machine is created, I changed the OS to VMware ESXi 5.x (experimental)
  NX/XD flag is already set to expose
  added - H - mask CPU; ECX
  Adds the following on the nested ESXi vmx file:
  Monitor.virtual_mmu = "hardware".
  Monitor.virtual_exec = "hardware".
  VHV. Enable = "true".
  monitor_control.restrict_backdoor = 'true '.
  Thanks in advance!

  According to the journal of the ESXi VM file, its configuration (.vmx) file does not contain the vhv.enable = "true" entry. Only the configuration file contains, that was how it should be done in ESXi 5.0, but not in ESXi 5.1.

  Try to add the entry to the ESXi VM and make sure you reload the configuration (see http://kb.vmware.com/kb/1026043) before turn VM ESXi.

  André

• Several ESXi hosts and need to share virtual machines

  I'm relatively new to ESXi (although a lot of vSphere, using iSCSI storage) and we are making a number of servers in remote site (with a proxy and utility VM to manage the file/print/dhcp) using ESXi. I have my VMs built on the first box and need to copy them off the coast to the other, but I have problems with the command ADD Storage... I can't seem to get the right information and I begin to think I'm missing something basic. Then...

  (1) can map you to the VMFS from another host esxi?

  (2) If you can, where do you find the location on the second machine information to set up the data store on the first machine?

  If it's important, we use Dell PE of the 1950s.

  Also, while I'm here...

  The size of a pain is to change the IP address or the name of the ESXi host area?

  Thanks in advance for any help!

  VMFS is not supported on USB drives.

  You can use FastSCP for example, http://www.veeam.com/vmware-esxi-fastscp.html

  And Yes, there are several devices that could share storage attached to the network locally, but I don't see them as a solution when you want to just copy existing virtual machines to another host ESXi.

• How to backup 4 ESXi host and guests?

  Instead of running 2 or 3 physical servers, I create 2 or 3 virtual servers on one physical host and save money, the trees, the planet and so on.

  Go green, as they say.

  But how do I save it?

  My first experiences with VMWare workstation (excellent product BTW), I thought that I could connect an external hard drive on the physical server via USB and back up virtual machines from time to time. Just as I could with VMWare workstation (not to mention the snapshot option...).

  Right...

  Indeed, virtual machines in case more than one front-end role rather than the portfolio databases that change on an hourly basis, an image on an external hard drive backup were possible.

  But it doesn't look like it works that way with ESXi.

  OK, the snapshot option is still there, so that offers backup features (update mess up system, go back to the last good snapshot).

  But when I connect the external hard drive, it is not recognized. Sounds fair?

  I heard that you could back up via iSCSI. Possibly using the software to create an iSCSI target on another server instead of investing in a unit of SAN.

  Despite this, where you re all or part of this?

  I don't see no backup option in the interface of vSphere 4.

  THS, that's what I have:

  X3350x IBM server | ESXi 4 | 1 guest running Windows 2003 server and the other running 2008 Server.

  That's all. No VCenter, no vMotion, no second failover server.

  Could someone clarify my options?

  Visit this link on this topic: http://www.vladan.fr/plug-in-the-external-usb-drive-to-esx-server-directly-to-backup-or-copy/

  ---

  iSCSI SAN software

  http://www.starwindsoftware.com

• Connection usb to esxi host and copy vmdk

  Hello

  I'm trying to migrate a vSphere cluster to another machines.  There is no network connectivity between the 2, so I intend to copy the files vmdk and vmx more via USB directly connected to the host for thoroughput max.  Anyone tried this?  I looked in the documentation and online, and I see that the only supported file systems FAT32 and ext3.  For a 40 GB virtual computer, can I use an ext3 formatted USB key, copy locally and then USB attach themselves to a host on the new cluster and copy?  Anyone see any problems with this?  We are doing this process via a USB port connected to a position of the user and SCPing between the host and the USB port on the network.  I think that cutting the transfer network will speed up the process, currently a 40-50 GB VM takes about 3 hours

  Hello

  I understand that you can read in what she argued, however...

  If there is a KB article while this does not mean that it is supported, it simply means that it is possible and you might be able to use it if the need is high enough. For example, in case of problems you can risk some stability/performance and fix the most urgent problem at hand, as a critical VM that was on a LUN which disappeared earlier that day there so that you only restore backup on a USB drive.

  Also note the supplement "additional note" at the bottom of the KB that you are facing

  Quote (my highlighting):

  More information

  The USB key must be a minimum of 4 GB in size. This procedure is not recommended for basic file transfers.

  This procedure includes steps on disabling the intercom USB host function. Then earlier in the article that they use the same feature to connect the USB drive to the guest.

  If this isn't everything, they use the DCUI for mode of tech support that their link in an article KB1017910 to using the console is already a bit dodgy on a production host. About using the console for day-to-day operations is a no No

  Another quote, this time from this KB article, underscores once again with me.

  Tech Support Mode

  Tech Support Mode (TSM) provides a command line interface that can be used by the Administrator to troubleshoot and correct abnormal conditionson hosts VMware ESXi. TSM is accessible in two ways:

  • Connecting directly to the ESXi Server console.
  • Remote SSH connection.

  Further down in this article, it is pointed out again that it is for support only, I would say is something different as 'supported environment.

  It does not mean that you can not and never use should the DCUI, but be careful.

  Back on the focus to what you're trying to do.

  If your USB drive is broken, you now have a hypervisor that attempts to mount it to the level of the hypervisor, which, in itself, can cause downtime at the level of the hypervisor risks of release for ALL your guests. USB transfer at least maintains these problems located in the virtual machine, it is attached to.

  Besides that... the only system files that you can mount is VFAT, so you can't even put files there that are larger than 2 GB (or 4 GB) in size.

  File systems ext2/ext3/ext4 that none of those who are supported, VFAT only for your external USB drive.

  Yes there are ways around the VFAT file size limit too, but you're just jumping through the next pole, and if something's not going then your users is satisfied by the retoric "but backups are faster".

  --

  Wil

• go esxi hosts and virtual machines in one vCenter to another

  I built a new vCenter (Windows vCenter), I intend to move on ESXi hosts the old vCenter (Virtual appliance vCenter) to the new vCenter. I don't know if it's feasible, please notify my step is correct or not: 1) build a new vcenter 2) create a cluster with two esxi hosts first 3) Mount data (NetApp Filer Storage) to the new vCenter warehouses 4) add an empty host for the new vCenter VMs) 5 download then upload to the host in new vcenter

  Hi friend

  Its doable without any problem.

  Please follow the procedure below.

  1 build a new vCenter (your first step is correct)

  2 creating a cluster (because it is new vCenter there will not be any available host.) That is why cluster creation wizard will not get to add in the new cluster host). While initially empty cluster would be created.

  3. once the cluster is created, immediately do a right-click on the cluster and add your hosts one by one. Not necessary to cancel the registration and the VM. Virtual machines will automatically be added who were there on the data store available with all guests.

  Don't forget,

  1. we do not mount any store data in vCenter, we assemble the data store on the host.

  2. If you mount the new data store (which did not exist before), you can mount once the new hosts are added to the new cluster. (Your SAN admin help)

  3. If you want to move your virtual machines from data store before the newly added/mounted data store, please SVMotion these virtual machines (by right-clicking on the VM > migrate > data store > select the data store that is new)... Please follow the same procedure for all virtual machines.

  4. you don't need to add empty hosts to the new cluster, add just as soon as all guests without you register VMs. Later, you can migrate to other store of data according to the requirement. NO need to download or download the VM.

  5. Please make sure that your ESXi hosts will be compatible with the new vCenter. Old version of ESXi always compatible with the new version of vCenter. Just check if you have all valid licenses.

  Please let me know if you need any clarification

• List of ESXi host and data managing paths

  can someone help me with a script to list the ESXi host name, then their data management of path for each data store that they are connected to?

  Thank you

  MikeP

  Sorry, I thought you ment the other script.

  Try it like this

  Write-Host "Connecting to vCenter" $VCent = "10.2.160.250" Connect-VIServer $VCent -user user -password passwd $VMHosts = Get-VMHost | Sort-Object Name Disconnect-VIServer -Server $VCent -Confirm:$False 
  
  $report = @()
  
  ForEach ($VMHost in $VMHosts)
  {
      $HostName = $VMHost.Name
      Connect-VIServer $HostName -User root -password passwd    $esxcli = Get-EsxCli  -VMHost $HostName    $esxcli.corestorage.device.list() |
      where {$_.IsLocal -eq "false" -and $_.DeviceType -eq "Direct-Access" -and $_.MultipathPlugin -eq "NMP"} | %{
           $report += ($_ | Select @{N="Host";E={$hostName}},Device, MultipathPlugin)
      }
      Disconnect-VIServer -Server $HostName -Confirm:$False}
  
  $report | Export-Csv "C:\report.csv" -NoTypeInformation -UseCulture
  

  You can try to change the Where clause to see all the plugins multipath.

      where {$_.IsLocal -eq "false" -and $_.DeviceType -eq "Direct-Access"} | %{
  

• Attempt vSwitch configuration change and now the ESXi host and virtual machines offline

  So I have no doubt, I have myself to blame for this one. I was trying to change my vSwitch from 100 Mbps to 1000 Mbps when an 'operation timed' error out jumps-to the top and my vCenter Server lost connection with my ESXi host. I tried to restart the host manually, but that did not help. The host is not the ping requests and all the virtual machines on that host are offline; None of them vMotion off to my other ESX Server.

  I tried to reconnect the host computer in vCenter, but it is obviously does not connect because it can't ping it. I logged the ESXi console and all the network settings appear to be correct. I'm used to connect to the ESX console where you can execute commands, but it's my first ESXi host, so I don't know what I can do.

  Any help is greatly appreciated!

  -D.

  If you had your management port and VMs on different vSwitches / NIC leave on framework would eliminate a false positive. As in your case the management port reportedly follows the cable / about speed, but the virtual machine network would be intact (and I'm assuming that your storage space as well).  In this case the VMs system would have worked very well even if the management port did not work.

  Dave

  VMware communities user moderator

  Now available - vSphere Quick Start Guide

  You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

• ESXi host and VM hardware upgrades

  Hi all

  I pretty well know the answer to these questions (I like to read manuals), but I just wanted a few reassuring those who have ventured in front me.

  1 / when the upgrade to ESXi hosts of 3.5 to 4.0, it is my understanding that there is no real emergency in the upgrade of the host of the virtual computer (tools and hardware to version 7) as vSphere 4.0 will run happily with the older virtual machine (but without the new features).  However, I am wondering if anyone has experienced problems do not upgrade the machine virtual shortly after the upgrade of the host.  My intention is to do it very shortly after, but sometimes the best-laid plans go out the window in my role, so I'd feel comfortable if I new I could run the old VM indefinitely without any problem.

  2 / how 'security' is upgraded version of the VM from 4 to 7 material?  VMware I don't expect any problems, but I would like to know if anyone has experienced problems that can cause interruptions of service extended to the VM guest.

  Thanks in advance,

  Steve.

  1. I would separate between VMware tools and hardware upgrade. New tools not only to upgrade virtual hardware drivers, they also inflating to update and other features VMware uses to communicate with the guest operating system. In my opinion, you should pass the VMware tools as soon as possible. I can't say for sure if you have any questions without upgrading. My personal opinion/experience, is that during the "normal" old tools will.

  The hardware upgrade should not too important. In environments with hundreds of guests, you will actually have to update all hosts (in a cluster) material in order not to lose the capacity of invited guests 3.5 vMotion.

  2. the only issues I've had so far with the upgrade of the hardware have been networked. I had a few VMs to reconfigure the network manually after the upgrade.

  André

• Affinity reserve esxi hosts and host rules

  I'm trying to reserve a few for some special VM ESXi hosts, I used affinity DRS rules to make the virtual machine to run on special guests, but other virtual machines are also coming on ESXi hosts reserved because of the DRS.

  I have about 300 virtual machines running on 10 ESXi hosts running VMware 5.0 Update 2

  Currently using Vcenter 5 Update 2

  I have just installed 3 new hosts ESXi running the same VMware 5.0 Update 2

  The new ESXi 3 hosts must be temporarily reserved for a project with 30 new VM only, but always be part of the main cluster because they will be used with the 300 existing virtual computer when the project is completed.

  I have a rule configuration of affinity for the new virtual machine only works on the new ESX hosts

  But the problem is that some of the other 300 vm get Vmotioned with DRS on the new hosts as they have a lot of free resources.

  There are new virtual machine being added to the VM s 300 all the time by other people that I can't control.

  I'm happy to manually add my special project of the virtual computer to the rule of the DRS of affinity for the reserved ESX hosts can not have "other persons" manually add the new virtual machine to another rule, should it be automatic for them.

  I would like to set up a global rule to tell if you are not a virtual machine in my special project group DRS that you are not allowed to run on the 3 new ESX host.

  Dose anyone know if this is possible?

  Why not move the hosts in a cluster instead?

  Linjo

• Setting up iSCSI between ESXi host and MD3000i, firewall Option missing

  I try to configure the iSCSI access and the MD3000i manual head to the firewall option in VI Client.  However, when I go to Configuration - & gt; Profile of security - & gt;  the option firewall appears briefly and disappears?

  I'm having problems to recognize the iSCSI host table and I think that this may be due to the firewall.

  Hello

  I believe that in the latest versions of ESX (3.5u3 for sure), 3260/tcp port (you need for iSCSI) is automatically opened when you turn on the iSCSI (iSCSI software that is).

  You should choose abe to connect using the VI client, click the host in question and select the 'configuration' tab and then the item "security profile. Who should be open all ports.

  Remember that when you use iSCSI, you must as well a VMkernel port and connection of console in your LAN IP storage space. If two IPs per ESX host. The Console launches the iSCSI link, the VMkernel carries the iSCSI connection data.

  EDIT: Sorry, only now I noticed that you are using ESXi. In this case, you won't need a port Console service (because ESXi has one)

  Visit my blog at http://erikzandboer.wordpress.com

• Access the SMB storage using esxi host and manage with MS server 2008

  Hi there, I know the subject line can be confusing, but I didn't know how to explain what I need in the line object in such a short sentence.

  in any case, I have a storage device SMB, a Promise VTrak M610P, which is attached to a blade server 1U HP through interface channels double Ultra 320 SCSI host. I can't configure the VTrak as a NFS, the only way to access logical drives is connected to a server via the scsi channels and using the operating system to share the drive and the shared disks.

  I would use a server blade with dual ultra 320 SCSI host interface channels and connect the VTrak to this server blade. Then I would install ESXI hypervisor OS 5.5 to this server blade. I want to know is if the ESXI operating system will recognize the logical drives and if I create a virtual machine with MS server 2008 and see if the virtual machine detects logical drives, so that I can share the drives? I hope that I'm supposed to and if I'm not, please let me know what makes no sense, I will do the best to explain it better.

  Thank you

  Andy

  So it turns out that there seems to be something wrong with vClient when you add a hard disk (virtual disk) to a virtual machine of size greater than 4 TB. Article VMware KB: value of range error message when you add more than 4 TB capacity discs in vSphere Client describes this if you encounter this problem, add the hard drive via vSphere CLI, CLI power or vmkfstools. So this seems to be a known issue on vClient. What I ended up doing was using vClient, creation of hard disk, adding to the virtual machine (size of the hard drive is to 5.45) and when I would get the error message on the DiskCapControl out of reach, I would just click OK and then finalize the creation of the hard drive on the virtual machine. Once the process is complete, I selected the virtual machine and noticed that he indeed added a new HDD size 5.45 TB even if he's complained about it. I pulled to the top of the virtual machine with windows server 2008 R2 installed and was able to create a new disk under windows and set it up as a shared drive on the network. Looks like vClient must be updated by VMware and correct this bug, if it's a bug that I think. Thank you for the help vervoort!

• Invited 3.5u4 swap ESXi host and memory size

  Hi all!

  I have VM (Debian Linux), graphs of performance on this subject shows swap use about 250 MB, real vswp file size is 1.6 G, but he came out of the guest operating system:

  Linux: ~ # vmstat

  procs-

  ---

  memory-

  ---

  -swap .

  ---

  IO- system -

  ---

  CPU-

  free buff cache r-b-swpd TR so bi bo in cs us sy id wa

  1 0 0 739896 135300 208828 0 0 2 42 20 68 1 1 98 0

  As seen, no swap no used. Why VI customer counters and swap file size differs so much use of guest operating system counters.

  Hello

  You are looking at two different levels of memory usage. VI customer, you can read information about the actual use of memory and swap ESX. It differs generally you can read from within the guest for example OS Linux. VM swap file (not asked) if used by VMkernel in situation when the assertion of memory occurs. Lack of memory is mapped in the Exchange. It is the last resort and causes significant performance degradation.

  Guest os swap is "high" this VM swap. It is entirely managed by the guest operating system. It size is based on the memory configured for VM and guest OS configuration. Only the situation when VMkernel can affect the exchange of comments is the balloon pilot. It is a breakthrough of technical recording memory that allows ESX to "say" the guest OS some free memory and use more swap file (Exchange of comments!). Freed memory can be reclaimed by VMkernel and used by other virtual machines. This driver is available for the guests with VM Tools installed.

  concerning

  Martin

• 6u2 ESXi host nested on VMware Workstation for Linux referee v12

  Hello all, I have

  I have a lab environment virtual running in VMware Workstation for Linux v12, and my ESXi hosts do not work correctly on one of the virtual networks. All my troubleshooting suggests a problem with nested ESXi hosts that may be a bug, but I want to assure you that I did everything properly first. That's why I post here with the hope that if I made a mistake that maybe someone else can point out he me.

  Physical system

  8 core Intel Xeon 2.1 GHz CPU

  128 GB of RAM

  OS - kernel Linux 64 - bit w/3.19.0-32-generic Linux Mint 17.3 (fully updated from this announcement)

  VMware Workstation 12 Pro - 12.1.1. Build-3770994 (fully updated from this announcement)

  Nested ESXi host VM

  ESXi v6.0.0 (Build 3825889, completely updated from this announcement)

  4 cards 'physical' (only 3 used for now)

  -all use the e1000 NIC hardware virtual, but also tried vmxnet3 NIC with no difference

  -vSwitch0 use vmnic0 & 1 vmnet16 of virtual network in a pair of active / standby

  -vSwitch1 uses vmnic2 on network virtual vmnet18

  -vmk0 used for management on vSwitch0 and vmk1 for iSCSI on vSwitch1

  -"Promiscuous" mode and forged passes enabled on all Port vSwitch groups (activating or turning off these features makes no difference)

  Test performed until now

  I checked that all the IP addresses and network masks used are correct.

  With the help of vmkping I ping other nodes on the network vmnet16 with success.

  With the help of vmkping I tried to ping the other nodes in the network vmnet18, but that has failed.

  I have depolyed other non - ESXi VMs on the vmnet18 network, and they are able to ping each other, but are unable to ping or ping by the ESXI host.

  I tried various material virtual NIC as mentioned before, but without changes in the results.

  I tried to use only local network instead of the vmnet18 guest network segments with no change in results.

  When I find out the status of the network adapters on the ESXi host through vCenter or host incorporated client vmnic0 & 1 time display network information, but vmnic2 shows no networks. Yet, I know that there is a network with different VM communicate on it. Moreover, I was able to get all of this work on a Windows system running 10 Workstation (this is the laptop that my employer gives me with).

  Having built nested ESXi labs on different platforms as well as physical environments in the past, I'm very confused as to why I can't get this special configuration to work. At this point my gut tells me that this is probably a bug any with the nested themselves ESXi hosts. Since I can get all this work on vmnet16 including the management of ESXi hosts and the VCSA that I use, I am sure that my vSwitch configuration is correct (other than the IP address space and vmnic configurations is bascially the same). Because I can get other virtual machines to communicate over the network vmnet18 I don't see how can be a VMware Workstation for the issue physical Linux host. Is there something obvious I'm missing here? I read on the ESXi hosts nested under VMware Workstation after having known problems and bugs with networking. If anyone else has experienced this?

  Thanks for any help others can provide!

  Kind regards

  Patrick

  Well, the problem is now resolved. The problem was what covelli was trying to explain, but I couldn't because the physical host network adapters being mentioned.

  The problem on the Linux host, but it was a problem of permissions with the virtual Ethernet adapters. The following article has the fix:
  With the help of Ethernet virtual cards in Promiscuous Mode on a Linux host (287) | VMware KB

  Even if I launched the workstation under the root user I have yet met this problem and which still makes no sense to me, but change the permissions solve the problem. I was not getting an error message on my Linux Mint and Ubuntu system, but when I tried on a second box of Linux Mint that I just got the error has been generated, and the error message was the above link it contains.

  So, here's what I learned:

  (1) the question has nothing to with a VMware Workstation definition that you can configure.

  (2) the question has nothing to do with a physical network card.
  (3) the question has nothing to do with any vmnic on the nested ESXi host.

  (4) apparently virtual Ethernet adapters are not the correct permissions when created.

  All you have to do to fix this is:

  (1) open a terminal.

  (2) run the command ' sudo chmod a + rw/dev/vmnet * "(don't forget to run this each time that you create a new virtual network).

  You can also create a group, as shown in the link above and simply give this group the correct permissions. Personally, I think it's easier to just give everyone the rw permission.

  I appreciate the help that others have offered. I did not understand what was asked for in previous answers because of the terms that have been used.

• Nested ESXi 5.5 lab for the SRM demo with iSCSI

  Hi all

  I was wondering if it is possible to install ESXi in ESXi 5.5 5.5 make recovery of the Server Tier - 1 Microsoft with Site Recovery manager?

  So level 1 server applications are: Exchange Server, SQL Server, SharePoint Server and AD DC servers with 5 x test Win 7 desktop.

  The external data store to the VMFS will take place by iSCSI NAS connected to the physical server.

  Any suggestion and input would be greatly appreciated.

  Thank you

  One thing you'll want to do is to make sure that use you VSphere switches distributed on your cluster nested to ESXi hosts so that you can use the network i/o control (NIOC). For me, I put iSCSI to high priority traffic and everything to normal priority.

  With the help of the NIOC will allow your cluster nested in order to operate more fluidly than without it.

  My SRM 5.x laboratory is fully nested - probably not supported in a production environment where supported VMware should however.

  Here's a blog post of Ather Beg on its results by using the nested NIOC and ESXi hosts - it is the reduction of the spikes that Ather blog article shows that made work nested ESXi hosts networks so much better:

  http://atherbeg.com/2014/02/04/why-enabling-NIOC-network-IO-control-in-a-home-lab-is-a-good-idea/

  Datto