Hi all,

Is there a migration path from VM's running on Microsoft Virtual Server 2005
to Microsoft HyperV or are there any conversion utilities?



Thanks,
Mike

Uninstall VMAdditions. Shut down guest OS (don't try to migrate saved
states.) copy VHD files to new Hyper-V host. Re-create VM by creating a new
VM and pointing to the VHD file(s). You'll have to redo networking, and your
boot disk must be IDE, but otherwise you should be fine.

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


"Mike" <nospam@xxxxxx> wrote in message
news:urJajmh1IHA.3884@xxxxxx

> Hi all,
>
> Is there a migration path from VM's running on Microsoft Virtual Server
> 2005 to Microsoft HyperV or are there any conversion utilities?
>
> Thanks,
> Mike

Thanks Charlie!

Maybe it's my lack of understanding here, but what do you do if you're
running hyperV on server hardware, where you would inevitably have SCSI or
SAN storage? I guess the boot disk would probably most likely always be SCSI
on server hardware.

Thanks,
Mike

"Charlie Russel - MVP" <charlie@xxxxxx> wrote in message
news:6000441B-8B03-4D8C-A535-AE574446AD79@xxxxxx

> Uninstall VMAdditions. Shut down guest OS (don't try to migrate saved
> states.) copy VHD files to new Hyper-V host. Re-create VM by creating a
> new VM and pointing to the VHD file(s). You'll have to redo networking,
> and your boot disk must be IDE, but otherwise you should be fine.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Mike" <nospam@xxxxxx> wrote in message
> news:urJajmh1IHA.3884@xxxxxx

>> Hi all,
>>
>> Is there a migration path from VM's running on Microsoft Virtual Server
>> 2005 to Microsoft HyperV or are there any conversion utilities?
>>
>> Thanks,
>> Mike

>

>>> Is there a migration path from VM's running on Microsoft Virtual Server

>>> 2005 to Microsoft HyperV or are there any conversion utilities?

>> Uninstall VMAdditions. Shut down guest OS (don't try to migrate saved
>> states.) copy VHD files to new Hyper-V host. Re-create VM by creating a
>> new VM and pointing to the VHD file(s). You'll have to redo networking,
>> and your boot disk must be IDE, but otherwise you should be fine.

>
>Maybe it's my lack of understanding here, but what do you do if you're
>running hyperV on server hardware, where you would inevitably have SCSI or
>SAN storage? I guess the boot disk would probably most likely always be SCSI
>on server hardware.

He was talking about the virtual hard disk. When you build a virtual
machine you use a virtual hard disk which is physically stored as a
file on the *host* system with the extension VHD.
On VPC2007 such virtual disks are always emulated IDE disks, but on
Virtual Server 2005 you can choose to use eiter an emulated IDE or an
emulated SCSI disk in the VHD file.

Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
IDE and this is the reason for his remark. If that is really the case
I don't know since I have not used HyperV myself, only VPC2007 and
VS2005.

Whatever the host uses to store the VHD file is completely irrelevent;
to the host the VHD is just another data file and can be stored in any
way useful for the host.

--

Bo Berglund (Sweden)

> He was talking about the virtual hard disk. When you build a virtual
> machine you use a virtual hard disk which is physically stored as a
> file on the *host* system with the extension VHD.
> On VPC2007 such virtual disks are always emulated IDE disks, but on
> Virtual Server 2005 you can choose to use eiter an emulated IDE or an
> emulated SCSI disk in the VHD file.
>
> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
> IDE and this is the reason for his remark. If that is really the case
> I don't know since I have not used HyperV myself, only VPC2007 and
> VS2005.
>
> Whatever the host uses to store the VHD file is completely irrelevent;
> to the host the VHD is just another data file and can be stored in any
> way useful for the host.
>
> --
>
> Bo Berglund (Sweden)

Yep, in Hyper-V the boot disk in the guest must be IDE. If you have
been booting from SCSI under Virtual Server, change it to boot from IDE
before you move it. It is pretty painless to do it then but painful to do it
later!

On Wed, 25 Jun 2008 09:14:33 +0200, Bo Berglund wrote:

> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
> IDE and this is the reason for his remark. If that is really the case
> I don't know since I have not used HyperV myself, only VPC2007 and
> VS2005.

A clarification here. In VPC _all_ virtual disks need to IDE, not just the
boot disk. VPC does not support virtual SCSI at all. In Hyper-V the boot
disk must be IDE but any other disks can be SCSI.

--
Paul Adare
http://www.identit.ca
The Geeks shall inherit the earth!

Thanks guys. I think this clears it up. I was under the impression that
the bare metal install of HyperV needed to be on an IDE boot disk, which
wouldn't make sense if HyperV is loaded bare metal to servers.

Do you know if HyperV supports some of the load balancing features like Xen
and Vmware's Vmotion features if you have 2 phsyical HyperV servers?

Thanks,

Mike


"Paul Adare" <pkadare@xxxxxx> wrote in message
news:19mrks6fsa4ac.n3xtyszsdno9$.dlg@xxxxxx

> On Wed, 25 Jun 2008 09:14:33 +0200, Bo Berglund wrote:
>

>> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
>> IDE and this is the reason for his remark. If that is really the case
>> I don't know since I have not used HyperV myself, only VPC2007 and
>> VS2005.

