How can I get the events for 'Revert to Snapshot '?

Just run a workflow if 'Revert to Snapshot ' operation on any VM.

Thanks,

Stanly

On Workstation Pro 15 Snapshot Manager one  VM shows a string of snapshots which are not really there, but cannot be deleted because when I try to I get the message "Error deleting. A required file was not found." Is there a way to get rid of the non-existent snapshots from the snapshot manager?

Hello,

This is my first post here - I do not really know about the structure of vmware community, so Sorry if I'm in wrong place.

I have been using vmware workstation since version 6, upgrading every 2 releases. Now I have upgraded from 12 to 15, mostly because at this moment 12.5 would not install correctly on new Linux systems, also for all this time I've been using same Windows 98 virtual machine without any problems, so I have not tried it during the 30 days free support time. Today I was trying to start it and I got "windows protection error". same machine is still working correctly on work station 12.5.9.

In step by step confirmation last loaded driver is mouse driver, then couple second of some hdd activity and black screen with protection error with system reboot information.

I found one article showing someone not being able to install Windows 98 on vmware 14, so my ques is this is something that changed then.

Any help will be appreciated, by I'm afraid this can not be done by changing some settings.

Thank You

I have to create a MS cluster on a ESXi 5.5 U3b cluster (I know, it's old, but that's the assignment). I can successfully create the 2 Win 2016 VMs, create the RDM disks; share them; create the cluster; even join the RDM disks as available storage to the cluster. All that is fine.

The cluster validation test is failing with "Physical disk 1 on <both nodes> does not support the inquiry data (SCSI page 83h VPD descriptor) that is required by failover clustering.

Now, here's the thing. Physical disk 1 on both nodes is a *local* disk - i.e., it's not intended to be used by the cluster at all. It's drive D: on those machines; it's where you install the application that will use the cluster (in my case MS SQL 2016). So I don't know know why it cares about a disk that will in no way be used as a cluster resource  ...

Those disks are defined as "thick provision lazy zeroed"; could that be the issue? Is it that any drive that isn't the boot drive must be "thick provisioned eager zeroed"?

(I can't test right now, it's doing Windows Updates. and if you've ever done WU on a Win 2016 server, you know that can take hours, even with only 3 cumulative updates)

I definitely need a 2nd local disk for application installation, otherwise I would just delete the disk and go. As I say, my 4 cluster disks are all configured, waiting in "Available Storage". I can even move them from one node to another. I just can't pass the validation test, and that test is required, before SQL will install as a SQL cluster.

It's got to be something simple I've missed, but what?

Thanks for any help.

I have multiple snapshots that are showing up in my datastore in ESXI.  I cannot see them in Snapshot manager, nor when I query the snapshots via SSH command line.  I am having huge performance issues and I need to remove these snapshots ASAP.  I have tried creating a snapshot manually and then running delete all.  This does not work.  I am stuck.  Are there any recommendations on how I should proceed?

2 questions regarding separate clusters and moving to new hosts:

We're getting in new hardware and will be replacing our current ESXi hosts with new ones.  In our vSphere environment, we have 5 hosts in one datacenter - in one server cluster with one vDS, which has 5 separate resource pools, all using one shared datastore (it's not a cluster).  The goal here is to ultimately phase out the old hosts completely, while we move to Intel-based hosts (from AMD) while maintaining the same system architecture, albeit with a newly created cluster for these Intel hosts.  Same setup, all new, but different vendor hardware.

As I understand it, the procedure so far is as follows:

1. Install ESXi hypervisor and configure the new hosts

2. Create a new host Cluster in vCenter

3. add the new hosts to that cluster

4. extend the distributed switch to the new hosts (add the new hosts to the vDS - configure uplinks and vmnics)

5. extend the shared storage to the hosts in the new cluster (present the existing storage to the new hosts, scan for new, add/configure the same as the old hosts)

5. power down the running VMs in the original cluster, then migrate their compute resources to the new cluster hosts.

6. Power the VMs on.

Question 0: is this procedure accurate above?

Question 1:   How do the existing resource pools impact this transition?  Is it just a matter of creating the same resource pools on the new cluster and configuring them the same way?  Is there a way to migrate or duplicate the settings?  Will there be any conflict by naming them the same as the existing pools in the new cluster under the same datacenter?

Question 2:  How do I add the existing shared storage to the hosts in the new cluster?  Is done on the host (Hosts & Clusters tab) or in the shared storage configuration (Storage tab)?  This should be simple and a refresher (i think) since we have a single shared datastore (fiber, 1 LUN, VMFS) across the hosts in the existing cluster.

Thanks in advance.

[Note, we will be adding a new storage system later, but would like to migrate VMs from the existing hosts before transition to new shared storage which will only be attached to the new hosts]

Hi all,

Let's say a VM with PFTT=1 that is currently registered to an ESXi at the P-Site in a VSAN Stretched Cluster. (SFTT can be anything, doesn't matter here).

I understand that you will need at least the P-Site and the Witness-Site to be up before the VM can boot. In other words, you don't need to up the S-Site to boot this VM.

This has been tested and shown to be true.

I was also under the impression that with a VM with PFTT=0 and the Affinity* locked to the P-Site, you don't need neither the Witness-Site nor the S-Site to be up to boot this VM.

*Remember if you set PFTT=0 you will be forced to pick the site affinity.

However, when I tested this, this is shown to not to work. Error shown in the below screenshot/attachment when trying to boot such a VM.

Basically, I booted a P-Site ESXi, but left the Witness-Site and S-Site both powered off.

Then, I login to the ESXi's Embedded Host Client, picked a VM that has a PFTT=0 and SFTT=0 Storage Policy that is registered to the ESXi, then tried to boot it, but it failed.

This is strange, shouldn't this VM NOT have any witness components whatsoever? Why does it need the Witness-Site to come up just to boot? Any ideas?

Entire VSAN Stretched Cluster environment is 6.7U1.

Thanks!

Unable to fetch flash drive metrics using VSN SDK, am getting null values. Kindly let me know which service call I have to use to get the flash dish health summary and what we have to pass in managed object.

Thanks in advance

Hi,

I am trying the new app remote collector in vROps 7.5. Installation and connection to vCenter is fine. Unable to install CentOs7 agent or Windows 2016 agent from the remote agent console. Both have VM Tools 10.2 installed (replaced open source version on CentOS). Since they both failed i thought it was the old vCenter issue with symbols in passwd, so I changed linux root user to other passwd. Still fails. I get:

com.vmware.adapter3.applicationdiscovery.AppOSAdapter.logAdapterActionResult - [2019-04-17 13:07:37.417000 UTC]Task with operation install failed at 1555506457417 with reason Failed to connect to vCenter. Please check the credentials. Unable to acquire token

[654] 2019-04-17 15:07:57,322 ERROR [pool-1-thread-8] (74) com.vmware.adapter3.applicationdiscovery.actions.dispatch.UCPActionExecutor.checkActionStatus - Could not fetch auth token from UCP API. Unable to fetch the status from doc link. Hence trying from file...

Any ideas ? Anyone tried this yet?

att customer service phone number

You can easily set up your AT&T email account to use with outlook, but sometimes it gets difficult for the users to do the same. So if you want to set up AT&T ,you can follow the steps mentioned below, and  your problem will be solved soon

Steps to set up AT&T email on Outlook are:

• Step 1: Go to the account settings of Microsoft Outlook
• Step 2: Fill in your details in the ‘user information.’
• Step 3: Choose POP3 in the server information
• Step 4: Type ‘pop.att.yahoo.com.’in the incoming mail server
• Step 5: Type ‘smtp.att.yahoo.com.’ in the outgoing mail server field
• Step 6: Do the SSL settings in ‘more settings’ in the last step

If you follow these steps carefully, you will easily be able to set up AT&T email on Outlook. If these steps did not turn out to be helpful, you could att tech support to get technical assistance from the experts.

Read More: contact at&t email customer care number

Hello VMwarers,

How can I let specific users to access this administration tab in VAMI

Hi,

I need to change the value of the setting “scsi.comparelunnumber” prior to boot to potentially fix a bootbank issue. Bootbank is currently mapped to tmp so a setting change isn’t retained across a reboot if it‘s changing from within the running ESXi environment.

Does anyone know how to change this setting prior to boot? Can it be applied somehow after pressing Shift-O from the boot menu?

ESXi 6.7 for reference.

Thanks

Matt

Hi There!

Our LIVE VM suddenly rebooted and we found out on the Vsphere events that the Guest OS Crashed

hello

