Getting started with Hyper-V

I plan to build my own 2008 Server/Hyper-V system and will not be using one
of the tested Dell or HP systems from the release notes and could use some
pointers as to my assumnptions and answers to a few questions.

Some getting started with Hyper-V assumptions. Please tell me if I am off
base here.

1. Any recent Intel quad core processor has the needed x64 architecture with
hardware assisted virtualization and data execution protection needed to run
Hyper-V.
2. Most motherboard/BIOS combinations that support an Intel quad core will
run 2008 Server and Hyper-V. If not please make some suggestions either for
or against any specific boards.
3. I will be able to use my Vista system to RDP to the 2008 Server to create
and manage the VM's.
4. My Vista machine will be able to RDP to any of the VM's once they are
running.

And some getting started questions:

1. Will my MSDN Empower subscription eventually include at least the
"standard" production version of 2008 Server and Hyper-V when released?
2. Will it be possible to somehow upgrade the 2008 Server RC1 and Hyper-V
beta bits to production so I can at least keep using the VM's I create till
then? Likely upgrade scenario would be appreciated.
3. I know XP Pro and Vista Ultimate are not officially supported under
Hyper-V now but has anyone tried to see if they actually work? I presume
[seriously] that it was a MSFT priority to get Linux running first!
4. Is there a means to create a VM from a physical bootable disk of an XP
Pro or Vista Ultimate system from a local or network drive?
5. I read about SCSI support from the VM handled almost native by Hyper-V
but did not understand well what was being explained. Are SCSI disks somehow
supported more efficiently than SATA 3G disks for the VM's?
6. Does Hyper-V support VT-d [Virtualization Technology for Directed I/O]
and do most recent motherboards/BIOS combinations support this OK?

Thanks so much for any and all pointers to getting this project started,

--
Dave

RE: Getting started with Hyper-V

Sorry this web mail posted without final verification from me and don't think
this is the appropriate newsgroup but if there is an MSDN "managed" newsgroup
that is please advise. 'Course if you have suggestions as to these issues
would be happy to hear them as I am setting this up for general .Net
development and testing. Thanks.
--
Dave


"CodeSlinger" wrote:

> I plan to build my own 2008 Server/Hyper-V system and will not be using one
> of the tested Dell or HP systems from the release notes and could use some
> pointers as to my assumnptions and answers to a few questions.
>
> Some getting started with Hyper-V assumptions. Please tell me if I am off
> base here.
>
> 1. Any recent Intel quad core processor has the needed x64 architecture with
> hardware assisted virtualization and data execution protection needed to run
> Hyper-V.
> 2. Most motherboard/BIOS combinations that support an Intel quad core will
> run 2008 Server and Hyper-V. If not please make some suggestions either for
> or against any specific boards.
> 3. I will be able to use my Vista system to RDP to the 2008 Server to create
> and manage the VM's.
> 4. My Vista machine will be able to RDP to any of the VM's once they are
> running.
>
> And some getting started questions:
>
> 1. Will my MSDN Empower subscription eventually include at least the
> "standard" production version of 2008 Server and Hyper-V when released?
> 2. Will it be possible to somehow upgrade the 2008 Server RC1 and Hyper-V
> beta bits to production so I can at least keep using the VM's I create till
> then? Likely upgrade scenario would be appreciated.
> 3. I know XP Pro and Vista Ultimate are not officially supported under
> Hyper-V now but has anyone tried to see if they actually work? I presume
> [seriously] that it was a MSFT priority to get Linux running first!
> 4. Is there a means to create a VM from a physical bootable disk of an XP
> Pro or Vista Ultimate system from a local or network drive?
> 5. I read about SCSI support from the VM handled almost native by Hyper-V
> but did not understand well what was being explained. Are SCSI disks somehow
> supported more efficiently than SATA 3G disks for the VM's?
> 6. Does Hyper-V support VT-d [Virtualization Technology for Directed I/O]
> and do most recent motherboards/BIOS combinations support this OK?
>
> Thanks so much for any and all pointers to getting this project started,
>
> --
> Dave

RE: Getting started with Hyper-V

Hi Dave,

Welcome to MSDN Managed Newsgroup!

As you have already noticed, this is not the best place to discussion
questions about Windows Server 2008.

Please note currently MSDN Managed Newsgroup support service doesn't cover
beta software and non development related questions, also due to resource
restriction we currently don't cover all developer tools/languages. You can
find complete list of supported managed newsgroups here:
http://msdn.microsoft.com/subscriptions/managednewsgroups/li st.aspx

I recommend you to post your question in following forums:

#TechNet Forums >> Windows Server 2008
http://forums.microsoft.com/TechNet/default.aspx?ForumGroupI D=161&SiteID=17

For questions about MSDN subscription (downloads, account, etc.), please
kindly use the contact information on the MSDN subscriptions portal:

http://msdn2.microsoft.com/en-us/subscriptions/default.aspx

Thanks for your understanding.


Sincerely,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
For MSDN subscribers whose posts are left unanswered, please check this
document: http://blogs.msdn.com/msdnts/pages/postingAlias.aspx

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications. If you are using Outlook Express/Windows Mail, please make sure
you clear the check box "Tools/Options/Read: Get 300 headers at a time" to
see your reply promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx .
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.