Same thing for me here.
Only i have this happening on a server with only one VM.
This was working perfectly up to last week.
I do get the following info alerts just before the error happens.

The setting "settings/shutdown/quit/was_running" for the virtual machine
configuration "Server" was changed from true to false.

The setting "hardware/bios/time_bytes" for the virtual machine configuration
"Server" was changed.`

The setting "settings/configuration/saved_state/path/absolute" for the
virtual machine configuration "Server" was changed from NULL to
"C:\virtual_servers\tfs\Server\Server.vsv".

The setting "settings/configuration/saved_state/path/relative" for the
virtual machine configuration "Server" was changed from NULL to
".\Server.vsv".







"Eduardo Nazato" wrote:

> I think several members of the forum are experiencing the same problems that
> I am.
>
> We have a schedule task that runs a script that automatically save the state
> of all VMs at Saturday nights, and restore them at Sunday mornings. This task
> runs on our 7 Virtual Server hosts.
>
> But one of the servers always have problems when restoring the state of the
> VMs.
> It starts showing this error:
>
>
> -------------------------------------------------------------------------------------
> """ has encountered a fatal error. Details have been logged to "C:\Documents
> and Settings\All Users\Application Data\Microsoft\Virtual Server\Crash
> Logs\VSCrashLog27090003456.txt"."
> -------------------------------------------------------------------------------------
>
>
> ... followed by:
>
>
> -------------------------------------------------------------------------------------
> "Virtual Server has encountered a non-fatal exception. Details have been
> logged to "C:\Documents and Settings\All Users\Application
> Data\Microsoft\Virtual Server\Crash Logs\VSCrashLog27090026519.txt"."
> -------------------------------------------------------------------------------------
>
>
> Then, every VM on this server stays "Saved".
> If we try to restore them manually, we receive this sequence of errors:
>
>
> -------------------------------------------------------------------------------------
> The virtual machine "virtual_machine_name" cannot connect virtual network
> adapter 1 because another virtual machine with the MAC address
> 00:03:FF:88:C2:59 is already running. This virtual network adapter will be
> left disconnected.
> -------------------------------------------------------------------------------------
> "virtual_machine_name" could not be started because one of its virtual hard
> disks is already in use by another running virtual machine
> -------------------------------------------------------------------------------------
> "virtual_machine_name" could not initialize the emulated Ethernet controller.
> -------------------------------------------------------------------------------------
>
>
> I've searched for the same errors (and possible solutions) posted in the
> forum by other members, but:
> - This server has 2 NICs, and one of them is disabled. Some people had
> problems with this configuration, but we have other severs with the same
> configuration that are not experiencing any problem;
> - Both NICs of this server have TCP Offloading enabled by default. Again,
> other severs too, and no problem with them up to here;
> - The VMs are in production environment. It is near impossible to restart
> any service on the host for test purposes;
> - Connecting and disconnecting the virtual network adapters didn't resolved
> the problem
>
> The problem was solved after restarting Virtual Server service, and after
> that (and pausedly), starting each VM again. But it's getting harder to
> resolve this problem every Monday morning, with so many calls and people
> blaming at the same time
>
> Is there any hotfix, patch or procedure to fix this network and fatal-errors
> issues?
>
> Thanks
> Eduardo
>

Reinstalled Virtual server SP1 and the problem has disappeared.
Not sure if this will .
I didn't have to re-attach any VHD's or anything like that.
It uninstalled the previous version, then had to re-install and all worked
fine

Keep an eye on it. The symptoms returned for me after a reinstall.

Rob


"Jamie" <Jamie@discussions.microsoft.com> wrote in message
news:A2B63643-E35D-4B4C-893B-A5BB0A4AA74D@microsoft.com...
>
> Reinstalled Virtual server SP1 and the problem has disappeared.
> Not sure if this will .
> I didn't have to re-attach any VHD's or anything like that.
> It uninstalled the previous version, then had to re-install and all worked
> fine

Yeah, you're right.
After moving the problematic server from production to a test environment, I
tried to reinstall Virtual Server 2005 too, and soon after the problem got
back =/

Initially I thought that the problem was related to our NICs. This server
has 2 NICs: the "original" one (on-board), and another one we've plugged
(off-board).
But even after removing the off-board NIC and reinstalling Virtual Server,
the problem persisted.
After all, we had to format the server. Only then it could be reused to host
VMs.

And now, to get things worse, another server is suffering from the same
problem, and this server is even more critical than the previous.
This server also has 2 NICs, but both are on-board. One is connected to our
internal network, and most of the VMs are only connected to it. The other NIC
is connected to the public network, and the other VMs are only connected to
it.
On the host, we've decided to leave only "Virtual Machine Network Services"
active for the second NIC (the public one), so the host can't use it.

The problem is basically the same, with some differences: last weekend only
the "public" VMs were offline, and this weekend only the "internal" VMs were
offline.





"Rob McShinsky" wrote:

> Keep an eye on it. The symptoms returned for me after a reinstall.
>
> Rob
>
>
> "Jamie" <Jamie@discussions.microsoft.com> wrote in message
> news:A2B63643-E35D-4B4C-893B-A5BB0A4AA74D@microsoft.com...
> >
> > Reinstalled Virtual server SP1 and the problem has disappeared.
> > Not sure if this will .
> > I didn't have to re-attach any VHD's or anything like that.
> > It uninstalled the previous version, then had to re-install and all worked
> > fine
>
>
>