I did not see a specific forum for VUM so I landed here. Let me know if this post would be better elsewhere.

We have a 4 host vCenter 6.5 cluster that I inherited a bit back. I felt my first task was to  bring all the hosts and VMs up to the current software baselines and am ready to move to VMware Tools.

In VUM the VMware Tools Upgrade Predefined Baseline is gone, I assume at some point it was deleted. After a lot of googling and some searching here, I cannot find how to recreate a predefined baseline.

Could anyone point me in the right direction? Blog, KB article, etc etc.

Thanks

Don

Hi All I am new to Horizon API and finding it difficult to get information. Essentially I want to  query RDSServerSetting - as per View API - VMware API Explorer - VMware {code}

Data Object Properties

Properties

My goal is disabling RDS Server when disk space reaches over 95%  - any help appreciated

So far I can run following $services1.RDSServer | gm    and that  will show me following but from there I have not been able to proceed

TypeName: VMware.Hv.RDSServer

Name                      MemberType Definition                                                                               

----                      ---------- ----------                                                                               

Equals                    Method     bool Equals(System.Object obj)                                                           

GetHashCode               Method     int GetHashCode()                                                                        

GetType                   Method     type GetType()                                                                           

RDSServer_Delete          Method     void RDSServer_Delete(VMware.Hv.RDSServerId id)                                          

RDSServer_Get             Method     VMware.Hv.RDSServerInfo RDSServer_Get(VMware.Hv.RDSServerId id)                          

RDSServer_GetSummaryView  Method     VMware.Hv.RDSServerSummaryView RDSServer_GetSummaryView(VMware.Hv.RDSServerId id)        

RDSServer_Recover         Method     void RDSServer_Recover(VMware.Hv.RDSServerId id)                                         

RDSServer_RecoverMachines Method     void RDSServer_RecoverMachines(VMware.Hv.RDSServerId[] ids)                              

RDSServer_Register        Method     VMware.Hv.RDSServerRegisterResult RDSServer_Register(VMware.Hv.RDSServerRegisterSpec spec)

RDSServer_Update          Method     void RDSServer_Update(VMware.Hv.RDSServerId id, VMware.Hv.MapEntry[] updates)            

ToString                  Method     string ToString()                                                                        

Client                    Property   VMware.Hv.HviClient Client {get;}                                                        

MoRef                     Property   VMware.Hv.ManagedObjectReference MoRef {get;}                                            

Data Object Properties

Properties

I am using Ubuntu GUI and Chrome browser to connect to vCenter.

I see the error that my connection may not be private:

Your connection is not private

Attackers might be trying to steal your information from 192.168.2.123 (for example, passwords, messages or credit cards). Learn more

Hello all! 

We have had an issue with certs over the last couple of days.

Our vcenter is installed on a windows machine, it is not an appliance.  We are on vCenter 6 version 3g.  I know it is out of date, we are not in a position to update any of it.  We currently have a new environment with updated software but it will be a few months as we migrate.  Within our vcenter we also have NSX and VCD so we are cautious about doing anything cert related.

Currently we cannot log into our vsphere environment unless we role back the time to a date prior to 8/15, after changing the date and restarting the web service, we are able to log in.  I know the location of the certificate manager application on the windows machine but we are unsure the best route to take dealing with these certs.  Again, we do not want to use custom certs or redo root certs, we just need to extend these 4 certs to get everything working while we migrate to the new environment.

Any help would be greatly appreciated.

just searched documents including https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-resource-management-guide.pdf  and https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/performance/vsphere-esxi-vcenter-server-67-p… to understand "non-uniform memory access".

I'd like to know the correct steps to utilize the basic NUMA on ESXi 6.7 to optimize the VM performance.

assume that i got an environment that indeed need to use NUMA, which included a cluster of ESXi hosts and some VMs of high virtual hardware(say 16 vCPU and 48GB vRAM).

if i wanna configure the ESXi hosts to automatically do the NUMA scheduling on these VMs, should I follow the procedure under:

1. check "interleaving memory" in each server's BIOS to make ESXi turn the node into NUMA node?

