Mac Os X High Siera 2017 Vt-x Or Amd-v Virtualization Must Be Enabled In Your Computer’s Bios10/14/2019
These days virtualization technology gets popularity in the world of Information Technology which is known as (IT). Isn’t just for geeks or those who run enormously powerful servers. It offers something for everybody, and if you haven’t yet dipped your toe into the virtualization ocean, then you’re at serious risk of being left behind. In its strictest sense, virtualization refers to running two or more operating systems on one physical PC.
Either the multiple operating systems run side-by-side, with a separate piece of software called a hypervisor used to manage them, or one operating system runs the other operating systems within program windows. The former is usually limited to servers, with the latter finding common use on desktop computers.
Create a High Sierra USB Installer. To install macOS the first thing you need to do is configure a flash drive with a macOS installer. To create a macOS installer you first need access to a mac or a virtual machine running macOS.
But in this guide, I’m going to show you to fix macOS High Sierra error on VirtualBox during the installation process. I’m not going so deep to explain about virtualization.
How to Fix macOS High Sierra Error on VirtualBox There are hundreds of people asking that how to fix macOS High Sierra Error on VirtualBox or VMware during installation steps. It’s somehow complicated for the Windows users to run macOS on their PC.
If it’s tough for them to, don’t worry there is another method also to run Mac operating system on their laptops. They can install macOS on their system by using virtualization technology such as VMware or VirtualBox. Related Post:. Important Note: It very important to quit or exit Virtualbox before adding the code to cmd otherwise most of the time it does not work.
It means you can’t install macOS High Sierra or later version on VirtualBox. Without waste of time lets introduce some errors and ways to fix them. The following issues mostly happen when someone wants to install Mac operating system on VirtualBox. VBoxManage.exe: error: Unknown option -cpuidset. Could not find a registered machine named “Your VM Name.”. A critical error has occurred while running the virtual machine.
Failed to open Virtual Machine. VT x is disabled in the BIOS. Hardware acceleration is not available. Guru Meditation error Keep in mind that before clicking on turn on the virtual machine, make sure to check out the following settings. It may help to run macOS High Sierra or later versions without any problem.
Memory Size to 4 GB (Recommended). Disable Floppy disk. Chipset to ICH9 or PIIX3 for some devices. Processor minimum 2 recommended 4. Video memory to 128 MB Step #1. Unkown option –cpuidset Whenever you face this “ VBoxManage.exe: error: Unknown option.
–cpuidset The VM hangs on boot” problem while adding the first code in the Command Prompt. It’s because of double hyphen. Use Double hyphen “- – “ before cpuidset.
Could not find a registered machine name #3. Missing Bluetooth Controller How to fix this “ Missing Bluetooth Controller” error. When you see this error.
Because you are running the commands ( Step #5) in the article while the Oracle VM software is open. Shut down the VM software completely and then run the commands. After the commands are run, open up Oracle VM and start your VM session. #4. A critical error has occurred while running the virtual machine The critical error most of the times happen due to the guest operating system.
It is trying to switch to the PAE mode which is currently disabled by default in VirtualBox. PAE support can be enabled using the VM settings (System/Processor)”. A Critical Error has Occurred while Running the Virtual Machine. Open VM VirtualBox. File - Settings - System - Processor.
Check Extended Features: Enable PAE/NX #6. Failed to Open Virtual Machine If you see this error that says failed to open the virtual machine. Mos of the time it is due to the vmdk or vhd file that is not selected, crushed or missing. Try to browse the file and try again. If this method does not work for you, just enable virtualization technology from your BIOS and VirtualBox settings. If you don’t know how to enable virtualization technology read step #7 of this guide.
#7. VT-X is disabled in the BIOS This error occurs if you have disabled Virtualization Technology from your main system and VirtualBox settings. You can enable virtualization technology by navigating to your bios setup. Just find your bios boot menu key from here.
Once you enter into bios search for Virtualization Technology or VT-X. Select it and choose Enabled.
Save the changes and boot normally and try again with installing macOS High Sierra 10.13 or any other operating system on VirtualBox. Enable Virtualization Technology (VT-X) #8. Guru Meditation error or Black Screen If you guys having the guru meditation error or black screen while installing macOS High Sierra or any other operating system like Kali Linux or Windows 10. Just follow the below instruction. For people with the black screen problem or Guro Meditation error, change operating system version from macOS 10.13 High Sierra (64-bit) or macOS 10.12 Sierra (64-bit) to just the Mac OS X (64-bit) and If didn’t work then settle the Video Memory Size to 128 MB from Virtual machine settings. It should work this time without any issue because it has worked for a lot of people.
![]()
I have a 'standard' Mac Pro 2008 (3,1) with the RAM upgraded to 12 gigs. It has the stock ATI Radeon AT2600 XT 256 video card.
A long-term project requires that I run Windows 7, which I'm running on a VMWare Fusion 6.0.2 vm to which I've given the 2 gigs of RAM that the VMware settings dialog suggests. The vm is on a spindle drive (WD Black) that's separate from the SSD that contains the MacOS. The Win 7 performance is adequate but I want it to be snappier. I need to run the vm at my 30' ACD's native 2560x1600 resolution and the response from Windows when launching apps or dragging windows just seems a bit sluggish. Activity Monitor on the Mac doesn't show any issue with RAM or CPU usage.
![]()
I don't want a dedicated, standalone PC for a bunch of reasons. The vm is 'almost there.' I just want to improve its performance. I'm going to spend time on the VMware forums to figure out the optimal settings for the VM, but on the Mac side I have a little bit of money to throw at the problem, but not a bunch. So I want to focus on the most improvement for my money.
How would you rank the following in terms of benefit to the Windows vm's performance? I can probably do one or two of the following: -Adding RAM to the Mac so that I can allocate more RAM to the VM -Upgrading the Mac's video card -Moving the vm from the spindle drive (WD Black) that it's on to an SSD -Something else I'm not thinking of. I have a 'standard' Mac Pro 2008 (3,1) with the RAM upgraded to 12 gigs. It has the stock ATI Radeon AT2600 XT 256 video card. A long-term project requires that I run Windows 7, which I'm running on a VMWare Fusion 6.0.2 vm to which I've given the 2 gigs of RAM that the VMware settings dialog suggests.
The vm is on a spindle drive (WD Black) that's separate from the SSD that contains the MacOS. The Win 7 performance is adequate but I want it to be snappier. I need to run the vm at my 30' ACD's native 2560x1600 resolution and the response from Windows when launching apps or dragging windows just seems a bit sluggish. Activity Monitor on the Mac doesn't show any issue with RAM or CPU usage. I don't want a dedicated, standalone PC for a bunch of reasons. The vm is 'almost there.'
I just want to improve its performance. I'm going to spend time on the VMware forums to figure out the optimal settings for the VM, but on the Mac side I have a little bit of money to throw at the problem, but not a bunch. So I want to focus on the most improvement for my money. How would you rank the following in terms of benefit to the Windows vm's performance? I can probably do one or two of the following: -Adding RAM to the Mac so that I can allocate more RAM to the VM -Upgrading the Mac's video card -Moving the vm from the spindle drive (WD Black) that it's on to an SSD -Something else I'm not thinking of. Click to expand.SSD is probably your biggest bottleneck followed by the only 2gb of RAM allocated.
I'd recommend moving the VM to an SSD first, then cranking up the RAM to 3 or 4 GB. If the latter has a positive affect, and OSX is now RAM starved, only then would I add RAM to your system. You might find that OSX runs just fine with only 8GB available (other 4 tied up in the VM). SSD would probably help the most. Also make sure vt-x is turned on (which I am 99 percent sure your procs support). Click to expand.Definitely give the VM at least 4 GiB of RAM. Even if it seems 'wasted', the extra RAM will be used for filesystem caches - which definitely helps 'snappiness'.
(To see how much is in cache - 'Start' - 'Administrative Tools' - 'Performance Monitor', then click the 'Open Resource Monitor' link and go to the 'Memory' tab. The 'Standby' memory is mostly filesystem cache.) Check the memory for the video card in Windows (right-click on desktop, 'Screen Resolution' - 'Advanced Settings'). You should see something like the attached image. You have installed VMware Tools in the guest, right? That is vital. Vt-x and Win 8 Hi, I did not know about vt-x, but I will be sure to enable it.
I also run the exact same 3,1 setup with a 30'ACD. I have 16gb, half dedicated to the VM. I have two SSD's - one for OSX and the other for the VMs.
Your video card is a bit underpowered, but that probably doesn't make much of a difference. I would switch to Win 8. It is 'snappier' than Win 7 - Win 7 wastes a lot resources for graphics and I am not sure what other overhead, but after installing Win 8 in six of our vintage 2009 iMacs and our other 3,1s in the office, those computers ran much faster VMs than XP Pro. They could barely run Win 7 in any iteration - with or without Aero graphics.
My conclusion, unscientific, is that Win 8 is more efficient and requires less resources than Win 7 so it will run in a lot more rudimentary hardware than Win 7 - which is basically what you have with a VM. Click to expand.Yes, VMWare Fusion for Mac requires VT-x/EPT. Directly from their documentation for Fusion 6.0: Verify that the host system has a CPU that is recent enough to support Virtualized Intel VT-x/EPT, performance counters, or both. For example, host CPUs that support advanced options include Intel CPUs based on the Nehalem, Westmere, or Sandy Bridge microarchitectures. With the current Intel naming convention, these processors include Intel Core i processors, such as Intel Core i5. Therefore, the processors in the 3,1 (since they are Core2duo based Xeons) do not have EPT which is a requirement to use that function in Fusion.
Fusion does not support VT-x only. Yes, VMWare Fusion for Mac requires VT-x/EPT. Directly from their documentation for Fusion 6.0: Verify that the host system has a CPU that is recent enough to support Virtualized Intel VT-x/EPT, performance counters, or both. For example, host CPUs that support advanced options include Intel CPUs based on the Nehalem, Westmere, or Sandy Bridge microarchitectures. With the current Intel naming convention, these processors include Intel Core i processors, such as Intel Core i5.
Therefore, the processors in the 3,1 (since they are Core2duo based Xeons) do not have EPT which is a requirement to use that function in Fusion. Fusion does not support VT-x only. I've never had these problems on my 3,1. Just checking, but the VMWare tools are installed, right? Otherwise performance might be handicapped.
I also make sure to give Windows 7 plenty of RAM. 4 gigs is a good amount.
If you don't have spare RAM on your computer, add more. 2 gigs isn't much for Windows 7. Windows 7 in VMWare Fusion for me feels pretty much native, except for slower game performance.
I've used it for Visual Studio projects before, no problem. Running off of a WD black should be totally ok.
Follow-up Thanks again, Gang, for your responses. Here's some follow-up info: -I have been running VMWare Tools. Currently it's version 9.6.2.1688356.The Mac Pro has the latest BIOS installed, per Apple's tech note. I did that years ago when it was released.The only way I know to enable VT-x is to go to the virtual machine settings in Fusion, choose Processors and Memory, and check 'Enable hypervisor applications in this virtual machine.'
Doing this causes Fusion to throw the previously described error when launching that VM ('Virtualized Intel VT-x/EPT is not supported on this platform. Continue without?' If there's something different I should be doing, I'd love to know. Also, I dug through my couch cushions and found enough pennies to throw 8 more gigs of RAM into the Mac and move the virtual machine to an OWC SSD drive. I just did that this morning and I can tell a difference. Windows now has 4 gigs of RAM (the Mac has a total of 18 gigs, so I could give Windows more, if necessary). The only thing now is optimizing settings within Windows and any additional Fusion settings that may make a difference.
I welcome feedback there. Thanks again. Click to expand.Fusion supports 3 kinds of virtualisation:. no vt-x at all aka binary translation.
ordinary VT-x. VT-x with EPT If you want to run a 64 bit guest OS the use of VT-x is mandatory (no VT-x means that you can not run a 64 bit guest OS). The Core 2 Duo and equivalent Xeon procs fulfil this requirement. If you want to run a 32 bit guest OS than the use of VT-x is not required nor recommended. VMware has a very efficient own virtualisation engine for this called binary translation.
They ran some tests to see if enabling VT-x speeds things up but it did the opposite or nothing at all. I think it was this paper:. Fusion will pick the right virtualisation engine automatically.
You really shouldn't set this manually unless you know exactly what they all mean. The same applies to any of the other settings in the 'Advanced' tab of the VM settings as well as the advanced settings in the cpu & memory tab: don't change those unless you exactly know what they are for.
Since you clearly don't, leave them as they are! If you want to run ESXi or Hyper-V as a VM to test them out or because you want to demo them to a client then you can use these settings. They'll enable a few things among VT-x with EPT in order to be able to use a hypervisor (ESXi, Hyper-V) in a VM. If you even bothered to read the help (click the?
Button) you'd have known this since it clearly states what these settings are for. An old Mac mini early 2009 with a Core 2 Duo cpu will do VT-x (enabled in the EFI by default) and binary translation without any problems. It won't do VT-x with EPT. I have such a Mac mini running Yosemite PB2 and it runs Fusion 6.0.4 without any problems.
The Windows 8.1 Enterprise vm is 64 bit so it uses VT-x and it runs fine (albeit a bit slowly, the C2D isn't as fast as the Core i5 that came after it and has far better VT-x support). Back to your original question: make sure you assign as less as vCPUs as possible and put the vm on the fastest disk (the ssd). If that still isn't fast enough you'll have to move to faster (newer) hardware. I have a 'standard' Mac Pro 2008 (3,1) with the RAM upgraded to 12 gigs. It has the stock ATI Radeon AT2600 XT 256 video card. A long-term project requires that I run Windows 7, which I'm running on a VMWare Fusion 6.0.2 vm to which I've given the 2 gigs of RAM that the VMware settings dialog suggests. The vm is on a spindle drive (WD Black) that's separate from the SSD that contains the MacOS.
The Win 7 performance is adequate but I want it to be snappier. I need to run the vm at my 30' ACD's native 2560x1600 resolution and the response from Windows when launching apps or dragging windows just seems a bit sluggish. Activity Monitor on the Mac doesn't show any issue with RAM or CPU usage.
I don't want a dedicated, standalone PC for a bunch of reasons. The vm is 'almost there.' I just want to improve its performance. I'm going to spend time on the VMware forums to figure out the optimal settings for the VM, but on the Mac side I have a little bit of money to throw at the problem, but not a bunch. So I want to focus on the most improvement for my money.
How would you rank the following in terms of benefit to the Windows vm's performance? I can probably do one or two of the following: -Adding RAM to the Mac so that I can allocate more RAM to the VM -Upgrading the Mac's video card -Moving the vm from the spindle drive (WD Black) that it's on to an SSD -Something else I'm not thinking of. Click to expand. Do you have a 4-core or an 8-core Early 2008 model?
If you have an 8-core, consider giving your VM 3 or 4 cores instead of 2. If you intend on keeping that Mac Pro around for a while, I'd upgrade the video card on principle; ATI Radeon HD 2600 XT's are somewhat unreliable over time, plus, by today's standards (and what new OS and software features leverage the GPU but don't support that card), that card is old. I'd try to find a Radeon HD 4870 (if you don't care about having a second video card), a Radeon HD 5770 (if you do care about having a second video card), or I'd delve deep into the 'Flashing a standard PC graphics card for use in a Mac Pro' modding sub-culture and get a card that will work with your Mac, but be substantially more modern and more powerful than even the Radeon HD 5870 (which was the newest/highest Apple-made/supported video card for ANY tower-based Mac Pro). That said, I don't believe any of that will matter for your VM; I digress. VMs are RAM hogs. Even if your VM isn't using all 2GB of RAM, that RAM is still in reserved for use by your VM.
12GB of RAM isn't much anyway. I'd up that and then up your VM to 4GB. It sort of depends on what you're doing in Windows anyway. Any particular reason why you're not using Boot Camp instead? You know that you can also virtualize a Boot Camp Partition so you can have the best of both worlds, yeah?
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |