Change resolution of framebuffer/TTY

This post was originally published on this site


I use arch linux. I use vmware workstation player 15. I installed the vmware tools. In a desktop environement resizing works however in the default terminal before opening desktop (tty for example) the window is too small,

Whether in vmware’s display options I set a fixed resolution (like 3000X2000) or I choose to have same resolutions in my guest than my host (windows 10, I have a 3000×2000) doesn’t change anything the resolution reported by hwinfo –framebuffer are between 400×300 and 1152×864 none of them being big enough. I follow the guide set the framebuffer resolution and so i change the GRUB’s config file GRUB_GFXMODE to the max resolution I of the hwinfo –framebuffer list I do the reload of the config with grub-mkconfig and reboot but still the framebuffer’s size is never changin.

So my tty terminal is like 1/30 of my screen (incredibly annoying on a 3000×2000 13 inches screen) even tho once again resizing a desktop env when I launch XORG works.

AppVol Provisioning and Windows 10 1809 Install Errors

This post was originally published on this site



I am experiencing an issue where when attempting to install software while provisioning an appstack, the software will fail to install usually giving errors 110. For example, installing Adobe Reader DC failed with a two part error being the first message, “The system cannot open the device or file specified” and the second half being “Error 2755. Server returned unexpected error 110 attempting to install package C:ProgramDataAdobeSetup{AC76BA86-7AD7-1033-7B44-AC0F074E4100}AcroRead.msi.”


Oracle Java 8u201 comes up with the same except just generic install error 110.


Use cases that I have confirmed:

  • Appvolume 2.14/2.15 on 1809 while provisioning, software errors out
  • Appvolume 2.14/2.15 on 1809 while not provisioning, software installs absolutely fine
  • Appvolume 2.14/2.15 on 1803 while provisioning, software installs absolutely fine.


Because of the use case on 1809 failing, I need to provision my software within the 1803 computer for now. However sometimes it causes an issue – for example, SSMS 17.9.2 throws a licensing error if it is not provisioned on the gold image that the VDI pools use. So I wouldn’t be able to move those machines over to 1809 that require SSMS.


Any help is appreciated.



The distributed switch configuration on the host differs from that of the vCenter Server.

This post was originally published on this site

I get this error after I changed vmkernel portgroup VLAN id. Synchronization succeeded but the error stay. Can I just let this error stay? Because all works, vCenter can communicate with ESXi and VLAN id was changed successfully. Also, before VLAN id change communication between ESXi and vCenter goes through vDS uplink directly. Now, after VLAN id change, communication between ESXi and vCenter goes through VM 3rd party firewall, one interface connected to portgroup with trunk and uplink enabled in teaming. Other firewall interface connects with other portgroup also trunk and no uplink. Vmkernel portgroup get its input not form ESXi uplink, but instead from this other portgroup.   ESXi uplink —> portgroup (trunk) —> Mikrotik firewall uplink interface —- Mikrotik firewall internal virtual interface —> portgroup (trunk and no teaming uplink) —> vmkernel portgroup (related to Mikrotik virtual interface vlan id)  

Workstation 15 Pro intermittent freezes and crashes…

This post was originally published on this site

I have run workstation pro every day for the last 8 years.  This past update has been the most unstable of all of them.  Approximately every other day it freezes or crashes. 


Here is a typical chunk from the hostd-log after a crash:



2019-02-21T16:27:54.282-05:00 verbose hostd[07672] [Originator@6876 sub=Proxy Req 01522] The client closed the stream, not unexpectedly.

2019-02-21T16:27:54.290-05:00 verbose hostd[07784] [Originator@6876 sub=Proxy Req 01523] New proxy client <SSL(<io_obj p:0x06cc4370, h:1088, <TCP ‘ : 443’>, <TCP ‘ : 52178’>>)>

2019-02-21T16:27:54.291-05:00 verbose hostd[04676] [Originator@6876 sub=Proxy Req 01523] Resolved endpoint : [class Vmacore::Http::LocalServiceSpec:0x063e3ff8] _serverNamespace = /sdk action = Allow _port = 8307

