In-Guest iSCSI vMotion Support

Similar Questions

• In-Guest iSCSI for Exchange 2010

  Hi, we just built and are ready to go into production with Exchange 2010 using LUNS in guest through the card Microsoft iSCSI initiator iSCSI separate network for iSCSI etc. Load tested with JetStress and everything seems fine. We just found out as snapshots are not supported with iSCSI in guest so we are concerned that the other things work or be taken in charge or another, i.e. of vmotion. So, does anyone know if we lose any other characteristic, and we need to change our minds and using ESX iSCSI? I read pieces on being comparable, that we stuck with a guest performance because that's what we know with our existing Exchange 2007 environment (physical). If we must change, is it simple?

  Hey everyone who is following this thread or found via Google.  It is important to understand what is and is not supported when you are running Exchange on a virtual machine.

  To be absolutely clear, combining Exchange 2010 DAG and migration technologies such as vMotion technology is supported.  You must ensure that you are running at least Exchange 2010 SP1 as well as a version of vSphere that sits on the server virtualization Validation program.

  I think that the link was already posted, but here is the final link:

  http://blogs.technet.com/b/Exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-Exchange-2010.aspx

  More specifically, since the post above (in bold italics):

  Combining Exchange 2010 high availability solutions (database availability groups (DAG)) with hypervisor clustering high availability and migration solutions that will be moving or automatically failover servers for mailboxes that are members of a DAG between clustered root servers, is now supported.

  Improved, that we did in Exchange Server 2010 SP1, with more comprehensive tests of Exchange 2010 in an environment that is virtualized, we are pleased to offer this additional deployment flexibility to our customers. Management of updated support applies to any provider of hardware virtualization that participate in the Windows Server Virtualization Validation Program (SVVP).

  Logiboy123, can you provide any documents to support the statement that Microsoft does not support this configuration?  The above quotes are directly from Microsoft and are very clear that they support not only the migration of Microsoft technology, but also similar to any other provider of the hypervisor technology, provided that they are in the SVVP program.

  Since vSphere is part of the SVVP, Microsoft has extended support for the technologies of migration such as vMotion, in addition to their own Live Migration.  Of course, simply support something does not automatically make it works.  If you want knots vMotion DAG works correctly, you might have settings described in this blog post extended the cluster heartbeat timeout (also a fully supported configuration change):

  http://www.thelowercasew.com/vSphere-and-Exchange-Admins-can-live-in-harmony-Microsoft-finally-supports-HA-and-VMotion

  To answer the original question in this post, using the Protocol in-guest iSCSI is supported and with vMotion in this configuration is supported as well.  You're not really 'give up whatever it is' using this configuration well so if it meets your needs, I would stick with it.  I prefer generally VMFS just because of the flexibility it offers, but all the world has different requirements and I have absolutely no problem with guest iSCSI if your organization requires it.

  Do not forget that whatever configuration, snapshots of virtual machine are not supported for Exchange. Here is another post which goes into detail on it and cover the declaration of support for Microsoft Exchange 2010 snapshots and machine virtual: http://www.thelowercasew.com/virtual-machine-snapshots-and-tier-1-apps-not-always-supported

  So in general, I would say that provided you are running the correct versions of Exchange and vSphere must then take full advantage of your configuration to use features like vMotion and HA without problem.  If you adjust your settings accordingly cluster heartbeat timeout, you should have no problem using vMotion with your knots of DAG.

  Matt

  http://www.thelowercasew.com

• iSCSI, vmotion creating separate network, ESXi

  Hello

  We have purchasd EMC SAN NX4 which is iscsi.  We have also 3 ESX server, we have installed ESXi on them.  My question is, in this version, I can create two types of connection a connection of the management and the other is vmkernal.  As I understand it the vmkernal is used for iscsi, vmotion, and NFS.  VMware told me that all this can be on the same network.  VMware tells me that if I quick vMotioning much something is not so generally for vmotion traffic is light.  Technology EMC says something different, he says that vmotion and iscsi connections should be different network.  So I'm a bit confused.  Please let me know what is the best way to proceed.

  Thank you.

  It depends on how many resources you have available on your ESX servers. If you have only 2 NIC card then you can not sperate VMotion and iSCSI. But recommended say seprate LAN, IP LAN, LAN seprate Managment seprate Storage VMotion. (includes failove)

  Now its up to you and your information TECHNOLOGY budget. These days LAN cards are pretty cheap so you can put more card and easily separate traffic.

• Is iSCSI boot supported with VMware 5.5?

  Hello

  I see that VMware 5.5 is supported with the latest UCS code.  Do you know if it supports the iSCSI boot?

  Thank you.

  Hi Carl,

  Yes, it is, you can also check by looking at the compatibility below matrix (see example).  I would like to know if you have any questions or accept this post if I answered your questions

  http://www.Cisco.com/Web/TechDoc/UCS/interoperability/matrix/matrix.html

  

• Is it necessary that the guest OS to support SSD if the file of the virtual machine is placed on an SSD?

  Dear,

  I have a plan to set up a file of the virtual machine on an SSD. The host system is windows 10 (on an other SSD, I'll use 2 SSD), it should support the SSD very well.  Then comes the question: should I also install an OS that needs support also guest SSD?

  My opinion is it does not matter since the disk i/o operation is made by host operating system, it is the host operating system which finally determin whick block data will be published (optimization of the disk).

  Am I wrong? Thank you.

  Sorry for the enigmatic answer...

  In your case, the answer is Yes: he cares about the type of media, while the virtual disk is a vmdk (virtual material treaty) and placed in an SSD.

  There are a few cases where you might use a physical disk directly to the virtual machine (called peripheral raw disk or RDM in vSphere environment).

  Concerning

• Paradoxum on vmware overview "Guest Operating System Support" homepage

  Hello there,

  you guys can help me by answering the following question:

  What is the difference of the supported guest operating system RHEL 5 and RHEL (32/64)?

  See in the table on the following link:

  http://www.VMware.com/technical-resources/advantages/guest-OS.html

  In addition, there are analogies like Windows XP and Windows XP (32/64) ?

  It is a paradoxum for me.    =)

  Can someone help me with this, please?

  BTW: I want to run a RHEL 5 x 86 (32 bit) as the guest on vSphere OS 5 and must be supported in case of disaster.

  Thank you very much and have a nice day!

  -JCCSysADM

  It is indeed a table very unclear.

  It is not the real compatibility list, but a comparison with other hypervisors.

  For a list of real OS comments compatibility, check here:

  http://www.VMware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16

• Cannot add to the inventory if virtual machine running on the other guests - iSCSI and VMFS5

  5.5 ESXi hosts free standalone version

  iSCSI mounts with multiple paths - relatively new unit with more modern hardware

  CHAP not used

  I'm running a few hosts in order to climb the same iSCSI data stores. The iSCSI LUN is visible and editable by all hosts. If Host1 is to map the iSCSI LUN (VMFS5) and a VM is powered, Host2 can add that VM to the inventory. It's possible with NFS iSCSI for a reason any. This is for a specific reason? Only when I turned off the virtual computer can I add it to both hosts. Other that just lock files are placed in the directory, I missed something related to the lock?

  From now on, adding new esxi hosts does not allow me to add existing virtual machine, less than the voltage first. Once again, NFS does, iSCSI, this isn't. Any ideas?

  It is not specific to ISCSI but rather to the use of VMFS. NFS has no awareness VM VMFS is and why it is not possible to do that with iSCSI / VMFS. There is a lock on the disk for each virtual machine of (race), and that's why the second host is not able to add this host to its inventory. With vSphere HA, this lock is released when a failover should occur.

