I am trying to deploy VMware APP Volume 3.0 in lab and trying to integrate App Volume with vCenter.
I don't have any firewall in between both vcenter and app volume server are in same IP Address Range
ping is working fine between app volume server and vCenter / ESXi host
Error:
Unable to connect to 192.168.109.200: Connection Failed!
This blog provides details on troubleshooting an App Volumes environment using the App Volumes logs.
Here are the log files that you can look at in order to troubleshoot:
The App Volumes Manager log files are:
These log files are located at C:\Program Files(x86)\CloudVolumes\Manager\Log on the App Volumes Manager server.
Here is the details about Production and SVManager logs:
production.log :
Here is a description of the main modules to search for in the production.log file.
svmanager_server.log :
The svmanager_server.log file captures App Volumes Manager server actions. You can correlate these actions with the Agent log files by checking time stamps from both the server and agent logs. The svmanager_server.log file also captures information relating to the App Volumes infrastructure.
The App Volumes Agent log files are:
Locations for Agent log files :
In releases earlier than App Volumes 2.9, the App Volumes Agent logs are located at C:\Windows on the Agent machines. The svcapture.log file is also located at C:\Windows , on the capture machine.
For App Volumes 2.9 and later, the Agent log locations have changed.
The svservice.logfile is located at C:\Program Files (x86)\CloudVolumesAgent\Logs on the Agent machines.
The svcapture.log file is located atC:\Program Files (x86)\CloudVolumesAgent\Logs on the capture machine.
SvService is the service responsible for communication between the App Volumes Agent and the App Volumes Manager, including the preparation of volumes, the running of post-attach scripts, refresh of variables, and registration of fonts. The log tracks this communication.
The SvCaptureservice performs provisioning and editing functions during application capture, such as generating policy files and metadata. The SvCapturereports this information to the App Volumes Agent and App Volumes Manager. The log tracks this activity and is available only on the capture machine.
SvDriver is a policy-driven driver file responsible for the virtualization of volume contents into the desktop OS. The policy file snapvol.cfg controls the files, directories, registry keys, and processes that are virtualized during application capture on each volume. The log tracks this activity.
IE11 is on my VMs as the standard browser. We still have legacy apps that need IE8, so, I managed to package it up with ThinApp using Peter Bjork's very helpful blog. However, I have run into a hiccup with ThinDirect. As a test, I entered 1 URL into ThinDirect to be repointed to my IE8 package (see screenshot #1). I go on my test VM, I open IE11, I try to go to the page, and sure enough, it starts to go to IE8 ThinApp. But then it just loops over and over again with screenshot #2. Anyone ever see this?
Just trying to understand DLR function. This is my understanding please correct me if i am wrong.
If we have multiple Vxlan hosted on one Esxi host we can do routing on Exsi host itself without even leaving hypervisor ,kind of inter vlan routing . When these VM's are hosted across multiple Esxi host we need to configure VTEP's to communicate.
is that mandatory to turn on DLR for VTEP to VTEP communication ? or that is done with Edge services. Any example would be appreciated.Another question I have VTEP IP pool is that going to be part of transport vlan ? I could not get any example which also talks about physical network stuff being configured on Vmware virtualization.
AJ
Hi,
I am new to this so asking. Might be you all knowing about this. please help
I have captured one application and If I look at HKEY_LOCAL_MACHINE.txt file there is one registry entry like.
HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{0E3DF841-C6D4-468C-AF16-DB62D646E791}\LocalServer32
Value=
REG_SZ~%ProgramFilesDir~0016\EnCorr\BIN\encorr.exe#2300
in REG_SZ it's %ProgramFilesDir~0016 but it should be %ProgramFilesDir%.
May I please know that ~0016 represents to % sign or it's having difference significance.
Appreciate your help.
Thanks,
Rushikesh
I see Nice Documentation @ below URL for Cloud Native Apps / Docker
But when I visit labs.hol.vmware.com (click on All Labs, search, I dont find 1630 Lab there for hands on)
Any idea how to access 1630
Hi ,
I need your help to set ratio for 1:1 processor mapping virtual to physical cores, this ratio will not be vaiolated by deploying any new VM or migrating VMs too.How can I set this limit?
Thank you
Hi,
I am new to vROPS. We are trying to get the total cpu demand in the cluster level , but the result is Zero GHZ. I used this metric
sum($This object:CPU Usage|Demand (MHz))/1000 Many thanks |
Hi
After upgrade from vRA 7.0.0 to vRA 7.0.1 I’m not the owner of some of my machine.
On the machine “item” I can see my user name as owner but I can't destroy the server. Also I get a new option to “Change Lease” but when I try to change the lease time I get “You are not entitled to perform “Change Lease” on item….”
What the hack?
The Upgrade process was not smooth, I had to unregister vRB after vRA upgrade. Also – I didn’t upgrade vRO yet.
I wish to automate and script the vmware environment. Can somebody please tell the command for dynamically adding memory, CPU and storage. Set-VM is not letting me do it ... Please help
Come and check this awesome demo video created by Bulent ToluVMware Horizon 6 - Linux VDI ile vGPU - YouTube . Check this blog post as well Horizon 6–– vGPU with RHEL 7.1 | BULENT TOLU
I had a problem where one of the disks ran out of space and halted the vm.
I was able to recover from that but snapshots seemed messed up and when I attempted to create a new snapshot then remove snapshot/consolidate everything went wrong from there.
I had two virtual machine drives connected and one of them was the one which ran out of space. I also seemed to lose the snapshots for disk #1 in the process.
Now the machine will not boot right and says the "unable to mount root fs"
I tried mounting the partition on another machine but it cannot recognize the partition.
If I could just get access to files on disk #1 I'd be happy. Since disk #2 is basically a copy of disk #1 files.
DISK #1
/vmfs/volumes/5443e52a-eea8b245-240a-e03f4947841b/NAS Server # ls -l
total 197143568
-rw------- 1 root root 2147483648 Apr 10 08:29 NAS Server-32c58521.vswp
-rw-r--r-- 1 root root 13 Apr 10 07:13 NAS Server-aux.xml
-rw------- 1 root root 271656681472 Apr 10 08:30 NAS Server-flat.vmdk
-rw------- 1 root root 8684 Apr 10 08:30 NAS Server.nvram
-rw------- 1 root root 499 Apr 10 08:29 NAS Server.vmdk
-rw-r--r-- 1 root root 43 Apr 10 07:33 NAS Server.vmsd
-rwxr-xr-x 1 root root 2948 Apr 10 08:29 NAS Server.vmx
-rw------- 1 root root 0 Apr 10 08:29 NAS Server.vmx.lck
-rw-r--r-- 1 root root 265 Aug 12 2015 NAS Server.vmxf
-rwxr-xr-x 1 root root 2948 Apr 10 08:29 NAS Server.vmx~
-rw------- 1 root root 1933312 Apr 10 06:43 vmmcores-1.gz
-rw-r--r-- 1 root root 119134 Apr 10 07:34 vmware-10.log
-rw-r--r-- 1 root root 165321 Apr 10 07:35 vmware-11.log
-rw-r--r-- 1 root root 160684 Apr 10 07:50 vmware-12.log
-rw-r--r-- 1 root root 47173 Apr 10 07:16 vmware-7.log
-rw-r--r-- 1 root root 160180 Apr 10 07:19 vmware-8.log
-rw-r--r-- 1 root root 160606 Apr 10 07:32 vmware-9.log
-rw-r--r-- 1 root root 139712 Apr 10 08:31 vmware.log
-rw------- 1 root root 117440512 Apr 10 08:29 vmx-NAS Server-851805473-1.vswp
DISK #2
/vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS # ls
NAS_2-000001-delta.vmdk NAS_2-000002-delta.vmdk NAS_2-000003-delta.vmdk NAS_2-flat.vmdk
NAS_2-000001.vmdk NAS_2-000002.vmdk NAS_2-000003.vmdk NAS_2.vmdk
/vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS # vmkfstools -e NAS_2.vmdk
Disk chain is consistent.
/vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS # vmkfstools -e NAS_2-000001-delta.vmdk
Failed to open disk link /vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS/NAS_2-000001-delta.vmdk :The file specified is not a virtual disk (15)Disk chain is not consistent : The file specified is not a virtual disk (15)
/vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS # vmkfstools -e NAS_2-000002-delta.vmdk
Failed to open disk link /vmfs/volumes/5308d36e-55ca274e-d7ba-e03f4947841b/NAS/NAS_2-000002-delta.vmdk :The file specified is not a virtual disk (15)Disk chain is not consistent : The file specified is not a virtual disk (15)
Hello i think i have very big problem.
Today when i try to start my server it stucks at
Starting up services
Running swapob jd start
The problem is there over 10 minutes. Can you please tell me what can i do now, why this does not want to start?
Thanks in advance!
Hello dear community.
Today when i try to start my server in ALT+F1 i see this message:
Error: More then one exception specification for tardisk /tardisks/s.v00
Error: Ignorin /etc/vmware/secpolicy/tardisks/VMware-sys
Message handler 1 failed: Busy
Invalind config: stat failed Input/output error
What is this error ? IS this releated to any of my hardisks? I am so worried?
How can i fix this, please help!
On my ESXi 6 host I am currently sending a USB external drive to a VM for backups, this drive is 2TB in size and I have had no problems with it at all. Recently, purchased a 5TB drive to replace it since my backups are getting quite sizeable, I was shocked when I found out that the passthrough in ESXi is not working for this drive. I was hoping to get some help.
The disk that works fine; details
[root@localhost:~] lsusb -vvv
Bus 002 Device 013: ID 4971:ce17 SimpleTech 1TB SimpleDrive II USB External Hard Drive
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x4971 SimpleTech
idProduct 0xce17 1TB SimpleDrive II USB External Hard Drive
bcdDevice 0.00
iManufacturer 10 HitachiGST
iProduct 11 SimpleDrive USB 2.0
iSerial 3 D20102500436
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 USB Mass Storage
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 6 MSC Bulk-Only Transfer
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
The disk that is detected but cannot be attached to VM
[root@localhost:~] lsusb -vvv
Bus 002 Device 036: ID 0480:d011 Toshiba America Info. Systems, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0480 Toshiba America Info. Systems, Inc.
idProduct 0xd011
bcdDevice 3.16
iManufacturer 1 TOSHIBA
iProduct 2 External USB 3.0
iSerial 3 20151124010354
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 42
bNumDeviceCaps 3
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {151ca73c-b946-4fd1-a3f8-925170fb369c}
Device Status: 0x0001
Self Powered
2016-03-05T06:35:05Z usbarb[1027049]: VTHREAD initialize main thread 3 "usbArb" pid 1027049
2016-03-05T06:35:05Z usbarb[1027049]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2016-03-05T06:35:05Z usbarb[1027049]: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.
2016-03-05T06:35:05Z usbarb[1027049]: DictionaryLoad: Cannot open file "//.vmware/config": No such file or directory.
2016-03-05T06:35:05Z usbarb[1027049]: PREF Optional preferences file not found at //.vmware/config. Using default values.
2016-03-05T06:35:05Z usbarb[1027049]: PREF Disabling user preferences because disableUserPreferences is set.
2016-03-05T06:35:05Z usbarb[1027049]: PREF Failed to load user preferences.
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- GLOBAL SETTINGS /usr/lib/vmware/settings
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- NON PERSISTENT
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- USER PREFERENCES
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- USER DEFAULTS //.vmware/config
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- HOST DEFAULTS /etc/vmware/config
2016-03-05T06:35:05Z usbarb[1027049]: DICT libdir = "/usr/lib/vmware"
2016-03-05T06:35:05Z usbarb[1027049]: DICT authd.proxy.nfc = "vmware-hostd:ha-nfc"
2016-03-05T06:35:05Z usbarb[1027049]: DICT authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
2016-03-05T06:35:05Z usbarb[1027049]: DICT authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
2016-03-05T06:35:05Z usbarb[1027049]: DICT authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
2016-03-05T06:35:05Z usbarb[1027049]: DICT authd.fullpath = "/sbin/authd"
2016-03-05T06:35:05Z usbarb[1027049]: DICT --- SITE DEFAULTS /usr/lib/vmware/config
2016-03-05T06:35:05Z usbarb[1027049]: USBArb: Error in '/etc/vmware/usbarb.rules' at line 1:0, '[' or '{' expected near end of file.
2016-03-05T06:35:05Z usbarb[1027049]: VMware USB Arbitration Service Version 13.1.14
2016-03-05T06:35:05Z usbarb[1027049]: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.
2016-03-05T06:35:05Z usbarb[1027049]: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket
2016-03-05T06:35:05Z usbarb[1027049]: SOCKET connect failed, error 2: No such file or directory
2016-03-05T06:35:05Z usbarb[1027049]: USBArb: Failed to connect to the existing arbitrator.
## after hostd restart and vpxa
2016-03-05T06:35:34Z usbarb[1027049]: USBArb: UsbArbPipeConnected: Connected to client, socket:12
2016-03-05T06:35:34Z usbarb[1027049]: USBArb: Client 1027130 connected (version: 6)
What I have tried; without success
# /etc/init.d/usbarbitrator stop
# /etc/init.d/usbarbitrator start
# /etc/init.d/hostd restart
# /etc/init.d/vpxa restart
Any help is greatly appreciated.
Hiya,
I haveen strugling with getting SSL certificates installed for a couple of days now, it always seem to fail on the vpxd_servicecfg command.
I have followed tuts like : https://myvirtualife.net/2014/04/01/how-to-replace-default-vcsa-5-5-certificates-with-microsoft-ca-signed-certificates/
There are more out there, but they are all simular to each other. I follow it to the letter, but all i get is:
vcenter:/ssl/vCenterSSO # /usr/sbin/vpxd_servicecfg certificate change chain.pem rui.key
VC_CFG_RESULT=650
The only thing i can emagine is that there is a difference in vcenter 5.5 and 6.0, but other then that i wouldnt know how to fix this.
Can anyone help?
Regards.
Hi Guys
im looking for a way to find all vm machines in my vcenter that is powered off for at least 180 days using info that can take last action date from "tasks and events"
how can i accomplish that using powercli script?
Thanks!
Since upgrading to vsan 6.2, I am seeing a major increase in read cache misses and write latency. Also, the physical disks show that the flash disks have 0 used capacity. This is a hybrid production environment. Does anyone have any thoughts on this?
こんにちは。 VMware の松田です。
今回は、Horizon Air で障害発生時の対処方法について紹介します。
Horizon Air で問題が発生したときには、大きく分けて 2 つの問題発生ポイントがあります。
1. Horizon Air の管理コンポーネントなど、システム全体で問題が発生している
2. 特定の仮想デスクトップやユーザーで問題が発生している
Horizon Air の管理コンポーネントで問題が発生している場合には、ユーザーからは対処が難しい場合がほとんどです。
そのため、管理ポータルなどでエラーが発生していたり、意図したとおりに動作しない場合には、まずは VMware のサポートに連絡して対応が必要です。
サポート窓口
http://info.vmware.com/content/apac_jp_co_support_contact_g
この場合には、以下の情報を事前に用意しておくと、その後の問い合わせがスムーズに行えます。
// 事前に用意する情報
- サービス ID もしくは利用されている会社名
- 状況が確認できるスクリーンショット
この場合には、まずは問題が起こっている仮想デスクトップやユーザーの特定を行います。
特定方法は、Horizon Air の管理ポータルからアクティビティ ログを採取して確認します。
※ ブラウザの言語は英語で取得した方が、文字化けなどなくログを取得できます。
※ アクティビティ ログに接続した形跡が残っていない場合には、そもそも接続元と Horizon Air との通信に問題がある可能性があります。
特定のユーザーに問題がある場合には、AD 上のユーザーに問題がある可能性があります。
まずは AD 観点で調査を行い、その後、Horizon Air の管理ポータルでマッピング情報を確認してください。
特定の仮想デスクトップに接続ができないなどの問題があれば、まずは Horizon Air の管理ポータルからエージェントの状態を確認します。
エージェントの状態が "Unknown" などになっていれば、まずは仮想デスクトップをリセットして、回復するかどうか確認しましょう。
それでも、事象が解消しない場合には、Horizon Air 管理コンソールを利用して直接該当の仮想デスクトップにアクセスして状況を確認します。
管理コンソールで仮想デスクトップに接続すると、コンソール画面を見ることができます。
この際、ログイン画面が表示されずに Windows のロゴやブート画面で止まっている場合があります。
この場合には、そもそも Windows が異常な状態になっている可能性が高く、復旧が難しい状況です。
仮想デスクトップの再作成の可否についてまずは検討してください。どうしても該当の仮想デスクトップが
作り直しが難しいような場合には、ひとまずサポートまでご相談ください。
通常の接続はできず、管理コンソールのみからアクセスできる場合には、ログなどからの調査が必要となります。
ただし、問題の発生原因は Horizon Air 関連のモジュールだけではなく Windows 自体の影響の考えられます。
- DaaSAgent のログの採取
- View Agent のログバンドルの採取
- Sysprep のログの採取
- グループポリシーの適用状況確認ログの採取
例: Windows 7 64bit の仮想デスクトップ環境上でのログ採取例
1. 管理コンソールからローカル アドミニストレーターでログインします。
2. 以下のファイルを採取します。
C:\Program Files (x86)\VMware\VMware DaaS Agent\service\logs\DaaSAgent
3. 以下のバッチファイルを実行しデスクトップに作成されたログバンドルを採取します。
C:\Program Files\VMware View\Agent\DCT\support.bat
4. "C:\Windows\Panther" と "C:\Windows\System32\sysprep\Panther" から "setupact.log" と "setuperr.log" を採取します。
5. 管理者権限で以下のコマンドを実行し、作成された HTML ファイルを採取します。
> gpresult /H GPO_export.html
- View Client のログバンドルの採取
例: Windows 7 64bit から接続している際の接続端末上でのログの採取
1. 以下のバッチファイルを実行しデスクトップに作成されたログバンドルを採取します。
C:\Program Files (x86)\VMware\VMware Horizon View Client\DCT\support.bat
ログを確認しても明確に原因がわからずお困りの際には、VMware へ相談しましょう。
サポート窓口
http://info.vmware.com/content/apac_jp_co_support_contact_g
なお、サポート依頼を行う際には以下の情報を採取していただくとスムーズに調査が開始できます。
- 事象の発生日時および発生頻度
- 事象の発生対象のユーザー名/仮想デスクトップ名
- 事象が確認できるスクリーンショット
- Horizon Air の管理ポータルから採取されたアクティビティ ログ
- 上記 3 のログファイル一式
- 利用しているブラウザとそのバージョン
また動画や Windows であれば Windows 標準の問題ステップ記録ツールなどを利用して事象を確認する操作など
連携いただけるとさらに有効な情報となります。
(参考情報)
VMware Horizon View のログと診断情報の収集 (2032715)
https://kb.vmware.com/kb/2032715
VMware View のログ ファイルの場所 (2035956)
https://kb.vmware.com/kb/2035956
VMware View コンポーネントでログ ファイルの動作を変更する (2087022)
https://kb.vmware.com/kb/2087022
sysprep ログ ファイルの場所 (2094341)
https://kb.vmware.com/kb/2094341
DaaS Agent log file (2100062)
http://kb.vmware.com/kb/2100062
ゲスト OS 内の VMware Tools のデバッグ ログを有効にする (2081832)
http://kb.vmware.com/kb/2081832
Enabling ThinPrint logging in VMware View Manager (2004001)
http://kb.vmware.com/kb/2004001
Gpresult
https://technet.microsoft.com/ja-jp/library/cc733160(v=ws.10).aspx
問題ステップ記録ツールの使用方法
http://windows.microsoft.com/ja-jp/windows7/how-do-i-use-problem-steps-recorder
【免責事項】
本ブログに記載された内容は情報の提供のみを目的としたもので、正式な VMware のテストやレビューを受けておりません。
内容についてできる限り正確を期すよう努めてはおりますが、いかなる明示または暗黙の保証も責任も負いかねます。
本ブログの情報は、使用先の責任において使用されるべきものであることを、あらかじめご了承ください。
このブログに記載された製品の仕様ならびに動作に関しては、各社ともにこれらを予告なく改変する場合があります。
非営利目的の個人利用の場合において、自由に使用してもかまいませんが、営利目的の使用は禁止させていただきます。
I'm owning Workstation 12 Pro for about half a year now. Since then it hasn't once been able to run my development environment in a VM flawlessly.
Whenever I install Microsoft Visual Studio 2015 in a Windows 10/64 VM, the Workstation graphics driver crashes and the VM then hangs - and incidentally my host's graphics driver crashes, too. Only a reboot can then regain me access to my host machine.
I'm running Workstation on three different hosts, so it surely is a Workstation error.
Moreover, playing audio in the guest is making the guest significantly lag, too.
By now I have already wasted three support tickets on these problems. They only get temporarily solved and then re-occur with the next update to Windows 10 or Visual Studio 2015.
VMware is showing a strong degradation in product quality. Apparently, VMware does not have the resources to create a good product anymore.
In Germany we call such enduring lack of quality an "Armutszeugnis". The dictionary calls it an evidence of incapacity.
My next host installation will use Hyper-V. I'm through with Workstation now. Waiting for half a year to get critical problems fixed is not what I'm paying for.