There are sometimes needs to run 32-bit VMware guest images on a 64-bit host. This is possible, for example in VMware Workstation 15 Player. The out-of-the-box behavior, however, is that the Player passes trough the CPU information more or less as such. The result is that the guest sees a x86_64 processor, not a x86 processor. Frequently this detection is made by reading the CPUID 29th feature bit for so-called “long mode” (see: https://en.wikipedia.org/wiki/CPUID#EAX=80000001h:_Extended_Processor_Info_and_Feature_Bits ). As this is seen by the guest, it might think it needs to run 64-bit image (Player does not force this, it is a decision of the image itself). The long mode bit seen from Linux /proc/cpuinfo :
UPDATE 2022-04-23: It seems WhatsApp has broken this functionality with its recent updates. Rest is kept for posterity.
We have arrived to the last part of our ESXi WhatsApp saga. This blog post will tell a very cumbersome way of authorizing WhatsApp Web clients so you can enjoy the benefits of the application with you preferred computer and browser. Follow on!
This post is the last part (so far) in the 3-part series:
I am one of those people who are perfectly fine with old style dumb 3G phones. But unfortunately some people are reluctant to communicate nowadays with regular phone calls, SMS or IRC, so I basically need to keep Android at hand for running WhatsApp.
Recently I found a way to run Android x86 7.1 on VMware ESXi 6.7. After a lot of teeth grinding, I was able to get WhatsApp running inside it. And after enormous test and debug efforts, I was even able to authorize WhatsApp Web clients. But with a lot of hoop-running. Extremely lot.
I chose Android x86 7.1 because it seems to be working completely for my desired purposes without (much) graphical glitches. For example 8.1 has horrible glitches which actually make many parts of initial setup widgets invisible 😀 . I chose VMware ESXi 6.7 as host because it is of the most stable main branch of the hypervisor. Host hardware is Intel NUC8i7HVK with 32GB RAM.
This is the list of articles of the whole operation (split due to big amount of screenshots):
Recently I discovered I was running out of resources on my old VMware ESXi host, a Lenovo Thinkpad X201. Because of some security concerns I don’t keep swap enabled. Therefore I need lots of real RAM on the host machine. I also prefer small form factor (as the earlier laptop is).
After a while googling around I came across Zotac Zbox ID90. It’s one of those small form factor PC’s. Relevant specs are: CPU: Intel Core i7 3770T; Chipset: Intel H61 Express; Maximum memory: 16GB. Looks sufficient, I thought. There were, however 2 concerns. I had no idea whether the on-board LAN chips were compatible with ESXi 5.5.0. One would think that if the chipset was from Intel, it would include Intel LAN chips, right? Right? Another issue was support for Intel VT-d technology. There was no way to determine this from the specs provided. I tried asking Zotac support, but they were unable to assist. I don’t blame them, since the only real-world way to determine setup support is to actually install ESXi and see if DirectPath I/O is supported. I decided to take my chances and order Zbox ID90.