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

Re: Windows 2008 R2 NFS Datastore keeps vanishing

0
0

Make sure your transport is set to TCP only, not TCP & UDP.


Re: VMware Fusion black screen on boot

0
0

Works for me too. Thanks I finally have a working Fusion install on my MBP.

Upgrade from 6.2 to 7.1

0
0

Hi,

 

I have an upgrade schedule for this weekend from Horizon 6.2 to 7. I was curious if it's ok to go straight from 6.2 to 7.1 while skipping 7.0. If it is, are there any caveats that are not listed in the patch notes I should worry about?

 

Thank you!

Re: netboot a Mac VM in vSphere

0
0

As far as I'm aware, a physical Mac will also default to booting from any available hard drive before attempting a NetBoot.

 

We also made the same keyboard hotkeys usable within a Mac OS X VM on vSphere as are available a physical Mac, too:

 

  • Holding Option (and nothing else) should cause the boot menu to be displayed instead of automatically finding and booting an OS.  Our boot menu is not as pretty as Apple's... ours is just text on a blue background.
  • Holding the N key should cause the VM to attempt NetBoot in preference to any other boot device.  It'll still fall back to booting from a local hard drive if no NetBoot service is available.
  • Holding Option+N should cause the VM to attempt a NetBoot, also forcing a fresh "Discover" operation to occur.  This will cause the VM and server to ignore any previously-used image selection and to honor the latest "default" image nominated by the server.  If it's the first time this particular VM has attempted NetBooting, this acts the same as if the N key alone was held.

 

You'll need to click into the VM's window in order to use those shortcut keys early during boot.  If you're using certain remote-access client software (VNC/RDP, etc.) to access the VM's console, you may encounter difficulty getting the VM to recognize the Option key on its own.

 

If you need to force the VM to prefer NetBoot over hard disk boot without interacting with the VM, you'll need to deploy the following extra/advanced configuration option:

 

   bios.bootOrder = "ethernet0"

 

IF you need to force the VM to boot only from the network, you'll need the following extra/advanced config option:

 

   bios.bootDeviceClasses = "allow:net"

 

If you need a longer time to click into the VM and activate the keyboard shortcut, you can delay the boot by configuring a boot delay.  This is equivalent to the config option:

 

   bios.bootDelay = "5000"

 

for a five-second (5000 millisecond) delay early in boot.

 

Cheers,

--

Darius

Re: CIP fails to load during vCenter installation

0
0

Any help? Second try

Re: vmware-tools.service failed because the control process exited with error code + poweron script failed message

0
0

Hi,

 

The steps on the mesa/gallium page are only needed if you really want to insist on running bleeding edge drivers.

Normally you would not want to go that far.

 

What I would do in your case is uninstall the open vmware tools.

  sudo apt-get purge open-vm-tools

  sudo apt-get purge open-vm-tools-desktop

 

and then instead install the VMware Tools that come with Player.

From the menu select "install VMware Tools" under the manage option.


That will present a virtual CD rom to your guest, which you can then mount from within linux.

 

Copy the tar.gz file with the tools, unpack it and run ./vmware-install-config.pl

If there's  a question about it suggesting to use open-vm-tools instead, then override that so you can install this version.

 

Your guest needs to have the kernel headers for your current kernel and the default build tools installed.

eg.

  sudo apt-get install build-essential

  sudo apt-get install kernel-headers

 

(this is all typed from memory, so hopefully no typos, otherwise.. adjust as needed)

 

--

Wil

Re: How to rebuild vROps vApp Container Data from PowerCLI

0
0

So, we're close.  That helps to export properties (and product info)... but the Get-VApp cmdlet doesn't work in this case because even though vROps 6 uses vApp properties and vApp is "enabled", it's not a true vApp Container.  Here's what I've come up with so-far but it's still not quite right...

 

param($RCVM,$SRCVC,$DSTVC)

 

# NOTE:  Power off VM first

 

# Connect to Source vCenter

$Creds = Get-Credential

Connect-VIServer $SRCVC -Credential $Creds

 

# Export RC vApp Product & Properties

$srcRC = Get-VM $RCVM

$srcRCView = Get-View $srcRC

$srcRCVAppProduct = $srcRCView.Config.VAppConfig.Product | Export-Csv RCvAppProduct.csv -NoTypeInformation -UseCulture

$srcRCVAppProperty = $srcRCView.Config.VAppConfig.Property | Export-Csv RCvAppProperty.csv -NoTypeInformation -UseCulture

 

Disconnect-VIServer $SRCVC -Force -Confirm:$false

 

 

# Connect to Destination vCenter

Connect-VIServer $DSTVC -Credential $Creds

 

