Version: 6.5.0

Build: 9451637

I know there are already a lot of discussions about this topic and I also tried their solutions but it still does not work. I had already three Webex sessions with VMware support without any success.

We also reinstalled a fresh vCSA together but getting the same error as before. DNS records and NTP are working correctly.

When i try to join the domain in cli i get the following error.

root@vcenter [ ~ ]# /opt/likewise/bin/domainjoin-cli join domain.local administrator password
Joining to AD Domain:   domain.local
With Computer DNS Name: vcenter.domain.local




Error: ERROR_GEN_FAILURE [code 0x0000001f]

SMB2 is also activated in vCenter and Windows Firewall is temporary disabled.

root@vcenter [ ~ ]# /opt/likewise/bin/lwregshell list_values '[HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\rdr]'
+  "Smb2Enabled"      REG_DWORD       0x00000001 (1)

We have an other test DC with SMB1 still enabled and joining this DC worked fine. I activated SMB1 on our productive DC and rebooted just to test this but it still did not work.

DC/AD is Windows Server 2012.

Maybe some of you had the same problem or any helpful tips. I dont want to use smb1 if possible....

I am trying to upgrade a fresh install of vCenter 6.0 U2A on windows to 6.5, the vCenter 6.0 is a newly installed with embedded VUM and PSC. The OS of Windows server is 2008 R2.

The upgrade progresses well till it fails at step 4 of 5 Installing Component: VCServiceManager.

The error message is:

Unable to find the issue in KB or online. Some KBs that are similar are 2120651, 2147547 and 2147548.

Looking for advice.

Thank you

Asaf

A customer of ours receive a PSOD on 2 of the 3 new vSphere 6.7 servers.

I cannot really  find the root of the issue, is there somebody who can give me some advice?

ESXi host fails with the error: PANIC bora/vmkernel/main/dlmalloc.c:xxxx - Corruption in dlmalloc (2147888)

here is the KB article : VMware Knowledge Base 

stated that there is no solution yet.

Anything i can do to solve this issue ... rather than opening a case with VMWare ?

Whats the difference between creating a full clone from VM menu vs right clicking the VM file and choosing "Duplicate" fro mthe context menu on Mac ?

Seems they both accomplish the same result, with the "Duplicate" option being a hell of allot faster  regardless.

There is any reason why doing a full clone is slow ? doesn't matter the size of the VM, a full clone seems always slower.

Hey,

I'd love some help with this please!

I have 2 VCSA, an External PSC that I have updated to 6.0.0.30400, updated from 6.0.0.200 last night, and a vCenter running 6.0.0.5110 which I am trying to upgrade to 6.0.0.30400

The patches stage ok but I get the errors shown below when I install them.

The PSC had been on 6.0.0.200 for a while. My colleague had previously been battling with the vCenter which was on 6.0.0. I managed to get the vCenter up to 6.0.0.5110 last night. I tried more recent updates but it always fails.

df -h shows good space

Filesystem                            Size  Used Avail Use% Mounted on

/dev/sda3                              11G  5.2G  5.1G  51% /

udev                                  7.9G  168K  7.9G   1% /dev

tmpfs                                 7.9G   36K  7.9G   1% /dev/shm

/dev/sda1                             128M   38M   84M  31% /boot

/dev/mapper/core_vg-core               50G   36G   12G  76% /storage/core

/dev/mapper/log_vg-log                 15G  7.6G  6.5G  55% /storage/log

/dev/mapper/db_vg-db                  9.9G  294M  9.1G   4% /storage/db

/dev/mapper/dblog_vg-dblog            5.0G  587M  4.1G  13% /storage/dblog

/dev/mapper/seat_vg-seat               25G  1.5G   22G   7% /storage/seat

/dev/mapper/netdump_vg-netdump       1001M   18M  932M   2% /storage/netdump

/dev/mapper/autodeploy_vg-autodeploy  9.9G  151M  9.2G   2% /storage/autodeploy

/dev/mapper/invsvc_vg-invsvc          9.9G  213M  9.2G   3% /storage/invsvc

I've rotated the log files '/etc/logrotate.d/logrotate -f /etc/logrotate.conf'

The only other solutions I have integrated are vRealize Operations Manager which is running 6.0.5571310

I've got the VMware-vCenter-Server-Appliance-6.0.0.30400-7464101-patch-FP.iso mounted

These are the commands I'm running:

Command> software-packages stage --iso --acceptEulas

[2018-03-06T11:20:32.065] : Staging software update packages from ISO

[2018-03-06T11:20:32.065] : ISO mounted successfully

