Windows 8 and 8.1 Forums


VMware or Windows 8 defect with HYPER-V

  1. #1


    Hafnarfjörður IS
    Posts : 4,377
    Linux Centos 7, W8.1, W7, W2K3 Server W10

    VMware or Windows 8 defect with HYPER-V


    Hi
    just testing W8 RP with HYPER-V. Seems that if you enable this VMware workstation no longer functions.

    I think from what I remember this worked OK in the Consumer preview.

    So is this a VMware or Ms bug -- I'd suspect it's VMware's bug because you could install VMware AFTER setting up your desired Windows 8 environment.

    Which is a pity since if it was an MS bug it would be on a fix list before RTM / Release candidate builds.

    Cheers
    jimbo
    Attached Thumbnails Attached Thumbnails hyper-v.png  

      My System SpecsSystem Spec

  2. #2


    Orbiting the Moon
    Posts : 2,975
    Windows 10 x64


    They cannot share VT-x from what I've found out.

    If you already run a virtualisation environment such as VMWare or VirtualBox (with 64-bit VMs only), they will no longer work. The reason is that the Hypervisor doesn't expose the VT-x extension to it's virtual machines (including your new root), and so other virtualisation products can't be ran with full effectiveness. The obvious workaround to this problem is to convert your VMWare/VirtualBox VMs to Hyper-V, and import them using the Hyper-V Manager.

    [...] By enabling Hyper-V on your machine, your root OS (which you use) will now run on top of a Hypervisor, which means it's essentially virtualised. It's not in the same sense as a virtual machine, as your OS will still have direct hardware access to essentials such as graphics cards for gaming etc.
    link:
    Windows 8 Web Browsing Freeze - WORKAROUND / FIX! - Latest General News - rudi visser, fresh development ideas

    Hope they will do something about this in the future or we'll have to choose sides.

    Cheers
    Hopachi
      My System SpecsSystem Spec

  3. #3


    Hafnarfjörður IS
    Posts : 4,377
    Linux Centos 7, W8.1, W7, W2K3 Server W10


    Quote Originally Posted by Hopachi View Post
    They cannot share VT-x from what I've found out.

    If you already run a virtualisation environment such as VMWare or VirtualBox (with 64-bit VMs only), they will no longer work. The reason is that the Hypervisor doesn't expose the VT-x extension to it's virtual machines (including your new root), and so other virtualisation products can't be ran with full effectiveness. The obvious workaround to this problem is to convert your VMWare/VirtualBox VMs to Hyper-V, and import them using the Hyper-V Manager.

    [...] By enabling Hyper-V on your machine, your root OS (which you use) will now run on top of a Hypervisor, which means it's essentially virtualised. It's not in the same sense as a virtual machine, as your OS will still have direct hardware access to essentials such as graphics cards for gaming etc.
    link:
    Windows 8 Web Browsing Freeze - WORKAROUND / FIX! - Latest General News - rudi visser, fresh development ideas

    Hope they will do something about this in the future or we'll have to choose sides.

    Cheers
    Hopachi
    Hi there
    the Hyper-V stuff is great - especially on a NON SERVER OS - but I NEED VMware as well for the foreseeable future.

    It might be that Ms is deliberately going out to hobble VMware . Could be a "business strategy".

    Incidentally does the same problem occur with VBOX -- haven't run VBOX so I can't say.

    s's strategy *might* work -since if I can get a SUSE 11.X system to work as a VM via HYPER-V I might just ditch VMware altogether - although VMware workstation has been great -- and now you can run vm's in the background like on a server the reason I was looking for an alternative has gone away.

    I don't want to have to run something like Esxi on a laptop.

    HYPER-V looked good on a decent 8GB intel i5 laptop. Pity about this glitch.

    cheers
    jimbo
      My System SpecsSystem Spec

  4. #4


    Orbiting the Moon
    Posts : 2,975
    Windows 10 x64


    Quote Originally Posted by jimbo45 View Post
    It might be that Ms is deliberately going out to hobble VMware . Could be a "business strategy".

    Incidentally does the same problem occur with VBOX -- haven't run VBOX so I can't say.
    That's a dirty move from MS if it's true.
    But yes it also occurs with VirtualBox (confirmed) and maybe Parallells and all of those trying to use VT-x.

    VMware always got very stable programs, they''ll never leave windows behind.

    I also like how the VM's in Hyper-V work.

    Let's hope they think about this issue.
      My System SpecsSystem Spec

  5. #5


    I have never been able to come to terms with Hyper-V. When you manage hypervisors which are not on a domain, from workstations that are on a domain, it's a real PITA to get everything working. It should be easy, just like the vmware client, but it isn't. You gotta jump through hoops, configured dcom stuff, etc. Bleh....everytime I look at Hyper V, I appreciate VMWare even more and it makes me forget about the high cost associated with VMWare. In my book, it's worth it.
      My System SpecsSystem Spec

  6. #6


    Posts : 1,308
    Windows 8 enterprise x64


    Quote Originally Posted by pparks1 View Post
    I have never been able to come to terms with Hyper-V. When you manage hypervisors which are not on a domain, from workstations that are on a domain, it's a real PITA to get everything working.
    This should not be an issue at all, when you run few Hyper-V host, you certainly don't want to run them outside a domain environment, especially if you use SCVMM to manage them.


    Quote Originally Posted by Hopachi View Post

    Let's hope they think about this issue.
    Again not a big issue , in production environment or in lab, you run only Hyper-V on the Server Host, their is no need to enable Hyper-V on the WS so you can use VMware WS.

    Jimbon, Hobachi, your issues come from the fact that you are using only 1 pc, throw in the game a dedicated Hyper-V host server and you are in business. I run all my Server OS on Hyper-V host and all my Client on VMware WS.
      My System SpecsSystem Spec

  7. #7


    Quote Originally Posted by area 66 View Post
    This should not be an issue at all, when you run few Hyper-V host, you certainly don't want to run them outside a domain environment, especially if you use SCVMM to manage them.
    In my case, my servers are in colocation facilities or remote data centers. My enterprise AD environment is NOT extended into these facilities. In these cases, if AD is required for anything, its a separate instance that is run in that environment, so my admin workstations and such are within a different domain...so the hassle certainly is there.
      My System SpecsSystem Spec

  8. #8


    Hafnarfjörður IS
    Posts : 4,377
    Linux Centos 7, W8.1, W7, W2K3 Server W10


    Quote Originally Posted by area 66 View Post
    Quote Originally Posted by pparks1 View Post
    I have never been able to come to terms with Hyper-V. When you manage hypervisors which are not on a domain, from workstations that are on a domain, it's a real PITA to get everything working.
    This should not be an issue at all, when you run few Hyper-V host, you certainly don't want to run them outside a domain environment, especially if you use SCVMM to manage them.


    Quote Originally Posted by Hopachi View Post

    Let's hope they think about this issue.
    Again not a big issue , in production environment or in lab, you run only Hyper-V on the Server Host, their is no need to enable Hyper-V on the WS so you can use VMware WS.

    Jimbon, Hobachi, your issues come from the fact that you are using only 1 pc, throw in the game a dedicated Hyper-V host server and you are in business. I run all my Server OS on Hyper-V host and all my Client on VMware WS.


    Hi there
    OK running it from a SERVER is another issue -- but then ask why did Ms offer this facility on a DESKTOP OS.

    I'm quite happy to have Ms say you need W8 server or whatever --but this was deliberately touted as a feature on a WORKSTATION OS and as such shouldn't interefere with currently installed applications.

    Jist my take on this -- at least MS should have stated in the W8 "sales spiel" that if you use HYPER-V you can't run another Virtualisation program.

    Cheers
    jimbo
      My System SpecsSystem Spec

  9. #9


    USA, Idaho
    Posts : 1,062
    Win 8, (VM win7, XP, Vista)


    If given a choice VMware is going to come in first all the time for me. I to used VM 8 in DP, but was surprised when it wouldn't work together with HYPER-V, thus HYPER-V got turned off. With all the VM player appliances I have it just seems smart to stay with VM 8.

    Also I like to have Win 7 running in a VM on my second monitor (of 3) all the time (use it for my MS Games that come in Win 7. Darn 8 doesn't have any).
    A good reason for having 16 gigs or more.
      My System SpecsSystem Spec

  10. #10


    Hafnarfjörður IS
    Posts : 4,377
    Linux Centos 7, W8.1, W7, W2K3 Server W10


    Hi there
    I'm actually trying it now on the "Non GUI" version of Windows 2012. Running this on a server is fine -- W7 / W8 VM's as well as w2003 server as a vm on HYPER-V is mega fine on this version of Windows 2012,

    cheers
    jimbo
      My System SpecsSystem Spec

VMware or Windows 8 defect with HYPER-V

Similar Threads
Thread Forum
Hyper V and VMWare on the same machine
Hi, I have many virtual machines in my VMWare Workstation install on Windows 7. I have now let Windows 8.1 lose on the bare metal of this machine as a dual booting system. I have enabled Hyper V on 8.1 to "play around with it and when I went to install VMWare the installer quit stating Workstation...
Virtualization
HYPER-V SERVER R2 (Esxi 5.5 needs PAID vCENTER - vmware)
Hi there. I LIKE the idea of a bare metal Hypervisor - I've tried Esxi (VMware) in the past and although it works it's a bit fiddly on what hardware it works on and there's no CLI for managing VM's --you have to do this with a separate machine using vCenter which USED TO BE FREE -- and now this...
Virtualization
Windows 8 Client Hyper-v verses VMWare Workstation 9
Hi I thought I would start a (impartial) discussion here as it would help me with it terms of how I might configure a new Windows 8 laptop. Ok, VMWare Worstation 9 was released on the 23rd August. As a freelance consultant I want to configure Windows 8 Pro to run multiple server virtual...
Virtualization
VMware Workstation 9 - VMware Player 5
Good news about VMs again. The latest VMware Workstation 9 brings a new UI and it's designed for Windows 8. Read about it here: VMware Announces VMware Workstation™ 9 Also VMware Player 5 is available for download....
Virtualization
Showstopper vmware and hyper-V incompatable
Hi everyone Found a mega show stopper here I MUST have VMware available on a laptop / workstation. If you enable HYPER-V on W8 then you can't start VMware I know if you use hyper-v you'll probably want it on a server - but on a WORKSTATION DEVELOPMENT OS I think people will be testing...
Virtualization
Fix for vmware 8.0 / vmware player 4.0 on w8 x-64
Hi all After a bit of googling found the fix This guy solved it -- works fine Now I can uset W8 x-64 on a Desktop with 16GB (I must have VMware working) Fix vmx86.sys error with Vmware workstation 7 and 8 | JB: Tech & Security Cheers jimbo
Virtualization
Install W8 in vmware workstation -- you must use version 8 of vmware
Hi all To install W8 developer edition (current version) as a VM with vmware workstation you have to download / upgrade to version 8. Version 7.1X and earlier won't work. Vmware player (current version) gives same problem as vmware workstation 7.1x. When you install choose W7 as the OS...
Virtualization
Eight Forums Android App Eight Forums IOS App Follow us on Facebook