다음을 통해 공유

More on Storage Options for Windows Server 2008 Hyper-V

  • 아티클

As I mentioned in a previous blog post, you can expose storage to a Hyper-V guest in many different ways.

After getting some feedback to that initial post, there are two frequent comments that I wanted to address.

You can boot a Hyper-V guest from an iSCSI LUN

I wanted to highlight that you can boot a Hyper-V child partition (guest) from an iSCSI LUN. To do that, you need to expose that LUN to the parent partition (host), make sure the LUN is set as an offline disk in the host and then use the passthrough option to expose the disk to the guest as IDE (ATA).

With that, you can successfully boot a Hyper-V guest from an iSCSI LUN. In fact, that works just the same for a fibre-channel LUN or SAS disks.

Here’s what the configuration of that virtual disk would look like:

Hyper-V Storage 2

There are also third-party solutions that will that will allow a Hyper-V guest to boot from an iSCSI LUN exposed directly to the guest. You can check a product from EmBoot that does exactly that at https://www.emboot.com.

How about a picture?

In the blog post, I had a table showing the different storage options, but someone pointed out that a picture would be a lot more useful than a table. So, here it is:

Hyper-V Storage 3

In the picture you see the different ways to expose a disk to a Hyper-V parent partition (host) and child partition (guest):

  • C: = Using a VHD file on a directly attached disk (X:) on the host
  • D: = Using passthrough to a directly attached disk on the host
  • E: = Using a VHD file on a SAN LUN mounted as a volume (Y:) on the host
  • F: = Using passthrough to a SAN LUN exposed to the host
  • G: = Using an iSCSI LUN exposed directly to the guest

Note that, for the first four options, the disk can be exposed to the guest as either SCSI or IDE (ATA), regardless of the physical disk interface used on the host. Also note that the last of the five options above is only available for iSCSI SANs, not fibre-channel.

For all the details of what you can and cannot do in each scenario, check the original post at:
https://blogs.technet.com/josebda/archive/2008/02/14/storage-options-for-windows-server-2008-s-hyper-v.aspx

Comments

  • Anonymous
    January 01, 2003
    Jose pinged a great email across a discussion list a few days back, with this diagram in, which really
  • Anonymous
    January 01, 2003
    I spent last week in Orlando, Florida, working at the Microsoft booth in the Storage Networking World.
  • Anonymous
    January 01, 2003
    (updated 7/23/08) My current project involves being the only dedicated technical resource on the Virtualization
  • Anonymous
    January 01, 2003
    PingBack from http://blogs.technet.com/josebda/archive/2008/02/14/storage-options-for-windows-server-2008-s-hyper-v.aspx
  • Anonymous
    January 01, 2003
    Hyper-V is here! As you can confirm on the press release linked below, the final release of Windows Server
  • Anonymous
    January 01, 2003
    Lately it's been very quiet on my blog. There are a couple of things to that. First and foremost there
  • Anonymous
    January 01, 2003
    Hello, this is Norm. I have been tinkering with Hyper-V, which I loaded onto a Dell Optiplex 745 machine.
  • Anonymous
    January 01, 2003
    I will be working at the Microsoft booth in the Storage Network World next week in Orlando, Florida.
  • Anonymous
    January 01, 2003
    There are many ways to implement Windows Server Failover Clustering with Hyper-V. I could actually find
  • Anonymous
    January 01, 2003
    There is a lot of information regards Hyper-V and storage options that is scattred in blog post. I aim
  • Anonymous
    January 01, 2003
    (updated 9/26/08) My current project involves being the only dedicated technical resource on the Virtualization