I have big problems getting my W2003 guest to start up with the
system...

This is my setup:
------------------
Host: Win XP-Pro SP2, member of a remote domain
Domain: Accessed via VPN conaction established manually
Virtual Server 2005 R2
Apache webserver version 2 (No IIS installed)
VRMC+ as administrative console

Guest: Windows 2003 server
Startup options:
Action when VS stops: Save State
Run this guest with specified account checked
Username: A local admin user on the host PC
Password: pwd of local admin user
Action: Always autostart guest
Startup delay: 60 s

This is what I get when I shut down my XP host and then start it:

- The guest remains in saved state, there seems to be no start attempt
- In the Event Log for Virtual Server I see these items:

Warning. EventID 1130 08:13:08
The service principal names for Virtual Server could not be
registered. Constrained delegation cannot be used until the SPNs have
been registered manually. Error 0x8007054b - The specified domain
either does not exist or could not be contacted.

Information. EventID 1025 08:13:08
Virtual Server successfully started.

Warning. EventID 1029 08:13:08
The service principal name for the VMRC server could not be
registered. Automatic authentication will always use NTLM
authentication. Error 0x8007054b - The specified domain either does
not exist or could not be contacted.

Warning. EventID 1136 08:13:08
An error has occured during the creation of Service Connection points
for Virtual Server in Active Directory. Either a domain controller is
not available to complete the operation or there is a security problem
accessing the domain. This operation will be retried the next time the
service starts. Error 0x8007054b - The specified domain either does
not exist or could not be contacted.


Obviously the Active Directory could not be contacted since it is 6000
miles away. Is it not possible to have Virtual Server running guests
automatically under a *local* account if the host is a domain PC but
the network connection to the domain controller is not established?

Seems very strange to me especially since the service started
successfully.

When I use VRMC+ I can start the guest just fine, it takes about 5
seconds to get it from the saved state to running.

Now when I look in Event Log I see the following additional entries:

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/additions_number" for the
virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/guest_os/short_name" for
the virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/guest_os/long_name" for the
virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/guest_os/build_number" for
the virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/guest_os/revision_number"
for the virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "integration/microsoft/version/guest_os/computer_name" for
the virtual machine configuration "AntaresVM" was removed.

Information. EventID 1025 09:41:59
"AntaresVM" was restored from saved state.

Information. EventID 1032 09:41:59
The setting "settings/configuration/saved_state/path/relative" for the
virtual machine configuration "AntaresVM" was removed.

Information. EventID 1032 09:41:59
The setting "settings/configuration/saved_state/path/absolute" for the
virtual machine configuration "AntaresVM" was removed.


So what is the problem here?
What should I be looking at?
Is it not possible to use VS2005 in my situation?



Bo Berglund

On Sat, 22 Mar 2008 09:50:44 +0100, Bo Berglund wrote:

> Guest: Windows 2003 server
> Startup options:
> Action when VS stops: Save State
> Run this guest with specified account checked
> Username: A local admin user on the host PC
> Password: pwd of local admin user
> Action: Always autostart guest
> Startup delay: 60 s
>
> This is what I get when I shut down my XP host and then start it:
>
> - The guest remains in saved state, there seems to be no start attempt

Virtual Server is doing exactly what you're telling it to do. When you shut
down the host, you're saving the state of the guest which means the guest
is started, it is just in a saved state. When the host reboots, VS sees
that the guest is started (though in a saved state) and thinks, ok, the
guest is started, I don't need to do anything. For this to work the way you
want it to you need to set the Action when VS stops to shut down the guest.

The rest of your post has nothing to do with the issue you're experiencing,
VS is doing exactly what you're telling it to do.

--
Paul Adare
MVP - Virtual Machines
http://www.identit.ca
System going down at 1:45 for disk crashing.

On Sat, 22 Mar 2008 05:39:32 -0400, Paul Adare <pkadare@gmail.com>
wrote:

>On Sat, 22 Mar 2008 09:50:44 +0100, Bo Berglund wrote:
>
>> Guest: Windows 2003 server
>> Startup options:
>> Action when VS stops: Save State
>> Run this guest with specified account checked
>> Username: A local admin user on the host PC
>> Password: pwd of local admin user
>> Action: Always autostart guest
>> Startup delay: 60 s
>>
>> This is what I get when I shut down my XP host and then start it:
>>
>> - The guest remains in saved state, there seems to be no start attempt
>
>Virtual Server is doing exactly what you're telling it to do. When you shut
>down the host, you're saving the state of the guest which means the guest
>is started, it is just in a saved state. When the host reboots, VS sees
>that the guest is started (though in a saved state) and thinks, ok, the
>guest is started, I don't need to do anything. For this to work the way you
>want it to you need to set the Action when VS stops to shut down the guest.
>
>The rest of your post has nothing to do with the issue you're experiencing,
>VS is doing exactly what you're telling it to do.

It's a matter of semantics apparently. To me a vm in saved state is
*not* running and the setting I tried to apply was for VS to start the
vm on service startup so it will be running and therefore usable.
The reason for making VS save state on shutdown is because it is so
much faster than a complete shutdown.

Apparently I was completely wrong here, I will change the save state
setting to shutdown and see what happens the next time I have to power
cycle my host (not so often, maybe 3-4 times per year, mainly
depending on what tricks Windows Update is playing.
But I really need the ability to recover from a host power fail, which
usually happens when I am not around...

The other stuff was there because I thought taht somehow the inability
to contact the AD controller caused VS to refuse to run the machine...


Bo Berglund

On Sat, 22 Mar 2008 13:22:56 +0100, Bo Berglund wrote:

> It's a matter of semantics apparently. To me a vm in saved state is
> *not* running and the setting I tried to apply was for VS to start the
> vm on service startup so it will be running and therefore usable.

It really doesn't matter what you think the state of a virtual machine in a
saved state is, what matters is what state Virtual Server thinks the guest
is in.

--
Paul Adare
MVP - Virtual Machines
http://www.identit.ca
I came, I saw, I deleted all your files.

On Sat, 22 Mar 2008 08:29:39 -0400, Paul Adare <pkadare@gmail.com>
wrote:

>On Sat, 22 Mar 2008 13:22:56 +0100, Bo Berglund wrote:
>
>> It's a matter of semantics apparently. To me a vm in saved state is
>> *not* running and the setting I tried to apply was for VS to start the
>> vm on service startup so it will be running and therefore usable.
>
>It really doesn't matter what you think the state of a virtual machine in a
>saved state is, what matters is what state Virtual Server thinks the guest
>is in.

I changed the settings so that VS will "shut down" the guest when it
stops and then left the other settings as is (except for some reason
even if not changing anything one has to give the guest account
password every time any setting has to be changed).
Now when I start the VS service it starts up the guest. :-)
I have not tried the full host system restart because there is so much
other stuff running that I will have to wait for that experiment.
But it seems promising so far. Thanks for the pointers!


Bo Berglund