ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Hyper-V iSCSI Question
* Hyper-V Shut down procedure
* P2V conversions with SCVMM
* SMM and Hyper-v out of Sync
* VirtualServer2005 cant access network
* XP Performance under Hyper-V
* Guess time-sync errors
* SCVMM best practices
* Shrinking a fixed-size VHD
* RE: Hyper-V and EventId 4096 after taking snapshot...
* Debug trace API for Hyper-V?
* Hyper-V and PXE Requests
* Event ID 1058 - non-fatal exception
* Adding host OS to domain when DC is a guest VM
* Ip 169
* HYPER-V R2 AND REAL DVD DEVICEs
* problems with SCVMM and domain trust
* R4 ds/dsi firmware-drivers de R4 Sdhc. R4 ultra, R4 new, R4 III upgrade, R4 v3
* Hyper-V clustering, Quick Migration and virtual domain controllers
* hyper-v - teaming recommded at physical host ?

Add Solution

Moving VMs on Hyper-V

Source: microsoft.public.virtualserver
Sent: 03/13/2009
From: "Dave Harry" <(email address - cut out)group>
Message:

I currently use VS2005, but have played with Hyper-V a little on a borrowed
machine.

Because VS emulated hardware I understand the emulated hardware is the same
on all VS servers. In VS, I can create a machine on my very old test gear
then shift it to the more modern production server with no problems. I just
have to specify the new host NIC in the .vmc file.

What about in Hyper-V? If the bare metal hardware is different, and the
guest sees that hardware, does that mean I can't shift a guest between
hosts - unless they're physically similar hosts?

--
Dave Harry

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Moving VMs on Hyper-V

Sent: 03/13/2009
From: Paul Adare <(email address - cut out)>
Message:

On Fri, 13 Mar 2009 16:56:57 +1100, Dave Harry wrote:

Hyper-V is no different in this regard than VS. The only difference is the
list of emulated hardware is different.

--
Paul Adare
MVP - Identity Lifecycle Manager
http://www.identit.ca

Show quoted text

> I currently use VS2005, but have played with Hyper-V a little on a borrowed
> machine.
>
> Because VS emulated hardware I understand the emulated hardware is the same
> on all VS servers. In VS, I can create a machine on my very old test gear
> then shift it to the more modern production server with no problems. I just
> have to specify the new host NIC in the .vmc file.
>
> What about in Hyper-V? If the bare metal hardware is different, and the
> guest sees that hardware, does that mean I can't shift a guest between
> hosts - unless they're physically similar hosts?

Re: Moving VMs on Hyper-V

Sent: 03/15/2009
From: Robert Comer <(email address - cut out)>
Message:

>I'll assume this means that Hyper-V still emulates the hardware, rather than

All the virtualization products like this only emulate the hardware,
none share. (other than the CPU that is)

--
Bob Comer

On Mon, 16 Mar 2009 11:27:18 +1100, "Dave Harry"
<(email address - cut out)group> wrote:

Show quoted text

>somehow sharing the actual hardware as I believed.
>Thank you Paul.
>>> I currently use VS2005, but have played with Hyper-V a little on a
>>> borrowed
>>> machine.
>>>
>>> Because VS emulated hardware I understand the emulated hardware is the
>>> same
>>> on all VS servers. In VS, I can create a machine on my very old test gear
>>> then shift it to the more modern production server with no problems. I
>>> just
>>> have to specify the new host NIC in the .vmc file.
>>>
>>> What about in Hyper-V? If the bare metal hardware is different, and the
>>> guest sees that hardware, does that mean I can't shift a guest between
>>> hosts - unless they're physically similar hosts?
>>
>> Hyper-V is no different in this regard than VS. The only difference is the
>> list of emulated hardware is different.
>
>I'll assume this means that Hyper-V still emulates the hardware, rather than
>somehow sharing the actual hardware as I believed.
>Thank you Paul.

Re: Moving VMs on Hyper-V

Sent: 03/16/2009
From: "Dave Harry" <(email address - cut out)group>
Message:

>> I currently use VS2005, but have played with Hyper-V a little on a

I'll assume this means that Hyper-V still emulates the hardware, rather than
somehow sharing the actual hardware as I believed.
Thank you Paul.

--
Dave Harry

Show quoted text

>> borrowed
>> machine.
>>
>> Because VS emulated hardware I understand the emulated hardware is the
>> same
>> on all VS servers. In VS, I can create a machine on my very old test gear
>> then shift it to the more modern production server with no problems. I
>> just
>> have to specify the new host NIC in the .vmc file.
>>
>> What about in Hyper-V? If the bare metal hardware is different, and the
>> guest sees that hardware, does that mean I can't shift a guest between
>> hosts - unless they're physically similar hosts?
>
> Hyper-V is no different in this regard than VS. The only difference is the
> list of emulated hardware is different.

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: