Windows 10: How to enable AutoStart of VMs on VMware ESXi and Workstation

​

If you are an administrator, you would want the VMs of your organization to start automatically so as not to hinder production and not to start them manually. To accommodate this privilege, you will have to enable AutoStart of VMs on VMware ESXi and Workstation. In this post, we are going to see how you can […]

This article How to enable AutoStart of VMs on VMware ESXi and Workstation first appeared on TheWindowsClub.com.

read more...

 

Esxi - Linux VM itself running VMWare Workstation

Hi there
@johnnyZ

Here's a screenshot of an Arch Linux system running as a VM on ESXI 5.7 (Esxi is the HOST OS) with the arch linux kernel at 5.3.11 and this VM running VMWare workstation -- so in theory your VM's could easily use any VMWare VM images from USB devices while the ESXI system could be run from a USB drive.

The response time of the VMWare workstation VM on the Esxi Host with the arch linux VM isn't too bad at all -- the top level VM (i.e the VM installed under the ESXI response time blows away any of the other Virtual machine options I've tried. It's a bit fiffly though to get it working -- I'm still trying a few experiments --but the POC (proof of concept) that you CAN run VMWARE workstation on a VM created under ESXi ) works just OK -- easiest is to use Arch Linux for testing as a simple command yay vmware-workstation will do all the hard bits for you !!!





Now I'm going to try some Windows VM's -- should also be able to get Windows VM with HYPER-V working too on Esxi although why I would need that I don't know -- maybe to try it just because it could be possible.


Once I'm satisfied and got all the glitches out I'll do a full blown tutorial.

One thing having trouble with --RDP from a windows laptop to the Esxi VM allows me to logon but then just shows blank screen even though I've installed xrdp on the main host and started the service -- I might need to connect / export the screen -- need to do more research. The web interface works OK though although resolution 1920 X 1080 is missing -- not a showstopper - especially if you have larger 4K monitors available and you use the VM as a server.

Seems VMWare with Esxi have finally got their act together --this stuff could work big time !!! I like the idea of the main HYPERVISOR being a miniscule OS. I think also though the default networking configuration must be bridged / external as the ifconfig output from the (top level) VM is 192.168.1.8 which is a physical address obviously rather than a virtual subnet etc.

Samba etc works on it (the top level VM under ESXI --100% connection to and from rest of Lan

Hundur -- this machine (Windows 10 on separate laptop, Hestur is a separate NAS Linux machine and Wulf is a VM under Esxi running on another physical machine with Esxi as the Host system Interconnection all ways from the 3 systems






I haven't tested the 2nd level VM's created on it with VMWare workstation yet that's a story for another day -- pub time now !!!!-- Done enough computing for today.

Cheers
jimbo

 

Windows 10 crashing when powering on VM on VMware workstation

Hi DaveM121,

My issue is windows 10 crashing when i power on VM on VMware workstation.

While we troubleshooting this issue, i have installed Virtualbox to create VM to create VMs as an alternate solution

However when we enabled driver verifier for 1st time, virtualbox driver caused BSOD during reboot which was initiated to get verifier settings into effect. As you informed, this crash was caused due to virtualbox driver hence i uninstalled it.

I have again enabled driver verifier for 2nd time and able to reproduce crash during powering ON vm on VMware workstation. It is caused by vmx86.sys which is relevant to VMware workstation hence I would need your expert advise on this.

am attaching minidump caused by vmx86.sys, kindly check and advise.

Microsoft OneDrive

Please note that I have disabled driver verifier after collecting crash

 

VMWare VM in Hpyer V


Hi there

OK not natively - but you can run a W10 VM with HYPER-V enabled ON THE VM !! and then run a VM on that.

Actually if you are using an SSD or better more than 1 SSD for storing the VM's the response isn't actually as bad as you might think !!! - ensure plenty of RAM and ensure the HOST (Physical machine) isn't too busy. Suggest you have an i5 CPU at least too.

To avoid confusion here

1) W10 HOST - HYPER-V NOT enabled. VMware workstation running
2) W10 VM created on VMWARE with HYPER-V enabled on this VM
3) Create VM under HYPER-V on the W10 VM created in step 2.

This type of multi-level VM works better though on HOST Linux machines as the Host OS is much leaner so almost ZERO overhead consumed by the host. Esxi is a great tool for this if you want to play around with this type of stuff.

A while ago I was using Esxi to create a Virtual W2k3 Server which had two W7 VM's and an XP VM running on it. Performance was fine - and that was in the days before SSD's were even thought of - much less being affordable.

I know slightly OT but I enclose the reference here for people who might be interested in this sort of stuff. Esxi is FREE too.

Free VMware vSphere Hypervisor, Free Virtualization (ESXi) | VMware United Kingdom

Note though Esxi can be quite picky with hardware - google "White box" for hardware Esxi likes - and it's really picky over the network adapter(s) that work on it-- INTEL PRO Nic's always seems to work in my experience on pretty well any OS.

@Kari - I think running a Windows VM on this and then running a VM on HYPER-V on this Windows VM would be interesting. The nice thing about Esxi is that 99.9% of resources are passed to the VM's -- so this should work almost indistinguishably from a HOST machine running HYPER-V.

I'll hope tp have a go with this later -- I've got some spare time this week - and plenty of spare machine "Horse Power". My main worry will be getting the Nic to work --I think I've still got a usable Intel PRO 100/1000 card somewhere.

Cheers
jimbo