VMware Communities
KirkA
Contributor
Contributor
Jump to solution

Orphaned VmWare Workstation Guest

I am Using Vm Workstation 7.1.3 build-324285.  My host OS is Windows Vista Business 64bit.  I Scheduled the start of a VmWorkstation Guest using the AT command as follow:

At 06:00 “C:\Users\Kirk\vm_win_xp_pro.bat”   The bat file contains:

**********************************************************************

cd "c:\Program Files (x86)\VMware\VMware Workstation"

vmrun start "C:\Vmware\Windows XP Professional\Windows XP Professional.vmx"

**********************************************************************

If I log into the Vista host with my user id that has administrator rights and issue the vmrun list command I get the following:

###################################################

C:\Program Files (x86)\VMware\VMware Workstation>vmrun list

Total running VMs: 0

###################################################

I used task manager and I can see the virtual machine’s processes running.

I created a batch file with the following contents:

**********************************************************************

cd "c:\Program Files (x86)\VMware\VMware Workstation"

vmrun list >>k_bat.log

**********************************************************************

The output of the k_bat.log is as follows:

###################################################

Total running VMs: 1

C:\Vmware\ Windows XP Professional\Windows XP Professional.vmx

###################################################

Is there a way for me to actually log into this guest that was started or is it unreachable?

How can I schedule the start of the workstation guest and be able to use it when I log into the Windows Vista Business Host?

Thanks in advance.  Kirk

Reply
0 Kudos
1 Solution

Accepted Solutions
WoodyZ
Immortal
Immortal
Jump to solution

If you did not previously configure the VM to be accessed via RDP then the only choice I can see is to suspend or shutdown the VM and then start it normally or from a Shortcut in the Users Startup folder.

Because you started the VM using the AT command and it's process is owned by SYSTEM you'll need to create another NT Command Script (or edit the one you have) with the vmrun suspend or shutdown command, I'd use suspend, and then schedule it with AT for a minute or two later and let it do its thing.  Once suspended or shutdown you should then be able to restart it normally.

With nothing else preconfigured to interact with the VM you're only other option would be to reboot or kill the vmware-vmx.exe and vmware.exe processes owned by SYSTEM however you risk corrupting the virtual hard drive doing that.

View solution in original post

Reply
0 Kudos
9 Replies
WoodyZ
Immortal
Immortal
Jump to solution

Is there a way for me to actually log into this guest that was started or is it unreachable?

Yes, although that all depends on how things are configured.

Why are you starting the Guest using the AT command?

Reply
0 Kudos
KirkA
Contributor
Contributor
Jump to solution

I am attempting to get the guest started on the Vista host at 6:00 a.m.  I tried to schedule using the Vista Task Scheduler and it does not execute it.  I am unable to find any errors in the event viewer or in the task history.  It is like it has no schedule.  I decided to give the "AT" a try and it did start the guest up.  Now the problem is when I log into this Vista host I can not see the guest running, nor can I use it as it is already up and running.  Is there a way for me to get into this guest that is running or do I use the "AT" command and schedule a stop and then log into the Vista host and then start the guest through the VmWare utility?  Thanks, Kirk

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

you can only get a GUI for VMs that were started using your account

does AT start the VM using the system account ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

I swear sometimes it's easier getting a tooth pulled then geting a full answer to a question! Smiley Happy

I already know you're starting it at 6 AM from the AT command line you presented and what I was looking for is the real reason as to why AT which you covered and beyond however I was hoping without having to specifically ask why the VM needs to be started at 6 AM and what is the VM being used for as in it is it being started in order to provide services on the LAN or are you just trying to have the VM available when you log in without having to manually start the VM or what, etc.

Anyway I guess that really doesn't matter because if it did you would have explained however to more directly answer your question let me say this since I do not have a clear picture and understanding why your doing what you are except for the fact it would not do it one other way you tried the bottom line is any machine physical or virtual can be accessed while it is running if it is properly configured to do so and you have proper credentials/rights to access it and it's just that simple although implementing it isn't always.

As an example I have a VM that is run as a Service and starts when the Host is started before anyone logs in or not and the VM is accessible on the physical LAV via RDP or just to access its shared resources via the Network.  There are may ways to configure/access things and how depends on the needs so without a complete picture from you I'm not wasting time providing all the possibilities when one may be all that you need base on why.  Get it? Smiley Wink

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

does AT start the VM using the system account ?

Yes by default the AT command uses the System Account however if executed when logged in and used with the "/interactive" parameter then it should be accessible via the GUI.

Reply
0 Kudos
KirkA
Contributor
Contributor
Jump to solution

Let me try again.  I want the guest machine to start by itself at 6 am so I do not have to start it manually.  This way as you stated before, it is already up and ready when I get to it.  I use this virtual machine for database work and thus I need to be able to get to it from the GUI.  In my attempt to schedule the start of the virtual machine as stated before I ended up using the “AT” command.  Currently I have this virtual machine running under the system account as asked.  I checked by the task manager and those processes are owned by system.  As you also pointed out I could RDP to it, but I did not set the virtual machine up to allow RDP. If there is any more information you need please let me know as I do not know what else to include.  I ask that you continue to be patient and help me provide the details you need in order to help me answer my  question which is how do I get to the GUI of this virtual machine that is running under the system account?  Thank you for your detailed examples and patience.  Kirk

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

Okay now that we've established the reason is laziness (just kidding) Smiley Happy were getting somewhere however again not enough information.

Automated Tasks on a Computer are typically done for very explicit and specific reasons however how exactly to automate depends on all the parameters of the situation and I feel I'm not getting all of the information and I really don't like having to keep asking questions in cases like this and do not understand why you can't be through in providing the details without having to be prodded with more questions.

As an example if your OP has said something like...

On my Windows Vista Business x64 Notebook, used only by me, and running VMware Workstation 7.1.3 build-324285 I would like one particular Virtual Machine to automatically start when I log in to my Desktop and then be able to use it just as if it was the physical machine I'm sitting at.  I have tried using Task Scheduler and it didn't work so I tried using vmrun with the AT command however I cannot access the VM from the GUI when started in this manner.

This would have provided a much clearer foundation to start a dialog from since we know it's a VM being used like a normal system by only you and only when logged into the Host's Desktop and from there I'd say put a Shortcut in the User's Startup Folder so when you login to the Desktop it automatically starts the VM in your User Space and it should then be fully and normally accessible by you.  It can be that simple however without knowing all the parameters there is not much sense in saying to much more.

I'm really not trying to bust your chops and only trying to ascertain the total scope of the situation in order to provide a best use case scenario solution however without all of the parameters the formula is incomplete and does not compute. Smiley Wink

Reply
0 Kudos
KirkA
Contributor
Contributor
Jump to solution

I understand your last reply to be a possible solution to the question of starting up a virtual machine when I log in.  I still have the outstanding question of how to connect to the virtual machine that I already have running that was started and owned by system by using the "AT" command.  Thanks, Kirk

Reply
0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

If you did not previously configure the VM to be accessed via RDP then the only choice I can see is to suspend or shutdown the VM and then start it normally or from a Shortcut in the Users Startup folder.

Because you started the VM using the AT command and it's process is owned by SYSTEM you'll need to create another NT Command Script (or edit the one you have) with the vmrun suspend or shutdown command, I'd use suspend, and then schedule it with AT for a minute or two later and let it do its thing.  Once suspended or shutdown you should then be able to restart it normally.

With nothing else preconfigured to interact with the VM you're only other option would be to reboot or kill the vmware-vmx.exe and vmware.exe processes owned by SYSTEM however you risk corrupting the virtual hard drive doing that.

Reply
0 Kudos