Sent: 02/27/2008
From: Robert Comer <(email address - cut out)>
Message:Like others have said, only the CPU is "different" when you move a VM
to another PC, so if it's in a shutdown state, all should be well --
however when going from PC's to others the VM can crash, but the cure
for that is to start in safe mode and then reboot and it should be
okay.
--
Bob Comer <Microsoft MVP Windows - Virtual Machine>
On Wed, 27 Feb 2008 16:35:48 -0800 (PST), (email address - cut out) wrote:
Show quoted text
>I'm familiar with cloning a drive and recognize it's limitations in
>that a clone image can't be easily applied to another workstation that
>has different hardware components.
>
>Does the same hold true with virtual pc or can a virtual pc be moved
>from one pc to another regardless of if the hardware is the same or
>different?
>
>Thank you
Sent: 02/28/2008
From: Anonymous <(email address - cut out)>
Message:In article <(email address - cut out)>
(email address - cut out) wrote:
Yes, you can move the VPC to another computer and it will work fine.
Show quoted text
>
> I'm familiar with cloning a drive and recognize it's limitations in
> that a clone image can't be easily applied to another workstation that
> has different hardware components.
>
> Does the same hold true with virtual pc or can a virtual pc be moved
> from one pc to another regardless of if the hardware is the same or
> different?
>
> Thank you
Sent: 02/28/2008
From: Bo Berglund <(email address - cut out)>
Message:On Wed, 27 Feb 2008 17:02:37 -0800, "Karl E. Peterson" <(email address - cut out)>
wrote:
Or rather leave the vmc file out of the copy, just move the vhd file
and create a new guest on the target. When asked for the virtual disk,
just point to the copied vhd file and continue. This way the issue of
the paths and MAC address etc will not surface.
Bo Berglund
Show quoted text
>(email address - cut out) wrote:
>> I'm familiar with cloning a drive and recognize it's limitations in
>> that a clone image can't be easily applied to another workstation that
>> has different hardware components.
>>
>> Does the same hold true with virtual pc or can a virtual pc be moved
>> from one pc to another regardless of if the hardware is the same or
>> different?
>
>In addition to what Steve offered, you may want to hand edit the VMC file to insure
>the fully-qualified path to VHD(s) correctly points to the new location.
Sent: 02/28/2008
From: "Karl E. Peterson" <(email address - cut out)>
Message:Bo Berglund wrote:
Yeah, that's another approach, I suppose. Seems like fewer steps to just point at
an existing one, to me, though. What's the issue with MAC addresses? I haven't run
into that, and I'm pretty sure the net.nazis that play the role of Mordoc here
would've seen to it I would have if there was one.
--
..NET: It's About Trust!
http://vfred.mvps.org
Show quoted text
> On Wed, 27 Feb 2008 17:02:37 -0800, "Karl E. Peterson" <(email address - cut out)>
> wrote:
>
>>(email address - cut out) wrote:
>>> I'm familiar with cloning a drive and recognize it's limitations in
>>> that a clone image can't be easily applied to another workstation that
>>> has different hardware components.
>>>
>>> Does the same hold true with virtual pc or can a virtual pc be moved
>>> from one pc to another regardless of if the hardware is the same or
>>> different?
>>
>>In addition to what Steve offered, you may want to hand edit the VMC file to
>>insure
>>the fully-qualified path to VHD(s) correctly points to the new location.
>
> Or rather leave the vmc file out of the copy, just move the vhd file
> and create a new guest on the target. When asked for the virtual disk,
> just point to the copied vhd file and continue. This way the issue of
> the paths and MAC address etc will not surface.
Sent: 02/28/2008
From: "Karl E. Peterson" <(email address - cut out)>
Message:Bo Berglund wrote:
Ahhhhh... Okay, but if you're pretty much self-contained, probably no-harm/no-foul.
Assuming you're not trying to run these at the same time, at any rate. Didn't know
that! That's another argument for creating new VMCs with each move/copy, then, for
sure.
You're starting to convince me. Thanks!
--
..NET: It's About Trust!
http://vfred.mvps.org
Show quoted text
> On Thu, 28 Feb 2008 10:59:13 -0800, "Karl E. Peterson" <(email address - cut out)>
> wrote:
>
>>> Or rather leave the vmc file out of the copy, just move the vhd file
>>> and create a new guest on the target. When asked for the virtual disk,
>>> just point to the copied vhd file and continue. This way the issue of
>>> the paths and MAC address etc will not surface.
>>
>>Yeah, that's another approach, I suppose. Seems like fewer steps to just point at
>>an existing one, to me, though. What's the issue with MAC addresses? I haven't
>>run into that, and I'm pretty sure the net.nazis that play the role of Mordoc here
>>would've seen to it I would have if there was one.
>
> The issue is that the network card MAC address used by the guest for
> its NIC when it communicates on the network is defined in the VMC file
> and it is a universally unique number for each *new* guest one makes.
>
> But if one copies the vmc together with the vhd file and then starts
> up this guest on a different (or same) host computer then if the
> original is also started there will be a card conflict on the network
> so one or both guests can no longer communicate.
> So if you start hand editing the vmc file then you should also change
> the MAC address item to make it unique...
> On the other hand by making a new guset on the new host VPC2007 will
> create a new MAC address that is guaranteed to be unique. And it will
> also fix the vhd file path problem. It is really quite simple to make
> a new guset with the wizard so I prefer this nowadays (I have done the
> edits before).
Sent: 02/28/2008
From: "Karl E. Peterson" <(email address - cut out)>
Message:Bill Grant wrote:
Yeah, looks like I've skated just around the border of trouble so far. Gonna keep
this in mind, thanks!
--
..NET: It's About Trust!
http://vfred.mvps.org
Show quoted text
> The MAC address problem only comes up if you copy an existing vmc file.
> Both the original vm and the copy will have the same MAC address for the
> NIC. It doesn't arise if you simply move the vmc file from one location to
> another.
Sent: 02/29/2008
From: Bo Berglund <(email address - cut out)>
Message:On Thu, 28 Feb 2008 10:59:13 -0800, "Karl E. Peterson" <(email address - cut out)>
wrote:
The issue is that the network card MAC address used by the guest for
its NIC when it communicates on the network is defined in the VMC file
and it is a universally unique number for each *new* guest one makes.
But if one copies the vmc together with the vhd file and then starts
up this guest on a different (or same) host computer then if the
original is also started there will be a card conflict on the network
so one or both guests can no longer communicate.
So if you start hand editing the vmc file then you should also change
the MAC address item to make it unique...
On the other hand by making a new guset on the new host VPC2007 will
create a new MAC address that is guaranteed to be unique. And it will
also fix the vhd file path problem. It is really quite simple to make
a new guset with the wizard so I prefer this nowadays (I have done the
edits before).
Bo Berglund
Show quoted text
>> Or rather leave the vmc file out of the copy, just move the vhd file
>> and create a new guest on the target. When asked for the virtual disk,
>> just point to the copied vhd file and continue. This way the issue of
>> the paths and MAC address etc will not surface.
>
>Yeah, that's another approach, I suppose. Seems like fewer steps to just point at
>an existing one, to me, though. What's the issue with MAC addresses? I haven't run
>into that, and I'm pretty sure the net.nazis that play the role of Mordoc here
>would've seen to it I would have if there was one.
Sent: 02/29/2008
From: "Bill Grant" <not.available@online>
Message: The MAC address problem only comes up if you copy an existing vmc file.
Both the original vm and the copy will have the same MAC address for the
NIC. It doesn't arise if you simply move the vmc file from one location to
another.
"Karl E. Peterson" <(email address - cut out)> wrote in message
news:%23ZF$(email address - cut out)...
Show quoted text
> Bo Berglund wrote:
>> On Wed, 27 Feb 2008 17:02:37 -0800, "Karl E. Peterson" <(email address - cut out)>
>> wrote:
>>
>>>(email address - cut out) wrote:
>>>> I'm familiar with cloning a drive and recognize it's limitations in
>>>> that a clone image can't be easily applied to another workstation that
>>>> has different hardware components.
>>>>
>>>> Does the same hold true with virtual pc or can a virtual pc be moved
>>>> from one pc to another regardless of if the hardware is the same or
>>>> different?
>>>
>>>In addition to what Steve offered, you may want to hand edit the VMC file
>>>to insure
>>>the fully-qualified path to VHD(s) correctly points to the new location.
>>
>> Or rather leave the vmc file out of the copy, just move the vhd file
>> and create a new guest on the target. When asked for the virtual disk,
>> just point to the copied vhd file and continue. This way the issue of
>> the paths and MAC address etc will not surface.
>
> Yeah, that's another approach, I suppose. Seems like fewer steps to just
> point at an existing one, to me, though. What's the issue with MAC
> addresses? I haven't run into that, and I'm pretty sure the net.nazis
> that play the role of Mordoc here would've seen to it I would have if
> there was one.
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>
Wiki