Does anybody tried to displace some VMs from one maschine with the
hardware "a" to another maschine with the hardware "b" ?
I've heard that doesn't work without problems...

I've moved many VMs without issue. Ideally, you should export the VM from
machine A, and then import them into machine B. In many cases you'll need to
redo the networking, but otherwise I haven't had issues, except sometimes
requiring re-activation.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"tbergfeld" <tom_bergfeld@xxxxxx> wrote in message
news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx

> Does anybody tried to displace some VMs from one maschine with the
> hardware "a" to another maschine with the hardware "b" ?
> I've heard that doesn't work without problems...

Ditto here...moving VMs from one Hyper-V system to another is typically
without incident.

--

Ryan Sokolowski
MVP - Clustering
MCSE, CCNA, CCDA, BCFP


"Charlie Russel - MVP" <charlie@xxxxxx> wrote in message
news:C3BCDB56-0EAF-490E-A709-6B829EB3E7F4@xxxxxx

> I've moved many VMs without issue. Ideally, you should export the VM from
> machine A, and then import them into machine B. In many cases you'll need
> to redo the networking, but otherwise I haven't had issues, except
> sometimes requiring re-activation.
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "tbergfeld" <tom_bergfeld@xxxxxx> wrote in message
> news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx

>> Does anybody tried to displace some VMs from one maschine with the
>> hardware "a" to another maschine with the hardware "b" ?
>> I've heard that doesn't work without problems...

>

On 4 Jun., 22:07, "Ryan Sokolowski [MVP]" <r...@xxxxxx>
wrote:

> Ditto here...moving VMs from one Hyper-V system to another is typically
> without incident.
>
> --
>
> Ryan Sokolowski
> MVP - Clustering
> MCSE, CCNA, CCDA, BCFP
>
> "Charlie Russel - MVP" <char...@xxxxxx> wrote in messagenews:C3BCDB56-0EAF-490E-A709-6B829EB3E7F4@xxxxxx
>

> > I've moved many VMs without issue. Ideally, you should export the VM from
> > machine A, and then import them into machine B. In many cases you'll need
> > to redo the networking, but otherwise I haven't had issues, except
> > sometimes requiring re-activation.

>

> > --
> > Charlie.
> >http://msmvps.com/xperts64
> >http://mvp.support.microsoft.com/profile/charlie.russel

>

> > "tbergfeld" <tom_bergf...@xxxxxx> wrote in message
> >news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx

> >> Does anybody tried to displace some VMs from one maschine with the
> >> hardware "a" to another maschine with the hardware "b" ?
> >> I've heard that doesn't work without problems...

thx guys...
And the hardware of the maschines are different? Like cpu etc...

Best regards,
Tom

yes, hardware different. In fact, I had a set of VMs that I had to work with
that were created by a friend for a project. He had an HP DL585 (quad
opteron), and I used them on a DL380 (dual Xeon) and a laptop. They worked
fine. I did get prompted for an activation on one of them, but that was as
likely to have been because of a change in the RAM and # of cores assigned
as anything else. And while annoying, wasn't a major deal.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"tbergfeld" <tom_bergfeld@xxxxxx> wrote in message
news:72aab703-89e2-45b5-9aa1-b3368f3febe4@xxxxxx

> On 4 Jun., 22:07, "Ryan Sokolowski [MVP]" <r...@xxxxxx>
> wrote:

>> Ditto here...moving VMs from one Hyper-V system to another is typically
>> without incident.
>>
>> --
>>
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP
>>
>> "Charlie Russel - MVP" <char...@xxxxxx> wrote in
>> messagenews:C3BCDB56-0EAF-490E-A709-6B829EB3E7F4@xxxxxx
>>

>> > I've moved many VMs without issue. Ideally, you should export the VM
>> > from
>> > machine A, and then import them into machine B. In many cases you'll
>> > need
>> > to redo the networking, but otherwise I haven't had issues, except
>> > sometimes requiring re-activation.

>>

>> > --
>> > Charlie.
>> >http://msmvps.com/xperts64
>> >http://mvp.support.microsoft.com/profile/charlie.russel

>>