2. disable the VM resource pool(if it exist) on this ESXi host cluster because NUMA will allocate recourses?

3. now the clusters will do the NUMA scheduling automatically without the need to configure on each VM(no need to configure "numa.nodeAffinity" paremeters)?

additional doubt is, how to know whether an ESXi host has been enabled with NUMA to function or not? only via the BIOS?

(The topic "Specifying NUMA Controls" in official document described only three NUMA manual options of affinity for VMs and i guess this is based on an already enabled NUMA system...)

Hello, I have a question regarding vSAN reclaim.

The environment is a CentOS8 VM running on vSAN RAID Level 5.

For disk 1, 40GB of space was allocated to install the OS, and 2TB of Disk 2 was configured as a DATA storage.

Disk 2 consists of a single partition of sdb1, and if you check with "df -h" command, 70GB of space is being used.

Based on vSAN RAID Level 5, it is calculated as 70G * 1.33, so it is expected to use about 93GB of space, but the disk uses about 262GB of VMDK capacity.

So I changed the VMDK's policy to RAID Level 1, and then reverted it back to the RAID Level 5 policy.

After doing this, the capacity of Disk 2 was reduced to 202GB.

With a question, I cloned the VM and performed the same operation, and the disk capacity of the cloned VM was 129GB.

Could you tell us an example of a situation similar to this one and a solution?

I made a bug report in Ubuntu thinking its might be a Ubuntu/Canonical problem, but it doesn't look like so:

https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1891976

I am thinking of using other alternatives of VMware. (Maybe Virtual Box)

This community looks barely alive. I DO NOT get a reply or solution or any form of tips. I have seen this on other questions too. It looks like its a common thing here.

Anyway, let me know what you guys think about Telegram not taking any keyboard & mouse input when I was using the latest stable Workstation Pro (with Kali Linux).

So i payed money for this product and it is god awful!

I have installed a ubuntu 20 04 LTS and i want to run i3, and not gnome desktop.

I am running a macbook pro with a retina screen. And VMWare fusion 11.5.6.

The bugs i have encountered so far:

- The mouse trackpad has awful response. Scrolling starts out with me dragging on the trackpad a full cm or two until it actually understands that it should start scrolling. Its like scrolling in mud! If i pull my fingers slow along the trackpad, the vm doesn't scroll at all. I have set that it should permanently not look for gaming. Fix the sensitivity!

- I set the resolution using xrandr in my vm, and i run it full screen. But if i flip to the host (macOS) and back, the host changes the resolution in the guest, so i need to reset the resolution. This also drives me crazy.

- Drag and drop does not work, and there is full of bad information so i have no idea how to fix it. The cd doesnt, mount, but the menu is grayed out and says in grey "reinstall vmware tools" which means they must be installed. When. running ps -ef | grep vmware i see that there is running vmware service. But still no drag n drop, or copy paste is working from host to guest.

None of the documentation i have found works or addresses any of these issues.

Fix your documentation so that it is relevant and easy, so that you actually can find information about how to solve this.

Hallo,

ich hab hier 2 ESXi (6.0.0 U3) die aufgrund eines Festplattenfehlers zweier NVME Platten kurzzeitig nicht bedienbar waren. Nach einem hardreset und einiger Wartezeit sind beide wieder oben.

Bei beiden ESXi war die Shell und SSH nach den neustart aktiviert (das war vorher ausgeschaltet)?

Jetzt frag ich micht wieso das da wieder an ist?

Danke

"Access denied" error while enabling ICMP

Set-NetFirewallRule -DisplayName "File and Printer Sharing (Echo Request - ICMPv4-In)" -enabled True -RemoteAddress "192.168.0.5" -Protocol ICMPv4 -IcmpType 8 -Direction Inbound -Action Allow

Any assistance that I can get would be much appreciated.

Thank you

**** 留意事項 *****

こちらのブログの内容はDECN（Dell EMC Community Network）に投稿されたブログの再掲です。

DECNが近い将来に廃止となるためこちらに移行させていただいております。

内容についてはオリジナルの執筆当時のものとなりますので最新ではない場合がありますがご容赦ください。

もしVCSAが突然使えなくなったらどうしますか？

VCSAがDownした場合はvMotionやvSANに関するオペレーションができなくなるか、かなり制限されます。

またHorizon環境ではVDIに接続できなくなったりするので被害が甚大になる場合があります。

この世の中に100％の可用性を保証するストレージは存在せず、VxRail（vSAN）も例外ではありません。

したがって、VCSAに限らず、失われたら困るデータやVMは必ずバックアップを取る必要があります。

しかしながら、バックアップは取ってはいるものの、いざリストアが必要になったときに手順がわからないといった不安や、

ベンダーの提供する手順書通りにリストアできない！といったトラブルはバックアップあるあるだと思います。

VxRail環境においてもきっと例外ではないでしょう。

VxRail環境では多くのユーザーでVDPによるバックアップをしていますが、特にVCSA/PSCのリストアをする際に以下の想定外に直面することになります。

1. VDPでVMをリストアする際にvCenterが必要なのでVCSA/PSCがない状態では、そもそもVMをリストアできない
2. VxRailは分散仮想スイッチしかないのでリストアしたVM（VCSA/PSC）をネットワークに接続するにはVCSA/PSCが必要
3. リストア後にVxRail Manager の内部DBの情報と齟齬が生じる

1つ目と2つ目は要するにVDPやVDSの観点でそもそもVCSA/PSCに依存しているため、金庫に鍵を閉じ込めたような状態になるわけです。

かといって、VCSA/PSCは重要なVMであり、リストアできませんでは話になりません。

3つ目はVxRail固有の問題とはなりますが、通常運用時は問題にならず、Upgradeや構成変更の際に顕在化することがあるのでリストア後に追加の対処が必要です。

ではどのようにしてこの矛盾を解決すればいいでしょうか？

１つ目の問題について

１については簡単です。というのもすでにVDPにはその機能があります。

EmergencyRestoreと呼ばれる機能で、vCenterがない状態でもESXiに直接VMをリストアできる機能です。

この機能があるのでVCSA/PSCに問題が発生したとしてもVDPが生きていればリストアが可能です。

詳細は下記VDP管理者ガイドに譲りますが概要としては以下です。

1. VDP GUIにログイン
2. Emergency Restoreのタブに移動し、VDPが稼働しているESXiを確認
3. 上記ESXiのGUIにログインして「vCenterからの切断」を実施
4. VDP GUIのEmergency Restoreタブから上記ESXiにVCSA/PSCのリストアを実行
5. リストア後、VCSA/PSCを起動して後に上記ESXiをvCenterに再接続する

・VDP管理者ガイド

https://docs.vmware.com/en/VMware-vSphere/6.5/vmware-data-protection-administration-guide-61.pdf

上記ドキュメントだけでは不安（英語だし。。。）というユーザは有事の際はDell EMCサポートにご相談下さい。

通常、リストア作業はユーザ作業範疇ですがDell EMCのVxRailサポートは旧EMCのエンタープライズサポート文化を継承しているので、より踏み込んだサポートを提供していると自負しています。

また以下のDECNブログでも詳しく説明されています。

VxRail 管理系VMのバックアップ・リストア方法【リストア・復旧編】

※残念ながら、DECNの廃止に伴い↑のページはなくなってしまいました。

VDP以外のバックアップソリューションを利用している場合は必ずVCSA/PSCへの対応状況を確認してください。

一部のバックアップソリューションはVCSA/PSCのリストアができない場合があります。

2つ目の問題について

2つ目の問題についてはどうでしょうか？

VDPの機能でVCSA/PSC VMをリストアした場合、リストアしたVMは新規VMということになりますが、新規VMのネットワークを設定する場合はVCSA/PSCが必要になります。

そのため、リストアしたVCSA/PSCは仮想スイッチに接続することができず、そのままでは役に立ちません。

この問題の解決方法として以下が考えられます。

