VMware Communities
leopoldj
Contributor
Contributor

Binary translation is incompatible with long mode

I have Vaio Fit laptop.

OS: Windows 8 64--bit

CPU: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz

Virtualization is enabled in BIOS. Task manager is reporting that virtualization is enabled.

I am trying to play an image of Ubuntu 32-bit that was copied from another machine. I get the error message "Binary translation is incompatible with long mode". I did a ton of Googling and most people are having this problem when booting 64-bit guest OS with virtualization is disabled in the BIOS. That doesn't apply to me. I have virtualization enabled in BIOS and I am booting a 32-bit guest OS.

Ubuntu guest OS is running fine but slow.

I can not find anyone else having this problem. Any idea how to fix this? Thanks.

Tags (2)
Reply
0 Kudos
17 Replies
continuum
Immortal
Immortal

In your vmx-file there seems to be an entry that orders specific CPU-settings instead of setting this automatically.
Attach your vmx-file to your next reply


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
WoodyZ
Immortal
Immortal

Remove the following two options from the .vmx configuration file, if they exist.

monitor.virtual_mmu = "software"

monitor.virtual_exec = "software"

Otherwise, attach your .vmx configuration file to a reply post.

NOTE: DO NOT copy and paste the contents of the .log or .vmx files into the body of a reply!  Use the "Use advanced editor" link in the upper right corner of the normal reply window to bring up the Advanced Editor where you'll be able to attach files via the Choose File button or Browse button (depending on the Browser) above the Post Message button! Smiley Wink

Reply
0 Kudos
admin
Immortal
Immortal

Please post your vmware.log file.

Reply
0 Kudos
leopoldj
Contributor
Contributor

The vmx and log files are attached.

I don't see virtual_mmu etc in the vmx file. Although, log file says:

HV Settings: virtual exec = 'software'; virtual mmu = 'software'

Reply
0 Kudos
admin
Immortal
Immortal

The VM is running with binary translation because VT-x is disabled and locked.  The message is merely informative.  It is not an error.  You may find that performance improves if you enable VT-x in your system BIOS.

Reply
0 Kudos
WoodyZ
Immortal
Immortal

leopoldj wrote: Virtualization is enabled in BIOS. Task manager is reporting that virtualization is enabled.

Was it originally disabled and you enabled it?  If yes has the system been completely shutdown/restarted since making the change, not just a reboot after making the change?

Reply
0 Kudos
admin
Immortal
Immortal

Are you running Player nested under some other virtualization product?  Your vmware.log file reports that MSR 0x3a has the value of 0x1, which is "VT-x disabled and locked."  It is possible that some other virtualization product has spoofed the value of this MSR, but if there is such a virtualization product running, it is not declaring itself through CPUID[1].ECX[32].

You're not running McAfee Deep Defender, by any chance, are you?

Reply
0 Kudos
leopoldj
Contributor
Contributor

Virtualization was originally disabled in BIOS. After enabling it I have completely shutdown and powered up using the power button.

Reply
0 Kudos
leopoldj
Contributor
Contributor

OK, I found the source of the problem. It is Avast anti-virus. I have seen old references to McAfee being a potential disabler of Vt-x. But, a few recent posts started talking about Avast the same way. So, I uninstalled Avast, rebooted and started my Ubuntu VM. This time I did not get any warning about "long mode". Performance is pretty good (as much as I can expect from a mid range laptop that I bought for my dad).

You guys have been awesomely helpful and steered me in the right direction.

Reply
0 Kudos
admin
Immortal
Immortal

This is the first I've heard of Avast potentially having a hypervisor of its own.  Can you tell me which Avast product you are using?

Reply
0 Kudos
leopoldj
Contributor
Contributor

OK, this is strange. Just to be sure that Avast was the problem, I installed it again and rebooted. VMWare is no longer showing the error message. Attaching the latest log file.

Reply
0 Kudos
admin
Immortal
Immortal

VT-x now looks like it is enabled and locked.

It is possible that your BIOS does not handle resume from hibernation correctly.  Try shutting down Player, hibernating your system, waking it from hibernation, and restarting Player.

Reply
0 Kudos
leopoldj
Contributor
Contributor

Windows 8 does not give me an option to hibernate when I click the power button. I only get Sleep, Shutdown, Restart.

For sure, uninstalling Avast and rebooting did fix the problem. Numerous cold reboots prior to that did not. I can not explain why after installing Avast again will not re-introduce the problem. Only that I want to add: the laptop came with Kapersky which I had uninstalled before originally installing Avast.

Let me keep using this for a few days. If any new finding emerges, I will report back.

Reply
0 Kudos
admin
Immortal
Immortal

Give 'sleep' a shot.

Reply
0 Kudos
admin
Immortal
Immortal

Hmmm...What happens if you enable AutoSandboxing in Avast?

Reply
0 Kudos
yriyat
Contributor
Contributor

I get this error after seeing the previous error message...

"Mac OS X is not supported with binary translation. To run Mac OS X you need a host on which VMware Player supports Intel VT-x or AMD-V."

Im using a lenovo i5 windows 8.1 ... should be working...

Also .. I did not make any bios changes......how exactly do you do that?

Reply
0 Kudos
WoodyZ
Immortal
Immortal

yriyat wrote: I get this error after seeing the previous error message...

"Mac OS X is not supported with binary translation. To run Mac OS X you need a host on which VMware Player supports Intel VT-x or AMD-V."

Im using a lenovo i5 windows 8.1 ... should be working...

Also .. I did not make any bios changes......how exactly do you do that?

VMware does not support the running of OS X under VMware Player/Workstation!  Also, running legally virtualizable versions of OS X in a Virtual Machine may only be done when done on Apple-branded hardware and when done while running under OS X and for that you need VMware Fusion not VMware Player/Workstation, otherwise you're violating the Apple SLA for that product.  Therefore no help can be provided to you for OS X in this use case scenario as it would violate VMware Community Terms of Use to do so.

Reply
0 Kudos