• SRM 5 guest operating system support

  I looked through the of compatibility Matrices for vCenter Site Recovery Manager 5.0 and see that RHEL 5.7 is not on the list.  He jumps from RHEL 5.5 to 6.0 RHEL.  It was last updated November 11, 2011, anyone know if RHEL 5.7 is now supported?  I was unable to find anything saying this is, and it would be very unfortunate if that were the case.

  Thank you!

  For clarity, the SRM 5.0 Campatability matrix shows only what VMware is considered most popular operating systems. The key is that SRM 5.0 supports the protection and recovery of all the operating systems supported by vSphere 5.0 comments. The full list of which are using the two links below:

  http://PartnerWeb.VMware.com/comp_guide/PDF/VMware_OS_Compatibility_Guide.PDF

  http://PartnerWeb.VMware.com/comp_guide2/search.php?testConfig=16&deviceCategory=software

• vCenter 4.1 Update 1 "Guest Operating System support customization"

  I was reading the release notes for vCenter 4.1 update 1. I noticed this statement regarding the additional customization support:

  "Additional support for customization of the operating system called: vCenter Server now supports the customization of the following systems: Windows Server 2008 R2 SP1 (x 32 and x 64)".

  (1) this means that we should not patch our model of Windows 2008 R2 with SP1, if we're still using vCenter 4.1 (without Update 1)?

  (2) in addition, it is possible that someone has already patched our model of Windows 2008 R2 with SP1. What would be the consequences or potential issues if some virtual machines have already been deployed and customized in vCenter 4.1 (without Update 1)?

  I doubt I'll see any error, warning or other if I tried to customize, but I want to assure you that it is not some underlying issues that would not easily noticeable.

  The reason is simple... SP1 is RTM and will be released in the coming weeks.

  First version of vCenter 4.1 can not support only because that there was not.

  Does not support does not mean that it is does not work (sorry for the pun).

  André

• bsod on guest operating system support

  I installed 2 guests on my esxi and when I try to create a virtual machine. He's still bsod on the third person. I use windows 2000 advance server on the buat comments he always bsod on the start screen or when installing windows. It is error page, kmode error, missing/corrupted to ntoskrnl.exe. Please just give me a solution thanks. ANW my server host using i7.

  You check the equipment, run memtest

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• VMWare ESXi 5.5 - VMotion & HA supported MDM physical or virtual

  Hello

  Hope someone can shed some light on the survey below:

  1. can you VMWare ESXI 5.5 HA and Vmotion supported with vmdk files located in front of multiple vmfs datastore 3/5? I have problems with VMotion or HA?
  
  2. can you VMWare ESXI 5.5 HA and Vmotion (not storage Vmotion) support with a VM scenario below:

  3 three nodes with iSCSI SAN storage

  VM1
  -Drive C-> vmfs Datastore1
  -Drive D-> RDM (is this support on a physical or virtual compatibility mode)
  

  VM2

  -Drive C-> vmfs Datastore 1

  -Drive D-> vmfs Datasore 2

  
  IV ' e seen these link below no mention if need pyshical or virtual mode
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1005241
  https://pubs.VMware.com/vSphere-55/index.jsp?topic=%2Fcom.VMware.vSphere.storage.doc%2FGUID-D9B143D8-9F93-41D1-A32F-9FF4DE4CDF14.html
  
  3. can you multiple access by 5.5 ESXi host the same data store (located on a San) vmfs using the free version of ESXi 5.5?
  Can I use this in a production environment? I have seen some companies test this on a non-production environment. Technically, it works.
  
  Thank you
  Paul

  Welcome to the community-

  (1) as long as the DRS HA cluster hosts see data even warehouses there will be no problem

  (2) once more, also longer than the nose can see data warehouses including the LUNS as the RDM it home should be without issue.

  (3) Yes multiple instances of the free version of ESXi can access LUNS shared - Yes it can be used in a production environment, but remember you can not handle the free hypervisor with vCenter.