# Prep Destination vApp

$dstRC = Get-VM $RCVM

$dstRCView = Get-View $dstRC

 

# Import vApp Product

$spec = New-Object VMware.Vim.VAppConfigSpec

Import-Csv .\RCvAppProduct.csv -UseCulture | %{

    $prod = New-Object VMware.Vim.VAppProductSpec

 

    $prod.Info = New-Object VMware.Vim.VAppProductInfo

    $prod.Info.Key = $_.Key

    $prod.Info.ClassId = $_.ClassId

    $prod.Info.InstanceId = $_.InstanceId

    $prod.Info.Name = $_.Name

    $prod.Info.Vendor = $_.Vendor

    $prod.Info.Version = $_.Version 

    $prod.Info.FullVersion = $_.FullVersion

    $prod.Info.VendorUrl = $_.VendorUrl

    $prod.Info.ProductUrl = $_.ProductUrl

    $prod.Info.AppUrl = $_.AppUrl

 

    $spec.Property += $prod

}

$dstVApp.ExtensionData.UpdateVAppConfig($spec)

 

 

# Import vApp Properties

$spec = New-Object VMware.Vim.VAppConfigSpec

 

Import-Csv .\RCvAppProperty.csv -UseCulture | %{

    $prop = New-Object VMware.Vim.VAppPropertySpec

 

    $prop.Info = New-Object VMware.Vim.VAppPropertyInfo

    $prop.Info.Category = $_.Category

    $prop.Info.ClassId = $_.ClassId

    $prop.Info.DefaultValue = $_.DefaultValue

    $prop.Info.Description = $_.Description

    $prop.Info.Id = $_.Id

    $prop.Info.InstanceId = $_.InstanceId

    $prop.Info.Key = $_.Key

    $prop.Info.Label = $_.Label

    $prop.Info.Type = $_.Type

    $prop.Info.TypeReference = $_.TypeReference

    $prop.Info.UserConfigurable = $_.UserConfigurable

    $prop.Info.Value = $_.Value

 

    $spec.Property += $prop

}

$dstVApp.ExtensionData.UpdateVAppConfig($spec)

 

 

Disconnect-VIServer $DSTVC -Force -Confirm:$false

Re: Host Secure Boot with a linux host

0
0

So any remote control malware that gains root access in the host can put its signature in the firmware with the following command and make a joke of Secure Boot versus traditional BIOS boot?

 

mokutil --import MOK.der

 


Re: Licencia VCenter

0
0

Si claro puedes migrar tu vCenter de un host a otro despues que este en el mismo Domain y que sea en una machine virtual nada cambia. Te recominedo lo siguiente:

 

1. Lockdown mode esta desabilitado en el hosts. verifica aqui

Host > Configuration > Security Profile > LockDown Mode.

 

2. Apaga el VirtualCenter Server "Service" aqui

Log in como administrator al server que tiene el vCenter Server.

 

Inicia > Run.

Escribe > services.msc.

Presiona > Enter.

Desde la lista has right-click en el servicio de VMware VirtualCenter Server

y para el servicio "Stop" No te olvides "Start" cuando la migracion termine

 

3. Por precaucion haz un Backup al SQL si tienes uno

 

Para mas information sigue estos pasos

LINK: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=5850444

 

Finalmente no te olvides de marcar esta respuesta corecta si lo es or de alluda para tu pregunta.

 

Raul.

VMware VDI Administrator

http://ITCloudStream.com/

Relevance of KB article

Re: Get all VMs that automatically start with Host

Re: powercli script to create datastore alarms

0
0

You will need to replace this line

 

$spec.expression =New-ObjectVMware.Vim.AndAlarmExpression

 

with this line

 

$spec.expression =New-ObjectVMware.Vim.OrAlarmExpression

 

This will OR the expressions (if you have multiple) instead of AND

Build 3 Node Vmware IDM 2.8 Cluster. Now can not sync with AD

0
0

AD sync was working when it was just a one node system.   Now it fails wit the following error:

 

Failed to complete sync due to a problem with the service. Exception Info:

JSONObject["etag"] not found.

 

 

"

Hello Rene,

Directory sync for directory cencol.ca on tenant PRCLASSAPPS01 has failed.

Please log in to the VMware Identity Manager admin console to check your

directory settings. You can view your directories in the Identity & Access

Management > Directories tab.

Last failed sync time: Wed Apr 26 15:59:52 UTC 2017

Sync failure reason: Failed to complete sync due to a problem with the
service. Exception Info: JSONObject["etag"] not
found.

Thanks

Identity Manager Service

"

 

Totally lost on what this could be

Help!

 

 

Rene

Question re FTT=0 for non-essential VMDK's

