VMware Workstation 17

JGToy said:

Is it there a way to resume(wake-up) a vm guest programmatically?

Click to expand...

OAT said:

A VM is self-contained.
The only way would be to create a shortcut pointing to the machine .vmx file.
It would load the VM in the state it was last active and wake it up if needed.

Click to expand...

OAT said:

A VM is self-contained.
The only way would be to create a shortcut pointing to the machine .vmx file.
It would load the VM in the state it was last active and wake it up if needed.

Click to expand...

OAT said:

You are very limited with what you can do from outside the VM.
Those are the command line switches, not much there to help you.

https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-7369457F-FE1D-40FE-97B6-B29CA4916CCD.html

Another way would be to modify the .vmx file for that VM using notepad and adding the line:

suspend. disabled = "TRUE"

I don't know if that serves your purpose or not but it prevents it from going to sleep.

Click to expand...

JGToy said:

@OAT

First, that can be a typo but [suspend. disabled = "TRUE"] cannot have the space between the dot and disabled, it will give you vmx corrupted message.

But, this idea of yours took me to another level, with Suspend disabled the VM Guest goes into normal sleep mode and that is the solution because TS then can wake it up and creates the backup without any hiccups.

How's that? Indirectly, you gave me the way out of my problem.

Thank you again.

Click to expand...

OAT said:

The formatting put an extra space, it is of course: suspend.disabled

Click to expand...

jimbo45 said:

@OAT
@JGToy

The problem isn't with the VM but the VM software running on the HOST -- A VM doesn't even need an account on the host machine if remote users can access it. Windows is essentially a single user system so if you logout even if the VM can run in background mode other users won't be able to access it.

Linux, and Windows server editions are multi-user systems and HYPER-V (Windows) or KVM (Linux) run a Hypervisor for the VM which is essentially "separate" from the Host OS system (which is why they are far more efficient than vmware player / workstation or virtual box which run under the user who starts the process).

VMware used at one time to have a VMserver which ran in the backgound so if a user logged off windows (not shut the system down BTW) users on the VM could still access it - but that option I think has long since gone.

However ANY VM will be unavailable if the host isn't available (powered off, crashed, sleeping etc).

Cheers
jimbo

Click to expand...

JGToy said:

Thanks...

I will be taking a close look into HYPER-V and see how's it goes!

Click to expand...

cereberus said:

Very much horses for courses. Hyper-V was designed for corporate systems for Windows server use and it is great for running Windows Pro (+) guests in enhanced mode.

However, it is not really designed to run non Windows OS guests and most (also Windows Home) will only run in basic mode which restricts certain aspects - main one being no audio.

Some Linux distros can run in enhanced mode with sound but can be tricky to setup (Kali is easiest I know).

Click to expand...

JGToy said:

Good thoughts!

Installed and testing... Up to now founded it very painful(perhaps my fault), I can't figure how exactly to maximize it without it taking the complete screen or being small(if not maximized).

Display Resolution is greyed out, but then I find out that disabling Enhanced Mode it works, but another things stop working.
I'm running it on Windows 10 Pro host with a Windows 11 Pro guest (both latest version/build), honestly, I haven't found it yet as a replacement to my VMware Workstation Pro 17(maybe to addict to it).

So, I will keep testing/trying and see where it will take me.

Click to expand...

OAT said:

I tested HyperV ,tested VirtualBox by Oracle (poor GUI) but settled on VMware.
My VMs are a mix bag of Linux & Windows.

Click to expand...