i have a windows 10 and a ubuntu14.04 and raspberry pi , horizon client 4.1 is installed in each os.

horizon is 7.9 and TLS1.0 is enable

when connect from windows 10 , desktop open successfully but when try to connect with ubuntu or raspberry ,desktop is black screen!!!!!!!

please help me

NSX-T による DHCP サービス機能で、MAC アドレスと IP アドレスの静的な割り当て（static-bindings）を設定してみます。

前回の投稿では、NSX Manager の Web インターフェースから設定しました。

NSX-T 2.4 で DHCP の static-bindings を使用してみる。（GUI 編）

今回は、REST API から同様の設定をしてみます。

環境の説明。

以前の投稿と同様に、下記の環境を利用しています。

自宅ラボで NSX-T 2.4 環境を構築する。まとめ

REST API へのアクセスには、下記の投稿のように curl + jq コマンドを利用しています。

NSX-T 2.4 を REST API で操作してみる。Part.1

この投稿でのコマンドライン中にある $CRED には「ユーザ:パスワード」、

$MGR には NSX Manager のアドレスを格納しています。

IP アドレスを割り当てる MAC アドレスの確認。

DHCP の static-bindings では、MAC アドレスに IP アドレスを割り当てます。

今回は、NSX-T を利用している vSphere（ESXi）上の VM がもつ vNIC に IP アドレスを設定します。

そのため、NSX Manager からでも VM ／ vNIC とその MAC アドレスが確認できます。

REST API では、この情報を virtual-machines と vifs の情報を GET することで確認できます。

今回は、例をシンプルにするため下記を前提としています。

• 環境内の VM 名に重複がない。
• VM の vNIC は 1つだけ。

VM の名前（vm01）から MAC アドレスを確認してみます。

vm01 の情報は、下記のように取得できます。

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/fabric/virtual-machines | jq -r '.results[] | select(.display_name == "vm01")'

{

  "host_id": "c33ad1aa-f3b4-4a24-98da-bc32eeff1f31",

  "source": {

    "target_id": "c33ad1aa-f3b4-4a24-98da-bc32eeff1f31",

    "target_display_name": "c33ad1aa-f3b4-4a24-98da-bc32eeff1f31",

    "target_type": "HostNode",

    "is_valid": true

  },

  "external_id": "501f7750-8d29-8c53-2d5e-e5b88b06f812",

  "power_state": "VM_RUNNING",

  "local_id_on_host": "1",

  "compute_ids": [

    "moIdOnHost:1",

    "hostLocalId:1",

    "locationId:564d7a4c-fa5e-33bf-1c3e-ca12ebd75f6f",

    "instanceUuid:501f7750-8d29-8c53-2d5e-e5b88b06f812",

    "externalId:501f7750-8d29-8c53-2d5e-e5b88b06f812",

    "biosUuid:421fa276-d1a6-c34a-2dc6-ea0de1d2ace5"

  ],

  "type": "REGULAR",

  "guest_info": {

    "os_name": "Oracle Linux 7 (64-bit)",

    "computer_name": "localhost.localdomain"

  },

  "resource_type": "VirtualMachine",

  "display_name": "vm01",

  "_last_sync_time": 1563839902208

}

ここから、下記のように VM の ID だけを取得することもできます。

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/fabric/virtual-machines | jq -r '.results[] | select(.display_name == "vm01") | .external_id'

501f7750-8d29-8c53-2d5e-e5b88b06f812

そして、VM ID をもとに、vNIC の MAC アドレスを確認します。

※ちなみにこの VM は、前回の投稿で DHCP による IP アドレス ／ ホスト名が設定がされた状態です。

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/fabric/vifs | jq -r '.results[] | select(.owner_vm_id == "501f7750-8d29-8c53-2d5e-e5b88b06f812")'

{

  "external_id": "501f7750-8d29-8c53-2d5e-e5b88b06f812-4000",

  "owner_vm_id": "501f7750-8d29-8c53-2d5e-e5b88b06f812",

  "host_id": "c33ad1aa-f3b4-4a24-98da-bc32eeff1f31",

  "vm_local_id_on_host": "1",

  "device_key": "4000",

  "device_name": "Network adapter 1",

  "mac_address": "00:50:56:9f:fa:ac",

  "lport_attachment_id": "5ccf3507-1001-419e-81be-3f197bf583f4",

  "ip_address_info": [

    {

      "source": "VM_TOOLS",

      "ip_addresses": [

        "172.16.1.101",

        "fe80::1b24:4d58:f0b4:bfe8"

      ]

    }

  ],

  "resource_type": "VirtualNetworkInterface",

  "display_name": "Network adapter 1",

  "_last_sync_time": 1563839902211

}