[2018-03-06 11:20:32,287] : Running pre-stage script.....

[2018-03-06T11:20:33.065] : Verifying staging area

[2018-03-06T11:20:33.065] : Validating software update payload

[2018-03-06T11:20:33.065] : Validation successful

[2018-03-06 11:20:33,828] : Processing software packages in update payload 231/231

[2018-03-06T11:21:52.065] : ISO unmounted successfully

[2018-03-06T11:21:52.065] : (212) packages staged successfully

[2018-03-06T11:21:52.065] : Staging process completed successfully

Command> software-packages install --staged

[2018-03-06 11:25:16,264] : Running test transaction ....

[2018-03-06T11:25:19.065] : Installation process failed

I have another SSH session to the vCenter so that I can tail the /var/log/vmware/applmgmt/software-packages.log

Here is the end of /var/log/vmware/applmgmt/software-packages.log

~#~

2018-03-06T11:21:52.065:root:Staging process completed successfully

2018-03-06T11:25:16.065:root:Installing software update packages {args = Namespace(acceptEulas=False, func=<function install at 0x7f71155c8b90>, iso=False, staged=True)}

2018-03-06T11:25:16.065:vmware.vherd.base.software_update:Iniitialized software update state

  Staged status = True

Staged packages:

{}

Installed packages:

{}

Payload packages:

{} MetaData:

{}

2018-03-06T11:25:16.065:vmware.vherd.base.software_update:Extracting information about packages in /var/software-packages/

2018-03-06T11:25:19.065:vmware.vherd.base.software_update:Test transaction failed to update package

out=Preparing...                ##################################################

error=warning: /var/software-packages/ruby2.1-rubygem-backports-3.6.6-1.3.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 0e9af123

warning: /var/software-packages/vmware-tools-core-10.1.10-1.sles11.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 66fd4949

        package libcom_err2-1.41.9-2.10.11.1.x86_64 is already installed

        package net-tools-1.60-725.35.1.x86_64 is already installed

        package popt-1.7-37.63.64.1.x86_64 is already installed

        package rpm-4.4.2.3-37.63.64.1.x86_64 is already installed

        package libdw1-0.152-4.9.17.x86_64 is already installed

        package sg3_utils-1.35-0.19.1.x86_64 is already installed

        package udev-147-0.107.1.x86_64 is already installed

rc=254

2018-03-06T11:25:19.065:root:Installation process failed

2018-03-06T11:25:19.065:root:Test transaction failed to update packages

Exception:

Traceback (most recent call last):

  File "/usr/lib/applmgmt/support/scripts/software-packages.py", line 143, in install

    installPackagesEP(staged=args.staged, iso=args.iso, acceptEulas=args.acceptEulas)

  File "/usr/lib/applmgmt/base/py/vmware/vherd/base/software_update.py", line 1093, in installPackagesEP

    _runTestTransaction(pkgType)

  File "/usr/lib/applmgmt/base/py/vmware/vherd/base/software_update.py", line 770, in _runTestTransaction

    raise GenericException("Test transaction failed to update packages")

GenericException: Test transaction failed to update packages

2018-03-06T11:25:19.065:vmware.vherd.base.software_update:Destroyed software update state

~#~

Many thanks,

Gerg

I tried to setup environment for python3.5 according to https://github.com/vmware/vsphere-automation-sdk-python. When I run

pip install --upgrade --force-reinstall -r requirements.txt --extra-index-url file:///root/vsphere-automation-sdk-python/lib

I get the following error in both general python environment and in virtual  defined in /root/vsphere-automation-sdk-python/:

Collecting twisted>=16.0.0 (from vapi-runtime==2.9.0->vapi-client-bindings==1.4.0->-r requirements.txt (line 5))
  Url 'file:///root/vsphere-automation-sdk-python/lib/twisted/' is ignored: it is neither a file nor a directory.
  Could not find a version that satisfies the requirement twisted>=16.0.0 (from vapi-runtime==2.9.0->vapi-client-bindings==1.4.0->-r requirements.txt (line 5)) (from versions: )