• Initiators of software iSCSI Microsoft Cluster in guest

  Hi guys

  I have a client who have iSCSI Storage... now they want to create a cluster, but I read that only FC SAN is supported for RDM...

  but it seems that iscsi is supported as iscsi in guest...

  If someone knows the configuration for this?

  or is it as simple as:

  1. create iscsi volume of Quorum

  2. create iscsi for data volumes

  3 activate the iscsi initiator in Windows 2008 guest VM

  4 map these to W2008 VM iscsi volume

  5. create an another PortGroup-VLAN for the private heartbeat (is it necessary or the private sector can take thje same segment as the notrmal network)?

  Thank you very much

  Oh, sorry I didn't answer your original question.

  You are right, you must configure the virtual computer with 3 vNIC on 3 different subnets, then make sure that the public network is on top, when configuring the network order in the BONE (don't know where it was in 2008 for Windows, in Windows 2003 is configurable in the advanced network settings) Guest.

  André

• T of what guest operating systems will start the VMware Support for EFI?

  Is there a list of support guest OS for the EFI firmware?  Mianly supported by VMware - do not try, fail, call support technique etc etc.   My experiences on the TP forums, I guess that there is not.  Some OS (such as Windows Server) come with a screen to choose BIOS/EFI firmware.  If not, you need to go to setting > Hard Drive OPtions-> advanced _ > boot using EFI.  In particular there at - it versions of Linux that you give you option of BIOS/EFI firmware before the confutation of VM is complete, so the hard drive then be custom.

  We will officially support the EFI firmware for any guest operating system to which all the following conditions are met:

  • We list this guest operating system, supported in the VMware Compatibility Guide for operating systems and your virtualization product.
  • The guest operating system supports EFI in the operating system installation media.
  • Support the guest OS EFI has no catastrophic flaws (for example Fedora 12 x 64, FreeBSD 11, Centos 6.0 through all the 6.2 have catastrophic flaws).

  New computer virtual assistant of 11 workstation has only the option of EFI firmware for Windows clients.  Special mention, do not yet support us Easy Install for non EFI customers in 11 workstations.  For all other customer support EFI OSes, you can do a manual installation after choosing the EFI firmware in the virtual machine settings > Options > Advanced > Boot with EFI instead of the BIOS.

  I don't understand your concern about the personalization of the hard drive... Could you elaborate?

  See you soon,.

  --

  Darius

• How a guest VM OS audio support audio?

  I have a guest operating system linux installed at vsphere5, but no sound can be heard when I open youtube in the browser.

  I can't find any sound card can be added to vsphere5.  I can know is to audio vsphere5 of guest operating system support?  How to set up?  Thank you!

  Check if this helps virtual HD Audio Hardware in vSphere 5

• MSA 2040 Direct attached iSCSI

  We implement a VSphere environment 5.5-3 hosts directly connected to an MSA 2040 with iSCSI.  Attached host to the MSA a question directly or have us use switches?  Our equipment provider said

  "in order for the volumes of VMWare to have access through shared storage needs through a switch. You can run questions where if they are directly attached, then the VMDK on the single host may not be seen or accessible on other hosts (high availability or Vmotion). »

  Also

  "Support from direct attach to the msa via iSCSI is dependent on the BONE."  Some OS support other don't. MSA does not directly connect to Vmware via iSCSI. "

  I talked to HP directly and they claim to direct connection via iSCSI is supported with the MSA 2040 and VMware.

  Is anyone running this configuration that can put my mind at ease?

  Thank you.

  Hello

  Yes, you can use a directly attached MSA 2040.

  I use this configuration yourself by using DAC 10 GB cables, also sold this solution to customers.

  Please note that each host must have 2 connections to the San (if the SAN has two controllers). Each host must have a connection to each controller on the SAN.

  4 directly attached hosts is supported (the controllers have 4 ports on each one).

  Please note that several subnets must be used and configured to allow a correct path discovery. A BIG note to stress also is DO NOT USE the PORT iSCSI MAPPING!

  Be sure to activate the Robin. Please note that you will see an active path perform I/O by the data store (since only one controller has a volume), but in case of rupture of the cable, or controller failure, there are switched to the other controller.

  I use this setup for a few years and I love it!