alextsa's Posts

Hi all Anyone know SRM can support the storage use different type of transport in protected and recovery site? Say protected site use FC between the ESXi and storage, but recovery site use iSCSI? Or it depends on the SRA? Best regards   Alex

Hi all We are using vCenter 6.0 and SRM 6.1.1, and working well for few years, and then we need to upgrade the vCenter 6.0 to U3. Once updated, then the SRM plug-in disappear in the vCenter. Then I go to check the compatibility matrix and found that vCenter 6.0 U3 need to work with 6.1.2, so I go to upgrade the SRM to 6.1.2. But unfortunately I still cannot see the SRM plug-in in the vCenter after upgrade. Then I go to check the vsphere_client_virgo.log and find the below error? Anyone have experience on this? Log search by Error [2019-11-22T13:44:58.216+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/rsls' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/rsls' already exists [2019-11-22T13:44:58.220+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.rsls' version '6.1.2': a web application with context path '/vsphere-client/srm/rsls' already exists. [2019-11-22T13:44:58.223+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.rsls' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:06.923+08:00] [ERROR] srm-topology-thread-4         c.v.srm.client.topology.impl.vmomi.osgi.VmodlContextInitializer   Failed to load package 'com.vmware.vim.binding.cis.metadata'. org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [com/vmware/vim/binding/cis/metadata/context.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/vmware/vim/binding/cis/metadata/context.xml] cannot be opened because it does not exist [2019-11-22T13:45:11.523+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/srm-bootstrap' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/srm-bootstrap' already exists [2019-11-22T13:45:11.526+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2': a web application with context path '/vsphere-client/srm/srm-bootstrap' already exists. [2019-11-22T13:45:11.529+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:15.735+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/inventory-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/inventory-ui' already exists [2019-11-22T13:45:15.738+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.inventoryui' version '6.1.2': a web application with context path '/vsphere-client/srm/inventory-ui' already exists. [2019-11-22T13:45:15.741+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.inventoryui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g... [2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g... [2019-11-22T13:45:20.143+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/abr-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/abr-ui' already exists [2019-11-22T13:45:20.146+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.abrui' version '6.1.2': a web application with context path '/vsphere-client/srm/abr-ui' already exists. [2019-11-22T13:45:20.149+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.abrui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:24.440+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/group-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/group-ui' already exists [2019-11-22T13:45:24.443+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.groupui' version '6.1.2': a web application with context path '/vsphere-client/srm/group-ui' already exists. [2019-11-22T13:45:24.446+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.groupui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:28.706+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/plan-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/plan-ui' already exists [2019-11-22T13:45:28.709+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.planui' version '6.1.2': a web application with context path '/vsphere-client/srm/plan-ui' already exists. [2019-11-22T13:45:28.712+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.planui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:37.293+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/vm-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/vm-ui' already exists [2019-11-22T13:45:37.296+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.vmui' version '6.1.2': a web application with context path '/vsphere-client/srm/vm-ui' already exists. [2019-11-22T13:45:37.298+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.vmui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start [2019-11-22T13:45:37.306+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.core.model.CompositeException                     CompositeException [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException Log search by vcDr [2019-11-22T13:44:56.415+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.vim.extension.VcExtensionManager                  Done expanding plugin package to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 [2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin id mismatch between the registered extension key (com.vmware.vcDr) [2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin version mismatch for com.vmware.vcDr between the plugin registration info (6.1.2.16353) [2019-11-22T13:44:56.421+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Deploying plugin package 'com.vmware.vcDr:6.1.2.16353'. [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException [2019-11-22T13:45:39.448+08:00] [WARN ] data-service-pool-307        70004163 100050 200040 com.vmware.vise.vim.data.adapters.search.impl.QueryExecutor       object with no server guid: urn:vri:cm:Service:e207e0da-b30c-4fb7-896b-2776ac26a58b_com.vmware.vcDr/MTAuMC4yMzMuMTA1 (class java.net.URI) Best regards Alex Tsang

Dear all I just installed a SRM6.1 and the storage is Dell Compellent running Storage Center version 7.1. After I installed the SRA, and the pair can be discovered successfully, but some of them cannot match the local datastore, just like below Then I checked the log in the SRM  and found the below, it said device "#" matches two different devices. Then I checked the NAA ID, the red one is the Protocol Endpoint presented by the Dell Compellent and the black one is the actual LUN. 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '5' matches two different devices 'naa.6000d310033f60010000000000000005' and 'naa.6000d310033f60000000000000000007' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '6' matches two different devices 'naa.6000d310033f60010000000000000006' and 'naa.6000d310033f60000000000000000008' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '8' matches two different devices 'naa.6000d310033f60010000000000000008' and 'naa.6000d310033f6000000000000000000a' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '9' matches two different devices 'naa.6000d310033f60010000000000000009' and 'naa.6000d310033f6000000000000000000b' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '10' matches two different devices 'naa.6000d310033f6001000000000000000a' and 'naa.6000d310033f6000000000000000000c' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '12' matches two different devices 'naa.6000d310033f6001000000000000000c' and 'naa.6000d310033f6000000000000000000e' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '13' matches two different devices 'naa.6000d310033f6001000000000000000d' and 'naa.6000d310033f6000000000000000000f' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '14' matches two different devices 'naa.6000d310033f6001000000000000000e' and 'naa.6000d310033f60000000000000000010' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '15' matches two different devices 'naa.6000d310033f6001000000000000000f' and 'naa.6000d310033f60000000000000000011' 2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '16' matches two different devices 'naa.6000d310033f60010000000000000010' and 'naa.6000d310033f60000000000000000012' So may I know any one here got the same experience? Why the vCenter/SRM think protocol endpoint are same as the protocol endpoint? And how to fix it? I checked Dell's manual seems we cannot disable the protocol endpoint in Storage. Best regards Alex Tsang

Dear all I just install a new SRM for my DR setup, and the Storage is Dell Compellent. It's quite smooth when I setup the array based replication by using DSM, installation of the SRM with embedded DB and pair site. Then I add the array manager for my production and DR storage, but I found that after complete pair the storage in the array manager, then the SRM service will stop. The below is the log I captured before the service stopped 2017-12-05T23:57:58.829+08:00 [04344 info 'TagManager' opID=40236f0a] Dr::Storage::TagCategoryStore::CreateTagsDone: Adding 'com.vmware.vcDr:::2429d66e-55eb-49ad-835f-92abd934d9ad' as used by to tag 574bb5db-fb90-4fb3-a7b6-d7d718e81129 2017-12-05T23:57:58.829+08:00 [04344 info 'TagManager' opID=40236f0a] Dr::Storage::TagCategoryStore::CreateTagsDone: Adding 'com.vmware.vcDr:::2429d66e-55eb-49ad-835f-92abd934d9ad' as used by to tag 995447f5-8352-4c31-b67f-a166459c767f 2017-12-05T23:57:58.829+08:00 [04344 info 'TagManager' opID=40236f0a] Dr::Storage::TagCategoryStore::CreateTagsDone: Adding 'com.vmware.vcDr:::2429d66e-55eb-49ad-835f-92abd934d9ad' as used by to tag bed81794-974c-4c9a-9320-1f854b09f2f7 2017-12-05T23:57:58.829+08:00 [05312 verbose 'QsProvider'] Created entry iterator [class Dr::QueryService::ObjectEntryIterator:000000000C0CE160] from generation 137. Max generation 140 2017-12-05T23:57:58.845+08:00 [05496 panic 'Default' opID=40236f0a] --> --> Panic: Assert Failed: "dsHostMountIt != dsHostMounts.end() (Dr::Storage::Data::CreateDeviceGroupInfoCollectionData: can't find host mounts for ds [vim.Datastore:e207e0da-b30c-4fb7-896b-2776ac26a58b:datastore-208])" @ d:/build/ob/bora-2700459/srm/src/storage/dataaccess/deviceGroupInfoCollectionData.cpp:216 --> Backtrace: --> --> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 6.0.0, build: build-2700459, tag: - --> backtrace[00] vmacore.dll[0x001BC46A] --> backtrace[01] vmacore.dll[0x0005B92F] --> backtrace[02] vmacore.dll[0x0005CA5E] --> backtrace[03] vmacore.dll[0x001D4F45] --> backtrace[04] vmacore.dll[0x001D503D] --> backtrace[05] vmacore.dll[0x0004CBFC] --> backtrace[06] dr-storage.dll[0x00290848] --> backtrace[07] dr-storage.dll[0x000B1DCF] --> backtrace[08] dr-storage.dll[0x000B180B] --> backtrace[09] dr-storage.dll[0x00306045] --> backtrace[10] dr-storage.dll[0x0030330C] --> backtrace[11] dr-storage.dll[0x00302C45] --> backtrace[12] dr-storage.dll[0x0030604D] --> backtrace[13] dr-storage.dll[0x0030330C] --> backtrace[14] dr-storage.dll[0x00302C45] --> backtrace[15] dr-storage.dll[0x003017E2] --> backtrace[16] connection.dll[0x00B4BE83] --> backtrace[17] connection.dll[0x00017E49] --> backtrace[18] connection.dll[0x001F6B9F] --> backtrace[19] connection.dll[0x00B75F55] --> backtrace[20] connection.dll[0x001DD1EE] --> backtrace[21] connection.dll[0x001DEF6E] --> backtrace[22] connection.dll[0x00B75F55] --> backtrace[23] connection.dll[0x004B359C] --> backtrace[24] connection.dll[0x001FCC9F] --> backtrace[25] connection.dll[0x001FB846] --> backtrace[26] connection.dll[0x00B75F55] --> backtrace[27] connection.dll[0x00017E49] --> backtrace[28] connection.dll[0x001FCC9F] --> backtrace[29] connection.dll[0x001FB846] --> backtrace[30] connection.dll[0x00B75F55] --> backtrace[31] connection.dll[0x00B75F55] --> backtrace[32] connection.dll[0x004B359C] --> backtrace[33] connection.dll[0x001FCC9F] --> backtrace[34] connection.dll[0x001FB846] --> backtrace[35] connection.dll[0x00B75F55] --> backtrace[36] connection.dll[0x0020043E] --> backtrace[37] connection.dll[0x002000AF] --> backtrace[38] vmomi.dll[0x0005C1FC] --> backtrace[39] vmacore.dll[0x001506FE] --> backtrace[40] vmacore.dll[0x00153F3F] --> backtrace[41] vmacore.dll[0x00155491] --> backtrace[42] vmacore.dll[0x001571C5] --> backtrace[43] vmacore.dll[0x00064EDB] --> backtrace[44] vmacore.dll[0x001526D0] --> backtrace[45] vmacore.dll[0x001D059B] --> backtrace[46] MSVCR90.dll[0x00002FDF] --> backtrace[47] MSVCR90.dll[0x00003080] --> backtrace[48] KERNEL32.DLL[0x0000168D] --> backtrace[49] ntdll.dll[0x00074629] --> [backtrace end] --> And even I start it again and it will stop immediately. Then same error occur. 2017-12-06T08:31:45.461+08:00 [12120 verbose 'SraCommand' opID=3086f6b1] Stopped listening for updates to file 'C:\Windows\TEMP\vmware-SYSTEM\sra-status-11-111' 2017-12-06T08:31:45.461+08:00 [12120 verbose 'SraCommand' opID=3086f6b1] Cancelling SRA command timeout 2017-12-06T08:31:45.461+08:00 [12120 info 'SraCommand' opID=3086f6b1] discoverArrays exited with exit code 0 2017-12-06T08:31:45.461+08:00 [12120 verbose 'SraCommand' opID=3086f6b1] discoverArrays responded with: --> <?xml version="1.0" encoding="UTF-8" ?> --> <Response xmlns="http://www.vmware.com/srm/sra/v2"  xmlns:compellent="http://www.compellent.com/srm/sra/v2"> -->     <Arrays> -->         <Array id="212832"> -->             <Name>Storage01</Name> -->             <Model> -->                 <Name>Storage01</Name> -->                 <Vendor>Dell Compellent</Vendor> -->             </Model> -->             <ReplicationSoftware> -->                 <Name>Storage Manager</Name> -->                 <Version>16.3.1.301</Version> -->             </ReplicationSoftware> -->             <PeerArrays> -->                 <PeerArray  id="245976" /> -->             </PeerArrays> -->         </Array> -->     </Arrays> --> </Response> 2017-12-06T08:31:45.461+08:00 [11984 panic 'Default' opID=4c664ceb] --> --> Panic: Assert Failed: "dsHostMountIt != dsHostMounts.end() (Dr::Storage::Data::CreateDeviceGroupInfoCollectionData: can't find host mounts for ds [vim.Datastore:e207e0da-b30c-4fb7-896b-2776ac26a58b:datastore-208])" @ d:/build/ob/bora-2700459/srm/src/storage/dataaccess/deviceGroupInfoCollectionData.cpp:216 --> Backtrace: --> --> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 6.0.0, build: build-2700459, tag: - --> backtrace[00] vmacore.dll[0x001BC46A] --> backtrace[01] vmacore.dll[0x0005B92F] --> backtrace[02] vmacore.dll[0x0005CA5E] --> backtrace[03] vmacore.dll[0x001D4F45] --> backtrace[04] vmacore.dll[0x001D503D] --> backtrace[05] vmacore.dll[0x0004CBFC] --> backtrace[06] dr-storage.dll[0x00290848] --> backtrace[07] dr-storage.dll[0x000B1DCF] --> backtrace[08] dr-storage.dll[0x000B180B] --> backtrace[09] dr-storage.dll[0x00306045] --> backtrace[10] dr-storage.dll[0x0030330C] --> backtrace[11] dr-storage.dll[0x00302C45] --> backtrace[12] dr-storage.dll[0x0030604D] --> backtrace[13] dr-storage.dll[0x0030330C] --> backtrace[14] dr-storage.dll[0x00302C45] --> backtrace[15] dr-storage.dll[0x003017E2] --> backtrace[16] connection.dll[0x00B4BE83] --> backtrace[17] connection.dll[0x00017E49] --> backtrace[18] connection.dll[0x001F6B9F] --> backtrace[19] connection.dll[0x00B75F55] --> backtrace[20] connection.dll[0x001DD1EE] --> backtrace[21] connection.dll[0x001DEF6E] --> backtrace[22] connection.dll[0x00B75F55] --> backtrace[23] connection.dll[0x004B359C] --> backtrace[24] connection.dll[0x001FCC9F] --> backtrace[25] connection.dll[0x001FB846] --> backtrace[26] connection.dll[0x00B75F55] --> backtrace[27] connection.dll[0x00017E49] --> backtrace[28] connection.dll[0x001FCC9F] --> backtrace[29] connection.dll[0x001FB846] --> backtrace[30] connection.dll[0x00B75F55] --> backtrace[31] connection.dll[0x00B75F55] --> backtrace[32] connection.dll[0x004B359C] --> backtrace[33] connection.dll[0x001FCC9F] --> backtrace[34] connection.dll[0x001FB846] --> backtrace[35] connection.dll[0x00B75F55] --> backtrace[36] connection.dll[0x0020043E] --> backtrace[37] connection.dll[0x002000AF] --> backtrace[38] vmomi.dll[0x0005C1FC] --> backtrace[39] vmacore.dll[0x001506FE] --> backtrace[40] vmacore.dll[0x00153F3F] --> backtrace[41] vmacore.dll[0x00155491] --> backtrace[42] vmacore.dll[0x001571C5] --> backtrace[43] vmacore.dll[0x00064EDB] --> backtrace[44] vmacore.dll[0x001526D0] --> backtrace[45] vmacore.dll[0x001D059B] --> backtrace[46] MSVCR90.dll[0x00002FDF] --> backtrace[47] MSVCR90.dll[0x00003080] --> backtrace[48] KERNEL32.DLL[0x0000168D] --> backtrace[49] ntdll.dll[0x00074629] --> [backtrace end] -->

Dear all I have a question about vMotion after the I have upgrade one host from 5.0 to 5.1 in a cluster which has two hosts and hope the expert here can give me some advices. Before I upgrade one of the ESX host in the cluster from 5.0 to 5.1, the vMotion run without any problem for the VM that are version 7 and 8. I upgraded one of the ESX host in the cluster form 5.0 to 5.1 and I vMotion all VM from that host that need to be upgraded, then after the upgrade success, I try to vMotion all hosts from that 5.0 host to the new upgraded 5.1 to do the remaining upgrade and I have the below symptom 1. VM Version 7 Guest OS can be migrated without any problem 2. VM Version 8 Guest OS failed in the validation stage with the attached error But when I try to shutdown the Guest OS and offline migrate from the 5.0 to 5.1 it is success and after we did action, the vMotion for that gues OS is working properly. So, anyone here encounter this issue? Best regards Alex Tsang

Dear all I have a ESX with initially installed ESX 4.1 U1 (4.1.0, 260247) and I am trying to upgrade it to ESXi 5 via the update manager. According to the documentation, a newly installed ESX 4.1 should be able to upgrade to ESXi 5 via the update manager. But when I try to do the upgrade in the update manager, the below error was shown, so may I know any one try to upgrade ESX 4.1 to ESXi 5 vai update manager? The host partition layout is not suitable for upgrade. Best regards Alex Tsang

Dear all Did any one trry to do guest OS customization when deploy a CentOS 6.x template? I configured a new VM with Linux installed a CentOS6.3, use ext3 for the partition and install the latest version of the vmware tools. Then deploy a new VM from  this template and do customization. Everything go smooth and the hostname name can be change but I found that only the NIC setting cannot be applied to the VM that deployed by this template - the old NIC -eth0 will remain in the OS but it cannot bring up and old configuration remain, then a new NIC -eth1 was generated but no IP was configured. But I checked the configuration under the /etc/sysconfig/networking-scripts, the IP address configured are applied to the script there. Moreover, anyone know the LVM or ext4 are the supported partition formation for the linux OS customization? Or still ext2 and 3 in ESX and vCenter 5? Best regards Alex Tsang

Dear all I am using VCenter and ESX 4.1 and I tried to use the VCenter Converter in VCenter or Converter standalone to convert a W2K3 SP2 machine, but I get "Unable to obtain hardware Information" just after the frist step. Then I export the log and found the below error From VMWare-converter-server1.log [#2] [2011-10-07 18:49:38.421 02692 warning 'Locale'] Requested locale '' and/or derived locale 'Chinese_Hong Kong' not supported on OS. Using English. [#3] [2011-10-07 18:49:41.531 02692 warning 'Locale'] Requested locale '' and/or derived locale 'Chinese_Hong Kong' not supported on OS. Using English. [#3] [2011-10-07 18:49:42.687 00332 error 'App'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1) [#3] [2011-10-07 18:50:47.421 02692 info 'App'] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded [#3] [2011-10-07 18:50:47.437 02692 info 'vmomi.soapStub[0]'] Resetting stub adapter for server PIPE:\\.\pipe\vmware-converter-worker-soap : Closed [#3] [2011-10-07 18:50:47.484 02692 warning 'vmomi.soapStub[0]'] Canceling invocation: server=PIPE:\\.\pipe\vmware-converter-worker-soap, moref=converter.agent.AgentSessionManager:ConverterAgentSessionManager, method=logout From Converter-gui3.log [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type microsoftVirtualPCVM not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type parallelsVM not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type vmwareVCBBackup not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type livestateBackup not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type shadowProtectBackup not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type acronisBackup not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type vmwareVM not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildFilter 3rd party type vmwareVCBBackup not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildThirdpartyHostedExtVector 3rd party type vmwareVM not found [2011-10-07 18:58:37.078 00212 error 'App'] SourceSelectPluginModel::BuildThirdpartyHostedExtVector 3rd party type vmwar [2011-10-07 18:58:46.078 00332 error 'wizardController'] Cannot query source HW info: vmodl.fault.SystemError So, may I know anyone encounter this and how to solve it? A converter log is attached for your reference. Please let me know if you have any quesiton, many thanks. Best regards Alex Tsang