Cannot add P2000 SAS LUN to host vmware

I have two HP DL380 G6 vmware hosts and a P2000 storage device. The P2000 is connected directly to the two hosts with two SAS controllers. In hosts, I installed HP Sc08e PCI HBA adapters. A host (running ESXi 4.0) is connected to the storage and can make use of data warehouses. The other host (running ESX 4.0) does not see the new storage adapter.  During POST, the server lists the new adapter so the hardware itself is aware that there is a new HBA, but within Vsphere host is not simply see the adapter.

The P2000 LUNS are mapped to all ports of P2000 for two guests. P2000 configuration the two hosts are set up for exactly the same thing.

Can anyone suggest why I'm having this problem?

Thanks in advance.

Are the two hosts on the same build? According to the HCL , looks that the driver has been added to ESX 4.0 with update 1. Before that, you need to download and install manually.

http://downloads.VMware.com/d/info/datacenter_cloud_infrastructure/vmware_vsphere/4_0#drivers_tools

André

Tags: VMware

Similar Questions

  • Cannot add the ESX 6.0 host to vCenter Server 6.0

    OK, I'm testing laboratory a vsan 6.0 cluster.

    I have my running 6.0.0 esx hosts and vcenter server is 6.0.0 also.

    I have the services platform on a virtual machine and vcenter on another. I was able to create a data center, then a cluster below.

    Then I went to try to add a host to my group and I get this error...

    Failed to contact the specified host (hostname\IP). The host may not be available on the network, may have a network configuration problem, or that the management on this host services may not respond.


    Per this KB: KB VMware: Add a host VMware ESXi/ESX from VMware vCenter Server fails


    I confirmed that my vcenter server and platform services server can see all esx hosts. From the vcenter server, it can ping the host esx and PuTTY can access all of them. I even installed the client and it can connect to all esx hosts. I used the netbios name, IP and FULL domain name and they all work.

    I have only a single subnet, so this isn't a problem. DNS resolution works in all areas of both sides, vcenter esx hosts and host esx to vcenter.


    I am quite puzzled.



    OK, after working with VMware on this issue, I think that I thought about it.

    All my hosts are DL360 G6 servers.

    My hosts are run the same build «VMware-ESXi-6.0.0-2494585-HP-600.9.2.38-Mar2015.iso» ESX Downloaded from HP.

    All buildings are in trial mode.

    After placing a call to VMware, they had me build some ESX VM, the services of the platform and the vcenter VM on an ESX host. We suspended because it took all day to go upward.

    Once I woke up all the parts (sql server, esx vm, server platform & vcenter) in virtualization nested, I created my data center, then Cluster then added the ESX host.

    The hosts added properly, no error. Then I remembered when I installed ESX inside a virtual machine, I am angry that the iso, I had the habit of HP does not work in my VM nested due to virtualized hardware.

    Then a fire came into my head. We will rebuild all of the physical cluster but NOT use the CV provided the iso file but use VMware provided iso file "VMware-VMvisor-Installer - 6.0.0 - 2159203.x86_64.iso".

    I did it today. I have rebuilt all hosts with the provided iso file VMware ESX...

    Spun SQL Server vCenter, service platform, all VM VM VM you need. My AD & DNS VM are on another server, so he has been upwards all the time.

    Connected to the web interface (yuck!).

    Created my data center...

    Created my Cluster...

    Add all my Cluster hosts.

    All of this worked!

    Therefore, if you encounter the same problem, I'm plan to generate your with the provided iso file VMware ESX hosts and try it. In my case, the provided HP iso file didn't work properly for me.

    I also downloaded the iso file of HP 2 other times to make sure and do a validation test and it did the same thing.

  • 5.5.5 Advanced VDP cannot add a license to a host

    I downloaded and installed the eval mainly to test the functionality of replication of 60 days.

    I have the license provided by vmware and added during the installation/configuration

    Enter the web client then the POS and the configuration tab.

    This page is supposed to have an advanced POS tab or link to go somewhere to add hosts to the allowed list.

    This facility does not have the Advanced tab.

    the configuration has confirmed the version and the mode is advanced vdp as shown on the left side of the configuration page

    Adds the License Manager to license in vcenter (device 5.5)

    I'm stuck, cannot do all the backups until I have a license to host.

    any suggestions?

    Thank you

    finish by closing the vcenter and all 5 devices of vdp

    interesting thing to note is that the element of Data Protection of vSphere in the left menu of the web client disappears when there is no POS device running.

    all brought to the top entered the advanced VDP connection and now the advanced license option is present and functional.  don't have an answer for this, but at least I can with the eval.

    at the same time, I was looking into using high processor on the device of vcenter 5.5 and found that it is POS devices.

    without any POS running host cpu is 40%, started 2 and it went to about 50%, 60 plus 2% more then in the last 4 hours, he established at 40%

    before complete stop of all POS and vcenter vc ran 90 percent even after a reboot of the Victoria Cross.  Looks like they have sometimes a few problems to agree, but a new start for everyone seems to get by.

  • Cannot add VMFS datastore to ESXi host

    Hi all

    I have a problem with the CF 1 logical unit number which can be seen as a device through several paths on all 10 hosts in a cluster, but it appear as a data store VMFS on 6 of the hosts. Other LUNS of the same Bay appear correctly on all hosts. 10 guests see the LUN with the same LUN ID and all hosts are identical regarding the version of ESXi (5.0 Update 2), HBA and firmware models.

    On the 4 hosts who can see the device but not the VMFS data store, it seems that he sees the LUN as a snapshot: 'list of snapshot storage vmfs esxcli' translates into:

    4f5e5cbb-a87cd2c6-86e9-d8d385f98034
    Volume name: LUN101_SAS2
    VMFS UUID: 4f5e5cbb-a87cd2c6-86e9-d8d385f98034
    Can mount: true
    Reason of mountability-United Nations:
    Can will: false
    Reason for non-resignaturability: the volume is actively used
    County of measure pending: 1

    The UUID VMFS above matches the UUID VMFS seen on 6 guests who can see the VMFS data store.

    When I try to use 'Add storage', the device appears with a lambel VMFS: LUN101_SAS2(head). I don't know why (head) was added to the label of VMFS. Oscreen n the following signature to keep 'existing' and "Assign a new signature" options are grayed out. The only option is "Disc Format. I need to keep the existing signature because it run virtual machines that have their files .vmx and hard on this LUN.

    Would the fact that I have virtual machines running on this LUN, I cannot choose the option to "keep the existing signature?

    I need to Storage vMotion these virtual machines to a different LUN before I add the VMFS datastore to 4 guests?

    TIA

    Hey RoscoT;

    Try the following command

    #esxcfg - volume - l

    This should show the volume

    To constantly increase the volume, use esxcfg-volume - M followed of the UUID or volume name

    Concerning

    one

  • vCenter 6 in a WAN configuration - cannot add 6.0.0 ESXi host, is stuck at 80%

    All,

    I tried a day now to find a solution to this. We have 6 break-in LAN1 vcenter, connect a host ESXi LAN1 and ESXi another I LAN2. LAN1 and LAN2 are connected with IPsec. Resolution of DNS works both ways, as far as I can tell and all ports are open between the hosts. We had everything up and running but due to hardware failure, needed to replace the ESXi I LAN2.

    With the new host in place, I am not able to add to vcenter. I tried to use the name and IP address. I even downgraded to a previous version of ESXi, but all does not work, stuck at 80% progress bar. Then the message "Failed to contact the host specified." Checking the logs I see that vcenter is actually connected to ESXi in LAN2 and creating the account vpxuser to communication works in one way at least.

    I remember I had the problems of implementation of the previous host in LAN2, but all of a sudden it worked simply.

    Someone at - he had no idea where to start looking?

    / Mattias

    Make sure you have the MTU settings assign identical values everywhere.

  • Add new storage "opération TimedOut" with RDM LUN on host. Pls Help

    Hello

    Installation program:

    4 ESX 3.5 hosts each with 2 HBA adapter connected to the HP MSA1000.

    Question:

    I set up MSCS SQL 2000 with RDM through host, MSCS failover without problem, performance wise is not a problem at all too. But the problem is that if the MSCS SQL resource is managed by the Active virtual machine that is running on host1, I can navigate to storage / adding LUNs, set in shape of new LUN with no problems.

    If I want to add new storage on the other host "host2" I received the error "Tor time to ask"is it because of the resource ROW being busy serving the machine virtual active it is why the host not allowing do not change with the addition of new storage?

    Guests see these LUNs. I can add the data store or to do a new analysis also long the LUNS are not presented to the host. Also I can browse the data store, able to see the addition of Storge Wizard when adding new

    Data store and make a new analysis only on the host where the operation of the active node. Suppose the preseneted RDM LUN on host1 and host2 and VM SQL running on host1, I can only browse the data warehouses, a new analysis and add new storge to this host. I can't do the same thing with

    hosts2.

    But if I take these "RDM LUN" LUNS in host2, host3 and host4. I can do a rescan, adding other LUNS as the RDM presented to the virtual machine, able to see the add storage wizard.

    I googled the error and found that the Ontario server is question, or DNS

    Best regards

    Hussain Al Sayed

    Post edited by: habibalby

    I had similar questions to those two problems here where I couldn't add a data store as he would expire and I got the long startup time. I also use RDM which I use for MSCS in the whole of boxes 2. Here's a quote from my previous post in which I found a response that helped me. Changingthe SCSI retry time increased my boot time and allowed me to add one more time without the question of the time-out, data warehouses.

    Response to previous Post:

    I did some research and I think I've made some progress. I found that I get lots of SCSI errors in the VMkernel newspaper. I did some more research and found out that I can change the time retrying SCSI 80 to 10 and it has done wonders for my time to reboot. Now, instead of taking 20 minutes to start, it takes less than 5 minutes now. Much better. I made the change in the host-> advance-> SCSI--> SCSI configuration try again. 80 a the default and 10A was suggested as being a good value. It helped and I will keep an eye on what can make the effect, but so far it has helped with startup times.

    http://communities.VMware.com//thread/203122?TSTART=0

  • vSphere 5 re-install-cannot add hosts

    Hi guys,.

    The short version:

    I installed 2 Physics Dell R710, with installed ESXi 5. Each has 4 Win2008R2 VM on them. Everything works fine. At the time I ran upward a VM specifically for vSphere vCentre server in order to manage these. I've added both ESXi hosts to a data center that I created in the vCenter. Because of the budgets he decided not to buy Essentials Plus a moment while the evaluation has expired I uninstalled the software.

    Fast forward to today and I bought Essentials. I have re-installed the software vCentre on this same machine virtual I've done before. I created a new data center. However, I can't add two existing ESXi hosts. I run the Wizard "Add host", put in the IP of the host, the same username and password I used on these hosts when connecting via customer vSphere th... and wait and wait the time out - not given error. I see in the event log of the host that the user @(l'ip dele de serveur vCenter) has in... but there is nothing after that... so he can see and hit the host OK... but then it expires and does not just add it.

    Has anyone else seen elsewhere or know a solution? Any advice or suggestions are greatly appreciated

    Hello

    When you have uninstalled vCenter right there you should remove the vCenter database, but you do not the same, because of which you there are old entries in the database and you cannot add an existing database to the host.

    If possible you uninstall the vCenter server and delete the database and redo the fresh install by creating the new vCenter database.

  • Cannot add 6.0 ESXi host to vCenter 6.0

    Hi guys,.
    I'm having a problem where I can not add any ESXi 6.0 host to vCenter 6.0. I can add an ESXi 5.5 without problem.

    I have the error that I get in the vpxd log is:

    2015 06-18 T 16: 36:37.312 + 01:00 info vpxd [03624] [sub Originator@6876 vpxLro = 120602 ca opID =] [VpxLRO] - tache-interne-69093--datacenter-26--vim BEGIN. Datacenter.queryConnectionInfo--524f7656-a68d-ef60-05e7-f24ec8a5f1b5(52359e42-f098-7b77-bc82-0cff38aa6ff9)

    2015 06-18 T 16: 36:37.314 + 01:00 vpxd error [04352] [Originator@6876 = 000001-HttpConnectionPool sub] [ConnectComplete] connection failed for < cs p:0000000008c8bfb0, TCP:192.168.0.12:443 >; CNX: (null), error: class Vmacore::Ssl:SSLException(SSL_Exception:_error:140000DB:SSL_routines:SSL_routines:short_read)

    2015 06-18 T 16: 36:37.314 + 01:00 vpxd error [03624] [sub Originator@6876 = opID httpUtil 120602 ca =] [HttpUtil::ExecuteRequest] error in sending request - SSL Exception: error: 140000DB:SSL routines: SSL routines: short read

    I can ping and resolve all ESXi host and checked the SSL certs and they look good too.

    Any help would be appreciated

    Dougie cordially

    Found the problem as vCenter 6.0 version I was running. I was running an older version of the VC and the current version of ESXi.
    Downloaded the current version and reinstalled and all good.

    Dougie

  • vMA 5.5 error: cannot add users.

    Hello.

    I need to add 3 guests to vMA.I is not domain controller.

    1 deploy charges vMA of the FVO and configure the IP and password for admin-vi.

    2. Add the first host from ESX01 successfully. ( vifp addserver esx02 - fpauth authpolicy)

    3. added ESXi of second and third finishing with failure. (commands below)

    VI-admin@vma02:~ > vifp addserver esx02 authpolicy - fpauth

    root@esx02's password:

    VI-admin@vma02:~ > vifp mailing lists

    esx02.localdomain ESXi

    VI-admin@vma02:~ > vifp addserver esx03 authpolicy - fpauth

    root@esx03's password:

    Error: Cannot add users

    in vSphere client, you can see something that:

    vma01.png

    For above tasks creates user-vi and vi-admin next. After that many seconds, vi-admin is removed (I dunno why...)

    /var/log/VMware/VMA/vifpd.log on vMA

    [2016 04-07 19:51:07.186 7F220CD47700 info "App"] command-> 1

    [2016 04-07 19:51:07.187 7F220AEC7700 info "App"] ADDSERVER

    [2016 04-07 19:51:07.197 7F220CD47700 info "App"] MessageQueue::RecvMessage - id of the queue is 0

    [2016 04-07 19:51:07.595 7F220AEC7700 info "App"] MessageQueue::SendMessage - id of the queue is 0

    [2016 04-07 19:51:12.144 7F220CD47700 info "App"] command-> 1

    [2016 04-07 19:51:12.145 7F220CD47700 info "App"] MessageQueue::RecvMessage - id of the queue is 0

    [2016 04-07 19:51:12.145 7F220AE45700 info "App"] ADDSERVER

    [2016 04-07 19:51:12.504 7F220AE45700 info "App"] Already connected.

    [2016 04-07 19:51:12.509 7F220AE45700 info "App"] Already connected.

    [2016 04-07 19:51:30.308 7F220AE45700 info "App"] permissions set for [email protected]

    Credstore [2016-04-07 19:51:30.345 7F220AE45700 info "App"]: Add [email protected] credstore vi-admin user

    [2016 04-07 19:51:30.361 7F220AE45700 info "App"] can take possession of the user [email protected].

    [2016 04-07 19:51:30.361 7F220AE45700 WARNING "App"] ownership of [email protected] because it seems to be created by us.

    [2016 04-07 19:51:52.534 7F220AE45700 error 'App'] addserver: error occurred when adding users to esx03.localdomain... roll back. Error in Vma

    kernel.

    [2016 04-07 19:51:52.582 7F220AE45700 info "App"] User [email protected] is created by vifp. Detached...

    [2016 04-07 19:51:52.703 7F220AE45700 info "App"] could not remove permissions for [email protected].

    [2016 04-07 19:51:52.704 7F220AE45700 info "App"] deleted user [email protected].

    [2016 04-07 19:51:52.733 7F220AE45700 info "App"] [email protected] the user is removed from vi-admin credstore.

    [2016 04-07 19:51:52.768 7F220AE45700 error 'App'] Cannot add users

    [2016 04-07 19:51:52.768 7F220AE45700 info "App"] MessageQueue::SendMessage - id of the queue is 0

    [2016 04-07 19:51:52.772 7F220AE45700 info "App"] MessageQueue::SendMessage - id of the queue is 0

    In what newspapers can I find something more?

    var/log/VMkernel.log on the host is not clear to me... but if someone asks I'll stick.

    What should I do more? I want only add 3 esxi servers at VMAs and the next time you connect to these esxi without putting password.

    Interesting, that's when I deployed the next vMA02 and VM03, I can only add an esxi to vMA. During the second and third esxi adding that generate the same mistakes... Now I have 1 vMA for each host ...

    Please on the suggestion and help... because my adventure with vMA is not good... the last time I was the problem with this vMA 5.5 the session is not authenticated after connect you to the target ESXi and not solved this in my second lab...

    Sebastian

    Update:

    I use this command to only simple time without authpolicy:

    Newspapers:

    Command [2016-05-11 04:15:20.216 7F7A93D87700 info "App"]-> 1

    [2016-05-11 04:15:20.219 7F7A91E85700 info "App"] ADDSERVER

    [2016-05-11 04:15:20.223 7F7A93D87700 info "App"] MessageQueue::RecvMessage - id of the queue is 0

    [2016-05-11 04:15:20.362 7F7A91E85700 info "App"] MessageQueue::SendMessage - id of the queue is 0

    Command [2016-05-11 04:15:24.144 7F7A93D87700 info "App"]-> 1

    [2016-05-11 04:15:24.144 7F7A93D87700 info "App"] MessageQueue::RecvMessage - id of the queue is 0

    [2016-05-11 04:15:24.144 7F7A91EC6700 info "App"] ADDSERVER

    [2016-05-11 04:15:24.196 7F7A91EC6700 info "App"] Already connected.

    [2016-05-11 04:15:24.198 7F7A91EC6700 info "App"] Already connected.

    [2016-05-11 04:15:24.732 7F7A91EC6700 info "App"] permissions set for [email protected]

    Credstore [2016-05-11 04:15:24.777 7F7A91EC6700 info "App"]: Add [email protected] credstore vi-admin user

    [2016-05-11 04:15:24.791 7F7A91EC6700 info "App"] can take possession of the user [email protected].

    [2016 05-11 04:15:24.793 7F7A91EC6700 WARNING "App"] ownership of [email protected] because it seems to be created by us.

    [2016-05-11 04:15:26.943 7F7A91EC6700 info "App"] permissions set for [email protected]

    Credstore [2016-05-11 04:15:26.980 7F7A91EC6700 info "App"]: adds the [email protected] vi-user credstore user

    [2016-05-11 04:15:27.052 7F7A91EC6700 info "App"] MessageQueue::SendMessage - id of the queue is 0

    Test:

    VI-admin@localhost:/var/log/VMware/VMA > vifp mailing lists

    ESX01.localdomain ESXi

    esx02.localdomain ESXi

    esx03.localdomain ESXi

    VI-admin@localhost:/var/log/VMware/VMA > vifptarget s esx03.localdomain

    VI-admin@localhost:/var/log/VMware/VMA[esx03.localdomain] > esxcli vm process list

    vMA02

    World ID: 35859

    Process ID: 0

    VMX Cartel ID: 35856

    UUID: 42 37 c3 b6 11 61 29 95 - 30 98 9f c1 b3 44 95 ba

    Full name: vMA02

    The configuration file: / vmfs/volumes/56edd79c-9225dbd5-c1a2-2cc260319711/vSphere Management Assistant (vMA) / vSphere Management Assistant (vMA) .vmx

    vMA03

    World ID: 39084

    Process ID: 0

    VMX Cartel ID: 39081

    UUID: 42 37 be 3rd 4 b 98 8 b - f0 to f9 cf 0c ec e6 f2 f9 0c

    Full name: vMA03

    The configuration file: /vmfs/volumes/56edd87a-e0640a1a-0842-2cc260319711/vMA03/vMA03.vmx

    Correct on esx03 I have vMA03 and vMA02.

    Then seems OK.

    Case closed.

  • Cannot add the printer network Windows 7 64 bit

    My laptop Home Premium 64 - bit of Windows 7 (client) cannot add the network printer that sits on the Windows 7 Ultimate 64 bit computer. A client XP computer easily added the network printer. When you try to add the network printer, the Windows 7 client searches for the driver on the host computer and says "unable to connect to the printer - the operation has failed with error 0x000003e3. I downloaded the driver from the manufacturer of the printer to the client computer. I also disabled the firewall on the computers... Any help would be appreciated.

    Hello

    ·         What is the number and model of the printer that you are using?

    ·         How many computers are connected to the host computer?

    ·         You are on a domain network?

    Method 1:

    You can check the items below that explain how to install a printer in Windows 7.

    Install a printer

    http://Windows.Microsoft.com/en-us/Windows7/install-a-printer

    Find and install printer drivers

    http://Windows.Microsoft.com/en-us/Windows7/find-and-install-printer-drivers

    Method 2:

    a. now follow the document below to add the printer to the Windows 7 computer.

    http://Windows.Microsoft.com/en-us/Windows7/share-a-printer

    b. If the steps above does not help try the procedure below.

    We need to change the port and check. Let us perform the steps below to install this printer and check.

    a. Click Start, click Control Panel, and double click on devices and printers.

    b. click Add a printer.

    c. Select "add a local printer.

    d. Select "create a new port". Select "Local Port" as the port type.

    e. in the "type a port name" box, type the address in the following format.

    \\[IP address of the host computer]------[the share name of the printer]

    And then click Next.

    f. Select the driver in the list of drivers. If no driver available, click the Windows Update button, wait the process finishes and then search for the driver again.

    g. complete the installation.

    For additional help, refer to the article below.

    Printer in Windows problems

    You can also check out the link below that addresses the same issue when you face:

    http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-hardware/error-0x000003e3-when-trying-to-install-network/2348b57b-7448-E011-8dfc-68b599b31bf5?msgId=d577ab02-DC48-E011-8dfc-68b599b31bf5

  • vifp addserver fails with the error cannot add the user

    This my first post on this forum that I couldn't find an answer via Google search. If I do not use correct terminology or fail to provide comprehensive information, please forgive me. I'm not an expert on VMWare, just a passionate curious tech. I found VMWare to be a very exciting and easy to use product. The VMWare knowledge base is excellent and so is the community of users.

    I have install VMWare ESXi 6.0 free House on servers Dell T420 and T110 II. I recently tested vMA 5 by installing it as a virtual machine on one of the servers. I watched the tutorial Youtube how to use vifp to add servers. I have network etc. on vMA installation and it works fine. Automatic update worked. I issue the command sudo vifp addserver 192.168.250.96, I am prompted for the password. When I enter the password, I get an error error: cannot add users. I checked the log file in /var/opt/vmware/vma/vifpd.log and the more descriptive message is:

    addServer: error occurred when adding users for 192.168.250.96... roll back. An error occurred during the creation of users on 192.168.250.96

    Then I noticed that since I'm on the console vMA to run these commands, as soon as the error occurs, I see that in the lower part, under recent tasks, I see an error: General system error: weak password. The details of the error says:

    vMA Error 1.JPG

    Weak password: not quite different characters or classes.

    Now my password is strong enough. I can't post it here but I'll post a similar password:

    4518Gabdhjg #01

    It is 14 characters and has the numbers, letter uppercase, lowercase letters and special characters. I read the VMWare documentation on passwords and for me, the password seems very well. Any help will be appreciated.

    Thank you

    Arun Gupta

    My bad. I didn't know that vMA 6.0 is available. I just downloaded and configured vMA 6.0 and the problem is solved. Sorry for disturbing everyone.

  • When you add the data to the host of the second store it wants to format storage

    I have two hosts ESXi 5.5, one is the main host who currently runs the set of virtual machine from this data store. I would add the data store to the host, but to do so is greyed out on the new server, and he wants I want to format the data store.

    UPDATE:

    I used this thread to solve: cannot add to ESXi host VMFS datastore

    More precisely:

    Try the following command

    #esxcfg - volume - l

    This should show the volume

    To constantly increase the volume, use esxcfg-volume - M followed of the UUID or volume name

    Thank you for looking, sorry to distract. I saw this thread when troubleshooting first. Good day to all!

    Post edited by: TH2

    What type of shared storage using you, and you haven't set up the presentation of the logic unit number for the second host in the same way that you did for the first host? Do you manage the host with vCenter Server, or if you use two autonomous host computers?

    André

  • After upgrading vSphere 5.5 replication device cannot add VM replication

    Dear all,

    We have improved our server vcenter and device of replicaion of vpshere of version 5.1 to 5.5. after upgrade cannot add new virtual machine replication replication vsphere device. Configure the replication vsphere option grey out on VM right click menu. See the image below.

    replication.JPG

    Please advice how to solve this problem.

    Thank you and best regards,

    Lasa.

    Hello

    There is a known issue for this behavior described in VMware vSphere replication 5.5 Release Notes (shares of vSphere in vSphere Client Web replication are not available after the upgrade.) The solution is to restart your Web Client vSphere

  • VMotion error: host vmware cpu is not compatible with the requirements of the judgment of the VM to CPUID level register 0 x 1 'ecx '.

    Problem: I can't move my Exchange vmserver2 a vmserver1 server.

    Error: "host vmware cpu is not compatible with the requirements of the judgment of the VM to CPUID level register 0 x 1"ecx"


    Details:

    Vmware KB:

    * Ensure that the hosts have the same features enabled in the BIOS of the servers. If there is an incompatibility between the servers BIOS configuration even if they are physically identical, they always show a compatibility error message. The two most common to check features are the No-Execute memory Protection (NX / XD) and virtualization technology (VT / AMD - V).

    A ran the CPU utility Vmware as referenced by

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003718


    "CPU that have similar features. "This means that the need of processors from the same manufacturer (AMD or Intel), be of the same family (Pentium, Xeon, etc.), and have common features extended between ESX servers involved in the VMotion.

    My results:

    vmserver1 Dell Inc.    PowerEdge 2950 2 Intel Xeon E5405 of CPU @ 2.00GHz
    vmserver2 Dell Inc.    PowerEdge 2950 2 Intel Xeon L5410 of CPU @ 2.33 GHz

    They both share exactly the same characteristics:
    FT support
    Enable VT
    VT Capable
    NX/XD
    FFXSR
    RDTSCP
    SSE
    SSE2
    SSE3

    Support Relaxations:
    NX/XD
    RDTSCP

    Relaxations unsupported:
    All THE features of the SSE
    FFXSR
    CMPXCHG18B

    In the 'Show Windows debug' it reads 'of the compatible CPU"

    This virtual Exchange machine works since Esxi version 3.5.  I am testing now vCenter Server 5.0 with version 5.0.1 on the Esxi server.

    Note: I've also been meeting random uses CPU high, leading from Windows Server 2008 to lock up completely.  I have found no trace of problems within the Windows host and Vcenter is not questions.  I have "reset" of the virtual machine in order to get the server back online.  The CPU to the top lock is random and the server can run for days with no problems. * Don't know if it's related...

    Virtual host config Exchange computer:
    Guest operating system: MS Windows Server 2008 64 bit
    version 8 of virtual machine
    CPU: 4vCPU
    Memory: 10240MB
    Overload memory: 420,61 MB
    vSphere HA Protection: protected
    Host CPU consumed: the 209 MHz

    Maps: vmserver1 watch "CPU is not compatible" CPU: 0% (none of the virtual machine running)
    Consumed host memory: 9823,00 MB
    Active memory of Fords: 409,00 MB

    Views of storage: I have a warning symbol on the QNAP iSCSI disk that hosts the virtual Exchange computer but I see no record... I'm new here...

    I understand that vmotion apply restrictions on the movement of VM compatibility to avoid it.  The components of the HA does not apply to these requirements.  We tested yesterday HA, succsessfully and this how we came to be stuck with the Exchange vm on vmserver2 and it cannot migrate to vmserver1.

    I appreciate your time and consideration,
    Tim

    It seems that you have two different processor speeds. Try the VCA mode and also check the BIOS version you and make sure they match.

  • Question about maximum of Configuration - 256 LUNS per host,

    Hi all

    maximum rates of configration document 5 vpshere says:

    FibreChannel:

    LUNS per host: 256

    Number of paths to a LUN: 32

    Number of total paths on a server: 1024

    within a Cluster VM guests didn't see all LUNS, so it would be easy to hit those numbers.

    What I want to know is:

    When 1 disk is visible on paths (at least) 2 - How many LUNS must be counted?

    For as far as I understand, EMC Powerpath (I think - multi pathing VMware also does) presents only pseudo-device as usable LUN.

    I count:

    1 LUN - because only the pseudo-device is considered by the kernel?

    or

    2 LUN - LUN visible via 2-way?

    or

    MON 3 - 2 paths more pseudo-device?

    Thanks in advance

    1 disk accessed by multiple path is considered to be a LUN

Maybe you are looking for