No matching distribution found for twisted>=16.0.0 (from vapi-runtime==2.9.0->vapi-client-bindings==1.4.0->-r requirements.txt (line 5)

I downloaded twisted tarball and installed it using "python setup.py install" in both general  and virtual envoironment in lib/python3.5/site_packages/Twisted-18.9.0-py3.5-linux-x86_64.egg.

But this didn't help because is searched lib/twisted. Can somebody advice please what to do? Thanks in advance

Hi,

I used the update feature of the VCSA portal to upgrade to 6.5.0.22000-9451637, on reboot, if I press "e" to clear the Photon splash screen, I am presented with:

setparams 'Photon'   linux "/"$photon_linux root=$rootpartition net.ifname=0 $photon_cmd\
line coredump_filter=0x37 consoleblank=0   if [ "$photon_initrd" ]; then       initrd "/"$photon_initrd   fi

If I then press F10 (to boot), I get the error message:

Booting a command list
error: not a regular file.
Press any key to continue...

So it looks like there is a bug in the update. The only result I can find, related to this message is here, however, I don't know where or how to get to photon.cfg.

Does anyone have any ideas on how I may be able to fix this?

If I get the ISO file and boot from the media, will this fix the issue, or wipe my install?

TIA.

W.

Dear's

we have ESXI 6.5 and VM 2008R2 working as file server , a snapshot was taken on last March and work proceed till october , for some unknown reason current stat was lost and it revert to last snapshot that taken at March so all of data on D drive return to March dated files and any other modifications was done at this period was lost , what kind of recovery should we make as there is no VMDK include this lost dates ,

Hello

We have just acquired Vmware Fusion Pro 11 at work and are very surprised that the GUI for adding port forwarding under NAT is not been offered. This GUI has been offered in Workstation Pro for Windows for ages via the Network Editor.

I have read on the net that this can be done modifying text files somewhere but why is this feature not been offered on the GUI in a professional version is beyond my understanding. This should have been definitely offered by Vmware directly in the GUI of Fusion Pro without the need to modify obscure settings in text files.

AutoVM is an open source Virtual Private Server (VPS) manager based on in VMware ESXI, gives you full control and automation of hosting companies and VPS Sellers.

With AutoVM you can assign unique panel for each user to make them fulfilled all about VPS Related.

This must be noticeable as AutoVM additional tools , except Automatic Monitoring you can give your billing managements to AutoVM! So you can give more-fast services to your customers.

Some of the features

• Bandwidth monitoring and manage VPS traffic usage.
• Install easily without any changes on the ESXI servers.
• Free modules for manage VPS on the WHMCS client area.
• Auto Provisioning VM After Payment Successfully.
• Auto assign IP and Network adapter once VM created.
• Auto installation of the operating system.
• Ability to assign the existing VM created for WHMCS users.

Prerequisite

the AutoVM platform is designed to be compatible with default VMware ESXI settings and does not require any changes on the network design. To launch the AutoVM platform, you can run it on the hosting control panel such as CPanel or DirectAdmin.

Get Started with free licence

To get and setup the system, please visit the installation article. If you have any questions, please read the FAQ section. If you do not find your answer, please contact us from Client area.

I am using vsphere 6.7 with Ubuntu Server 18.10.

I add a USB Bluetooth Device on vsphere-host for access from ubuntu-server-client.

Repeatly I got this error:

[44028.066466] Bluetooth: hci0: command 0x041b tx timeout

[44327.589481] Bluetooth: hci0: command 0x041b tx timeout

[44628.392205] Bluetooth: hci0: command 0x041b tx timeout

...

[253728.887847] Bluetooth: hci0: command 0x041b tx timeout

[254028.379649] Bluetooth: hci0: command 0x041b tx timeout

[254329.182844] Bluetooth: hci0: command 0x041b tx timeout

[254628.737610] Bluetooth: hci0: command 0x041b tx timeout

[254928.260071] Bluetooth: hci0: command 0x041b tx timeout

lsusb shows correctly:

Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Access via bluetooth working most the time, except many timeouts?

Any ideas for that?

Hello

I have several Windows VMs inside macOS Mojave in Fusion 11. I use an external keyboard and mouse with my Macbook pro.

When I am inside the Windows guests and I press the left alt key nothing happens. The right alt key works as expected. They key works fine in macOS.

The Command and Option keys have been modified in macOS so they switch functions between them when using my external keyboard (Logitech G710) but the right Alt key (that in the physical keyboard is the Windows key) works fine.

Why isn't the left Alt key working inside my Windows guests?

Thank you.

Hi,

Am checking the network requirements to upgrade from vcsa 6.0 and one of them is:

You can use the GUI installer to perform an interactive upgrade of a vCenter Server Appliance 5.5 or 6.0

that uses an embedded vCenter Single Sign-On or Platform Services Controller to

vCenter Server Appliance 6.5 with an embedded Platform Services Controller. You must run the GUI

upgrade from a Windows, Linux, or Mac machine that is in the same network as the appliance that you

want to upgrade.

Does this mean that the only option left is to login to the same ESXi host where the current vcsa is installed and deploy a new VM by using the new vcsa OVF file?

If so once created I will browse to the new vcsa temporary IP (Port:5480). Using the same host will probably facilitate/speed up the stage 2 transfer.

The current vcsa is connected to a distributed port, will the above step with OVF file setup on the ESXi allow me to connect the new vcsa VM to the same distributed port of the current vcsa so they can talk to each other before they switch over?

Document recommends to take a snapshot of the current vcsa, does this mean that at any stage in case of issues or failure to the new vcsa I should be able to revert back to using the old vcsa?

Is there anything from your experience that should be checked/done which might not be in the document?

Reference:

https://docs.vmware.com/en/VMware-vSphere/6.5/vsphere-esxi-vcenter-server-652-upgrade-guide.pdf

Thanks

Hi,

Am in the process of unmounting a number of datastores from vcsa 6.0 (all VMs migrated from them) but this is failing for a small number of hosts due to "File system is busy" message.

I am going to follow the steps shown in this link VMware Knowledge Base but not sure what is the impact on the hosts if the dumpfiles are removed? (Will it automatically create a new one on a new random datastore next time)

How can I check if the datastore is used as an HA heartbeat as when I checked the HA configuration the "Use datastores from the specified list and complement automatically if needed" but none of the datastores is ticked. Would this prevent me from un-mounting the datastore or would HA pick up another datastore automatically without any impact?

The datastore is not part of a Datastore Cluster and Storage I/O Control is disabled for the datastore, let me know if you have other suggestions as suspect that there are files on the datastore that are still actively used/locked by one or more ESXi hosts. Want to avoid rebooting the hosts which cannot have the datastore unmounted from.

Thanks

Hi, is it possible to access VMware virtual host from local network ?

I try to ping VM1 from PC4 or SecondRouter and get nothing.

CentOS 5系に、vCloudDirector5.5.2をインストールしています。

vCloudDirectorのデータベースは、別サーバにインストールされているSQL Server2008を使用しています。

このvCDにて、構成変更作業(NICアダプタタイプの変更)を計画しており、作業失敗時の切戻し方法として、

事前に取得したクローンからの復旧を検討しておりますが、

クローンからの戻しで、正常に元の状態に戻せるという理解でよろしいでしょうか。

SQL　Serverと連携している為、クローンからの戻しのみで、正常に元の状態に復旧できるかを懸念しています。

VMwear Fusion11からWindowsを起動しようとすると「/dev/vmmon を開くことができませんでした：パイプが壊れています。」

が表示されて起動できません。

過去の情報にある解決策を試みますが、解決できません。

機器：MacBook Air　2012年　mid

OS:macOS Mojave

CPU:Core i7

メモリ:8GB

解決策をご存じのかたご教示下さい。

Hi All, could anyone suggest on the above error. I have installed VMware Workstation Player 14.1.3. Its vmxi file (vixwrapper-config) configuration detail is:

#@Version-Info

#

# VixAllProducts revision mapping

#

# This file translates product version specifications into the appropriate Vix

# implementations.

#

# Each @Version-Info line has 5 white-space seperated entries:

#

#    provider-type: ws, esx, viserver, etc

#    apiVersion: the apiVersion supported, as passed in from VixHost_Connect()

#    ipc-type: none, vmdb, vmodl, cim

#    product-version: the product version string

#

#    implementation-directory: the path to the library that implements the

#          version described by the first 4 parameters

#

#

# The configuration is based on the first 4 fields, which describe

# the product.  The 5th field is the location.  To force it to try

# multiple location, the same configuration can be repeated.  Note that

# list is built in LIFO order, so the latest entry in the configuration

# will be the first used.  If for some reason that value fails, it will

# continue through any other matches.

# Workstation 12.0.0

ws        19  vmdb  12.0.0 Workstation-12.0.0

player    19  vmdb  12.0.0 Workstation-12.0.0

# EOF

I was trying to add Workstation 14.1.3 in the file, but was not able edit.

Could anyone suggest how to proceed?

Thansk a lot.

vSAN の機能検証などで、ネステッド ハイパーバイザ環境を利用することがあります。

そこで、1台の物理マシンに vSAN 環境をセットアップした様子を紹介します。

今回の環境構築の方針。

今回は、下記のような vSAN 環境をセットアップします。

• 物理マシンは 1台のみ利用する。
• スペックは下記。
  • CPU： 4コア / 8スレッド（ただし 8スレッド必須というわけではない）
  • メモリ： 32GB
  • ディスク： 500GB SSD x 1つだけ
  • NIC： 1Gbps を 1ポートだけ
• ネステッド ハイパーバイザ環境のベースになる物理サーバの ESXi も、vCenter に登録する。
  • これは、vCenter に登録したほうが ESXi / VM の管理をしやすいため。
• vCenter は vSAN クラスタ（vSAN データストア）の外に配置する。
  • vCenter を vSAN データストア上に配置することもできるが、
    まず vSAN そのものを勉強するためには vSAN 外にある方がよいと思うので。
• vCenter Server 6.7 U1 / ESXi 6.7 U1
  • せっかくなので最新版を利用する。

物理マシン ESXi / ネステッド ESXi の関係。

この環境では、物理マシンの ESXi 上の VM に ESXi をインストールしています。

前スクリーンショットの vCenter インベントリでのネステッド ESXi（Nest-ESXi）と

VM の関係を図示すると、下記のようになります。

• 物理マシン ESXi には、下記を配置します。
  • vCenter（仮想アプライアンスである VCSA を利用）
  • ESXi をインストールする VM（ESXi VM）3台
  • ESXi VM のテンプレート
• 物理マシン ESXi に配置している VM へのリソース割り当ては下記にしました。
  • vCenter: VCSA の「極小」（Tiny）スペック。vCPU: 2、メモリ: 10GB
  • ESXi VM: vCPU: 2、メモリ: 6GB、VMDK: 16GB。（これを 3VM作成）
• 物理マシン ESXi 1台は MGMT-Cluster に登録します。
  • Nest-ESXi の実体となる ESXi VM は、こちらのクラスタで見えます。
• Nest-ESXi のインストールは、だいたい下記のいずれかになるはずです。
  • 物理 ESXi のデータストアに格納した ISO ファイルを、
    ESXi VM の仮想 CD/DVD ドライブに接続してインストール。
  • PXE Boot によるネットワーク経由での Kickstart インストール。
• 物理マシン ESXi 側でインストールした Nest-ESXi 3台は、vSAN-Cluster に登録します。

ESXi VM はそれぞれ ESXi をインストールするか、

あらかじめ ESXi をインストールした VM をテンプレート（クローン元 VM）を利用します。

今回の ESXi VM では、下記のような設定をします。

• ゲスト OS の種類は「ESXi 6.5 以降」を選択。
• CPU で「ハードウェア アシストによる仮想化をゲスト OS に公開」のチェックを入れる。
• 起動オプション → ファームウェアは BIOS にする。

ストレージ（データストア / VMDK）の関係。

Nest-ESXi のローカルディスクで vSAN データストアを構成しますが、

その実体は、ESXi VM に接続された VMDK ファイルです。

（下図では Nest-ESXi が1台ですが、実際は 3台で vSAN データストアを構成します）

Nest-ESXi で vSAN 構成後にそのうえで VM （図の Nest-VM）を作成すると、

当然ながら、その VMDK もネストされることになります。

ネットワーク（vSwitch / ポートグループ / vNIC）の関係。

Nest-ESXi 上で VM（Nest-VM）を作成した場合、Nest-VM の vNIC では、

自身のものとは異なる MAC アドレス / VLAN の通信が発生します。

デフォルトの状態ではそのような通信ができないため、
物理マシン ESXi 側で、下記の設定をします。

• Nest-ESXi を接続するポートグループを追加します。
  • 今回は Nested-Trunk-Network という名前で作成。
  • シンプルに、標準仮想スイッチ（vSS）の、標準ポートグループで作成。
• 作成したポートグループで、無差別モードを許可する。
  • これで 自身の MAC アドレス以外の通信も受け取るようになる。
  • MAC アドレス変更 / 偽装転送 は、標準ポートグループでは許可されているので、そのまま。
• 作成したポートグループで、VLAN ID 4095 を設定する。
  • これで 物理 ESXi のポートグループで VLAN ID を付与したまま通すようになり、
    Nest-ESXi 側のポートグループで VLAN ID を付与できるようになります。

Nest-ESXi 側では、とくにネストしていることを意識することなく

ネットワークを構成します。

vSAN では VMkernel（vmk）ポートで vSAN トラフィックを有効にする必要がありますが、
これは Nest-ESXi 側だけで設定します。

物理 ESXi で作成したポートグループに、すべての ESXi VM の vNIC を接続します。

作成したポートグループでは、下記のように

無差別モードを有効化、VLAN ID 4095 を設定しています。

環境構築自体は、ネストであるかどうかにかかわらず、

一般的な vSphere Client（旧 HTML5 Client）や vSphere Web Client での操作となります。

また、ラボを頻繁に構築するようであれば PowerCLI などによる自動化もできます。

構築 Tips につづく・・・かもしれない