1. 事前に短期ポート（Ephemeral Port）を作成しておく
2. 一時的に標準仮想スイッチを作成し、vmnicの一つを割り当てる（冗長性の低下が発生）
3. VxRail Manager VMのポートを借りてネットワークに接続する

１の方法は短期ポート（短期バインド）とよばれる、VDS上のポートグループでありながらESXiのみで管理可能なポートになります。※短期ポート（短期バインド）の説明（https://kb.vmware.com/s/article/1022312?lang=ja）

ただし、短期ポートの作成自体はVCSA/PSCが必要なため、復旧用に事前に作成しておく必要があります。

※作成する短期ポートのポートグループは既存のvCenterネットワークポートグループと同様のVLANを設定し、IPの変更なくESXiと疎通できる必要があります。

事前に作成さえしておけば、この方法が最も簡単なリストア方法になります。

やり方としては、Emergency RestoreでVCSA/PSC VMをリストアしたのちに対象のESXiのGUIにログインして、短期ポートとして作成しておいたポートグループをアサインするだけです。

2の方法は既存VDSに割り当てられているvmnicの一つを引っぺがして、新しく作った標準仮想スイッチに割り当てなおすことで、VCSA/PSCなしで新規VMを外部ネットワークと疎通させることができます。

この方法はすでにご紹介済みのDECNブログで説明されていますのでそちらをご参照ください。

VxRail 管理系VMのバックアップ・リストア方法【リストア・復旧編】

※残念ながら、DECNの廃止に伴い↑のページはなくなってしまいました。

同様のやり方が、Dell EMC KB#530187に記載されてますのでそちらをご参照ください。

3の方法は既存のVMから作成済みの分散仮想スイッチポートを借用する方法です。

要するに既存の接続済み仮想マシンに成りすまして分散仮想スイッチのポートグループに接続してしまう、という方法です。

この方法はDell EMC KB#504380にて説明されている方法です。

犠牲となるVMはVxRail Managerでなくとも、vCenterと同じポートグループに接続されているVMであれば構いません。

Shutdownする必要があるので、業務影響のないVMを選んでください。

古いVCSA/PSCのポートを借用可能であればそれを流用して構いません。

詳細は上記KBに譲りますが、概要は以下です。

1. VxRail Manager VMをShutdownする
2. VxRail Managerのvmxファイルからdvs.portIdとdvs.connectedIdをメモする
3. リストア済み（ネットワーク未接続）のVCSA VMをShutdownする
4. リストア済みVCSAのvmxファイルを編集してdvs.portIdとdvs.connectedIdをVxRail Manager VMのものと書き換える
5. VCSA VMを起動する
6. 起動後VCSA VMを別のHostにvMotionする。vMotionすることでdvs.portId情報が更新されます。
7. VxRail Manager VMを起動する

3つ目の問題について

3つ目の問題はVCSA/PSCのリストア後に発生する問題です。

VxRail Managerでは内部DBにVCSA/PSCのuuidとmorefIdを保存していますが、VCSA/PSCをリストアすることでその値が変わってしまうため、内部DB側も編集してあげる必要があります。

この作業はDell EMCサポートにて実施すべきものなので、リストア後はDell EMCサポート窓口にご連絡ください。

なお、VxRail Manager の内部DBの値が実際のUUID/MorefIDと異なっていたとしても、業務影響はありませんのでご安心ください。

即座に対処する必要はありませんが、将来的にUpgradeや構成変更時にVxRail ManagerがVCSA/PSCを見つけられずにエラーとなる可能性がありますので忘れずに対処しましょう。

いかがでしたでしょうか。

いきなりすべてを理解するのは難しいかもしれませんが、障害時は迅速な復旧が求められる場合もありますので一度関連KBや資料に目を通しておかれることをお勧めします。

An abstract of my vmkernel.log

We had storage incidents (crashes for unresolved bugs, being a readcache merge problem and a backend driver issue) on Unity 650F.