2019-02-21T16:27:54.292-05:00 verbose hostd[21708] [Originator@6876 sub=Proxy Req 01523] Connected to localhost:8307 (/sdk) over <io_obj p:0x06cc45b0, h:1840, <TCP ‘::1 : 52179’>, <TCP ‘::1 : 8307’>>

2019-02-21T16:27:54.292-05:00 verbose hostd[07672] [Originator@6876 sub=AdapterServer opID=66f4c741 user=B] New request: target=’vmodl.query.PropertyCollector:ha-property-collector’, method=’waitForUpdatesEx’

2019-02-21T16:27:54.292-05:00 warning hostd[22468] [Originator@6876 sub=PropertyCollector opID=66f4c741 user=B] Session 52c3176c-59e4-2d27-ccd8-a4220e4335b5 has issued 3 concurrent blocking calls to the property collector. This is almost certainly an error in the logic of the client application.

2019-02-21T16:28:54.137-05:00 verbose hostd[21708] [Originator@6876 sub=AdapterServer opID=66f4c73f] IOException while sending the response: class Vmacore::IOException(System exception while trasmitting HTTP Response:

–> error id = 10053


Can anyone make heads or tails of what is going on here?

How to integrate awsdk with xamarin forms ?

This post was originally published on this site

Hi All,


I am trying to integrate awsdk with xamarin forms and getting lot of issues. Does anyone has any sample app. I Know vmware provide sample app for and Xamarin.ios , I have already tried both, both are working fine but when I try to integrate with xamarin forms then i am getting weird errors. SO if someone can provide me sample app then it will be very helpful, And sample should be provided by VMWARE team for XAMARIN.FORMS

NFS Data Store Will Not Mount on one Esxi Host

This post was originally published on this site

VMware ESWXI 6.5


I have 8 ESXI 6.5 hosts with many VM’s


I have NFS storage shared across all ESXI Hosts.


On one ESXI host it does not appear in the data store list.

When I go to the Dat store tab on my Datacenter I right click on the NFS storage and select Mount Datastore to Additional Hosts


The Esxi host show in the list I select it


I get this error


The specified key, name, or identifier “Datastore name’ already exists.


Any ideas?


I was thinking maybe a restart of the host but was hoping  command to try.


Thank you



ESXI 6.7 and Nvidia GPUs

This post was originally published on this site

Hi all,


Just a quick post as a work in progress…


Now I know the first reply to this post will be something like, “Well it’s unsupported hardware…”.  And I want to thank you in advance for all the help.


Ok, enough snarking for today.


I’ve noticed GPU passthrough issues with ESXI 6.7 when I had things working with 6.5+, and it seems others are seeing this as well.


I tried a couple different hosts with different NVIDIA cards (1030, 1080ti) and got the same results, after seeing the card initialize it would shut down/crash.  From that point forward the dreaded error code 43 on device properties.  I read many posts in the past that said 43 was an intentional disable in software when the driver detected it was running in a VM.  So it got me thinking…


I always made sure that I had “hypervisor.cpuid.v0=FALSE” in my config before ever passing through the video card.  But something changed in 6.7, or maybe Nvidia is looking for something else?


So I tried this:


Build a Windows10 VM (v1809)

don’t install vmware tools

install Chocolatey ( For easier install of teamviewer and nvidia drivers

install teamviewer via chocolatey (so I can connect remotely) *also I didn’t have usb hardware that I could passthrough

Disable svga(vmware vga) adapter “svga.present=FALSE” in vm advanced config

set “hypervisor.cpuid.v0=FALSE”

Add 2 PCI devices: 1080TI, Audio Device

boot while simultaneously crossing fingers.


Ok so the start was not pretty as Windows detects the video card and you need to reboot after initial install and you don’t have vmware tools installed so its a cringe-worthy moment.


but alas after the reboot and the driver took, the output looked stable.


after that I installed the latest nvidia drivers via chocolatey (geforce-game-ready-driver) and all seems ok.


Quick testing with Cinebench and Unigine Superposition seems to work fine with a 1080p medium windowed score of 18390.


So, what was it?  svga present? vmware tools?


If I had to guess it might be svga, because I saw a similar issue with Ubuntu 18.10.  I was having problems getting the nvidia driver to work in Ubuntu so on a fluke I disabled the svga device and voila!  Ubuntu 18.10 on a GPU!


I may install vmware tools and see if that makes a difference.


Anyways, I wanted to throw this out there for all the folks suffering with this issue.  If it’s Nvidias doing then I suppose it’ll just be a matter of time for them to find another way.



Compiling drivers for the Aquantia AQC 10GB NICs

This post was originally published on this site

Hi, I started this week an attempt of compiling the linux drivers for the AQC line of 10gb cards to the ESXi. This would allow ESXi to be more functional on hardware such as the Mac Mini.


I downloaded the 32 bit CentOS 5.6 and the 6.7U1 toolchain, and it is looking promising. I still get a lot of errors, but I guess they can be solved.

There’s one thing, however, that I am failing to understand. On the AQC drivers, there are references to the `struct page` and to the `count` member of this structure.

However, on the mm.h file distributed on the source code from vmware, we learn that the structure page is actually empy:



#if defined(__VMKLNX__)


*  struct page – page handle structure


*  ESX Deviation Notes:                   

*  As we don’t support page handle, this should be an opaque structure. In vmklinux

*  a page handle represents the actual page number.

*  Such an handle should not be deferenced nor used in any form of pointer

*  arithmetic to obtain the page descriptor to any adjacent page. The pointer

*  should be treated as an opague handle and should only be used as argument to

*  other functions.



/* _VMKLNX_CODECHECK_: page */

struct page {



Is there an approach to go around this, or is this a dead end?

VCSA 6.0 -> 6.5 CLI Upgrade Fails at 58% with Vmware VirtualCenter failed firstboot.

This post was originally published on this site

We have a 6.0 vCenter Server Appliance with two external PSC [all build 9448190 / 6.0 Update 3h] we are attempting to upgrade to 6.5 U2e build 11347054.


We’ve been completely unsuccessful trying to use the GUI updater, as for some unknown reason the GUI upgrader will not connect to the vCenter/PSC during the initial connection in Stage 1.


However, with the CLI upgrader using a .JSON file, we’ve upgraded the PSCs (two external PSCs) without issue.


The vCenter Server Appliance, however, fails to upgrade with an error at 58%:


Progress: 58% Starting VMware vCenter Server…




     Problem Id: install.vpxd.action.failed

     Component key: vpxd



          Vmware VirtualCenter failed firstboot.

          An error occurred while invoking external command : ‘Command: [‘/usr/sbin/vpxd’, ‘-L’] Strerr: ‘


     Resolution: Please search for these symptoms in the VMware Knowledge Base…..

     vCSACliInstallLogger – DEBUG – Running command on vm [new vCenter name]: /bin/bash –login -c ‘ls `install-parameter` /system-data/’

     vCSACliInstallLogger – DEBUG – Running command on vm [new vCenter name]: /bin/bash –login -c ‘/opt/vmware/bin/python `install-parameter` /system-data/’

     vCSACliInstallLogger – ERROR – Fail to revert the target vm IP address: Failed to run and wait for command in guest with error ‘Command ‘[u’/opt/vmware/bin/python’, u’`install-parameter`/system-data/’]’ exited with non-zero status 1′


We were able to find a KB with the ‘Command: [‘/usr/sbin/vpxd’, ‘-L’] Strerr: ‘ issue listed, and it seems to refer to duplicate vDS and vDPG names.  However we were not able to find any dupes.


(KB 2147547 for the vDS / vDPG issue: VMware Knowledge Base and a related one showing how to connect to postgres VMware Knowledge Base KB 2147285.)


There is only one additional issue seen in the vcsa-installer.log.  We see a message “Failed normalizing ip: [FQDN of the vCenter being upgraded


Does anyone have any ideas on this one?