2

After a few discussions (here, here, and here), I am still unable to create a simple VM that will be used as a fileserver hosted on my Hyper-V box. I have created a fixed 700GB SCSI drive (.vhd file), as I have learned an IDE drive of this size is not possible. Not to sound too cynical, but its blown me away at how much trouble its been to create a large amount of space and start using it.

What is the best way to create a fileserver with a drive of this size hosted on Hyper-V Server 2008, and how can I get it going???

Inclusion of OS, driver, integration tools etc, anything you feel is required would be greatly appreciated.

Extra information

  • I am using the stand-alone version of Hyper-V server, and not Windows Server 2008.
  • I have tried loading the Linux Integration Tools (linked in the comments of the last link above) onto a SUSE 11 VM and the installation fails, the machine cannot see the vhd at all.

Thanks very much,

Community
  • 1
barfoon
  • 750
  • 3
  • 14
  • 29
  • Pass-through disk for file server data I'd say... – Oskar Duveborn Sep 18 '09 at 09:41
  • What is a pass-through disk? – barfoon Sep 18 '09 at 17:32
  • a pass-through disk is where you allow direct access to the physical drive for your VM - pros and cons are discussed elsewhere on SF :) ..eg http://serverfault.com/questions/57575/attach-local-disk-to-a-vm-in-vmware-esxi || http://serverfault.com/questions/30720/vmware-server-2-0-physical-disks – warren Sep 28 '09 at 12:35
  • alright cool so how do i make/use one? – barfoon Sep 29 '09 at 01:17

3 Answers3

1

I would assume that this is issue with drivers.

However, IDE has same size limit as SCSI on Hyper-V. Usually IDE disks are a LOT easier to use in Linux and that solves problems with visibility in most cases. In your case that is a problem since you use first Hyper-V Server 2008 release.

If you can, I would recommend moving to Hyper-V Server 2008 R2 which will allow you to have big disk on IDE interface and thus avoid any driver issues with Linux and SCSI.

P.S. You can just disconnect already existing VHD and re-attach it as IDE since format is not dependent on interface.

Josip Medved
  • 1,674
  • 2
  • 18
  • 18
  • Reattached it as IDE, comes up as 127GB in YasT – barfoon Sep 18 '09 at 00:41
  • http://www.virtualizationadmin.com/articles-tutorials/general-virtualization-articles/chapter-2-hyper-v-overview.html "Virtual hard disks connected via IDE cannot exceed 127 GB. Virtual hard disks connected via SCSI cannot exceed 2040 gigabytes." – barfoon Sep 18 '09 at 00:45
  • Your link: "Applies To: Windows Server 2008, Windows Server 2008 R2" – barfoon Sep 18 '09 at 00:46
  • @berfoon: I seems that this limitation is specific for original Hyper-V Server 2008. I tried attaching 700 GB disk to virtual machine under Hyper-V Server 2008 R2 and it recognizes it without problems. I cannot check what happens with original Hyper-V since I upgraded all machines. – Josip Medved Sep 18 '09 at 09:06
0

I'm not sure what you're having a problem with, we have a 700+ gb vhd running BackupPC on CentOS - was on Virtual Server 2005, then Hyper-V, then migrated to another platform (no technical problem with either Microsoft solution though).

I don't remember doing anything particularly complex to make it work. We created a boot disk that was smaller, perhaps 32gb - installed Linux there, additions, etc. then after everything worked added an additional disk.

Do you have any particular errors you can post?

LVM would be handy in the future as warren said but I don't think that is related to your HyperV issue any.

Steve Radich-BitShop.com
  • 573
  • 3
  • 7
0

You might also consider creating several smaller virtual disks (which might even be on different drives), and then use LVM inside Linux.

This would also allow you to add to the size later easily :)

warren
  • 17,829
  • 23
  • 82
  • 134
  • I do not want to have to manage 5-6 disks to get the same amount of space. Surely there must be a way to use the 700GB VHD? – barfoon Sep 28 '09 at 16:09