Dell is writing on a 'custom' fix on both issues. In the mean time we were asked to mitigate the controller autoresets, and upgrade to OE 5.0.3 which they agreed upon will not resolve the current controller resets. After complaints from our side, they digged into every component of our infra, to mitigate on the impact/issues on their storage. The following SCSI sense codes were found in the vmkernel log and we are referred to further seek host support to suppress 'illegal scsi commands'

These according to them are to addressed as they are contributing problems to crashe of a controller node , as target reset attempts are being made by the hosts (as seen from the storage side persfective)

2020-08-17T01:49:15.677Z cpu108:65805)ScsiDeviceIO: 3015: Cmd(0x439e4341dfc0) 0xfe, CmdSN 0xbbc2e5 from world 65687 to dev "naa.60060160e8004b00e2ca985c1400127d" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e4368a5c0, 65687) to dev "naa.60060160e8004b007e9d9a5cf732ff8e" on path "vmhba2:C0:T11:L47" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43720dc0) 0xfe, CmdSN 0x719b30 from world 65687 to dev "naa.60060160e8004b007e9d9a5cf732ff8e" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435e02c0, 65687) to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" on path "vmhba3:C0:T10:L102" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43502940) 0xfe, CmdSN 0x382ef0 from world 65687 to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

2020-08-17T01:49:15.877Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435079c0, 65687) to dev "naa.60060160e8004b00de1a995cd70e3c6a" on path "vmhba3:C0:T12:L30" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

I entred those value to

https://www.virten.net/vmware/esxi-scsi-sense-code-decoder/?host=8&device=0&plugin=0&sensekey=80&asc=41&ascq=0&opcode=

so according to this, the HBA does a reset of the target, which in this case is a DELL EMC Unity FC port.

And now what ?

dev "naa.6006" is DELL EMC Storage, in my case Dell EMC Unity 650f running OE 4.5.1 (UWDC01) & OE 5.0.3 (UWDC02)

Current Dell EMC Unity Target code is OE 5.0.3

[root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160de004b005f5d2a5fbbcad438"

naa.60060160de004b005f5d2a5fbbcad438:1                                     /vmfs/devices/disks/naa.60060160de004b005f5d2a5fbbcad438:1                                     5f2a5df1-f99059c6-eed8-20040ff4978e  0  UWDC01_IT-PROD-WDC_V005

[root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160e8004b00e595255ec02cf074"

naa.60060160e8004b00e595255ec02cf074:1                                     /vmfs/devices/disks/naa.60060160e8004b00e595255ec02cf074:1                                     5e2596ab-2bec8188-f141-20040ff4978e  0  UWDC02_IT-PROD-WDC_V103

[root@esx070:~] vmkchdev -l | grep vmhba

0000:00:11.5 8086:a1d2 1734:1230 vmkernel vmhba0

0000:00:17.0 8086:a182 1734:1230 vmkernel vmhba1

0000:17:00.0 1077:2261 1077:029b vmkernel vmhba2 ----------------> FC HBA

0000:6d:00.0 1077:2261 1077:029b vmkernel vmhba3 ----------------> FC HBA

[root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d

Dumping all key-value instance names:

Key Value Instance:  vmhba3/qlogic

Key Value Instance:  vmhba2/qlogic

Key Value Instance:  vmhba1/vmw_ahci

Key Value Instance:  vmhba0/vmw_ahci

Key Value Instance:  MOD_PARM/qlogic

[root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -l -i vmhba2/qlogic
Listing keys:
Name:   ADAPTER
Type:   string
value:
QLogic 16Gb 1-port FC to PCIe Gen3 x8 Adapter for QLE2690:
        FC Firmware Version: 8.05.61 (d0d5), Driver version 2.1.73.0

Host Device Name vmhba2

BIOS version 3.61
FCODE version 4.11
EFI version 6.11
Flash FW version 8.05.61
ISP: ISP2261, Serial# RFD1722T35676
MSI-X enabled
Request Queue = 0x4309f6548000, Response Queue = 0x4309f6569000
Request Queue count = 2048, Response Queue count = 512
Number of response queues for CPU affinity operation: 4
CPU Affinity mode enabled
Total number of MSI-X interrupts on vector 0 (handler = 23) = 26676
Total number of MSI-X interrupts on vector 1 (handler = 24) = 2186
Total number of MSI-X interrupts on vector 2 (handler = 25) = 1090148738
Total number of MSI-X interrupts on vector 3 (handler = 26) = 583007145
Total number of MSI-X interrupts on vector 4 (handler = 27) = 2055128386
Total number of MSI-X interrupts on vector 5 (handler = 28) = 1406005796
Device queue depth = 0x8
Number of free request entries = 1271
FAWWN support: disabled
FEC support: Disabled
Total number of outstanding commands: 0
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 29
Host adapter:Loop State = [READY], flags = 0x20ae200
Link speed = [16 Gbps]

Dpc flags = 0x0
Link down Timeout =  010
Port down retry =  010
Login retry count =  010
Execution throttle = 2048
ZIO mode = 0x6, ZIO timer = 1
Commands retried with dropped frame(s) = 297

Product ID = 4953 5020 2261 0001

NPIV Supported : Yes
Max Virtual Ports = 254

SCSI Device Information:
scsi-qla0-adapter-node=20000024ff149042:160a00:0;
scsi-qla0-adapter-port=21000024ff149042:160a00:0;

Name:   TARGET
Type:   string
value:
Driver version 2.1.73.0

Host Device Name vmhba2

FC Target-Port List:
scsi-qla0-target-0=500000e0da81df29:122300:0:Online;
scsi-qla0-target-1=500000e0da81df39:142300:1:Online;
scsi-qla0-target-2=5006016249e4121e:140000:2:Online;
scsi-qla0-target-3=5006016349e0121e:120000:3:Online;
scsi-qla0-target-4=5006016849e4121e:140100:4:Online;
scsi-qla0-target-5=5006016a49e4121e:120200:5:Online;
scsi-qla0-target-6=5006016249e415ff:0e0000:6:Online;
scsi-qla0-target-7=5006016349e015ff:100000:7:Online;
scsi-qla0-target-8=5006016849e415ff:100100:8:Online;
scsi-qla0-target-9=5006016a49e415ff:0e0100:9:Online;
scsi-qla0-target-10=5006016249e41688:0e0500:a:Online;
scsi-qla0-target-11=5006016349e01688:100200:b:Online;
scsi-qla0-target-12=5006016849e41688:100300:c:Online;
scsi-qla0-target-13=5006016a49e41688:0e0300:d:Online;

Name:   NPIV
Type:   string
value:
Driver version 2.1.73.0

Host Device Name vmhba2

NPIV Supported : Yes

Looking at the Qlogic Site (Marvell Nowadays) and looing for the QL2690, we are at version -1 compared to the latest

QLogic / Marvell Driver Download

README

                   Read1st for Cavium Flash Image Package

                     --------------------------------------

                   **** ONLY FOR 268x/269x/27xx Series Adapters ****

1. Contents Of Flash Package

--------------------------------

The files contained in this Flash image package are zipped into a file that

will expand to provide the following versions for the 268x/269x/276x Series Adapters.

*  Flash Image Version 01.01.91

   BK010191.BIN contains:

   ----------------------

     Bootcode FC

       FC BIOS       v3.62

       FC FCode      v4.11  (Initiator)

       FC FCode      v4.10  (Target)

       FC EFI        v7.00  (Signed)

     FC Firmware   v8.08.231

     MPI Firmware  v1.00.19

     PEP Firmware(Quad-port)        v1.0.27

     PEP Firmware(Single/Dual port) v2.0.12

     PEP SoftROM(Quad port)         v1.0.16

     PEP SoftROM(Single/Dual port)  v2.0.11

     EFlash tool  v1.18

Hi there,

Am using win2012 on my vmworkstation 15.0.2,when i start the vm it goes completely to black screen see below screen shot for reference.For work around i will restart my laptop and if i got luck it start the vm other wise it goes in to black screen,but this done'st happen quite often.pls advice.

Hi everyone,

I am using VMware Fusion 11.5 on my MacBook Pro (15", 2018) and for a couple of weeks now, my whole system has become mostly unusable when the VM is running.

The issue emerged when using macOS Catalina 10.15.5, so I do not think it is related to the known issue relating to the memory leak. Since then I have updated to 10.15.6, but the issue remains. I have not yet encountered the memory leak as the system is crashing before. The problem exists in both VMware Fusion 11.5.5 and 11.5.6.

What is happening? When using the VM over time the whole system (both guest OS and host OS) hangs for some seconds every other minute. After some of these freezes (sometimes just a few minutes, sometimes after an hour), everything goes black, I am back at the macOS login screen. When logging in, the VMware is not visible anymore (but still running), so I have to suspend and restart the VM. Then, again, I have a couple of minutes running the VM until the same issue happens again.

• Using a freshly booted host and/or guest OS does not make any difference.
• The issue only occurs when the VM is running - absolutely no problems, when the VM is turned off or suspended.
• It seems to me the issue occurs more quickly when I have many windows open, but I haven't validated this systematically yet.
• Deactivating 3D acceleration does not solve this issue.

When looking at Console.app the culprit seems to be macOS' WindowServer (see attached crash report):

Process:               WindowServer [288]
Path:                  /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier:            WindowServer
Version:               600.00 (451.4)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           WindowServer [288]
User ID:               88


Date/Time:             2020-08-08 13:01:17.161 +0200
OS Version:            Mac OS X 10.15.6 (19G73)
Report Version:        12
Bridge OS Version:     4.6 (17P6065)
Anonymous UUID:        083DF09A-B169-7F44-E3EB-1E021FF1CEDC




Time Awake Since Boot: 10000 seconds


System Integrity Protection: enabled


Crashed Thread:        0  Dispatch queue: com.apple.main-thread


Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

In system.log I see a couple of messages, but I have those mdworker-logs also when the system does not freeze:

Aug  8 12:55:39 MacBook-Pro-3 VTDecoderXPCService[74544]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Aug  8 12:55:39 MacBook-Pro-3 VTDecoderXPCService[74544]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Aug  8 12:55:39 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mdmclient.74575): Failed to bootstrap path: path = /usr/libexec/mdmclient, error = 108: Invalid path
Aug  8 12:55:40 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.backupd.74579): Failed to bootstrap path: path = /System/Library/CoreServices/backupd.bundle/Contents/Resources/backupd, error = 2: No such file or directory
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0700-0000-0000-000000000000[74580]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0300-0000-0000-000000000000[74570]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0700-0000-0000-000000000000[74583]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0400-0000-0000-000000000000[74584]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0200-0000-0000-000000000000[74586]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:19 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0200-0000-0000-000000000000[74110]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:22 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0400-0000-0000-000000000000[74582]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:44 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0100-0000-0000-000000000000[74588]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:56:48 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0700-0000-0000-000000000000[74587]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0100-0000-0000-000000000000[74571]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0200-0000-0000-000000000000[74581]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0100-0000-0000-000000000000[74578]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0000-0000-0000-000000000000[75390]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0500-0000-0000-000000000000[75216]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:49 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0500-0000-0000-000000000000[75295]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:57:57 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0200-0000-0000-000000000000[75759]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:58:13 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.CloudDocs.MobileDocumentsFileProvider[74229]): Service exited due to SIGKILL | sent by launchd[1]
Aug  8 12:59:06 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0600-0000-0000-000000000000[76153]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 12:59:39 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0300-0000-0000-000000000000[75296]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:00:22 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.TouchBarServer.410): Failed to bootstrap path: path = /usr/libexec/TouchBarServer, error = 108: Invalid path
Aug  8 13:00:30 MacBook-Pro-3 Microsoft Edge[74537]: BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked { 0x7fa521424370[source], ident: 73275 / 0x11e3b, handler: 0x106ea92f0 }
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0100-0000-0000-000000000000[77924]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0200-0000-0000-000000000000[77980]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0000-0000-0000-000000000000[77981]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:07 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0700-0000-0000-000000000000[77979]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0200-0000-0000-000000000000[77978]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0400-0000-0000-000000000000[77976]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:08 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[77975]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[77977]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0200-0000-0000-000000000000[77973]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[77974]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0300-0000-0000-000000000000[77847]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0600-0000-0000-000000000000[76560]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0200-0000-0000-000000000000[77972]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[77637]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:09 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0700-0000-0000-000000000000[77821]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:12 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0200-0000-0000-000000000000[77982]): Service exited due to SIGKILL | sent by mds[195]
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.WindowServer[288]): Service exited due to SIGABRT
Aug  8 13:01:17 MacBook-Pro-3 sessionlogoutd[78459]: DEAD_PROCESS: 252 console
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.ViewBridgeAuxiliary[78461]): Service exited with abnormal code: 2
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.imklaunchagent): This service is defined to be constantly running and is inherently inefficient.
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.coreservices.UASharedPasteboardProgressUI): Unknown key for Boolean: DrainMessagesAfterFailedInit
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.UserEventAgent-LoginWindow): This service is defined to be constantly running and is inherently inefficient.
Aug  8 13:01:17 MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.user.loginwindow.78463.4294967295): com.apple.universalaccessd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

