Importing a bootcamp partition into VMWare Fusion when it has Hyper-V enabled.

This is quick note on importing a Windows 8 or Server 2012 BootCamp partition that had Hyper-V hypervisor enabled.

By default, you cannot have Hyper-V booted inside of Fusion because of hardware vitualization conflicts.  You know you have this problem if you see the following messages in the guest machine's window in VMWare Fusion.
Your PC ran into a problem and needs to restart.  We're just collecting some error info, and then you can restart. (100% complete)
If you'd like to know more, you can search online later for this error:  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (winhv.sys)

Edit the Fusion VMX configuration file directly.

You can fix this by editing the vmx file directly.


  1. Shutdown Fusion
  2. Find your Virtual Machine definition. Navigate to /users/<username>/Library/Application Support/VMWare Fusion/VirtualMachines/Boot Camp.
  3. Right Click on the Boot Camp package and select Show Package Contents
  4. Edit the file that ends in .vmx using TextEdit or your default file editor
  5. Add a line at the end containing
    hypervisor.cpuid.v0 = "FALSE"
  6. Save the file.
  7. Launch Fusion 
  8. Run the imported BootCamp virtual machine


Using the GUI

You're supposed to be able to do this via the Fusion 6 GUI but that did not work for me. This section is here to provide breadcrumbs for future searchers with this problem.

  1. Bring down the crashed imported Boot Camp virtual machine
  2. Edit the Virtual machine settings via the menu Virtual Machine Settings --> Processors & Memory --> Advanced
  3. Check "Enable hypervisor applications in this virtual machine"
  4. Close the settings
  5. Restart the virtual machine






Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more