>
> A clarification here. In VPC _all_ virtual disks need to IDE, not just the
> boot disk. VPC does not support virtual SCSI at all. In Hyper-V the boot
> disk must be IDE but any other disks can be SCSI.
>
> --
> Paul Adare
> http://www.identit.ca
> The Geeks shall inherit the earth!

I currently have a VM running under Virtual Server 2005 booting from a SCSI
disk and I want to move it to Hyper-V. To change it to IDE do I just
configure the VHD attachment from SCSI to Primary Channel (0)?

Thanks,

John

"Bill Grant" <not.available@xxxxxx> wrote in message
news:OegiAlp1IHA.2068@xxxxxx

>
>

>> He was talking about the virtual hard disk. When you build a virtual
>> machine you use a virtual hard disk which is physically stored as a
>> file on the *host* system with the extension VHD.
>> On VPC2007 such virtual disks are always emulated IDE disks, but on
>> Virtual Server 2005 you can choose to use eiter an emulated IDE or an
>> emulated SCSI disk in the VHD file.
>>
>> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
>> IDE and this is the reason for his remark. If that is really the case
>> I don't know since I have not used HyperV myself, only VPC2007 and
>> VS2005.
>>
>> Whatever the host uses to store the VHD file is completely irrelevent;
>> to the host the VHD is just another data file and can be stored in any
>> way useful for the host.
>>
>> --
>>
>> Bo Berglund (Sweden)

>
> Yep, in Hyper-V the boot disk in the guest must be IDE. If you have
> been booting from SCSI under Virtual Server, change it to boot from IDE
> before you move it. It is pretty painless to do it then but painful to do
> it later!
>
>

Before you try to migrate it, set the vm to boot from IDE, not from SCSI.
You don't have to make any changes to the vhd.

"John" <john_corangamite@xxxxxx> wrote in message
news:OltPEoQ2IHA.4672@xxxxxx

> I currently have a VM running under Virtual Server 2005 booting from a
> SCSI disk and I want to move it to Hyper-V. To change it to IDE do I just
> configure the VHD attachment from SCSI to Primary Channel (0)?
>
> Thanks,
>
> John
>
> "Bill Grant" <not.available@xxxxxx> wrote in message
> news:OegiAlp1IHA.2068@xxxxxx

>>
>>

>>> He was talking about the virtual hard disk. When you build a virtual
>>> machine you use a virtual hard disk which is physically stored as a
>>> file on the *host* system with the extension VHD.
>>> On VPC2007 such virtual disks are always emulated IDE disks, but on
>>> Virtual Server 2005 you can choose to use eiter an emulated IDE or an
>>> emulated SCSI disk in the VHD file.
>>>
>>> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
>>> IDE and this is the reason for his remark. If that is really the case
>>> I don't know since I have not used HyperV myself, only VPC2007 and
>>> VS2005.
>>>
>>> Whatever the host uses to store the VHD file is completely irrelevent;
>>> to the host the VHD is just another data file and can be stored in any
>>> way useful for the host.
>>>
>>> --
>>>
>>> Bo Berglund (Sweden)

>>
>> Yep, in Hyper-V the boot disk in the guest must be IDE. If you have
>> been booting from SCSI under Virtual Server, change it to boot from IDE
>> before you move it. It is pretty painless to do it then but painful to do
>> it later!
>>
>>

>

If you are talking about the movement of guests between physical hosts, then
yes. Hyper-V has what is called Quick Migration and it works in conjunction
with Windows Server 2008 failover clustering. Not really load balancing,
but fault-tolerance in case of the loss of a physical server or if you need
to do maintenance on a particular server. You can migrate the guest to a
different host. This would however require that you are connected to some
shared storage between physical hosts. Here is a post from the
Virtualization Team.

http://blogs.technet.com/virtualizat...on-part-1.aspx

--
Rob McShinsky
http://www.virtuallyaware.net

"Mike" <nospam@xxxxxx> wrote in message
news:%23ZDJ9zt1IHA.4704@xxxxxx

> Thanks guys. I think this clears it up. I was under the impression that
> the bare metal install of HyperV needed to be on an IDE boot disk, which
> wouldn't make sense if HyperV is loaded bare metal to servers.
>
> Do you know if HyperV supports some of the load balancing features like
> Xen and Vmware's Vmotion features if you have 2 phsyical HyperV servers?
>
> Thanks,
>
> Mike
>
>
> "Paul Adare" <pkadare@xxxxxx> wrote in message
> news:19mrks6fsa4ac.n3xtyszsdno9$.dlg@xxxxxx

>> On Wed, 25 Jun 2008 09:14:33 +0200, Bo Berglund wrote:
>>

>>> Apparently like the VPC2007 HyperV needs the *guest* boot disk to be
>>> IDE and this is the reason for his remark. If that is really the case
>>> I don't know since I have not used HyperV myself, only VPC2007 and
>>> VS2005.

>>
>> A clarification here. In VPC _all_ virtual disks need to IDE, not just
>> the
>> boot disk. VPC does not support virtual SCSI at all. In Hyper-V the boot
>> disk must be IDE but any other disks can be SCSI.
>>
>> --
>> Paul Adare
>> http://www.identit.ca
>> The Geeks shall inherit the earth!

>