I have attached the vmware-vmfusion.log file, but could not find any evident problem there as well.

Using Google or searching the communities did not reveal any issue that might be related except for the memory leak bug, but since the problem occured already in the previous version of Catalina I do not think it is related.

Any ideas how to resolve this except for re-installing both guest and host OS?

Thanks

Christopher

Hello,

it is possible to find out if our users use apple id ?

We disabled apple id in profile under restrictions but for some users we have created exception profile. now we would like to know if any users use apple id.

I search only for result true or false or something else. I dont need to see complete apple id from user

Hi,

Since yesterday we see a lot of Findings on the Skyline Advisor are popping up.

What we see is that there are findings that are not for our version of ESXi hosts.

We have multiple clusters running. All clusters have the same ESXi versions.  We only see 3 hosts popping up in some findings where all servers are configured same way.

Anybody noticed this as well?   Solution???

Thanks

Gert

I am using Windows 10 in VMware Player 15.5.6 build-16341506 on a Linux Min 20 host. The main reason for the Win10 VM is Office 365 and especially Teams. For my work I have to use Teams a lot and the Linux version for Teams is not up to scratch (no screen sharing, among other things).

The webcam I use is a Logitech C930e. Works fine with Linux Mint 20, and worked fine under Windows, when I had Windows installed on this same PC. However, on the virtual machine the webcam sometimes is available, sometimes it is not.

The VMware taskbar tells me the camera is connected:

And in Windows the USB key in the tray gives me the option to remove the webcam:

Nevertheless, the device is sometimes found with no problems by Teams or other apps in Windows, but sometimes no webcam is found by any application. In these situations the webcam is also not present in device manager.  In some instances, I start out using the webcam in Teams with no issues, but half an hour later, during the same VM session, the webcam is suddenly no longer available.

These are my VMware settings

I am new to VMware Player so maybe I am overlooking something or maybe I need to add extra info. Please let me know.

Thanks,

BJ

Hi All,

I am trying to Eval Horizon 7 for my workplace to implement a work from home solution.

I have installed the ESXi Hosts, added vCenter Server (Licenses) and now have added Horizon Connection Server

I have a 90 day Horizon Universal Evaluation Serial number, I am trying to apply the serial number and getting the following error

License data could not be obtained for this product type

Any help would be appreciated.

i know this uuid

56 4d 06 97 4f 06 b4 73-91 d8 a7 ad ed 8f 95 ee

but i want to know this type uuid.

ex) 4216b4c6-9645-1e24-bbcf-9d2916d

where can i find this uuid in vcenter7.12 or esxi6.7 page?

because i got this error in horizon

failed to delete vm - vmware.sim.fault.invalidParameterFaultParam: sviCloneIds

Detail : DoesNotExist

so if i know the uuid,   i will change vm_uuid. in dbo.sviclone db of horizon composer vm