MAC アドレスだけを取得することもできます。

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/fabric/vifs | jq -r '.results[] | select(.owner_vm_id == "501f7750-8d29-8c53-2d5e-e5b88b06f812") | .mac_address'

00:50:56:9f:fa:ac

DHCP static-bindings の設定。

IP アドレスの静的割り当て（static-bindings）は、NSX-T による DHCP サーバに対して設定します。

まず、DHCP サーバの ID を確認します。

今回も、DHCP サーバ名は「dhcp-sv-001」にしています。

$ DHCP_SV_ID=`curl -ks -u $CRED -X GET https://$MGR/api/v1/dhcp/servers | jq -r '.results[] | select(.display_name=="dhcp-sv-001") | .id'`

$ echo $DHCP_SV_ID

73445136-5ab5-459a-a357-d736e534a467

静的割り当てのための JSON ファイル「dhcp-bind_vm01.json」を作成しておきます。

今回は、下記のパラメータのみ指定しています。

• 表示名（display_name）
• MAC アドレス ※必須
• IP アドレス ※必須
• ホスト名

JSON ファイルのパラメータは、前回の GUI での設定時と同じものです。

同じ静的割り当て設定が存在するとエラーになるので、

すでに設定がある場合は、NSX Manager などから削除しておきます。

$ cat ./dhcp-bind_vm01.json

{

  "display_name": "00:50:56:9f:fa:ac",

  "mac_address": "00:50:56:9f:fa:ac",

  "ip_address": "172.16.1.101",

  "host_name": "vm01"

}

作成した JSON ファイルを指定して POST メソッドを実行すると、DHCP の静的割り当てを作成できます。

curl を実行すると、作成された設定の情報が表示されます。

$ curl -ks -u $CRED -X POST -H "Content-type: application/json" -d @./dhcp-bind_vm01.json https://$MGR/api/v1/dhcp/servers/$DHCP_SV_ID/static-bindings

{

  "mac_address" : "00:50:56:9f:fa:ac",

  "ip_address" : "172.16.1.101",

  "host_name" : "vm01",

  "resource_type" : "DhcpStaticBinding",

  "id" : "bb2cd277-20f3-4184-81c5-250f20f71f7a",

  "display_name" : "00:50:56:9f:fa:ac",

  "lease_time" : 86400,

  "_create_user" : "admin",

  "_create_time" : 1564095298669,

  "_last_modified_user" : "admin",

  "_last_modified_time" : 1564095298669,

  "_system_owned" : false,

  "_protection" : "NOT_PROTECTED",

  "_revision" : 0

}

これで、対象 MAC アドレスに IP アドレスが設定されるようになります。

DHCP static-bindings の削除。

一方、 静的割り当ての削除は、DELETE メソッドで実施できます。

静的割り当て設定の ID は、作成時にも表示されていましたが、

下記のように VM 名などから取得することもできます。

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/dhcp/servers/$DHCP_SV_ID/static-bindings | jq -r '.results[] | select(.host_name == "vm01") | .id'

bb2cd277-20f3-4184-81c5-250f20f71f7a

そして、削除は DELETE メソッドで削除できます。

$ curl -ks -u $CRED -X DELETE https://$MGR/api/v1/dhcp/servers/$DHCP_SV_ID/static-bindings/bb2cd277-20f3-4184-81c5-250f20f71f7a

$ curl -ks -u $CRED -X GET https://$MGR/api/v1/dhcp/servers/$DHCP_SV_ID/static-bindings

{

  "results" : [ ],

  "result_count" : 0

}

うまく工夫をすると、NSX-T で IPAM（IP アドレス管理）を実現することもできそうかなと思います。

以上、NSX-T での DHCP static-bindings 設定でした。

Hallo Community,

