Quantcast
Channel: VMware Communities: Message List
Viewing all 230656 articles
Browse latest View live

Cannot get virtual machines to communicate outside the physcal VM Host but the host (via vmk0) can

$
0
0

May be missing something simple here - this is the setup.

 

  • latest version of ESXi
  • 2 x CentOS virtual machines in one port group
  • 1 x vswitch that CenOS VMs and management network connected to
  • 2 x physical Nics

 

The scenario is - the 2 x CentOS VM's can ping each other and the management console (VM host), but cannot ping the gateway (physical switch) or any other physical machines on the network. However, from the command prompt on the management console, it can ping the switch and any other physical machine. When running pktcap and monitoring the ip address of the 2 CentOS VM's - packets are captured when they ping themselves or the management console but packets are not captured (transmitted) when they try and ping a physical machine outside of the VM host. Routing is all set up OK under CentOS, no f/w running or selinux

 

Bottom line, the VM host appears to be able to get out of the physical VM server with no issues but the two virtuals cannot

 

Any thoughts welcome :-)

 

Cheers - Mike


Re: Horizon 7 replication issue with German Windows 2012 R2 versions?

$
0
0

I didn't have the chance to open a support case yet, and have to delay it until the next time I visit the customer.

 

André

Re: Compatibility CPU and ESXi  5.1 U3, 5.5, 6.0

$
0
0

Hello Richardson,

thanks a lot for your reply, I very appreciate your comments. Basically what you propose is the correct way and I fully agree. But there is a complication, primary goal is to increase a performance of current vSphere 5.1 cluster (running on old HP blades) as soon as possible. But we have to at first resolve inter-compatibility between VMware products which we are using now (SRM 5.1, Horizon), prepare detailed plan for upgrade from vSphere 5.1 to 6.0 and for Horizon, SRM as well, everything with minimal downtime. Without proper plan and with good time budget it is difficult to do it in my opinion. So one quick solution was try to find some CPUs which supports vSphere 5.1 U3 and vSphere 6.0. To support vSphere 6.0 is because in the future there is definitely a plan to upgrade all VMware products (vSphere, SRM, VDI) to 6.0, so it doesn't make sense now to buy old blade servers supporting only vSphere 5.1 and through it away after upgrade to vSphere 6.0. Thank you, Hejbi

Re: Compatibility CPU and ESXi  5.1 U3, 5.5, 6.0

$
0
0

I will provide blade server types tomorrow, but in my opinion there is keypoint CPU type in this case.

Re: Office 2013 configuring after every launch

$
0
0

I have no other versions of Office on the base image. I followed all the guidelines for provisioning too including not opening any application and activating using the ospp.vbs.

Office activates without any issue and if I open Word for example I don't get the configuring box and Office is activated as it should be.

 

Only seems to happen with Outlook for some reason.

Re: LogInsight Agent is Not sending SQL Data

$
0
0

If this solves your problem, can you please mark this question as answered? Thanks.

Re: Vmware Workstation Player 12 - Compatibility USB controler 3.0 is missing

$
0
0

Ah, I missed that you are using Workstation Player, and it looks like upgrading virtual hardware versions is a feature only in Workstation Pro.

 

If I were in your shoes, I'd power down the VM (not suspend) and exit Workstation Player and directly edit the VM's config file, find the existing line with virtualHW.version, and change the value to "12", if it's not already 12.  I suspect it is 11 or lower, and hardware version 12 is required for Windows 7 USB 3 compatibility to appear in the VM's settings.

 

Now if you launch Workstation Player and go into the VM's settings, you should be able to choose USB 3 compatibility.

 

Cheers,

--

Darius

Installing Mirage Server 5.7 fails with MSI error

$
0
0

Hi All,

 

I'm trying to install Mirage and I have completed the Mirage Management Server successfully.

 

