Did come across this on the forums and seems fairly ubiquitous insofar as reports.
If you recently:
i) upgraded to version 6.0 Update 1 for ESXi
ii) Running the latest VMware Tools for View Desktops
iii) But have an older view agent installed
Will see in the PCOIP logs (<drive letter>\ProgramData\VMware\VDM\logs
LVL:0 RC:0 EXTERN :svga_devtap ==> second render failed: 0xc0000008
LVL:0 RC:0 EXTERN :svga_devtap ==> Error: screen dma failed
LVL:0 RC:0 IMG_FRONTEND :flip_frame_buffer: General flip error [1 results for 1 displays]: [4001, 0]
LVL:0 RC:-500 IMG_FRONTEND :open_displays(): Flip error in open display first flip.
Upgrade your View agent to the latest version (issue above occurred for me in Horizon 6.2 so latest View agent there and i was up and running).
Couple of symptoms here:
i) Running ESXi 6.0
ii) Running with the maximum amount of RAM and vCPU count
This was an interesting one insofar it would only occur if if you had updated the VM’s to use above.
VM’s would upwards to an hour to boot.
Upgrade to ESXi 6.0 patch 1 (build 2809209)
https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2127782&sliceId=1&docTypeID=DT_KB_1_1&dialogID=32536068&stateId=0 0 32534952
In terms of actual detail never got the time to truly ascertain why the slowness occurred for me – occurred during the splash screen phase.
Quite simple this one – thought picture would say a 1000 words and all that.
On the left hand side is the configuration from within the MSTSC GUI, the middle is obviously command-line and on the right is if you need to configure within an .RDP file
Recently had an issue starting one of my VM’s up in the lab. Turns out one of the disks had a lock in play.
A lock on the
.vmdk file can prevent a virtual machine from starting. However, since virtual machine disk files can be configured for use with any virtual machine, the file may be locked by another virtual machine that is currently running, in my case i had it running on a cloned box.
So quick scout on the web , found this command and resulted in me being able to determine:
# egrep -i DISKNAME.vmdk /vmfs/volumes/*/*/*.vmx
ESXi VM hardware versions 10 and 11 include a SATA controller for CD/DVD by default. If the SATA and SCSI controller are present on the PVS Target Device, the target will fail to boot. PVS relies on the SCSI controller, SATA is the only one that can be removed. To resolve this issue, change the Virtual Device Node for the CD/DVD Media from SATA to IDE and remove the SATA controller. This must be performed prior to installing the operating system.
To get around this do the following:
i) While creating a new VM from the vSphere web client, under Edit Settings > Customize hardware > Virtual Hardware, change the Virtual Device Node from SATA to IDE for CD/DVD Media.
ii) After selecting the corresponding IDE radio Button, the Remove option for New SATA Controller becomes active. Get rid of it by clicking the “X” at the right hand side of the New SATA controller line
Note: If the Virtual Machine is already created, the mentioned steps should be performed by going to Edit Settings -> Virtual hardware in the vSphere Web Client.
Found this type courtesy of http://support.citrix.com/article/CTX200969 – which also provided info on other issues relating to vSphere 6 and citrix products
Diagnostics information can be sent to a remote host instead, or in addition to the local store. This information is useful for troubleshooting host failures. Here is how to configure from the command prompt in 7 easy steps:
To configure hosts for Netdump with the command line, perform the following steps:
1.Open a console session to the host or connect remotely via SSH.
2.Review the current settings:
esxcli system coredump network get
3.Specify the outbound interface, IP address, and UDP port of the remote collector:
esxcli system coredump network set –interface-name –server-ipv4 –server-port PortNumber
4.Enable the configuration:
esxcli system coredump network set –enable true
5.Check the functionality of the collector server:
esxcli system coredump network check
6.Output in case of success should be as follows:
Verified the configured netdump server is running
7.Save the configuration permanently: