Save State

I'm having this problem with virtual PC 2007, I have the latest service pack
installed on all of my Windows Desktops and Laptops. All my virtual machines
on an external hard drive. Whenever I do 'save state', disconnect the drive,
and try to use it on another PC, the error message shows up: "The virtual
machine could not be restored because the saved state was either corrupt or
incompatible with this version of virtual PC". have to delete the saved
state" in order to start the virtual machine, but I really want the state to
be saved. I had some luck with my office PC and home PC, but a few days ago,
it stop working, too.
For the two laptop computers (Vista Ultimate SP1) that I have, the saved
state never worked with each other neither.

Whoever is reading this post, thank you!

You can't save state and move it to another machine, you have to shut
the VM down all the way and then move it. It's a fluke it ever worked
with save state -- the machine must be fairly close hardware-wise.

No workaround.

--
Bob Comer



On Thu, 25 Jun 2009 10:46:02 -0700, Hill
<> wrote:

>I'm having this problem with virtual PC 2007, I have the latest service pack
>installed on all of my Windows Desktops and Laptops. All my virtual machines
>on an external hard drive. Whenever I do 'save state', disconnect the drive,
>and try to use it on another PC, the error message shows up: "The virtual
>machine could not be restored because the saved state was either corrupt or
>incompatible with this version of virtual PC". have to delete the saved
>state" in order to start the virtual machine, but I really want the state to
>be saved. I had some luck with my office PC and home PC, but a few days ago,
>it stop working, too.
>For the two laptop computers (Vista Ultimate SP1) that I have, the saved
>state never worked with each other neither.
>
>Whoever is reading this post, thank you!

Thanks for your post, Robert.

It's suprising that I have been using the saved state between two machines
for quite a while (about a year), and the two computers are actually nothing
alike. The home PC is qual-core, 4GB Memory running Win Vista Ultimate. The
office machine is Dual-core, 2GB running Windows XP. Different Video card,
different sound card different everything. I guess it's just a pure fluke
like you said...

Thank again,

Best Regards,

Hill

"Robert Comer" wrote:

> You can't save state and move it to another machine, you have to shut
> the VM down all the way and then move it. It's a fluke it ever worked
> with save state -- the machine must be fairly close hardware-wise.
>
> No workaround.
>
> --
> Bob Comer
>
>
>
> On Thu, 25 Jun 2009 10:46:02 -0700, Hill
> <> wrote:
>
> >I'm having this problem with virtual PC 2007, I have the latest service pack
> >installed on all of my Windows Desktops and Laptops. All my virtual machines
> >on an external hard drive. Whenever I do 'save state', disconnect the drive,
> >and try to use it on another PC, the error message shows up: "The virtual
> >machine could not be restored because the saved state was either corrupt or
> >incompatible with this version of virtual PC". have to delete the saved
> >state" in order to start the virtual machine, but I really want the state to
> >be saved. I had some luck with my office PC and home PC, but a few days ago,
> >it stop working, too.
> >For the two laptop computers (Vista Ultimate SP1) that I have, the saved
> >state never worked with each other neither.
> >
> >Whoever is reading this post, thank you!
>

You're welcome, sorry I couldn't really help.

The main problem with moving between PC's is the CPU, but it's
possible a BIOS setting could have changed on one that would make them
incompatible. (like turning on or off VT on one and not the other.)

If it's a different type of CPU, then there really isn't much you can
do. (a core 2 quad really isn't much different than a core 2 duo, they
are pretty compatible.)

--
Bob Comer




On Thu, 25 Jun 2009 11:50:01 -0700, Hill
<> wrote:

>Thanks for your post, Robert.
>
>It's suprising that I have been using the saved state between two machines
>for quite a while (about a year), and the two computers are actually nothing
>alike. The home PC is qual-core, 4GB Memory running Win Vista Ultimate. The
>office machine is Dual-core, 2GB running Windows XP. Different Video card,
>different sound card different everything. I guess it's just a pure fluke
>like you said...
>
>Thank again,
>
>Best Regards,
>
>Hill
>
>"Robert Comer" wrote:
>
>> You can't save state and move it to another machine, you have to shut
>> the VM down all the way and then move it. It's a fluke it ever worked
>> with save state -- the machine must be fairly close hardware-wise.
>>
>> No workaround.
>>
>> --
>> Bob Comer
>>
>>
>>
>> On Thu, 25 Jun 2009 10:46:02 -0700, Hill
>> <> wrote:
>>
>> >I'm having this problem with virtual PC 2007, I have the latest service pack
>> >installed on all of my Windows Desktops and Laptops. All my virtual machines
>> >on an external hard drive. Whenever I do 'save state', disconnect the drive,
>> >and try to use it on another PC, the error message shows up: "The virtual
>> >machine could not be restored because the saved state was either corrupt or
>> >incompatible with this version of virtual PC". have to delete the saved
>> >state" in order to start the virtual machine, but I really want the state to
>> >be saved. I had some luck with my office PC and home PC, but a few days ago,
>> >it stop working, too.
>> >For the two laptop computers (Vista Ultimate SP1) that I have, the saved
>> >state never worked with each other neither.
>> >
>> >Whoever is reading this post, thank you!
>>