But when attempting to install the Mirage Server or a new 2012R2 Std Server (I have tried 3 different ones, all with .Net 4.5.1 or greater installed, it fails with

 

The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 2869.

 

Anyone come across this or fixed it.

 

I am using the installation version 570.119795

 

Thanks


Chris

 

Fixed, ran it from a CMD prompt as Admin

 

Message was edited by: Chris Farmer


Re: Identifying disk slot in a diskgroup in vSAN 5.5

Re: Mirage 5.7... Now I'm confused

$
0
0

how do you mean provision?

 

Thanks

 

Chris

Re: Compatibility CPU and ESXi  5.1 U3, 5.5, 6.0

$
0
0

I really believe that the CPU will not be an issue, just go ahead.

 

And if you look at the following URL you will see some referent to ESXi 5.1 U3 and Xeon 2600-v3 Series: VMware Compatibility Guide - cpu

 

But again, I believe that CPU will not be a problem, and the fact you can't found that CPU on HCL for version 5.1 U3 is maybe due the fact that these CPU are newer than the ESXi 5.1 U3 release and so any vendor wasted time for check compatibility for an older ESXi version.

 

Note that when looking for ESXi hardware requirements, you will found:

 

64-bit Processor

  • ESXi 5.1 will install and run only on servers with 64-bit x86 CPUs.
  • ESXi 5.1 requires a host machine with at least two cores.
  • ESXi 5.1 supports only LAHF and SAHF CPU instructions.
  • ESXi 5.1 requires the NX/XD bit to be enabled for the CPU in the BIOS.
  • ESXi 5.1 supports a broad range of x64 multicore processors. For a complete list of supported processors, see the VMware Compatibility Guide.


RAM

  • 2GB RAM minimum
  • Provide at least 8GB of RAM to take full advantage of ESXi 5.1 features and run virtual machines in typical production environments.


Hardware Virtualization Support

  • To support 64-bit virtual machines, support for hardware virtualization (Intel VT-x or AMD RVI) must be enabled on x64 CPUs.
  • To determine whether your server has 64-bit VMware support, download the CPU Identification Utility from vmware.com.

 

And I am pretty sure that these newer CPU includes all these requirements.

Re: Cannot get virtual machines to communicate outside the physcal VM Host but the host (via vmk0) can

$
0
0

Your ESXi host is installed on physical machine or it is a nested ESXi ?

ESXi 6 free for commercial use?

$
0
0

Hello everyone

 

I am in discussion with my colleagues regarding the license for ESXi6 free edition and if its free for commercial use. I say that it is, but they disagree. I have been searching the VMware website for a document or statement saying that its free for commercial/business use. Is there a representative on this forum from VMware that can confirm that it is indeed free for commercial/business use, or can point me to a reference on the VMware website that states this?

 

Thanks,
Sam.

Re: Cannot get virtual machines to communicate outside the physcal VM Host but the host (via vmk0) can

$
0
0

Physical machine on its own subnet.

 

Cheers - Mike

Broken config element sync?

$
0
0

I am on 5.5.3. Trying to update existing configuration element between two instances. Source config element has 2 attributes, type string. My change is to remove one attribute, and add a new attribute. Saved and bumped config's revision. Upon sync, destination gets updated with new attribute but retains the one that was deleted on source instance. Is that expected configuration element behavior during synchronization?


Re: ESXcli 5.5 UNMAP and PowerCLI script?

$
0
0

Hi Travis,

 

Create a csv file with column name "datastore" and put all ur datastores which you want to unmount under this column. Then import the same to ur script. this will solve ur problem. I have updated the same in the below script

 

Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Scope Session -Confirm:$False | Out-Null

$dsimport = @()

$datastore = @()

$dsimport = @(import-csv "csv file location")

$datastore = get-datastore $dsimport.datastore

 

foreach ($ds in $datastore)

 

{

 

$esx = Get-VMHost -Datastore $ds | Get-Random -Count 1

 

$esxcli = Get-EsxCli -VMHost $esx

 

$esxcli.storage.vmfs.unmap($null, $ds.Name, $null)

 

}

Re: Error while taking a snapshot on ESX 6.0.

$
0
0

Can you check some logs from VM folder vmware.log and maybe from host var/log/hostd.log from time when this is happening. Can you copy and paste this logs on forum?

Re: Cannot deploy VM from template to different vCenter Server (in same SSO domain)

$
0
0

I have a similar problem as detailed here:

Need help updating script to work with new vSphere 6 environment

 

I've managed to get the clone to work from one vCenter to another now and it did require adding in the ServiceLocation spec as LucD indicated in his previous post.

The final code I am currently using to clone a server from vc01 to vc02 within the same SSO domain is below.

 

# Virtual Centre server parameters
$aryVIServer = @("vc01.domain.com", "vc02.domain.com")
$strDestVC = "vc02"
$strDestVCThumbprint = "11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11"
$strVCUsername
$strVCPassword

# Load VMware environment
Set-PowerCLIConfiguration -DefaultVIServerMode Multiple -InvalidCertificateAction Ignore -Confirm:$false | Out-Null
$VIServer = Connect-VIServer $aryVIServer

# Server cluster group to deploy to
$strVMCluster = "DestCluster"
# Datastore for storage
$strDatastore = "DestCluster-VMFS1"
# Destination Folder
$strFolder = "Folder1"

# Define source server to clone from
$CloneServer = "Server1"
# Define name of new server including environment prefix
$vmName = "$($CloneServer)-Clone"

# Select Host with least memory consumption
$selectedHostObj = Get-VMHost -Location $strVMCluster | Sort-Object -Property MemoryUsageGB | Select-Object -First 1
# Select folder to place VM guest into
$folderObj = Get-Datacenter -Cluster $strVMCluster | Get-Folder $strFolder
# Select datastore with most available space
$selectedDatastoreObj = Get-DataStore -VMHost $selectedHostObj | Sort-Object -Property FreeSpaceGB -descending | Select-Object -First 1
# Select destination cluster
$selectedClusterObj = Get-Cluster $selectedHostObj.Parent.Name

$ Select source VM to clone
$origVM = Get-VM -Name $CloneServer

$ Create clone spec
$spec = New-Object VMware.Vim.VirtualMachineCloneSpec
# Relocate spec for clone
$spec.Location = New-Object VMware.Vim.VirtualMachineRelocateSpec
$spec.Location.Datastore = $selectedDatastoreObj.Id
$spec.Location.Host = $selectedHostObj.Id
$spec.Location.Pool = $selectedClusterObj.ExtensionData.ResourcePool
$spec.Location.Transform = [Vmware.Vim.VirtualMachineRelocateTransformation]::sparse
# New Service Locator required for Destination vCenter Server
$service = New-Object VMware.Vim.ServiceLocator
$credential = New-Object VMware.Vim.ServiceLocatorNamePassword
$credential.username = $strVCUsername
$credential.password = $strVCPassword
$service.credential = $credential
$service.instanceUuid = ($VIServer | where { $_.Name -match $strDestVC }).instanceUuid
$service.sslThumbprint = $strDestVCThumbprint
$service.url = (($VIServer | where { $_.Name -match $strDestVC }).ServiceUri) -replace "/sdk",""
$spec.Location.service = $service
# Final settings
$spec.PowerOn = $false
$spec.Template = $false

$newVM = $origVM.ExtensionData.CloneVM($folderObj.ExtensionData.MoRef,$vmName,$spec)
$newVM = Get-VM -Id $newVM

# Configure network adapter to selected network
$newVM | Get-NetworkAdapter | Set-NetworkAdapter -PortGroup $selectedNetwork -Confirm:$false

Re: vCenter 5.5 and ESXi 5.5 trial upgrade to licensed version

$
0
0

Yes, if you are using vSphere 6 key then you need to use ESXi 6 and vCenter 6.

am not sure if you can get license keys for 5.5 from your VMware account where license is attached. You can give a try.

 

ESXi Upgrade is easy process. it requires downtime of ESXi Host and VMs if you are not using shared storage.

Re: Move a Virtual Machine between Clusters

$
0
0

Hi,

 

You can disconnect ESXi 5.5 Host from vCenter 5.5 and add it to vCenter 6. ( disable HA in vcenter 5.5 before disconnecting host)

Connect new EMC storage to ESXi 5.5 Host and do the Storage migration.

Connect new EMC storage to ESXi 6 Host.

 

Do VM vMotion from ESXi 5.5 Host to ESXi 6 Host. ( if you are using different hardware, then due to CPU compatibility VM live migration may fail in that case you need to Power off VMs and do the migration )

Also you can try to create new Cluster with ESXi 6 and ESXi 5.5 Host with VMware EVC but to do this your CPU needs to be from same CPU family and compatible.

 

Once you finish VM vMotion, you can remove ESXi 5.5 Host from vCenter 6.

Viewing all 230656 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>