0
0

hi all

 

I have a VSAN Datastore that i need to deploy some large SQL VM's on.  To minimise the amount of  space used by 'replicas' for non-essential drives, such as the backup drive on the sql server, i was contemplating creating a storage policy with FTT=0.  I would apply this policy to the SQL Backup drives - lets call it the F drive.  FTT=1 for all other drives.

 

My question is to understand the impact to the availability of the F drive should a disk / host fail that some of the F drives components are running on.

 

If i have a FTT=0 policy applied to a VMDK (F drive), and a piece of hardware that is running some of the F drives components fails, the VMDK will become unavailable.

 

If this situation occurred, is it still possible to perform a resync of the components that are on the failed piece of hardware so that they are rebuilt elsewhere in the cluster ? So whilst the VMDK will not be continuously available as would be the case of FTT=1, after a brief period of unavailabilitty while the components are rebuilt, the components on the failed piece of hardware would be rebuilt elsewhere - therefore avoiding the need of creating a new VMDK

 

Is that assumption correct ?

 

thanks in advance

 

chris

Esxi host disconnected in Vcenter 6.0

0
0

Hi,

 

We currently have 2 identical hardware ESXI 6.0 hosts connected to Vcenter 6.0.

 

One esxi 6.0 host has an additional VLAN for Voice and is in a disconnected state on Vcenter. I can ping the default VLAN IP and DNS name from every device on the network except from the Vcenter server. From the Vcenter server I can not  ping the default  VLAN by IP or DNS name, but can ping the Voice VLAN.

 

There are 2 vswitches and Vswitch0 has the only Vkernal for Management Network and the Vlan is set to 0

 

Any ideas would be appreciated


Re: Question re FTT=0 for non-essential VMDK's

0
0

We don't recommend using FTT=0 for this, and many other reasons. You won't be able to rebuild the object since the disk/host will be unavailable. You could rebuild the object if you had one copy available (FTT=1), but in this scenario that copy is the only copy and not available.

 

You are also assuming that the VM is up and only lose the vmdk. If you lose the host where the VM is running (or reboot for that matter), HA will restart the VM, and since that one vmdk is unavailable, you are likely to not be able to boot that VM unless you remove drive F.

 

We recommend using FTT=1 at a minimum. If you are worried about space for that object, you could use Raid5 EC for that VMDK if you have all-flash.

 

Hope this helps.

Re: ESXi 6.0 U2 - "Failed to deploy VM: postNFCData failed." - when importing a OVA template via ESXi Host Client 1.5.0.

0
0

had the same issue whilst deploying BigIp VE on ESXi 6.5. Thank you for the solution DataBitz!

Re: Migration to VSAN

0
0

You are able to present storage to a vSAN cluster the same way as you do to non-vSAN vSphere Clusters. Once you present the data, you can do cold migration or vMotion (resource +storage).

Re: ESXi 6 Manual Network Configuration help

0
0

I see that you are getting 169. from an unused NIC in this computer. Well! optionally you can just use that "Ethernet Adapter Ethernet 2: to access you ESXI 6 and all VMs in a separated segment, just put the same IP setting for both ESXI/VMs & Ethernet 2 with different machine number.

 

EXAMPLE:

 

ESXI

IP Address (IPv4):      10.10.10.10

Subnet Mask (IPv4):  255.255.255.0

Gateway (IPv4):         10.10.10.1

DNS if there is one    XXX.XXX.XXX.XXX

 

VM-1 and so on VM-2, etc... changing the last computer ID #

IP Address (IPv4):      10.10.10.11

Subnet Mask (IPv4):  255.255.255.0

Gateway (IPv4):         10.10.10.1

DNS if there is one    XXX.XXX.XXX.XXX

 

Computer that will be using vSphere Client "Ethernet Adapter Ethernet 2"

IP Address (IPv4):      10.10.10.12

Subnet Mask (IPv4):   255.255.255.0

Gateway (IPv4):         10.10.10.1

DNS if there is one     XXX.XXX.XXX.XXX

 

In this way you separate your WIFI from The ESXI network, and work on both.

 

Raul.

VMware VDI Administrator

http://ITCloudStream.com/

Error in launching vApp - "Insufficient resources to satisfy configured failover level for HA error"

0
0

I am actually deploying VMware Integrated OpenStack in Compact mode.. The OVF file is successfully imported and deployed, but I am facing an issue in Launching the two VMs .. in the Integrated OpenSack Manager vApp  and I have a message telling me : "Insufficient resources to satisfy configured failover level for HA error"

I would be grateful if you could help me in this matter!!

Viewing all 168190 articles
Browse latest View live




Latest Images