none
IDE HDD Size 127 GB in HyperV 2008R2 + CentOS 6.2 + Linux Integration Services 3.2

    Question

  • Hello everybody,

    on our HyperV (Windows Server 2008R2) i set up a new VM with a 500 GB HD (IDE).

    After Installing CentOS 6.2 only 127 GB are visibel in Linux. I installes Integration Components too but nothing changes.

    I searched the internet and forums but i found no solution.

    When checking the integration components i get:

    =============================================================

    /sbin/modinfo hv_vmbus

    filename:       /lib/modules/2.6.32-220.el6.x86_64/weak-updates/microsoft-hyper-v/hv_vmbus.ko
    version:        3.2
    license:        GPL
    srcversion:     C6A2763EE7CA2A246E31600
    alias:          acpi*:VMBus:*
    alias:          acpi*:VMBUS:*
    depends:
    vermagic:       2.6.32-71.el6.x86_64 SMP mod_unload modversions
    parm:           vmbus_loglevel:int
    =============================================================

    /sbin/modinfo hv_netvsc
    filename:       /lib/modules/2.6.32-220.el6.x86_64/weak-updates/microsoft-hyper-v/hv_netvsc.ko
    alias:          vmbus:635161f83edfc546913ff2d2f965ed0e
    description:    Microsoft Hyper-V network driver
    version:        3.2
    license:        GPL
    srcversion:     A756A543F127C8F13F2CFA5
    depends:        hv_vmbus
    vermagic:       2.6.32-71.el6.x86_64 SMP mod_unload modversions
    parm:           ring_size:Ring buffer size (# of pages) (int)

    =============================================================

     /sbin/modinfo hv_storvsc
    filename:       /lib/modules/2.6.32-220.el6.x86_64/weak-updates/microsoft-hyper-v/hv_storvsc.ko
    alias:          vmbus:32264132cb86a2449b5c50d1417354f5
    alias:          vmbus:d96361baa104294db60572e2ffb1dc7f
    description:    Microsoft Hyper-V virtual storage driver
    version:        3.2
    license:        GPL
    srcversion:     389EF689CCD93B047F084DF
    depends:        hv_vmbus
    vermagic:       2.6.32-71.el6.x86_64 SMP mod_unload modversions
    parm:           storvsc_ringbuffer_size:Ring buffer size (bytes) (int)

    =============================================================

    /sbin/modinfo hv_blkvsc
    ERROR: modinfo: could not find module hv_blkvsc

    =============================================================

    /sbin/modinfo hv_utils
    filename:       /lib/modules/2.6.32-220.el6.x86_64/weak-updates/microsoft-hyper-v/hv_utils.ko
    alias:          vmbus:e7f4a0a9455a964db8278a841e8c03e6
    alias:          vmbus:394f16571591784eab55382f3bd5422d
    alias:          vmbus:30e62795aed07b49adcee80ab0175caf
    alias:          vmbus:31600b0e13523449818b38d90ced39db
    license:        GPL
    version:        3.2
    description:    Hyper-V Utilities
    srcversion:     76B93D2BF71B3CFE04ACB98
    depends:        hv_vmbus
    vermagic:       2.6.32-71.el6.x86_64 SMP mod_unload modversions

    =============================================================

    Perhaps the missing hv_blkvsc is the problem? But how to get it work? I also read that blkvsc is now integrated in storsvc - is that right, and i dont need blkvsc?

    How can i use the full space of 500 GB unter Linux?

    Greetings

    Juergen

    Sunday, March 18, 2012 3:36 PM

Answers

  • This is a known issue. You can work around this by using LVM and expanding your volumes after the LIS drivers are installed.

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

    Tuesday, March 20, 2012 4:52 PM
    Owner

All replies

  • Hi Jürgen,

    AFAIK it's a restriction for IDE HDDs under Hyper-V. Only 128 GByte can be seen by the VM. A possible workaround is to have two HDDs in your VM: an IDE HDD (a small one for OS) and a SCSI HDD, the last can be greater then 128 GByte of size.

    Please look into this thread: http://social.technet.microsoft.com/Forums/en-ZA/winserverhyperv/thread/f5784096-808b-4a66-9bfd-fecb0a0946cc

    Regards,

    Hermann Maurer

    Monday, March 19, 2012 8:52 AM
  • Hi Hermann,

    thank you for your reply.

    I read the thread you linked but i cant find a definite answer. On one hand it seems to be a limitation on 127GB
    on the other hand people say this limitation does not exist in HyperV and only affects VPC. Whats right?

    Would this limitation on 127GB at IDE still remain if i install W2K8 instead of CentOS?

    At least, i think i will have to do the workaround.

    Regards,

    Juergen

    Monday, March 19, 2012 9:21 AM
  • Hello,

    We can reproduce this on our installations, using a test-VM with a 200 GB IDE drive.

    Without Integration Components, we see

       % fdisk -l /dev/sda
    
       Disk /dev/sda: 136.9 GB, 136899993600 bytes
       255 heads, 63 sectors/track, 16643 cylinders
       Units = cylinders of 16065 * 512 = 8225280 bytes
       Sector size (logical/physical): 512 bytes / 512 bytes
       I/O size (minimum/optimal): 512 bytes / 512 bytes
       Disk identifier: 0x000c4803
    
          Device Boot      Start         End      Blocks   Id  System
       /dev/sda1   *           1         131     1048576   83  Linux
       Partition 1 does not end on cylinder boundary.
       /dev/sda2             131       16644   132641792   8e  Linux LVM
    
    When we add IC 3.2, we see
       % fdisk -l /dev/sda
    
       Disk /dev/sda: 214.7 GB, 214748364800 bytes
       255 heads, 63 sectors/track, 26108 cylinders
       Units = cylinders of 16065 * 512 = 8225280 bytes
       Sector size (logical/physical): 512 bytes / 512 bytes
       I/O size (minimum/optimal): 512 bytes / 512 bytes
       Disk identifier: 0x000c4803
       
          Device Boot      Start         End      Blocks   Id  System
       /dev/sda1   *           1         131     1048576   83  Linux
       Partition 1 does not end on cylinder boundary.
       /dev/sda2             131       16644   132641792   8e  Linux LVM
    
    This causes problem when we use Anaconda to install the VM, as the installation kernel does not have the IC's loaded, and the partition table is "truncated". cheers, Jan
    Tuesday, March 20, 2012 11:37 AM
  • This is a known issue. You can work around this by using LVM and expanding your volumes after the LIS drivers are installed.

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

    Tuesday, March 20, 2012 4:52 PM
    Owner
  • Thanks Mike.

    Will this issue be addressed? Also: is there a list of known issues w/ Integration Components that we can consult?

                thanks, Jan

    Tuesday, March 20, 2012 10:35 PM
  • I have the same issue and it's just an 80GB drive. Great job, MS.

    I mean seriously, linux on Hyper-V just never works, never ever, there is always an issue...

    ...is there any hope that MS will ever manage to release something that just WORKS, out of the box, liked a normal (=non-MS) product?

    Friday, March 23, 2012 2:47 AM
  • You should not see the issue on a drive that is less than 127 GB. The root cause of the bug has to do with the ATA emulator code and its support for volumes that are larger than 127 GB.

    sz.levi, what other issues are you seeing that are preventing you from getting expected behaviour from Linux on Hyper-V?


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

    Tuesday, March 27, 2012 5:32 PM
    Owner