Ever since I've upgraded to Mojave on my MID 2012 MBP (i7 2.6 GHZ, 16GB ram, SSD HDD) I cannot run any VM's.  I've tried creating new VM's and still get the same errors.  I have given Fusion Full disk access in security settings and still no joy.

VM workload is red zone on vROPs but the CPU usage and Demand utilization is 30-40%

We had an issue for few of the VMs where the CPU usage and demand ( % ) are normal but the VM workload shows in red zone.

Seems the VM was captured on busiest VM report.

My question , how can the VM workload shows in red zone even the CPU has more capacity.

I got the workload metric on vROPs.

Example attached one sample VM details

the VM is part of over provisioned VM , it is captured on red zone ( workload %)

CPU capacity : 67 GHz

Usage: 6.73 GHz ( 10% of total capacity )

Demand: 6.76 GHz

VM workload is red zone on vROPs but the CPU usage and Demand utilization is 30-40%

We had an issue for few of the VMs where the CPU usage and demand ( % ) are normal but the VM workload shows in red zone.

Seems the VM was captured on busiest VM report.

My question , how can the VM workload shows in red zone even the CPU has more capacity.

I got the workload metric on vROPs.

Example attached one sample VM details

the VM is part of over provisioned VM , it is captured on red zone ( workload %)

CPU capacity : 67 GHz

Usage: 6.73 GHz ( 10% of total capacity )

Demand: 6.76 GHz

Hello,

we need a separate broadcast domain in our local network. To do so I need to have a dedicated network interface on my Windows Server 2016 DHCP-Server.

Not sure which way is best to realize it. My idea is to add a new portgroup to my existing vSwitch and then add a free network interface to the portgroup.

VLAN ID is 100. When configuring VLAN ID, VLAN is tagged or untagged?

Kind regards,

Roland

Looks like the hardware acceleration driver within VMware is faulty. If you have been seeing white text (or very light color) on white background dialogues in Chrome such as this:

The latest update to the screen driver in Vmware seems to be bugger. By disabling hardware acceleration you will get your black on white text back:

In chrome enter the following URL:

chrome://settings/system

Then turn off the "Use hardware acceleration when available" - which you can see in the same screenshot above.

Hi all,

Working on a Windows 10 1803 project and one of the requirement was to make Onedrive available in a non-persistent VDI environment

With the new client installed on the local machine instead of installing it under "appdata/local"  and doing some additional configuration it works........

After testing some days, we have noticed that after a user uploads content to Onedrive from the local physical machine and logged in directly with a new session in VDI, all the old content will be deleted in the cloud and only the recent uploaded files shows up for on-demand!!! within the virtual desktop

we have managed the following configuration with Ivanti/Appsense

# to avoid warnings that the onedrive folder has been removed or replaced. the following folders and registry settings to provide SSO will be saved.

Include

-      {CSIDL_LOCAL_APPDATA}\Microsoft\OneDrive\settings\

-      C:\Users\%username%\OneDrive - vmware\.*

Exclude

-     C:\Users\%username%\OneDrive - vmware\

Registry

Include

-     HKEY_CURRENT_USER\Software\Microsoft\OneDrive\

If we don't include the file "C:\Users\%username%\OneDrive - vmware\.*" Onedrive will ask the user at every login that the folder has been replaced, so you can choose to retry or setup onedrive again.

Does anyone have a clue what happened? Is there somebody who experienced the same with UEM or while using Writable volumes?

Greetz,

Kevin

Hello, everybody

There is the HA Cluster (IvyBridge v2, EVC turned on) of four IBM Servers.

Every week at the same time one of our VM reboots after same error vcpu-0| W115: MONITOR PANIC: vcpu-1:VERIFY vmcore/vmm/platform/common/platform.c:30 bugNr=17332

There are no resource overcommits. We can't find any additional errors.

VM was relocated on other host in the HA Cluster but event is still there.

I had to restart my computer and now I am locked out. I have tried every possible password so I am wondering if I can reset so I do not lose all my work.

I have 9 VM/Host Rules and need to show when this rules was made and change. Is any log or script i can use to see that?