>> > "tbergfeld" <tom_bergf...@xxxxxx> wrote in message
>> >news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx
>> >> Does anybody tried to displace some VMs from one maschine with the
>> >> hardware "a" to another maschine with the hardware "b" ?
>> >> I've heard that doesn't work without problems...

>
> thx guys...
> And the hardware of the maschines are different? Like cpu etc...
>
> Best regards,
> Tom

On Thu, 5 Jun 2008 02:57:27 -0700 (PDT), tbergfeld
<tom_bergfeld@xxxxxx> wrote:

>On 4 Jun., 22:07, "Ryan Sokolowski [MVP]" <r...@xxxxxx>
>wrote:

>> Ditto here...moving VMs from one Hyper-V system to another is typically
>> without incident.
>>
>> --
>>
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP
>>
>> "Charlie Russel - MVP" <char...@xxxxxx> wrote in messagenews:C3BCDB56-0EAF-490E-A709-6B829EB3E7F4@xxxxxx
>>

>> > I've moved many VMs without issue. Ideally, you should export the VM from
>> > machine A, and then import them into machine B. In many cases you'll need
>> > to redo the networking, but otherwise I haven't had issues, except
>> > sometimes requiring re-activation.

>>

>> > --
>> > Charlie.
>> >http://msmvps.com/xperts64
>> >http://mvp.support.microsoft.com/profile/charlie.russel

>>

>> > "tbergfeld" <tom_bergf...@xxxxxx> wrote in message
>> >news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx
>> >> Does anybody tried to displace some VMs from one maschine with the
>> >> hardware "a" to another maschine with the hardware "b" ?
>> >> I've heard that doesn't work without problems...

>
>thx guys...
>And the hardware of the maschines are different? Like cpu etc...
>
>Best regards,
>Tom

Be careful with CPU. I haven't tried with Hypver-V, but there used to
be a potential for issues when moving from AMD to Intel or vice-versa.
The VM's OS can install specific kernals for the particular CPU and
cause problems in Virtual PC and Virtual Server.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
I do not work for Microsoft.

Not an issue with any 64-bit VM, since there's only a single kernel. But
could be an issue with older OS's, certainly.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Steve Jain" <noreply.-@-.essjae.com> wrote in message
news:0j5g44p06nceonc19kp945fl7e2hc1o1c9@xxxxxx

> On Thu, 5 Jun 2008 02:57:27 -0700 (PDT), tbergfeld
> <tom_bergfeld@xxxxxx> wrote:
>

>>On 4 Jun., 22:07, "Ryan Sokolowski [MVP]" <r...@xxxxxx>
>>wrote:

>>> Ditto here...moving VMs from one Hyper-V system to another is typically
>>> without incident.
>>>
>>> --
>>>
>>> Ryan Sokolowski
>>> MVP - Clustering
>>> MCSE, CCNA, CCDA, BCFP
>>>
>>> "Charlie Russel - MVP" <char...@xxxxxx> wrote in
>>> messagenews:C3BCDB56-0EAF-490E-A709-6B829EB3E7F4@xxxxxx
>>>
>>> > I've moved many VMs without issue. Ideally, you should export the VM
>>> > from
>>> > machine A, and then import them into machine B. In many cases you'll
>>> > need
>>> > to redo the networking, but otherwise I haven't had issues, except
>>> > sometimes requiring re-activation.
>>>
>>> > --
>>> > Charlie.
>>> >http://msmvps.com/xperts64
>>> >http://mvp.support.microsoft.com/profile/charlie.russel
>>>
>>> > "tbergfeld" <tom_bergf...@xxxxxx> wrote in message
>>> >news:db283786-86af-4e43-855c-45523e8b6b72@xxxxxx
>>> >> Does anybody tried to displace some VMs from one maschine with the
>>> >> hardware "a" to another maschine with the hardware "b" ?
>>> >> I've heard that doesn't work without problems...

>>
>>thx guys...
>>And the hardware of the maschines are different? Like cpu etc...
>>
>>Best regards,
>>Tom

>
> Be careful with CPU. I haven't tried with Hypver-V, but there used to
> be a potential for issues when moving from AMD to Intel or vice-versa.
> The VM's OS can install specific kernals for the particular CPU and
> cause problems in Virtual PC and Virtual Server.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> I do not work for Microsoft.