VMware Workstation and Hyper-V on same machine

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 456
    Windows 10 Pro
       #11

    Yes, that workaround has actually fixed the Caps Lock and Num Lock issues for me. It's nice of them to provide a workaround in a timely manner. However it would have been better to thoroughly test the build before releasing it. It's not like these are hidden bugs, they are fairly obvious and apparently wide spread.
      My Computer

  2. hsehestedt's Avatar
    Posts : 1,100
    Windows 10 Pro, 2004
    Thread Starter
       #12

    Jimbo45, you wanted a screenshot... here it is. Win 10 in Vmware and Hyper-V at the same time. Note that I don't have networking enabled on the Hyper-V system yet and that I have not set the timezone on that VM yet, but it is working.VMware Workstation and Hyper-V on same machine-desktop.jpg
      My Computers

  3. Compumind's Avatar
    Posts : 2,541
    Windows 10 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #13

    hsehestedt said:
    Here's an update just in case anyone following this topic is interested:

    VMware is aware of the problem and they have provided a workaround to me for now.

    Simply add the following line to %PROGRAMDATA%\VMWare\VMware Workstation\config.ini:

    mks.win32.useInjectedMagic=FALSE

    It's working for me.
    Thanks for the heads-up. Is there an ETA for a complete fix?

      My Computer

  4. jimbo45's Avatar
    Posts : 9,281
    Windows / Linux : Arch Linux
       #14

    hsehestedt said:
    Jimbo45, you wanted a screenshot... here it is. Win 10 in Vmware and Hyper-V at the same time. Note that I don't have networking enabled on the Hyper-V system yet and that I have not set the timezone on that VM yet, but it is working.VMware Workstation and Hyper-V on same machine-desktop.jpg

    Hi there
    That doesn't quite look like what I'm asking to see.

    Yiu've got 2 VM's both running with HYPER VM -- there's not a problem usually running "nested" VM's.

    What I want to see as I showed in my screen shot a VM running directly from VMWare and then another one at the same time running directly from HYPER-V -- Networking / other issues can always (hopefully) be resolved later -- but the essence of what I'm trying to say is that I want to see 2 independent VM's running under their own (separate) VM systems rather than using a "nested VM" technique.

    However I might have mis-understood the diagram though.


    Cheers
    jimbo
      My Computer

  5. hsehestedt's Avatar
    Posts : 1,100
    Windows 10 Pro, 2004
    Thread Starter
       #15

    @jimbo45, the VM on the left is running within VMware and the one on the right is in Hyper-V. They are NOT both running in Hyper-V. My apologies if the screenshot is confusing as it's a 4K screen squeezed down to a fairly small size. If you magnify the image you should be able to see that the left VM is running within the VMware UI and the right side within Hyper-V. I hope that helps.

    @Compumind - VMware did not provide an ETA, they simply confirmed that they were aware of the issue and that they are working on it. I may go back to my thread on their support forums and inquire whether they have any sort of ETA.
      My Computers

  6. jimbo45's Avatar
    Posts : 9,281
    Windows / Linux : Arch Linux
       #16

    hsehestedt said:
    @jimbo45, the VM on the left is running within VMware and the one on the right is in Hyper-V. They are NOT both running in Hyper-V. My apologies if the screenshot is confusing as it's a 4K screen squeezed down to a fairly small size. If you magnify the image you should be able to see that the left VM is running within the VMware UI and the right side within Hyper-V. I hope that helps.

    @Compumind - VMware did not provide an ETA, they simply confirmed that they were aware of the issue and that they are working on it. I may go back to my thread on their support forums and inquire whether they have any sort of ETA.
    Hi there
    Thanks for the explanation --I see it now.

    Cheers
    jimbo
      My Computer

  7. hsehestedt's Avatar
    Posts : 1,100
    Windows 10 Pro, 2004
    Thread Starter
       #17

    Another update: It seems that my enthusiasm may have gotten the better of me. Now that I'm actually creating new VMs, I'm running into another problem with 15.5.5. I'm creating some new sysprep images of Windows 10 2004 and I'm finding that I'm getting frequent BSODs within the VM on x86 VMs. Note that this is happening very early in setup before setup even starts copying files. It also does not happen every time, but it has happened multiple times today.

    At least so far, I've not had any difficulty with x64 editions.

    I'm about to see what VMware has to say on the matter.

    Bottom line: It might be best to wait for 15.5.6
      My Computers

  8. jimbo45's Avatar
    Posts : 9,281
    Windows / Linux : Arch Linux
       #18

    hsehestedt said:
    Another update: It seems that my enthusiasm may have gotten the better of me. Now that I'm actually creating new VMs, I'm running into another problem with 15.5.5. I'm creating some new sysprep images of Windows 10 2004 and I'm finding that I'm getting frequent BSODs within the VM on x86 VMs. Note that this is happening very early in setup before setup even starts copying files. It also does not happen every time, but it has happened multiple times today.

    At least so far, I've not had any difficulty with x64 editions.

    I'm about to see what VMware has to say on the matter.

    Bottom line: It might be best to wait for 15.5.6
    Hi there
    Have you tried messing around with the 20H2 (VMware) V 16 free trial version --could be interesting for you --free download and doesn't expire until October.

    What Windows version are you using as the HOST machine --would be interesting to know

    I doubt if there will be a 15.5.6 -- seems the effort is in pushing for V16. Could always be wrong though.

    I've though found for running VM's that I really do useful work on -- using QEMU/KVM gives me by a zillion times better performance than either HYPER-V or VMWare -- although to set it up properly with the appropriate pass thru hardware you need to have some decent hardware and plenty of patience in tinkering around. Using Native I/O on the VM for example is far better than some of the paravirtualised I/O formats such as vhd / vhdx etc.

    The main problem with VMware is that you have to have the overhead of the Host OS while HYPER-V doesn't seem to like a lot of hot plugging of devices to the VM's and having to use slow things like RDP for managing / logging on to VM's slows down the whole experience. Using a Linux remote laptop it's quite easy to access Windows VM's on a Linux host via all sorts of "X" servers which work a lot better than the native Windows RDP protocol -- faster and better security. Also using things like OPENVPN works too.

    IMO wouldn't waste time with X-86 editions any more -- they will soon be history even though support for 32 bit programs will continue for a long time yet.

    I haven't had any problems though with XP or W7 - X86 version as VM's -- haven't bothered with W10 x-86 stuff at all.

    Cheers
    jimbo
      My Computer

  9. hsehestedt's Avatar
    Posts : 1,100
    Windows 10 Pro, 2004
    Thread Starter
       #19

    Jimbo, thanks for the suggestions. I've tried the trial of v16 yet. I may give it a try at some point soon.

    You were curious about what Windows version I'm using for the host. It's the final released build of Win 10 2004 because that is the only version that supports VMware and Hyper-V coexisting together.

    The only reason I'm messing with the x86 stuff at all is for the sake of completeness. I wrote a program for myself that injects all the latest updates into Windows editions and then combines them all into a single ISO image. So I have one single image that includes every x64 edition, every x86 edition, as well as syspreped editions for x64 UEFI and BIOS based system, and a syspreped x86 BIOS edition. Other than creating the sysprep reference installation, the whole process is automated.

    I know that the writing is on the wall for x86 editions. In fact 2004 is the first version for which Microsoft will now longer make x86 editions available for new OEM machines so they are clearly signaling their intent to begin phasing out x86.
      My Computers

  10. cereberus's Avatar
    Posts : 11,426
    Windows10
       #20

    Just tried VMW 15.5.5 and it worked find. Installed a Linux iso and just cannot get sound working. VMW detects my audio card, but Linux does not want to talk to VM.

    Any idea why?

    Funny, I have used Hyper-V so much I know settings inside out but I had forgotten all the VMW quirks as it is years since I used it.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:29.
Find Us




Windows 10 Forums