A world first, I think: 14393 guest 2008R2 host, possible !!!!

Discussion in 'Virtualization' started by T-S, Dec 3, 2016.

  1. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    #1 T-S, Dec 3, 2016
    Last edited: Dec 4, 2016
    People playing with hyper V are surely aware that MS backs just one version of guests after the host's one.

    So theoretically on Hyper-V 2008R2 you can run just Win 8.0 VMs, on Win 8/2012 hosts you can run just Win 8.1/2012R2 guests and so on.

    Practically on 2008R2 hosts you can run w/o major problems any VM from Win 8.0 to W10 10586 (and Server 2016 TP4).

    Anyway W10 anniversary and Server 2016 RTM won't run at all.

    Now happened tath I needed to run a Server 2016 RTM inside a Server 2008R2, and although TP4 still runs fine and w/o any major problem, the RTM version is obviously the preferred choice.

    So I spent a couple of hours one week to prove my theory, and then a week to perfect a method to make it simple to implement:

    In short my guess was that the problem was not the kernel or any other fundamental component of builds 14393, but the bundled Hyper-V itself, so I started to test an image with HyperV totally removed from it, and it worked!

    Then I narrowed down further the culprit to the guest integration components alone, finally I ended to identify THE single, tiny, file responsible of the boot hang of the Anniversary VMs.

    That file is HyperVideo.sys :mad: and it is the VGA driver who takes care of the emulated VGA for the Hyper-V consolle alone (i.e. not the remote desktop video).

    In short you can replace it with the one taken from anything from 9600 to 10586, but you can also remove it altogether from boot.wim and install.wim, and everything will still work as usual.

    The VGA performance of the Hyper V consolle are poor anyway, so even if you remove the file instead of replacing it, practically nothing changes. Practically it's just a 26KB "fake" driver.

    Either way, Win 10 anniversary will work nicely and rock solid, w/o any other problem, on 2008R2 hosts.

    I'm sure that the week spent on it will help a lot of people unwilling to upgrade a perfectly working server just to run a W10/2016 guest (core versions are affected as well).

    So enjoy more years of life to your 2008R2 server thanks to a stupid 26KB file killed or replaced :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    2,814
    1,333
    90
    Thanks for the info, but the 2008R2 server is ancient. I suppose if you just like it, but in software terms it is really out of date. Sort of like running Windows 7 these days. :confused:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    #3 T-S, Dec 4, 2016
    Last edited: Dec 4, 2016
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120

    Stop posting those stupid sentences.

    There is not ancient SW. There is SW that does what you need and software that doesn't.

    For the record, that 2008 R2 server is acting as WMC server/HTPC, as a Primary Domain Controller, as a centralized backup server and also, thanks to HV is running nicely the deduplication on its storage.

    Also given it's classified as an "home" product you can install on it most standard antivirus, and partitioning programs which are usually forbidden on server.

    If you have a better and cheaper solution I'm all ears :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. dhjohns

    dhjohns MDL Guru

    Sep 5, 2013
    2,814
    1,333
    90
    Using this software is akin to using Windows 3.0 instead of Windows XP! It is just as old.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Myrrh

    Myrrh MDL Expert

    Nov 26, 2008
    1,387
    491
    60
    Thanks for this. Could have saved me a couple hundred bucks, as the solution I chose was to move the hard drive array from a Core 2 Q6600 machine to a system I bought on ebay containing a Xeon W3690 (pretty much equivalent to a Core i7-990X)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. liliactr

    liliactr MDL Member

    Sep 3, 2009
    141
    61
    10
    Thank you for this great discovery. Unfortunately i do not see thanks button anymore.
     
  8. 3sidedcube

    3sidedcube MDL Member

    Oct 1, 2009
    114
    12
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. KNARZ

    KNARZ MDL Addicted

    Oct 9, 2012
    865
    447
    30
    wvmbusvideo.inf is the driver. I'm pretty sure it's inbox-flaged so not removeable unless someone patches the check (I got that for W7) it's in the DISM Provider: DmiProvider.dll
    Would be happy if someone would patch it anyway besides from this issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    #10 T-S, Dec 22, 2016
    Last edited: Dec 25, 2016
    (OP)
    That's the inf not the driver.
    Whaterver... Yepp... this looks as one of those drivers that needs the double signature check (aka you can't load another one even with the driver signature enforcement disabled). In that very case we are lucky because the driver does practically nothing of useful.

    But if were something more important like the scsi or network driver we were out of luck:mad:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. KNARZ

    KNARZ MDL Addicted

    Oct 9, 2012
    865
    447
    30
    are you kidding? the inf is indeed not the sys, for sure. but a driver is defined by it's inf - so in my definition inf is a driver.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    3,384
    4,921
    120
    How about:

    sys = driver

    inf = installer
     
  13. KNARZ

    KNARZ MDL Addicted

    Oct 9, 2012
    865
    447
    30
    nope. inf is the driver, as there are also null-drivers that are just based on inf and cat.
    but let us go forward and come over this smart ass stuff.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120

    No. Period.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    Exactly. In that case the driver is "null", still not the inf.

    I agree. no one will die if you stick with the wrong definition. ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    5,562
    12,987
    180
    Bit Off-topic but interesting

    There are even exotic drivers file extensions: For example Virtualbox is loading kernel drivers with an extension of .r0
     
  17. biorpg

    biorpg MDL Novice

    Jul 18, 2010
    22
    8
    0
    So you mean to say 2008R2 is more capable and lighter weight than the current offering? Please provide details.
     
  18. burnix

    burnix MDL Novice

    Jan 4, 2011
    34
    2
    0
    T-S. I cannot mp you. But in the first post you mean that if i replace in boot ans install wim the sys file i can run all os on 2008r2 ????

    Thank you for your reply (im going to use the search option) :)