In meiner Firma ist der VM-Spezialist im Urlaub. Ich und ein Paar Andere Kollegen haben neue Laptops Bekommen. Das Host.OS ist Windows 10 Enterprise 1903. Nun wollte ich meine "alte" Windows 7 VM auf den neuen Rechner umziehen. Kurz nach dem Start geht sie sofort in Suspend, da die VM meint, mein Host-Akku ist leer. Das ganze wird auf einem HP ZBook 17 G5 Betrieben. Da wir häufiger in Akku-Betrieb sind wäre die Anzeige im der VM natürlich von vorteil. Hänge ich den Laptop ans Stromnetz bleibt meine VM laufen. Steck ich ihn aus, geht sie innerhalb von 10 Sekunden in Suspend.

Mit einer neuen VM von unserem VM-Guru habe ich das selbe Problem. Unterschiedlich sind lediglich die Hosts. Bisher waren es Zbook G4 mit einem 4-Kern Intel nun haben wir 6-Kern Intel verbaut.

Im Gerätemanager der VM habe ich schon versucht alles was mit Akku oder Netzteil zu tun hat zu deaktivieren/deinstallieren, die HW wieder zu suchen und Treiber upzudaten. Dies hatte alles kein Erfolg. Was mir bisher aufgefallen ist, dass de VM manchmal nur einen leeren akku anzeigt, und nach einem Reboot den Akku mit einem roten X : "kein Akku wurde ermittelt".

Kann mir jemand helfen, das Problem zu beheben?

Eine komplette neuinstallation der VM´s ware zwar möglich, aber unter enormen Zeitaufwand: Produktiv-System Siemens SPS Programmierung (S7 Kalssik, Tia Portal 13, 14, 15 15.1 und andere IBN Software... ergo 3-4 Tage installationsaufwand.

Genutzte HW/SW:

Intel i7-8850H 2,6Ghz, 6 Kerne

32 Gb Ram

1 x 1 TB SSD M.2

1 x 500 GB SSD Sata

Windows 10 Enterprise 1903

VM Workstation Pro 15.1.0 build-13591040

Die Aktuellen VMWare Tools. Ver . 10.3.10

Vielen Dank schonmal

mfg

Daniel

RT, i upgraded the host OS to win10 1903 a few days ago. then i found vmware can't report battery info to guest OS. if the guest os is win98se, the guest OS will hang during boot. if the guest os is winme, it will hang when you open power management -> power meter tab. if the guest os are others eg. 98/2k/xp/vista/7……, it displays the battery level 0%. if you unplug the ac adapter to use battery, the guest os will say the battery is low. i tried vm 14.1.7 & 15.0.4, they are all same.

the screenshot below is winme. in this picture i switched to the power meter tab but the content is still the tab power scheme. it already hung.

this is win98 original not 98se. the battery level is 0%

I needed to expand my Lubuntu boot disk as there was 0% free and it was not allowing logins. To do this I did the following:

- increased the disk allocation in vSphere

- rebooted the VM to a GParted ISO

- extended the linux-swap partition to use the new unallocated space

- moved the linux-swap partition to the right

- decreased the linux-swap partition size back to its original 2GB

- extended the primary partition size to use the unallocated space

- rebooted the VM.

The partition operations appeared to go OK, but how when I try to boot the VM I get past the splash screen and then the OS hangs - just displaying a dark grey screen.

The partitions now look as follows:

/dev/sda1 - 58GB

/dev.sda2 extended 2GB

   /dev/sda5 linux-swap 2GB

  unallocated 1MB

Any idea how I can get the VM to boot again? I'm running ESXi 6.5 and Lubuntu 17.10

with vRO 7.6 in presenation set maximum string length to 40

run workflow using REST client fails.

2019-07-27 13:20:54.722+0000 [https-jsse-nio-0.0.0.0-8281-exec-6] ERROR {} [BaseController] Error invoking REST [unknown]

java.lang.IllegalArgumentException: 1 error(s) found: [ { Password - The maximum number of characters allowed for this field is 40 } ]

        at com.vmware.o11n.web.presentation.service.PresentationServiceImpl.validateParameters(PresentationServiceImpl.java:369)

        at com.vmware.o11n.web.workflow.ExecutionController.startWorkflowExecution(ExecutionController.java:354)

any known solution to this ?

if i remove maximum string length check it works , if i set it to large number like length = 400 it works

Hi,

What are the default credentials for Velocloud devices?

We are trying to setup on prem VCO and the CLI is asking for ubuntu login. Tried Admin/Admin but failed.

Any help will be appreciated.

Thanks.