To clarify a bit:

When we go to restore a saved state virtual machine, we do not check the
CPU version - rather we check to see if the CPU has the same (or more)
features than the source computer.

This means that there are times when you can move saved states between
different processors.

It also means that there are times when you can move a saved state from
computer A to computer B - but not from computer B to computer A (this
happens if B has a super-set of CPU features of A).

Cheers,
Benjamin Armstrong
===========================
Senior Program Manager Lead
Windows Virtualization

Blog: http://blogs.msdn.com/Virtual_PC_Guy
Book: http://tinyurl.com/ysxcbm

This posting is provided "AS IS" with no warranties, and confers no
rights. You assume all risk for your use.

Robert Comer wrote:
> You're welcome, sorry I couldn't really help.
>
> The main problem with moving between PC's is the CPU, but it's
> possible a BIOS setting could have changed on one that would make them
> incompatible. (like turning on or off VT on one and not the other.)
>
> If it's a different type of CPU, then there really isn't much you can
> do. (a core 2 quad really isn't much different than a core 2 duo, they
> are pretty compatible.)
>

Thanks for clarifying that Ben.

--
Bob Comer


On Thu, 25 Jun 2009 12:21:08 -0700, "Benjamin Armstrong [MSFT]"
<> wrote:

>To clarify a bit:
>
>When we go to restore a saved state virtual machine, we do not check the
>CPU version - rather we check to see if the CPU has the same (or more)
>features than the source computer.
>
>This means that there are times when you can move saved states between
>different processors.
>
>It also means that there are times when you can move a saved state from
>computer A to computer B - but not from computer B to computer A (this
>happens if B has a super-set of CPU features of A).
>
>Cheers,
>Benjamin Armstrong
>===========================
>Senior Program Manager Lead
>Windows Virtualization
>
>Blog: http://blogs.msdn.com/Virtual_PC_Guy
>Book: http://tinyurl.com/ysxcbm
>
>This posting is provided "AS IS" with no warranties, and confers no
>rights. You assume all risk for your use.
>
>Robert Comer wrote:
>> You're welcome, sorry I couldn't really help.
>>
>> The main problem with moving between PC's is the CPU, but it's
>> possible a BIOS setting could have changed on one that would make them
>> incompatible. (like turning on or off VT on one and not the other.)
>>
>> If it's a different type of CPU, then there really isn't much you can
>> do. (a core 2 quad really isn't much different than a core 2 duo, they
>> are pretty compatible.)
>>

Thank a lot, Ben for your explanation! It's truly great to look at the
concept on how it works.

Thank you for both of your comments!

Best Regards,

Hill

"Benjamin Armstrong [MSFT]" wrote:

> To clarify a bit:
>
> When we go to restore a saved state virtual machine, we do not check the
> CPU version - rather we check to see if the CPU has the same (or more)
> features than the source computer.
>
> This means that there are times when you can move saved states between
> different processors.
>
> It also means that there are times when you can move a saved state from
> computer A to computer B - but not from computer B to computer A (this
> happens if B has a super-set of CPU features of A).
>
> Cheers,
> Benjamin Armstrong
> ===========================
> Senior Program Manager Lead
> Windows Virtualization
>
> Blog: http://blogs.msdn.com/Virtual_PC_Guy
> Book: http://tinyurl.com/ysxcbm
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. You assume all risk for your use.
>
> Robert Comer wrote:
> > You're welcome, sorry I couldn't really help.
> >
> > The main problem with moving between PC's is the CPU, but it's
> > possible a BIOS setting could have changed on one that would make them
> > incompatible. (like turning on or off VT on one and not the other.)
> >
> > If it's a different type of CPU, then there really isn't much you can
> > do. (a core 2 quad really isn't much different than a core 2 duo, they
> > are pretty compatible.)
> >
>