Hi Team, I'm trying to install vcsa 6.7 and I'm having issues with my DNS is there a way I can install without a DNS. I do have a DNS but when I'm in the server room I'm unbale to ping any machines its probably the network connection?

Hi Luc ,

i thought of adding few additional functionalities to attached script which we discussed some days back .

can you suggest if this follows proper power shell script structure ??

i am getting some strange results especially in ntp section .

i have attached the script.

Hi all,

Does ghettoVCB support for EXSi 6.0? I'd like to backup my system which running ESXi 6.0 but it always shows error.

If it support please show me how?

Tks so much,

NTQ

PS: to admin: please move this thread to correct place if it's wrong. Tks!

Depending on your Disaster Recovery preferences, at the time of VM recovery do you prefer to:

Hi

We have in the company license for vcenter but I can download  vcenter ISO

Author : ygeorgieff

URL : http:////docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.networking.doc/GUID-DAF824CD-104D-4ED7-8BA3-D769DF688CEB.html

Topic Name : Create a vSphere Standard Switch

Publication Name : vSphere Networking

Product/Version : VMware vSphere/6.7

Question :

When I run the command "esxcli network vswitch standard list"  I see the output of a vswitch,  but my vswitch Class type is indicated as a cswitch and not etherswitch.  What is a cswitch?

I am receiving constant errors in the ESX servers corresponding to an inconvenience with the storage, I indicate the error:

2019-05-1311:26:51.508

2019-05-13T15:26:51.503Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-04, 1> Write Seek error for stats file -1

2019-05-1311:26:51.508

2019-05-13T15:26:51.504Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-02, 1> Write Seek error for stats file -1

2019-05-1311:26:51.508

2019-05-13T15:26:51.505Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-01, 1> Write Seek error for stats file -1

2019-05-1311:26:55.514

2019-05-13T15:26:55.511Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-04, 1> Write Seek error for stats file -1

2019-05-1311:26:55.514

2019-05-13T15:26:55.511Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-02, 1> Write Seek error for stats file -1

2019-05-1311:26:55.514

2019-05-13T15:26:55.512Z SINFRA133.intra.banesco.com storageRM:  <DS-FL-UNITY-PROD-01, 1> Write Seek error for stats file -1

grateful with any help I can receive about it

VMware Photon OS 3.0 の参照 DNS サーバの設定は、

これまでの Photon OS とは様子が変わっているようです。

今回は、Photon OS 3.0 の DNS サーバ アドレスの確認と、設定変更をしてみます。

Photon OS 3.0 は、GitHub の URL からダウンロードできる

「OVA with virtual hardware v13 (UEFI Secure Boot)」を利用しています。

Downloading Photon OS · vmware/photon Wiki · GitHub

root@photon-machine [ ~ ]# cat /etc/photon-release

VMware Photon OS 3.0

PHOTON_BUILD_NUMBER=26156e2

Photon 3.0 の /etc/resolv.conf は下記のように、

nameserver に「127.0.0.53」というアドレスが設定されています。

root@photon-machine [ ~ ]# cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.

#

# This is a dynamic resolv.conf file for connecting local clients to the

# internal DNS stub resolver of systemd-resolved. This file lists all

# configured search domains.

#

# Run "resolvectl status" to see details about the uplink DNS servers

# currently in use.

#

# Third party programs must not access this file directly, but only through the

# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,

# replace this symlink by a static file or a different symlink.

#

# See man:systemd-resolved.service(8) for details about the supported modes of

# operation for /etc/resolv.conf.

 

nameserver 127.0.0.53

このアドレスは、DNS サーバ関連のようで、UDP 53 番ポートで待ち受けているようです。

root@photon-machine [ ~ ]# ss -an | grep 127.0.0.53

udp   UNCONN  0        0                              127.0.0.53%lo:53                                               0.0.0.0:*

そして 53番ポートのプロセスを確認してみると、

resolv.conf のコメントとも関係ありそうな systemd-resolve というものです。

root@photon-machine [ ~ ]# tdnf install -y lsof

root@photon-machine [ ~ ]# lsof -i:53 -P -n

COMMAND   PID            USER   FD   TYPE DEVICE SIZE/OFF NODE NAME

systemd-r 205 systemd-resolve   12u  IPv4   3644      0t0  UDP 127.0.0.53:53

root@photon-machine [ ~ ]# ps -p 205

  PID TTY          TIME CMD

  205 ?        00:00:00 systemd-resolve

これは、systemd 229 以降に導入された名前解決マネージャーの仕組みのようです。

https://www.freedesktop.org/wiki/Software/systemd/resolved/

ちなみに、Photon 3.0 は systemd 239 でした。

root@photon-machine [ ~ ]# rpm -q systemd

systemd-239-10.ph3.x86_64

DNS サーバのアドレスは、/etc/systemd/network/*.network ファイルの

「DNS=」で設定したものが反映されます。

Photon OS 3.0 では、デフォルトでは DHCP 設定のファイルが配置されています。

root@photon-machine [ ~ ]# cat /etc/systemd/network/99-dhcp-en.network

[Match]

Name=e*

 

[Network]

DHCP=yes

IPv6AcceptRA=no

現時点では、DHCP 設定により自宅ラボの  DNS サーバ 2台が設定されています。

root@photon-machine [ ~ ]# resolvectl dns

Global:

Link 2 (eth0): 192.168.1.101 192.168.1.102

resolvectl では、より詳細な情報も確認できます。

（デフォルトだとページャが作用しますが、とりあえず cat で全体表示しています）

root@photon-machine [ ~ ]# resolvectl | cat

Global

       LLMNR setting: no

MulticastDNS setting: yes

  DNSOverTLS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

Fallback DNS Servers: 8.8.8.8

                      8.8.4.4

                      2001:4860:4860::8888

                      2001:4860:4860::8844

          DNSSEC NTA: 10.in-addr.arpa

                      16.172.in-addr.arpa

                      168.192.in-addr.arpa

                      17.172.in-addr.arpa

                      18.172.in-addr.arpa

                      19.172.in-addr.arpa

                      20.172.in-addr.arpa

                      21.172.in-addr.arpa

                      22.172.in-addr.arpa

                      23.172.in-addr.arpa

                      24.172.in-addr.arpa

                      25.172.in-addr.arpa

                      26.172.in-addr.arpa

                      27.172.in-addr.arpa

                      28.172.in-addr.arpa

                      29.172.in-addr.arpa

                      30.172.in-addr.arpa

                      31.172.in-addr.arpa

                      corp

                      d.f.ip6.arpa

                      home

                      internal

                      intranet

                      lan

                      local

                      private

                      test

 

Link 2 (eth0)

      Current Scopes: DNS

       LLMNR setting: yes

MulticastDNS setting: no

  DNSOverTLS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

  Current DNS Server: 192.168.1.101

         DNS Servers: 192.168.1.101

                      192.168.1.102

ためしに、DNS サーバのアドレスを変更してみます。

設定ファイルを vi エディタで編集します。

root@photon-machine [ ~ ]# vi /etc/systemd/network/99-dhcp-en.network

今回は、下記の赤字部分を追記します。

[Match]

Name=e*

 

[Network]

DHCP=yes

IPv6AcceptRA=no

Domains=go-lab.jp

DNS=192.168.1.1

DNS=192.168.1.2

ネットワークを再起動します。

root@photon-machine [ ~ ]# systemctl restart systemd-networkd

DNS サーバアドレスが追加登録されました。

DHCP サーバによる DNS サーバのアドレスよりも高優先度で

ファイルに追記した DNS サーバが追加されました。

root@photon-machine [ ~ ]# resolvectl dns

Global:

Link 2 (eth0): 192.168.1.1 192.168.1.2 192.168.1.101 192.168.1.102

resolvectl コマンドの末尾 10行だけ表示してみると、

「Domains」のドメインも追加されています。

root@photon-machine [ ~ ]# resolvectl | tail -n 10

       LLMNR setting: yes

MulticastDNS setting: no

  DNSOverTLS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

         DNS Servers: 192.168.1.1

                      192.168.1.2

                      192.168.1.101

                      192.168.1.102

          DNS Domain: go-lab.jp

実際に名前解決が発生すると、利用されている DNS サーバ（Current DNS Server）がわかります。

root@photon-machine [ ~ ]# resolvectl | tail -n 10

MulticastDNS setting: no

  DNSOverTLS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

  Current DNS Server: 192.168.1.1

         DNS Servers: 192.168.1.1

                      192.168.1.2

                      192.168.1.101

                      192.168.1.102

          DNS Domain: go-lab.jp

DNS サーバ のアドレスが変更されても、/etc/resolv.conf のアドレスは

127.0.0.53 のままですが、サーチドメインは追加されます。

root@photon-machine [ ~ ]# grep -v '#' /etc/resolv.conf

 

nameserver 127.0.0.53

search go-lab.jp

以上。Photon OS 3.0 の DNS サーバ アドレス設定の様子でした。

Hi

We are running vSphere 6.7.0.2 and ESXi 6.7.0 11675023 in our environment.

We begun to test with Windows Server 2019. We have made a template an deployed a few test machines.

Everythings seams to be working as it should except that we have problem taking snapshots where we want to quiesce the guest file system.

We are running VMware Tools 10.3.5.10430147 on the servers.

We get the following errors:

Warning message on XXXX on XXXXXXX in vDatacenter: The guest OS has reported an error during quiescing. The error code was: 5 The error message was: 'VssSyncStart' operation failed: IDispatch error #8454 (0x80042306)

Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE1) fails with winerror 1168.  hr = 0x80070490, Element not found.

Running VSSADMIN LIST WRITERS show the following problem:

Writer name: 'System Writer'

Writer name: 'ASR Writer'

Writer name: 'WMI Writer'

Writer name: 'Registry Writer'

Writer name: 'COM+ REGDB Writer'

Writer name: 'Shadow Copy Optimization Writer'

All with the same state and error:

   State: [7] Failed

   Last error: Timed out

No errors in VSSADMIN before trying to take a snapshot.

Anyone else with this problem?

Help appreciated.

/Olof

I'm trying to upgrade from a Windows VCS (6.5) to VCSA (6.7).   Falling at the first hurdle though -- the migration assistant, run on the Windows VCS fails with:

Error: Unable to enumerate and validate the root certificates from the TRUSTED_ROOTS VECS store.

Resolution: Make sure that the vmafd service is reachable and started before continuing.

The VMware afd service is running though (it runs as a Windows service, "Local System" user).  I have tried the usual, restarting service to no avail.  The service does have "Allow service to interact with desktop" selected. Under the vSphere Web Client / Root Certificates I can see the normal CA cert (VMware Engineering) which is not expired and looks fine.

No idea why this isn't working (I'm not really a Windows guy), so any pointers appreciated.

I've gone through this about half-a-dozen times with different types of certificates each with the same message of failure in /var/log/proton/nsxapi.log. This same process worked fine with NSX-T 2.3. Let me explain my topology (screenshots for sauce).

• NSX-T 2.4
• 3 nodes
  • cz-nest-nsxtm01 (10.2.21.16)
  • cz-nest-nsxtm02 (10.2.21.17)
  • cz-nest-nsxtm03 (10.2.21.18)
• 1 HA VIP address (ILB)
  • cz-nest-nsxtm (10.2.21.19)

I have referenced the steps in VVD 5.0.1 and used the CertGen utility to create certificates signed by my internal enterprise CA. When replacement on cz-nest-nsxtm01 with the node cert did not work, I attempted steps with a self-signed cert only with the same failure. I upload the CA cert and upload the node certs, including the one for the cluster IP. SAN contains FQDN and IP. I don't think this is an issue of cert contents.

I retrieve the ID of the cert in question. For more details of the cert, if I curl to /api/v1/trust-management/certificates it returns the following:

I post to the necessary URI as follows:

curl -k -u admin:VMware1!' -X POST "https://cz-nest-nsxtm01.domain.com/api/v1/node/services/http?action=apply_certificate&certificate_id=5c4f0ee9-00cb-4acd-8431-07903767204a"

In response I receive:

{  "error_code": 36235,  "error_message": "Error updating certificate usage.",  "module_name": "node-services"
}

Upon examination of /var/log/proton/nsxapi.log I find the following messages logged after the operation returns failure (markup by VS Code for convenience):

2019-05-04T13:19:18.849ZINFOhttp-nio-127.0.0.1-7440-exec-1 PreAuthenticatedAuthenticationProvider - - [nsx@6876 comp="nsx-manager" subcomp="manager"] User node-mgmt. Granted authorities: ''

2019-05-04T13:19:18.849ZINFOhttp-nio-127.0.0.1-7440-exec-1 PreAuthenticatedAuthenticationProvider - - [nsx@6876 comp="nsx-manager" subcomp="manager"] User node-mgmt. Granted authorities: ''

2019-05-04T13:19:18.876ZINFOhttp-nio-127.0.0.1-7440-exec-1 AuditingServiceImpl - SYSTEM [nsx@6876 audit="true" comp="nsx-manager" reqId="bbf540a7-e46c-4590-811f-b078753c526e" subcomp="manager"] UserName="node-mgmt", ModuleName="CertificateManager", Operation="GetPrivateCertificate", Operation status="success", New value=["5c4f0ee9-00cb-4acd-8431-07903767204a"]

2019-05-04T13:19:18.924ZINFOhttp-nio-127.0.0.1-7440-exec-2 PreAuthenticatedAuthenticationProvider - - [nsx@6876 comp="nsx-manager" subcomp="manager"] User node-mgmt. Granted authorities: ''

2019-05-04T13:19:18.925ZINFOhttp-nio-127.0.0.1-7440-exec-2 PreAuthenticatedAuthenticationProvider - - [nsx@6876 comp="nsx-manager" subcomp="manager"] User node-mgmt. Granted authorities: ''

2019-05-04T13:19:18.936ZINFOhttp-nio-127.0.0.1-7440-exec-2 TrustStoreFacadeImpl - SYSTEM [nsx@6876 comp="nsx-manager" subcomp="manager"] Reserve certificate 5c4f0ee9-00cb-4acd-8431-07903767204a

2019-05-04T13:19:18.944ZINFOhttp-nio-127.0.0.1-7440-exec-2 TrustStoreServiceImpl - SYSTEM [nsx@6876 comp="nsx-manager" subcomp="manager"] Reserve service type API for node 4c9f2c42-57fd-88d4-24bb-3917f5e69a12 for certificate node-cz-nest-nsxtm01

2019-05-04T13:19:18.950ZERRORhttp-nio-127.0.0.1-7440-exec-2 PrincipalOwnerValidator - - [nsx@6876 comp="nsx-manager" errorCode="MP289" subcomp="manager"] XXX Principal 'node-mgmt' with role '[]' attempts to delete or modify an object of type ImmutableCertificateEntity it doesn't own. (createUser=nsx_policy, allowOverwrite=null)

2019-05-04T13:19:18.951ZINFOhttp-nio-127.0.0.1-7440-exec-2 AuditingServiceImpl - SYSTEM [nsx@6876 audit="true" comp="nsx-manager" reqId="5ce8722f-1c1e-4681-a181-db21e86aa72e" subcomp="manager"] UserName="node-mgmt", ModuleName="CertificateManager", Operation="CertificateReserve", Operation status="failure", New value=["5c4f0ee9-00cb-4acd-8431-07903767204a" {"service_type":"API","node_id":"4c9f2c42-57fd-88d4-24bb-3917f5e69a12"}]

2019-05-04T13:19:18.952ZINFOhttp-nio-127.0.0.1-7440-exec-2 NsxBaseRestController - - [nsx@6876 comp="nsx-manager" subcomp="manager"] Error in API /nsxapi/api/v1/trust-management/certificates/5c4f0ee9-00cb-4acd-8431-07903767204a?action=reserve caused by exception com.vmware.nsx.management.container.exceptions.InvalidOwnerException: {"moduleName":"common-services","errorCode":289,"errorMessage":"Principal 'node-mgmt' with role '[]' attempts to delete or modify an object of type ImmutableCertificateEntity it doesn't own. (createUser=nsx_policy, allowOverwrite=null)"}