Anonymous

My feedback

  1. 23 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Virtualization » Hypervisor  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 1,905 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    265 comments  ·  General Feedback » Misc  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Also, virtualbox supports nested VMS "exclusively" on AMD chips.. in windows. Release notes indicate that it can also use Hyper-V as the hypervisor. Unsure if that's a potential workaround until MS resolves the issue but it's certainly worth a try.
    https://docs.oracle.com/cd/E97728_01/F12469/html/nested-virt.html

    An error occurred while saving the comment
    Anonymous commented  · 

    Opened a ticket with MS and AMD. MS responded through our partner channel with a simple statement of "we're working on it". AMD has yet to respond but it definitely isn't their issue as it's supported on most every other hypervisor. This is silly.
    Also, there's a competing thread at AMD's forums. I recommend bombarding them as well.
    https://community.amd.com/thread/224825

    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    So, just plunked the cash down for a 2990wx and found out most of the drivers don't support server 2019, there's no nested virtualization, and MS still hasn't fixed the kernel scheduler bugs. This isn't a new platform anymore and it has been around for around two years. AMD's SVM is older than that. There is absolutely no excuse for this unless MS is intentionally driving business to Intel.

Feedback and Knowledge Base