Virtualization

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Hyper-V 2019 - Guest VMs shutdown unexpectedly

    When the host server shuts down, a bug in which guest VMs are not automatically shut down occurs in Windows 10 1809 or Windows Server 2019.
    It is also a topic in the forum.
    Please solve this bug as soon as possible.

    https://social.technet.microsoft.com/Forums/en-US/e8c45a15-0b9a-4b2c-ae2a-c546eadbcf41/hyperv-2019-guest-vmamp39s-shutdown-unexpectedly?forum=winserverhyperv

    54 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Volume 100% on reconnect always

    Using vmconnect.ext to connect to guest. Volume in guest is always preset to 100% which is exremely annoying. Volume should have a custom preset or same like host.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Full screen on dual monitor does not restore correctly

    On Windows Server 2019 we have exactly this issue: https://social.technet.microsoft.com/Forums/en-US/c95e831d-36ae-4307-b3fd-a9daac6b5790/full-screen-on-dual-monitor-does-not-restore-correctly?forum=win10itprovirt

    Solution in this thread was mentioned to change the WDDM settings in gpedit. This does not fix it in our case. Neither on Windows 10 and not on Windows 8.1 guests as there is no such setting in gpedit in Windows 8.1.
    We are using vmconnect.exe to connect toguest with 2 monitors. Both monitors are enabled in enhanced session. Minimizing leads to the issue that monitors are only restored on one monitor not on both. Additionally restoration has errors as scrollbars are being displayed and clicking on icons does not…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. Host custom DPI scaling breaks Modern UI in guests

    We are running Windows Server 2019 with Windows 8.1 guest.
    Custom scaling on host ist set to 130% which is perfect setting for our eyes to work on computer screen all day.
    According to this blog post https://blogs.msdn.microsoft.com/virtualpcguy/2016/06/23/hyper-v-ui-updates-for-high-dpi/ in enhanced session the guest gets all dpi information from the host.
    This needs to be fixed so we can revert to custom scaling again.
    However the modern ui does not scale correctly. Start screen, charms bar and settings pages are way too big. Apps cannot be started, error message is "This app can’t open. The screen resolution is too…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. VSS Hyper-V VM bug

    There is a bug, uncovered when using Veeam backup software which they describe as -

    "Application-aware processing of Active Directory domain controllers running on guest OS other than Windows Server 2016 fails with the “Failed to create VM recovery checkpoint” error (32770). This is a Hyper-V 2016 issue that Microsoft is planning to address in the future update."

    Any news on a fix for this would be great.

    14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Hyper-V CimSession Caching Bug

    The Server 2016 Hyper-V module caches CimSessions, presumably to make queries for related entities faster. The problem is that it also caches explicitly provided CimSessions that it does not own the lifetime of. So, if you ever use a CimSession with a Hyper-V cmdlet, then close that session, Hyper-V will try to use that disposed CimSession for any future interaction with the host in question. This is wrong, you can't cache objects with a lifetime you don't control without at least handling the case when that lifetime has been ended by the actual owner of the object.

    Repro:
    $someHyperVServer =…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add-VMGroupMember does not work

    Add-VMGroupMember does not seem to work as described in https://technet.microsoft.com/en-us/itpro/powershell/windows/hyper-v/add-vmgroupmember
    Just do
    $vm = Get-VM -Name "ABC"
    Add-VMGroupMember -Name "XYZ" -VM $vm

    Add-VMGroupMember : The operation failed.
    At line:1 char:1
    + Add-VMGroupMember -Name "CrmDBClu" -VM $vm -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [Add-VMGroupMember], Virtualizatio 
    

    nException

    + FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.A 
    

    ddVMGroupMember

    PowerShell version: 5.1.14393.1480
    Windows Server 2016

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Windows Server 2016 as Hyper-V Guest: Successfully Installed, but then RDP closes itsefl, hyper-v connect just black screen

    Windows Server 2016 as Hyper-V Guest: Successfully Installed, but then RDP closes itsefl, hyper-v connect just black screen

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base