You really deserve a lot more subscribers. Every comment there is, you reply back. Most youtubers don't. And because you're doing things that work in the UK, SUBSCRIBED!
That’s really very kind of you. Being a small channel presents the opportunity to get to know our audience, often personally, and we’re really enjoying all of the conversations and trying to resolve tech issues. We’ll certainly be continuing to post content which is relevant here in our home country, but we’re also grateful for a huge percentage of views from overseas, so there will also be content which hopefully has an even wider appeal. Finally, we’re very grateful for your support and subscription. Good luck with your projects.
I've tried like 100 different tutorials by now within the past 6 months, and this is the first one that actually worked and booted. I don't know why only this tutorial is the only one that has worked in months, but thank you so much! Very appreciated :)
Hi again @NotFunny. This is something which we’ve struggled with throughout the history of this project, and our virtual machines have been silent from the earliest High Sierra machine. We’ve had plenty of feedback from viewers who have looked into this and who have also drawn a blank. Our working theory is that drivers for both input and output don’t translate well in the virtual environment, although this isn’t an issue on all guest operating systems. We’re hoping that someone may ultimately point us in the direction of a workable solution. We’re ideally looking for native drivers rather than relying upon third party modifications of unknown provenance, but, so far, they have proven elusive. We will publish a specific update in the event that a solution is found, but, until then, the lack of sound remains an issue we still need to resolve.
To the other youtubers who are bloating youtube with incoherent/ incomplete/incorrect/and ambiguous tutorials and claim they know their stuff... please take notes from this video, this is how to properly make a tutorial. straight to the point and no BS. Period.
Wow. Thank you very much indeed for taking the time to comment with such positivity about the tutorial. As a creator, this is very much appreciated and means a great deal.
Thanks for mentioning the educational aspect of the video. We place far more value in the process than the product, and there’s so much to learn in these projects, even in failure. Once you understand the process, it can be modified to accommodate other versions of macOS.
Hi Ian, and thanks for your kind words about this video. Yours is the first feedback we’ve had where the virtual machine hasn’t worked at the first attempt, so we don’t have previous data to call upon when looking into this. We do, however, have the experience of our previous projects, so a few thoughts come to mind. Forgive is if you’ve already considered them, having watched the video: 1 )..Have you created your own installation .iso, as described in the first two chapters of the video? Although it’s mentioned in our introduction, we’re often asked to troubleshoot installations where the hard drive file is downloaded in a pre-prepared format. As this method differs from ours, we aren’t in a position to assist in these instances. 2 )..Assuming you have created your own .iso, were there any obvious issues during the creation process, and did the .iso file transfer from Mac to Windows? Do checksums or file sizes match pre and post transfer? 3 )..Are you using an AMD processor? This is frequently a cause for failure, and is something we discuss and resolve here: ruclips.net/video/sV42TRZNmDc/видео.html 4 )..Have you increased the processor count from 1 to 2? Omitting this simple option can lead to failure at this stage. 5 )..Have all of the commands been entered at the Windows Command Prompt? 6 )..If none of the above are relevant, it might be worth trying to recreate the .iso by repeating the early part of the tutorial, purely to rule out one-off errors. You may also wish to recreate the virtual hardware. Sorry that this is more of a troubleshooting checklist than a definitive solution. At this early stage, we don’t have any solved failures to refer to. If none of this helps, do get back to us and we’ll take it from there.
@@TechFixFlix Hi - thanks for taking the time to respond it is much appreciated. I did create my own iso in fact I did it twice just to make sure there wasn't an error - checked file size on both occasions and both matched. All went smoothly on both occasions with no errors I tried deleting the VM and re-created it several times tweaking the setting to try and make a difference but same result install freezes after a few seconds. I am using an AMD processor but did include the command included in your tutorial - I'll check out the video link you have sent to see if this helps Thanks again
One other possibility relates to the fact that your last error message specifically references date and time. In our previous macOS projects, we’ve seen the virtual machine fail because its internal clock is set to a date which is rejected by the macOS installer, which appears to be time-sensitive, and will not install if the system clock doesn’t meet its expectations. As Big Sur is the current version of macOS, it’s a reasonable assumption that it will anticipate something close to the current date, and if, for some reason, the virtual machine’s date is set to well before that, it may cause the issue you’re experiencing. Presumably this would only happen where the virtual machine inherits its clock from the host machine, and that host machine is either not synchronised via internet time or has a flat CMOS battery, meaning that the virtual machine thinks that the year is not 2020. We don’t know whether this is at all relevant to you, but we’ll offer it up as another possibility, and one which has genuinely caused issues on some of our previous projects.
@@TechFixFlix I thought the same having messed with Hackingtosh machines n the past - on this occasion server is brand new and time is synchronised - I'm going to try the install on an intel laptop over the weekend to see how it goes - thanks for taking the time to try and assist
getting the error: Configuration error: Querying "GetKeyFromRealSMC" as a boolean failed (VERR_CFGM_NOT_INTEGER). I have tried re entering the appropriate cmd prompts and got nothing, any advice? I am using *Monterey* for this. also checked the iso and it is still attached
Hi @cobra 727. Given that your error message specifically references "GetKeyFromRealSMC," we can safely assume that the command generating this error is: VBoxManage setextradata "Monterey" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Where “Monterey” is the name of your virtual machine. If your virtual machine is called anything other than “Monterey,” the name of your virtual machine would replace “Monterey” between the quotation marks. The error message also references “not integer,” which would suggest that we’re missing a number. Have you included the number 1 which appears at the right end of the command?
@@TechFixFlix Ok did another attempt and got a little further the 2nd time. It went to the black apple loading bar and looped between that and the code execution screen for a while. Closed the VM and tried again and finally got all the way through. Even the audio works now.
That’s great. Glad you got this up and running. Did you do anything special to get the audio working? You might be the first person to have working audio following this project.
@@TechFixFlix I actually have no idea how I got the audio working, all I remember doing is changing what the sound effects play through. Just changing it to internal speakers. Might just be that im on Monterey and not Big Sur.
Thank you very much indeed for the reply @cobra 727. We’ve also extended this project to Monterey (see our video “Create A macOS Monterey Installer ISO - For VirtualBox Running On Windows” at ruclips.net/video/q9koLQSqrlc/видео.html for details) but it remains silent in terms of both audio input and output. Nevertheless, it’s great that yours is functioning normally.
Hi TechFixFlix, I followed your instructions exactly. I keep getting this error message from VirtualBox on start. Failed to open a session for the virtual machine Big Sur. "Failed to query SMC value from the host (VERR_INVALID_HANDLE)." "Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole"
Hi @Joshua East. Glad to hear you’re been faithfully following our instructions. Not so glad to hear that they aren’t quite working for you. The error code 0x80004005 is typically associated with new or updated Windows builds or changes to Hyper-V. We’d be interested to know if this error is present in any virtual machine you create, or whether it purely impacts upon this project. If you’re happy to disable Hyper-V, and don’t use it for any other purpose, we’d give that a try first. You can always re-enable it later if necessary. Disabling Hyper-V can be done in one of three ways. Method A - Control Panel 1 )..Press your Windows key on the keyboard or click your “Start” button. 2 )..Type “Turn Windows Features On Or Off” and run the top search result. 3 )..Look for the “Hyper-V” feature and expand it. 4 )..Remove the tick next to “Hyper-V Hypervisor.” 5 )..Click O.K. and reboot the system. Method B - Elevated Command Prompt 1 )..Press your Windows key on the keyboard or click your “Start” button. 2 )..Type “CMD” and select the option to run Command Prompt as Administrator. 3 )..Enter the following command: bcdedit /set hypervisorlaunchtype off 4 )..Exit Command Prompt and reboot the system. Method C - PowerShell 1 )..Press your Windows key on the keyboard or click your “Start” button. 2 )..Type “PowerShell” and select the option to run PowerShell as Administrator. 3 )..Enter the following command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor 4 )..Exit PowerShell and reboot the system. Whichever method you choose, try restarting your virtual machine after your system reboots. Hopefully this will clear the error message. If not, get back in touch.
Got any solution for the audio issue? The same installation in vmware instead of virtualbox has audio working well. So, is there any solution for virtualbox?
Hi Naveen. We’ve performed many experiments in relation to sound, and we’ve received extensive feedback via the comments for our videos, all of which suggest that audio input and output devices don’t appear to be supported in VirtualBox. Your feedback in relation to VMWare is particularly interesting, as it does support our theory that this issue is specific to VirtualBox, rather than any other aspect of the method. It also leaves open the possibility that future updates to VirtualBox might ultimately allow us to enable sound.
We can immediately see from your channel why audio is important to you, but we’re afraid the news here isn’t good. Unfortunately, all of our virtual Mac projects to date have been silent, and this is something we mention at 24:21 in the video. We’ve been aware of this issue since our first Mac project in 2019, and, despite numerous investigations both here and amongst our community, we’ve yet to find any fix for this. You’ll note within Settings that there are no devices listed for audio input or output, and we believe this to be a limitation of VirtualBox. We’re still hopeful that a workaround will appear at some future point, although for now we’re still very much in search of a solution.
Hi there @Toxic Productions, glad you like the presentation of the video. It’s fantastic to have a platform where we can make content about our favourite subjects then discuss it with friends around the world, so “happy and excited” is absolutely the correct description. Of course, not every project works successfully at the first attempt, and this one is particularly complex. As you’re stuck on a screen featuring the Apple logo, our hunch would be that the installer .iso has become corrupted, during one of the many file-handling processes undertaken during the first part of the tutorial on macOS. This does seem to happen to a significant proportion of people following this tutorial. Typically, where the installer becomes corrupted, it can be difficult to detect because it will allow a certain amount of progress to occur before failing, rather than failing immediately as you might expect (although it does also fail immediately in some cases). The solution is to repeat the first part of the tutorial and create a new installation .iso. You might think the outcome will be the same, but often one-off errors do not occur on a second run-through. Hopefully this will resolve your issue. If not, do get back to us and we’ll explore further.
There's a problem on my VM, on first boot it shows me this error: " [EBILOG:EXITBS:START] 2021-03-26T09:22:45 " I've tried over 20 tutorials before this one and nothing helps. I keep getting the same error.
Unfortunately, that’s a fairly generic error which doesn’t identify a specific cause. You’ve mentioned that you’ve tried over twenty tutorials, which suggests that you’re probably experimenting quite a lot, which we’d always encourage, but we do need to ask whether you’re following our method strictly, and specifically whether you’ve created your own .iso as shown in the first ten minutes of our video. Many people use our tutorial as a troubleshooter, having previously downloaded a pre-prepared .vdi, .vdmk or .iso from the web, and we are unable to offer assistance here as we have no way of knowing how these files were created.
@@TechFixFlix Indeed I was using a downloaded iso file, sorry. I'm currently making a USB through a relatives mac as shown in the vid, I'll update on how it goes. Thanks for the fast reply!
@@TechFixFlix Hey, I followed everything in the video from start until 18:20 now and it still shows me the same error. I checked the .iso file and it's size which was the same, checked if the .iso is still attached, it was. I added the command for AMD processors as I'm running on Ryzen processor. I installed everything on default locations on my laptop. It gets stuck on a certain line of code (NOTE: Before this code, it shows me a couple of Errors similar to this one) " [EB.LD.LKCIR.2] " for around 5 seconds and after that it throws me to the [EBILOG:EXIT:START] 2021-03-26T19:21:31
@@TechFixFlix I uploaded the two screenshots of these errors to imgur. Here's the link: imgur.com/gallery/iY9INcd Maybe this can give you a better idea on how to help me or what the error might be.
Our third command is this one: sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSur -nointeraction Provided that you have copied the command from our description and pasted it into your Terminal app, we would fully expect it to work as shown in the video. The only exceptions we’ve experienced where the command itself fails occur with much older versions of macOS which have not been updated, so we’d be curious as to which version of macOS you’re using to create the installation media. We’d assume that you’ve downloaded the installer app directly from the App Store, that it’s located in your Applications folder, and that you’ve copied the command directly from the description. If you’ve already ruled out all of the possibilities mentioned above, it’s possible that your system is experiencing an issue which is beyond the scope of this tutorial, and we’d recommend reading the article below for possible further suggestions: osxdaily.com/2018/05/24/command-not-found-mac-terminal-error-fix/#:~:text=The%20four%20most%20common%20reasons,directory%20was%20deleted%20or%20modified
Hi @rps HD. You should be able to follow the tutorial using High Sierra as your starting point and indeed we’ve used High Sierra for an earlier tutorial in this series. Here are some quick thoughts to consider… 1 )..Have you downloaded the full version of the Big Sur installer? Was it sourced directly from the App Store? Is it located in your Applications folder? 2 )..Did the first and second commands execute without generating an error message? 3 )..Have you copied the command directly from the video description using cut and paste? 4 )..What is the exact error message which appears when the third command fails? 5 )..Is your version of macOS fully updated, and is the system date / time correctly set?
@TechFixFlix Could you do a video on installing Windows 8.1 on virtualbox? I know the official way to get the iso, but whenever the machine restarts, it goes back to the beginning and goes onto the first screen again. Thanks.
Hi again Ibrahim. Quite some time ago, we published a video installing Windows on VirtualBox, which you’ll find at ruclips.net/video/zqbMXXDJEyI/видео.html, although this video features Windows 10, rather than Windows 8, so it might only be indirectly relevant to you. From your description of your installation looping, we think you might need to eject the installation .iso once the initial installation has been performed. If the .iso isn’t ejected, there’s a possibility that it will be detected once the machine reboots, taking you back to the start of the installation process, in a loop which will continue until broken.
Hi TechFixFlix, I followed your instructions and end up with a UEFI startup.nsh error and a Shell> prompt. I also re-do a few times and end up with the same issue. Is there a solution for this? Thanks.
Hi there @Duuc Huung. Sorry to hear this isn’t going smoothly for you. Under normal circumstances, our advice to anyone experiencing this issue is to double check that the .iso you created in the first part of the tutorial has been attached to the virtual optical drive. We’ve seen examples on more than one occasion of the virtual disc becoming detached before the virtual machine is run, even when the user has specifically attached it. We say this because, when the virtual machine boots, the first thing it does it to check whether there is bootable media attached from which it is able to boot, and, where it fails, it will exit to the shell prompt, which happens to be where you currently are. However, the fact that you mention that you’ve redone the tutorial a few times only to end up at the same point does give us concern that there might be something else going on here which we haven’t experienced before. One of the things we mention in the video is the various version numbers of the installers and operating systems we are using…Are there any significant differences in your setup? We also mention file sizes and checksums for the .iso file…Are you confident that the file has transferred correctly from Mac to Windows, and that it is the correct size? Naturally, there are quite a few variables here, so the cause of the issue might not be immediately obvious.
Hi@@TechFixFlix . Thanks for getting back to me on this issue. Yes, you are correct concerning the ISO file. The one I used was corrupted somehow. I've made a new one and it's working fully now running on Virtualbox. Thanks for the tutorial, subbed and liked.
Thank you for the sub and like, both of which are truly appreciated. Thanks also for the feedback in relation to the corrupted .iso, as this will be helpful for others in the same situation. We can only speculate that the number of file handling operations in the early part of the tutorial (i.e. downloading then repeatedly converting before transferring across platforms) opens the door to corruption. Sometimes a corrupted .iso will allow a partial installation. Your example shows us that a corrupted installer might also halt the installation at VM startup and send the user into the EFI shell environment, which is useful to note.
Hi @Howard Goff. We don’t know whether or not you’ve had the opportunity to read the much longer discussion thread we had with “@Me and the Mrs” in which we set out every issue and potential resolution which is known to us. This was started as a separate discussion thread, and contained several possible avenues to explore. Although we weren’t able to resolve the specific issue which we were investigating, there’s a possibility that something in there might be useful to you, so we’d recommend checking out that thread. We didn’t receive any final feedback from “@Me and the Mrs,” so we aren’t sure if there’s a solution to be shared. Please accept our sincere apologies for the delay in responding to your comment. We have been extensively pursuing activities outside of the RUclips platform for the past six weeks, and consequently we are only now catching up on feedback and questions. Thank you for your patience and understanding.
it keeps stopping at step 20:40 "Forcing CS_RUNTIME for entitlement: com.apple.rootless.restricted-block-devices" can someone help me figure out what's wrong?
We typically recommend repetition here, purely to rule out the possibility of one-off errors. In particular, we’d advocate recreating the installer .iso from the opening chapters of the tutorial, as the number of file-handling operations undertaken introduces the risk of accidentally corrupting the data, and it may well be the case that recreating the .iso produces a more favourable outcome on the second occasion. Beyond that, we’d recommend ensuring that the configuration of the virtual machine closely matches ours, and that all command line entries have been input, as even minor variations here can cause the machine to fail to boot.
We don’t doubt that you’ve followed the steps perfectly, and something which we often mention is that when we create the .iso in the opening part of the tutorial, we are essentially performing multiple sequential file handling operations, as we first download the installer, then perform multiple conversion operations, before finally transferring from macOS to Windows. With each file handling operation, we introduce extra potential for corruption, and, of course, this isn’t something which you as the user have any real opportunity to detect until much later when you attempt to run the virtual machine. It’s for this reason that we always recommend recreating the .iso by repeating the early part of the tutorial. Whilst you may expect the same result, it is often the case that a one-off corruption occurring during the first run will not happen during the second, immediately fixing the problem. So our advice here is to recreate the .iso and try again. If it fails in the same way, you’ll at least confirm that the error can be replicated, and we can investigate further from there, but here’s hoping that it simply works.
Unless anyone can advise us to the contrary, we believe that Thunderbolt passthrough support is not presently implemented in VirtualBox, and seems unlikely to be in the future. We’d point you toward this article www.virtualbox.org/ticket/17730, which discusses PCI passthrough and Thunderbolt passthrough interchangeably. Of course, that position could change at any given moment, but presently adding Thunderbolt accessory support seems not to be possible.
Hi @Mahdi Hasan. We might need a little more context to fully understand your question, but we’ll set out a brief overview…In terms of your host machine (the Windows P.C.), you can set up your virtual machine using any drive which has sufficient free space, and this drive can either be your default system drive, or a drive specifically set up to host your virtual machine. Indeed, there’s enough flexibility that you could set up the virtual machine on one drive, and later transfer it to another should you wish. However, you don’t need to specifically create a new drive for this purpose, and the virtual machine and its associated virtual hard drive are nothing more than files which can be stored wherever you can accommodate them. In terms of your virtual machine, we mention at 19:04 in the video that you need to create a drive upon which the macOS installation will take place. This is purely because no drive is initialised by default, meaning that there would otherwise be no drive upon which the installation could be performed. This new drive is, of course, a virtual drive stored on the virtual hard drive file created during the initial setup of the virtual machine, and its storage space is derived directly from your host machine. So, all you’re really doing at this stage of the installation is pointing the virtual machine to its own virtual storage container. If this doesn’t answer your question, please get back in touch and we’ll explore this further.
@@TechFixFlix I read a blog post about this topic where it says, "It's highly recommended to create a new drive on your Windows PC and install macOS Big Sur on that drive." which also uses VirtualBox. It means creating a new partition. What is the reason for this and is this necessary?
Thanks for replying with the extra context @Mahdi Hasan. It poses an interesting question, and our honest answer is that we don’t think it is necessary, and have never created a new partition purely to accommodate a virtual machine. We could understand why this would make sense when using a physical machine (i.e. a “Hackintosh”), in which circumstance you’d want to maintain separate systems with a dedicated bootloader on the Mac side, but you mention that the blog post specifically references using VirtualBox, and this seems like overkill when both the virtual machine and its virtual hard drive are simply single files which can be stored and accessed much like any other. We’re certain that your blog poster will have a valid reason for this, but we can only really speculate. It might be that they have in mind allocating a fixed portion of the drive to their VM, with a set amount of storage. They would then select “Fixed” rather than “Dynamic” storage allocation during the configuration phase for the virtual machine. This will offer some performance benefits, because the machine isn’t then required to dynamically allocate storage as the drive fills. In this scenario, having a pre-allocated partition means that space is specifically reserved by the virtual machine and cannot be easily reclaimed by the system volume. Alternatively, the poster might have something entirely different in mind. We would therefore suggest that you certainly don’t need to create a new drive to perform the installation, and indeed we don’t show this process in our video. We remain curious as to why the blog post believes this to be “highly recommended” and would benefit from a more detailed explanation. We’re guessing that the post you’ve read might be www.wikigain.com/how-to-install-macos-big-sur-on-virtualbox-on-windows-pc/ and, if so, we note that the sentence is offered without additional explanation, so there’s no further context to assist.
Hi there. We’ve experienced a similar error in some of our earlier projects, and the solution is somewhat counterintuitive. Whilst you’d think that everything is fine with the installer because it has made it all the way through until less than a minute remains, where it refuses to make further progress, this is almost certainly indicative of a corrupt installation .iso. You are effectively tricked into thinking this cannot be the case, because you have made so much progress. In such instances, the only fix is to recreate the installation .iso by following the steps shown in the opening part of the tutorial. This typically occurs because we perform so many file-handling tasks in the early part of the tutorial, each increasing the risk of corrupting the data, and repeating these steps will eliminate any one-off errors which occurred during the first attempt.
@@TechFixFlix i was able to track the error to 16:10 i changed the directory to D: where i had installed the virtual box, after the countdown it stuck again but this time on 20:37
That’s really unfortunate, as you’re so close to success. You mentioned in your last reply that you’d made changes at 16:10 to reflect that your VirtualBox directory is in your D: drive, which is absolutely to correct thing to do, but, having taken those changes into account, is there any possibility that the issue we mentioned in our first reply could still be having an impact here, namely that the installer .iso is partially corrupt, allowing you to make significant progress but not complete the installation? In your position, we’d be inclined to rebuild the installation .iso to see if you can obtain a more positive outcome.
That’s unusual, and not an error which we’ve encountered before with this project. Once you’ve completed the installation and reached the dark screen with the white commands, have you tried manually resetting the virtual machine (Using the Machine > Reset command)? If so, does it simply return to the same screen? Apologies for not resolving this one quickly. As mentioned, this is the first time we’ve experienced this particular outcome.
Hi @Spencer Sexton. Much as we’d love to offer a positive update here, regrettably the position is unchanged from the publication of the video, and we’re still very much seeking improvements to general performance and sound input/output. One minor suggestion in relation to the sluggish mouse response was suggested in the comments…Essentially, it appears that a great amount of data processing is taking place in the immediate aftermath of the installation, typically at the point where the user is personalising their setup (from around 20:42 onward in our video). This high volume of background data transfer seems to contribute to the slow mouse response mentioned in the video at this point, which continues until well after the appearance of the macOS desktop. The suggested fix here is to allow a lengthy pause for these background processes to complete, after which the initial performance of the VM will be far less sluggish. Whilst this won’t represent a massive performance improvement, it may make the personalisation phase a little more tolerable. As before, if anyone reading these comments can offer any further suggestions to address the performance issues with the virtual machine, we’d love to hear from you.
It’s certainly not you, and no matter how powerful the hardware you throw at these projects, they are distinctly laggy, and there really is no substitute for running macOS on genuine Apple hardware. Originally, we were so thrilled to get macOS running under Windows - something which is rarely discussed or attempted - that we were prepared to overlook the lack of performance. Obviously, when this goes out to the wider world, people are understandably looking for something which is genuinely functional, rather than simply a technological curiosity. Naturally, there is a huge performance overhead from trying to run one extremely powerful and capable modern operating system within another. We had considered whether there were potential optimisations which might elevate the performance level to something more acceptable, but that hasn’t come to fruition yet.
We’ll need a bit more detail in order to help you progress here @Anej050. With a project of this size and complexity, there are many opportunities for it to go off course. Here are some of the most commonly encountered issues and questions: 1 )..Did you create your own .iso file as shown in the opening chapters of the tutorial? As ever, we are only able to assist people who are following our method, and unfortunately we cannot offer assistance to those who have sourced their .iso from elsewhere. 2 )..Repetition can be helpful, either to eliminate one-off errors in the process, or to confirm that whatever is causing the error can be reproduced. We would certainly recommend repeating the creation of the .iso file and the configuration of the virtual machine to see whether a better outcome can be obtained at the second attempt. 3 )..Be sure that the configuration of the virtual machine closely matches ours. Even small configuration issues can prevent the virtual machine from running. 4 )..Ensure that all commands are entered at the Windows Command Prompt, as the project will fail without them. 5 )..Double check that the .iso file is attached to the virtual machine as a virtual optical disc. We’ve experienced instances where it becomes detached, resulting in boot failure. 6 )..When reporting errors, it’s helpful to know the corresponding timecode in our video, expressed in minutes and seconds. It can also be helpful to include any error messages or text witnessed on screen.
I am trying to install macOS Big Sur on Virtual Box.. A few weeks back, the installation went on flawlessly on my first attempt then after 3 days or so I started getting the above error when I tried to boot in... Bottom line I deleted that instance of the vm and tried reinstalling it but to no avail... I keep getting the above error. My Tech Specs: 16GD RAM 512 GB SSD 4GB NVIDIA 1650TI Graphics Intel Core i7 - 10th Generation user-images.githubusercontent.com/34577844/126802530-143c2209-6214-46e9-9a13-f06c4fa77f96.png
Hi @Nishith P. That’s certainly a frustrating one, having worked for a short time before failing. One of the reasons we mentioned version numbers at some length in the video is that we’re dealing with an interaction between your physical hardware, Windows, VirtualBox, macOS current and the macOS installer. With effectively four “moving parts,” there always exists the possibility that something which worked in the past inexplicably stops because one of the four moving parts has evolved to a new version, breaking the chain which was previously successful. We’re assuming that, between the creation of your first successful virtual machine and your second, a disruptive change of this type may have occurred. Whilst we’re grateful for the screenshot, and they are almost always useful, in this project there’s always somewhat of a disconnect between the error messages you’ll see on screen, and the potential causes and remedies which are available to you, and, in this instance, there’s nothing in the screenshot which would point us toward a successful resolution. One thing we did consider was the name of your virtual machine. For example, if your first VM has worked then crashed as you described, then you deleted it and you created a new one, it’s possible that, if you recycled the same VM name, it would presumably inherit some aspects of its configuration from the previous VM with the same name. When starting over, we’d advocate a completely clean slate using a new name, fully recreating the virtual hardware etc and only keeping the installation .iso, which you already know works perfectly having tested it successfully. When starting from scratch with a working .iso, remember that you’ll need to repeat every step of the tutorial from around 11:15 onward. We’ve certainly experienced instances where even a single missed setting or command can cause a project to fail whilst presenting us with no obvious explanation. Do get back to us if you’re still struggling.
@@TechFixFlix Hey, Thanks for your reply.. I forgot to mention that the above screen remains for a period of time after which the vm restarts due to panic and the same process continues in a loop (please refer ss) user-images.githubusercontent.com/34577844/126889294-6a8750a4-3c7e-4ed7-a3fc-3032737e9477.jpg
Hi again. There’s nothing quite as reassuring as an error message featuring the word “panic,” and it certainly wouldn’t fill the average user with a great deal of confidence. We’re wondering whether you’ve yet had the opportunity to try recreating your VM a further time beginning with a blank slate, as mentioned in our last reply, and, if so, are the same error messages repeating?
Thanks for a very informative and clear video I just have one small issue, I have been trying to get macOS up and running on my rig for months and to date I haven't found a solution so would like to pose it to you, I have the following hardware: CPU: AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s) Motherboard: ROG STRIX B550-E GAMING RAM: 64.0 GB GPU: NVIDIA GeForce RTX 3080 Ti OS: Microsoft Windows 10 Enterprise Version: 10.0.19044 Build 19044 After following your instructions to the letter and using a self create ISO following your other videos I and presented with the following: # [EB.WL.DTIt] Err (0xE) # [EB.LD.LKFS1-?] Ok (0) # [EB.LD.LKCI-?] Ok (0) # [EBIFWFM] Ox00000000800003FF # [EBIFWFT] Ox0000000080000015 # [EBIBST:REV1] # [EB.CSR.FI!] Err(0xE) # [EB.LD.OFSIOPEN!] Err (0xE) # [EB.RH.LRHIP!] Err (0xE)
Hi @Lee Bailey. Glad to hear that you’re strictly following our method, and kudos to you for creating your own .iso. If this is a graphics issue, you’ll definitely want to experiment with the VirtualBox display settings. Right click your virtual machine and select “Settings” from the menu which appears. Then navigate to “Display” and check out your options under the “Graphics Controller” dropdown. We’d advocate trying each of the graphics controller options in turn, running the VM after each change, to see whether changing the specified graphics controller has any impact upon the performance of your virtual machine. If that fails, the next suggestion is extremely straightforward, but don’t forget to include the command which makes your VM believe that it is running on an Intel platform. We’ve featured this command in the tutorial, but do be sure to include the following amongst the entries at the Windows Command Prompt: VBoxManage modifyvm "Big Sur" --cpu-profile "Intel Core i7-6700K" (This assumes that you VM is named “Big Sur.”) If you’re still having no joy, it might be worth attempting to remake the .iso by repeating the steps from the beginning of the tutorial. We’ve certainly had experiences where an .iso can become corrupted during the creation process, and undertaking exactly the same steps on a second occasion can sometimes yield a more positive outcome. One other possibility relates to the fact that your last error message specifically references date and time. In our previous macOS projects, we’ve seen the virtual machine fail because its internal clock is set to a date which is rejected by the macOS installer, which appears to be time-sensitive, and will not install if the system clock doesn’t meet its expectations. As Big Sur is quite a recent version of macOS, it’s a reasonable assumption that it will anticipate something close to the current date, and if, for some reason, the virtual machine’s date is set to well before that, it may cause the issue you’re experiencing. Presumably this would only happen where the virtual machine inherits its clock from the host machine, and that host machine is either not synchronised via internet time or has a flat CMOS battery, meaning that the virtual machine thinks that the year is not 2022. We don’t know whether this is at all relevant to you, but we’ll offer it up as another possibility, and one which has genuinely caused issues on some of our previous projects. If none of this is useful, do get back in touch and we’ll try something else.
If it helps, I just posted my notes from some trials I ran about a month ago at pastebin.com/J5rCYysv. I think the last line in your post indicates MacOS doesn't like the idea of running on an AMD cpu. Maybe try: VBoxManage modifyvm "Monterey" --cpu-profile "Intel Xeon X5482 3.20GHz" You may get it running and find it panics randomly after install for some timeing reason. If so try: VBoxManage setextradata "Monterey" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
You really deserve a lot more subscribers. Every comment there is, you reply back. Most youtubers don't. And because you're doing things that work in the UK, SUBSCRIBED!
That’s really very kind of you. Being a small channel presents the opportunity to get to know our audience, often personally, and we’re really enjoying all of the conversations and trying to resolve tech issues. We’ll certainly be continuing to post content which is relevant here in our home country, but we’re also grateful for a huge percentage of views from overseas, so there will also be content which hopefully has an even wider appeal. Finally, we’re very grateful for your support and subscription. Good luck with your projects.
I've tried like 100 different tutorials by now within the past 6 months, and this is the first one that actually worked and booted. I don't know why only this tutorial is the only one that has worked in months, but thank you so much! Very appreciated :)
That’s great to hear. We’re really glad this worked for you.
@@TechFixFlix Is there anyway to get the sound to work?
Hi again @NotFunny. This is something which we’ve struggled with throughout the history of this project, and our virtual machines have been silent from the earliest High Sierra machine. We’ve had plenty of feedback from viewers who have looked into this and who have also drawn a blank. Our working theory is that drivers for both input and output don’t translate well in the virtual environment, although this isn’t an issue on all guest operating systems.
We’re hoping that someone may ultimately point us in the direction of a workable solution. We’re ideally looking for native drivers rather than relying upon third party modifications of unknown provenance, but, so far, they have proven elusive. We will publish a specific update in the event that a solution is found, but, until then, the lack of sound remains an issue we still need to resolve.
To the other youtubers who are bloating youtube with incoherent/ incomplete/incorrect/and ambiguous tutorials and claim they know their stuff...
please take notes from this video, this is how to properly make a tutorial. straight to the point and no BS. Period.
Wow. Thank you very much indeed for taking the time to comment with such positivity about the tutorial. As a creator, this is very much appreciated and means a great deal.
Your video is one of the best tutorials I've used in a long time. Subscribed for life!
Thank you very much indeed. That is very kind of you.
You are the best on many ive watched , explained well and on short, Well done!
Thank you very much indeed. Glad you found the content useful.
Amazing tutorial!!
Thank you very much indeed. That’s very kind of you.
@@TechFixFlix No problem!! This is like the only RUclips tutorial that actually works and teaches you clearly! Thanks again!
Thanks for mentioning the educational aspect of the video. We place far more value in the process than the product, and there’s so much to learn in these projects, even in failure. Once you understand the process, it can be modified to accommodate other versions of macOS.
@@TechFixFlix Definitely!
YES! IT IS HERE! I HAVE BEEN WAITING ALL WEEK FOR THIS :D
It took a little while longer than we’d hoped, but we got there in the end.
@@TechFixFlix Yep!
Clear and precise explanations. Thank you so much.
Thank you very much indeed @hicham Abdellaoui. Your positive feedback is very much appreciated.
Last line in the installer is EBILOG : EXITBS:START and then date and time
Hi Ian, and thanks for your kind words about this video. Yours is the first feedback we’ve had where the virtual machine hasn’t worked at the first attempt, so we don’t have previous data to call upon when looking into this.
We do, however, have the experience of our previous projects, so a few thoughts come to mind. Forgive is if you’ve already considered them, having watched the video:
1 )..Have you created your own installation .iso, as described in the first two chapters of the video? Although it’s mentioned in our introduction, we’re often asked to troubleshoot installations where the hard drive file is downloaded in a pre-prepared format. As this method differs from ours, we aren’t in a position to assist in these instances.
2 )..Assuming you have created your own .iso, were there any obvious issues during the creation process, and did the .iso file transfer from Mac to Windows? Do checksums or file sizes match pre and post transfer?
3 )..Are you using an AMD processor? This is frequently a cause for failure, and is something we discuss and resolve here: ruclips.net/video/sV42TRZNmDc/видео.html
4 )..Have you increased the processor count from 1 to 2? Omitting this simple option can lead to failure at this stage.
5 )..Have all of the commands been entered at the Windows Command Prompt?
6 )..If none of the above are relevant, it might be worth trying to recreate the .iso by repeating the early part of the tutorial, purely to rule out one-off errors. You may also wish to recreate the virtual hardware.
Sorry that this is more of a troubleshooting checklist than a definitive solution. At this early stage, we don’t have any solved failures to refer to. If none of this helps, do get back to us and we’ll take it from there.
@@TechFixFlix Hi - thanks for taking the time to respond it is much appreciated. I did create my own iso in fact I did it twice just to make sure there wasn't an error - checked file size on both occasions and both matched. All went smoothly on both occasions with no errors
I tried deleting the VM and re-created it several times tweaking the setting to try and make a difference but same result install freezes after a few seconds. I am using an AMD processor but did include the command included in your tutorial - I'll check out the video link you have sent to see if this helps
Thanks again
One other possibility relates to the fact that your last error message specifically references date and time. In our previous macOS projects, we’ve seen the virtual machine fail because its internal clock is set to a date which is rejected by the macOS installer, which appears to be time-sensitive, and will not install if the system clock doesn’t meet its expectations. As Big Sur is the current version of macOS, it’s a reasonable assumption that it will anticipate something close to the current date, and if, for some reason, the virtual machine’s date is set to well before that, it may cause the issue you’re experiencing. Presumably this would only happen where the virtual machine inherits its clock from the host machine, and that host machine is either not synchronised via internet time or has a flat CMOS battery, meaning that the virtual machine thinks that the year is not 2020. We don’t know whether this is at all relevant to you, but we’ll offer it up as another possibility, and one which has genuinely caused issues on some of our previous projects.
@@TechFixFlix I thought the same having messed with Hackingtosh machines n the past - on this occasion server is brand new and time is synchronised - I'm going to try the install on an intel laptop over the weekend to see how it goes - thanks for taking the time to try and assist
Hope it works out for you. Keep in touch with any significant developments.
getting the error:
Configuration error: Querying
"GetKeyFromRealSMC" as a boolean failed
(VERR_CFGM_NOT_INTEGER).
I have tried re entering the appropriate cmd prompts and got nothing, any advice?
I am using *Monterey* for this.
also checked the iso and it is still attached
Hi @cobra 727. Given that your error message specifically references "GetKeyFromRealSMC," we can safely assume that the command generating this error is:
VBoxManage setextradata "Monterey" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
Where “Monterey” is the name of your virtual machine. If your virtual machine is called anything other than “Monterey,” the name of your virtual machine would replace “Monterey” between the quotation marks.
The error message also references “not integer,” which would suggest that we’re missing a number. Have you included the number 1 which appears at the right end of the command?
@@TechFixFlix Ok did another attempt and got a little further the 2nd time. It went to the black apple loading bar and looped between that and the code execution screen for a while. Closed the VM and tried again and finally got all the way through. Even the audio works now.
That’s great. Glad you got this up and running. Did you do anything special to get the audio working? You might be the first person to have working audio following this project.
@@TechFixFlix I actually have no idea how I got the audio working, all I remember doing is changing what the sound effects play through. Just changing it to internal speakers. Might just be that im on Monterey and not Big Sur.
Thank you very much indeed for the reply @cobra 727. We’ve also extended this project to Monterey (see our video “Create A macOS Monterey Installer ISO - For VirtualBox Running On Windows” at ruclips.net/video/q9koLQSqrlc/видео.html for details) but it remains silent in terms of both audio input and output. Nevertheless, it’s great that yours is functioning normally.
Very well explained!!! Thanks!
That’s much appreciated. Thank you.
You deserve a sub!
That’s very kind. Thank you very much.
@@TechFixFlix Man, I love your voice
That's appreciated.
Hi TechFixFlix, I followed your instructions exactly. I keep getting this error message from VirtualBox on start. Failed to open a session for the virtual machine Big Sur. "Failed to query SMC value from the host (VERR_INVALID_HANDLE)." "Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole"
Hi @Joshua East. Glad to hear you’re been faithfully following our instructions. Not so glad to hear that they aren’t quite working for you. The error code 0x80004005 is typically associated with new or updated Windows builds or changes to Hyper-V. We’d be interested to know if this error is present in any virtual machine you create, or whether it purely impacts upon this project. If you’re happy to disable Hyper-V, and don’t use it for any other purpose, we’d give that a try first. You can always re-enable it later if necessary.
Disabling Hyper-V can be done in one of three ways.
Method A - Control Panel
1 )..Press your Windows key on the keyboard or click your “Start” button.
2 )..Type “Turn Windows Features On Or Off” and run the top search result.
3 )..Look for the “Hyper-V” feature and expand it.
4 )..Remove the tick next to “Hyper-V Hypervisor.”
5 )..Click O.K. and reboot the system.
Method B - Elevated Command Prompt
1 )..Press your Windows key on the keyboard or click your “Start” button.
2 )..Type “CMD” and select the option to run Command Prompt as Administrator.
3 )..Enter the following command: bcdedit /set hypervisorlaunchtype off
4 )..Exit Command Prompt and reboot the system.
Method C - PowerShell
1 )..Press your Windows key on the keyboard or click your “Start” button.
2 )..Type “PowerShell” and select the option to run PowerShell as Administrator.
3 )..Enter the following command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
4 )..Exit PowerShell and reboot the system.
Whichever method you choose, try restarting your virtual machine after your system reboots. Hopefully this will clear the error message. If not, get back in touch.
Got any solution for the audio issue? The same installation in vmware instead of virtualbox has audio working well. So, is there any solution for virtualbox?
Hi Naveen. We’ve performed many experiments in relation to sound, and we’ve received extensive feedback via the comments for our videos, all of which suggest that audio input and output devices don’t appear to be supported in VirtualBox. Your feedback in relation to VMWare is particularly interesting, as it does support our theory that this issue is specific to VirtualBox, rather than any other aspect of the method. It also leaves open the possibility that future updates to VirtualBox might ultimately allow us to enable sound.
Is there a way to enable audio? I'm looking at trying to use Garageband and video editing software and they obviously both require audio
We can immediately see from your channel why audio is important to you, but we’re afraid the news here isn’t good. Unfortunately, all of our virtual Mac projects to date have been silent, and this is something we mention at 24:21 in the video. We’ve been aware of this issue since our first Mac project in 2019, and, despite numerous investigations both here and amongst our community, we’ve yet to find any fix for this. You’ll note within Settings that there are no devices listed for audio input or output, and we believe this to be a limitation of VirtualBox. We’re still hopeful that a workaround will appear at some future point, although for now we’re still very much in search of a solution.
you sound so happpy and exited love the energy man but mine is stuck on the installing screen near the middle on the apple logo any help
Hi there @Toxic Productions, glad you like the presentation of the video. It’s fantastic to have a platform where we can make content about our favourite subjects then discuss it with friends around the world, so “happy and excited” is absolutely the correct description.
Of course, not every project works successfully at the first attempt, and this one is particularly complex. As you’re stuck on a screen featuring the Apple logo, our hunch would be that the installer .iso has become corrupted, during one of the many file-handling processes undertaken during the first part of the tutorial on macOS. This does seem to happen to a significant proportion of people following this tutorial. Typically, where the installer becomes corrupted, it can be difficult to detect because it will allow a certain amount of progress to occur before failing, rather than failing immediately as you might expect (although it does also fail immediately in some cases).
The solution is to repeat the first part of the tutorial and create a new installation .iso. You might think the outcome will be the same, but often one-off errors do not occur on a second run-through.
Hopefully this will resolve your issue. If not, do get back to us and we’ll explore further.
@@TechFixFlix Thank you for your support
You are very welcome.
There's a problem on my VM, on first boot it shows me this error: " [EBILOG:EXITBS:START] 2021-03-26T09:22:45 " I've tried over 20 tutorials before this one and nothing helps. I keep getting the same error.
Unfortunately, that’s a fairly generic error which doesn’t identify a specific cause. You’ve mentioned that you’ve tried over twenty tutorials, which suggests that you’re probably experimenting quite a lot, which we’d always encourage, but we do need to ask whether you’re following our method strictly, and specifically whether you’ve created your own .iso as shown in the first ten minutes of our video. Many people use our tutorial as a troubleshooter, having previously downloaded a pre-prepared .vdi, .vdmk or .iso from the web, and we are unable to offer assistance here as we have no way of knowing how these files were created.
@@TechFixFlix Indeed I was using a downloaded iso file, sorry. I'm currently making a USB through a relatives mac as shown in the vid, I'll update on how it goes. Thanks for the fast reply!
That’s great. Hopefully a change of method will produce a better outcome. Looking forward to hearing how you get on.
@@TechFixFlix Hey, I followed everything in the video from start until 18:20 now and it still shows me the same error. I checked the .iso file and it's size which was the same, checked if the .iso is still attached, it was. I added the command for AMD processors as I'm running on Ryzen processor. I installed everything on default locations on my laptop. It gets stuck on a certain line of code (NOTE: Before this code, it shows me a couple of Errors similar to this one) " [EB.LD.LKCIR.2] " for around 5 seconds and after that it throws me to the [EBILOG:EXIT:START] 2021-03-26T19:21:31
@@TechFixFlix I uploaded the two screenshots of these errors to imgur. Here's the link: imgur.com/gallery/iY9INcd
Maybe this can give you a better idea on how to help me or what the error might be.
At the third terminal command it says command not found and it dosnt start to convert or show the progress please help
Our third command is this one:
sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSur -nointeraction
Provided that you have copied the command from our description and pasted it into your Terminal app, we would fully expect it to work as shown in the video. The only exceptions we’ve experienced where the command itself fails occur with much older versions of macOS which have not been updated, so we’d be curious as to which version of macOS you’re using to create the installation media.
We’d assume that you’ve downloaded the installer app directly from the App Store, that it’s located in your Applications folder, and that you’ve copied the command directly from the description.
If you’ve already ruled out all of the possibilities mentioned above, it’s possible that your system is experiencing an issue which is beyond the scope of this tutorial, and we’d recommend reading the article below for possible further suggestions:
osxdaily.com/2018/05/24/command-not-found-mac-terminal-error-fix/#:~:text=The%20four%20most%20common%20reasons,directory%20was%20deleted%20or%20modified
@@TechFixFlix i have the same problem. running High Sierra (10.13). any solution?
Hi @rps HD. You should be able to follow the tutorial using High Sierra as your starting point and indeed we’ve used High Sierra for an earlier tutorial in this series. Here are some quick thoughts to consider…
1 )..Have you downloaded the full version of the Big Sur installer? Was it sourced directly from the App Store? Is it located in your Applications folder?
2 )..Did the first and second commands execute without generating an error message?
3 )..Have you copied the command directly from the video description using cut and paste?
4 )..What is the exact error message which appears when the third command fails?
5 )..Is your version of macOS fully updated, and is the system date / time correctly set?
@TechFixFlix
Could you do a video on installing Windows 8.1 on virtualbox? I know the official way to get the iso, but whenever the machine restarts, it goes back to the beginning and goes onto the first screen again. Thanks.
Hi again Ibrahim. Quite some time ago, we published a video installing Windows on VirtualBox, which you’ll find at ruclips.net/video/zqbMXXDJEyI/видео.html, although this video features Windows 10, rather than Windows 8, so it might only be indirectly relevant to you. From your description of your installation looping, we think you might need to eject the installation .iso once the initial installation has been performed. If the .iso isn’t ejected, there’s a possibility that it will be detected once the machine reboots, taking you back to the start of the installation process, in a loop which will continue until broken.
@@TechFixFlix Ok, thanks
You’re very welcome.
Hi TechFixFlix, I followed your instructions and end up with a UEFI startup.nsh error and a Shell> prompt.
I also re-do a few times and end up with the same issue. Is there a solution for this? Thanks.
Hi there @Duuc Huung. Sorry to hear this isn’t going smoothly for you. Under normal circumstances, our advice to anyone experiencing this issue is to double check that the .iso you created in the first part of the tutorial has been attached to the virtual optical drive. We’ve seen examples on more than one occasion of the virtual disc becoming detached before the virtual machine is run, even when the user has specifically attached it. We say this because, when the virtual machine boots, the first thing it does it to check whether there is bootable media attached from which it is able to boot, and, where it fails, it will exit to the shell prompt, which happens to be where you currently are. However, the fact that you mention that you’ve redone the tutorial a few times only to end up at the same point does give us concern that there might be something else going on here which we haven’t experienced before. One of the things we mention in the video is the various version numbers of the installers and operating systems we are using…Are there any significant differences in your setup? We also mention file sizes and checksums for the .iso file…Are you confident that the file has transferred correctly from Mac to Windows, and that it is the correct size? Naturally, there are quite a few variables here, so the cause of the issue might not be immediately obvious.
Hi@@TechFixFlix . Thanks for getting back to me on this issue. Yes, you are correct concerning the ISO file. The one I used was corrupted somehow. I've made a new one and it's working fully now running on Virtualbox. Thanks for the tutorial, subbed and liked.
Thank you for the sub and like, both of which are truly appreciated. Thanks also for the feedback in relation to the corrupted .iso, as this will be helpful for others in the same situation. We can only speculate that the number of file handling operations in the early part of the tutorial (i.e. downloading then repeatedly converting before transferring across platforms) opens the door to corruption. Sometimes a corrupted .iso will allow a partial installation. Your example shows us that a corrupted installer might also halt the installation at VM startup and send the user into the EFI shell environment, which is useful to note.
Hi - excellent video - my install freezes at the same place each time after a few seconds - where it shows a start time ........ any ideas ?
Did you ever figure this out? I have the same thing. Using Windows 10 on an AMD processor.
Hi @Howard Goff. We don’t know whether or not you’ve had the opportunity to read the much longer discussion thread we had with “@Me and the Mrs” in which we set out every issue and potential resolution which is known to us. This was started as a separate discussion thread, and contained several possible avenues to explore. Although we weren’t able to resolve the specific issue which we were investigating, there’s a possibility that something in there might be useful to you, so we’d recommend checking out that thread. We didn’t receive any final feedback from “@Me and the Mrs,” so we aren’t sure if there’s a solution to be shared.
Please accept our sincere apologies for the delay in responding to your comment. We have been extensively pursuing activities outside of the RUclips platform for the past six weeks, and consequently we are only now catching up on feedback and questions. Thank you for your patience and understanding.
it keeps stopping at step 20:40
"Forcing CS_RUNTIME for entitlement: com.apple.rootless.restricted-block-devices"
can someone help me figure out what's wrong?
We typically recommend repetition here, purely to rule out the possibility of one-off errors. In particular, we’d advocate recreating the installer .iso from the opening chapters of the tutorial, as the number of file-handling operations undertaken introduces the risk of accidentally corrupting the data, and it may well be the case that recreating the .iso produces a more favourable outcome on the second occasion. Beyond that, we’d recommend ensuring that the configuration of the virtual machine closely matches ours, and that all command line entries have been input, as even minor variations here can cause the machine to fail to boot.
But I follow all the steps and didn't change anything even a single thing
We don’t doubt that you’ve followed the steps perfectly, and something which we often mention is that when we create the .iso in the opening part of the tutorial, we are essentially performing multiple sequential file handling operations, as we first download the installer, then perform multiple conversion operations, before finally transferring from macOS to Windows. With each file handling operation, we introduce extra potential for corruption, and, of course, this isn’t something which you as the user have any real opportunity to detect until much later when you attempt to run the virtual machine. It’s for this reason that we always recommend recreating the .iso by repeating the early part of the tutorial. Whilst you may expect the same result, it is often the case that a one-off corruption occurring during the first run will not happen during the second, immediately fixing the problem. So our advice here is to recreate the .iso and try again. If it fails in the same way, you’ll at least confirm that the error can be replicated, and we can investigate further from there, but here’s hoping that it simply works.
How do I add thunderbolt accessories support
Unless anyone can advise us to the contrary, we believe that Thunderbolt passthrough support is not presently implemented in VirtualBox, and seems unlikely to be in the future. We’d point you toward this article www.virtualbox.org/ticket/17730, which discusses PCI passthrough and Thunderbolt passthrough interchangeably. Of course, that position could change at any given moment, but presently adding Thunderbolt accessory support seems not to be possible.
Is this necessary to create a new drive to install mac os?
Hi @Mahdi Hasan. We might need a little more context to fully understand your question, but we’ll set out a brief overview…In terms of your host machine (the Windows P.C.), you can set up your virtual machine using any drive which has sufficient free space, and this drive can either be your default system drive, or a drive specifically set up to host your virtual machine. Indeed, there’s enough flexibility that you could set up the virtual machine on one drive, and later transfer it to another should you wish. However, you don’t need to specifically create a new drive for this purpose, and the virtual machine and its associated virtual hard drive are nothing more than files which can be stored wherever you can accommodate them.
In terms of your virtual machine, we mention at 19:04 in the video that you need to create a drive upon which the macOS installation will take place. This is purely because no drive is initialised by default, meaning that there would otherwise be no drive upon which the installation could be performed. This new drive is, of course, a virtual drive stored on the virtual hard drive file created during the initial setup of the virtual machine, and its storage space is derived directly from your host machine. So, all you’re really doing at this stage of the installation is pointing the virtual machine to its own virtual storage container.
If this doesn’t answer your question, please get back in touch and we’ll explore this further.
@@TechFixFlix I read a blog post about this topic where it says, "It's highly recommended to create a new drive on your Windows PC and install macOS Big Sur on that drive." which also uses VirtualBox. It means creating a new partition. What is the reason for this and is this necessary?
Thanks for replying with the extra context @Mahdi Hasan. It poses an interesting question, and our honest answer is that we don’t think it is necessary, and have never created a new partition purely to accommodate a virtual machine. We could understand why this would make sense when using a physical machine (i.e. a “Hackintosh”), in which circumstance you’d want to maintain separate systems with a dedicated bootloader on the Mac side, but you mention that the blog post specifically references using VirtualBox, and this seems like overkill when both the virtual machine and its virtual hard drive are simply single files which can be stored and accessed much like any other.
We’re certain that your blog poster will have a valid reason for this, but we can only really speculate. It might be that they have in mind allocating a fixed portion of the drive to their VM, with a set amount of storage. They would then select “Fixed” rather than “Dynamic” storage allocation during the configuration phase for the virtual machine. This will offer some performance benefits, because the machine isn’t then required to dynamically allocate storage as the drive fills. In this scenario, having a pre-allocated partition means that space is specifically reserved by the virtual machine and cannot be easily reclaimed by the system volume. Alternatively, the poster might have something entirely different in mind.
We would therefore suggest that you certainly don’t need to create a new drive to perform the installation, and indeed we don’t show this process in our video. We remain curious as to why the blog post believes this to be “highly recommended” and would benefit from a more detailed explanation. We’re guessing that the post you’ve read might be www.wikigain.com/how-to-install-macos-big-sur-on-virtualbox-on-windows-pc/ and, if so, we note that the sentence is offered without additional explanation, so there’s no further context to assist.
20:27 mine is stuck on installation part on "less than a minute remaining"
Hi there. We’ve experienced a similar error in some of our earlier projects, and the solution is somewhat counterintuitive. Whilst you’d think that everything is fine with the installer because it has made it all the way through until less than a minute remains, where it refuses to make further progress, this is almost certainly indicative of a corrupt installation .iso. You are effectively tricked into thinking this cannot be the case, because you have made so much progress. In such instances, the only fix is to recreate the installation .iso by following the steps shown in the opening part of the tutorial. This typically occurs because we perform so many file-handling tasks in the early part of the tutorial, each increasing the risk of corrupting the data, and repeating these steps will eliminate any one-off errors which occurred during the first attempt.
@@TechFixFlix i was able to track the error to 16:10 i changed the directory to D: where i had installed the virtual box, after the countdown it stuck again but this time on 20:37
That’s really unfortunate, as you’re so close to success. You mentioned in your last reply that you’d made changes at 16:10 to reflect that your VirtualBox directory is in your D: drive, which is absolutely to correct thing to do, but, having taken those changes into account, is there any possibility that the issue we mentioned in our first reply could still be having an impact here, namely that the installer .iso is partially corrupt, allowing you to make significant progress but not complete the installation? In your position, we’d be inclined to rebuild the installation .iso to see if you can obtain a more positive outcome.
@@TechFixFlix the installation process has completed but it wasn't able to load past the dark screen with white commands
That’s unusual, and not an error which we’ve encountered before with this project. Once you’ve completed the installation and reached the dark screen with the white commands, have you tried manually resetting the virtual machine (Using the Machine > Reset command)? If so, does it simply return to the same screen?
Apologies for not resolving this one quickly. As mentioned, this is the first time we’ve experienced this particular outcome.
Any update on mouse or general performance in the VM?
Hi @Spencer Sexton. Much as we’d love to offer a positive update here, regrettably the position is unchanged from the publication of the video, and we’re still very much seeking improvements to general performance and sound input/output. One minor suggestion in relation to the sluggish mouse response was suggested in the comments…Essentially, it appears that a great amount of data processing is taking place in the immediate aftermath of the installation, typically at the point where the user is personalising their setup (from around 20:42 onward in our video). This high volume of background data transfer seems to contribute to the slow mouse response mentioned in the video at this point, which continues until well after the appearance of the macOS desktop. The suggested fix here is to allow a lengthy pause for these background processes to complete, after which the initial performance of the VM will be far less sluggish. Whilst this won’t represent a massive performance improvement, it may make the personalisation phase a little more tolerable.
As before, if anyone reading these comments can offer any further suggestions to address the performance issues with the virtual machine, we’d love to hear from you.
You definitely earned my sub.
That’s appreciated. Thank you very much indeed.
I installed all ok, but is it me or smth wrong? ... kinda slow really
It’s certainly not you, and no matter how powerful the hardware you throw at these projects, they are distinctly laggy, and there really is no substitute for running macOS on genuine Apple hardware. Originally, we were so thrilled to get macOS running under Windows - something which is rarely discussed or attempted - that we were prepared to overlook the lack of performance. Obviously, when this goes out to the wider world, people are understandably looking for something which is genuinely functional, rather than simply a technological curiosity. Naturally, there is a huge performance overhead from trying to run one extremely powerful and capable modern operating system within another. We had considered whether there were potential optimisations which might elevate the performance level to something more acceptable, but that hasn’t come to fruition yet.
I cant get past white text.
We’ll need a bit more detail in order to help you progress here @Anej050. With a project of this size and complexity, there are many opportunities for it to go off course. Here are some of the most commonly encountered issues and questions:
1 )..Did you create your own .iso file as shown in the opening chapters of the tutorial? As ever, we are only able to assist people who are following our method, and unfortunately we cannot offer assistance to those who have sourced their .iso from elsewhere.
2 )..Repetition can be helpful, either to eliminate one-off errors in the process, or to confirm that whatever is causing the error can be reproduced. We would certainly recommend repeating the creation of the .iso file and the configuration of the virtual machine to see whether a better outcome can be obtained at the second attempt.
3 )..Be sure that the configuration of the virtual machine closely matches ours. Even small configuration issues can prevent the virtual machine from running.
4 )..Ensure that all commands are entered at the Windows Command Prompt, as the project will fail without them.
5 )..Double check that the .iso file is attached to the virtual machine as a virtual optical disc. We’ve experienced instances where it becomes detached, resulting in boot failure.
6 )..When reporting errors, it’s helpful to know the corresponding timecode in our video, expressed in minutes and seconds. It can also be helpful to include any error messages or text witnessed on screen.
THANK YOU SO SO SO SO SO SO MUCH!
You are very welcome. Thanks for your support and encouragement.
@@TechFixFlix No problem :)
I am trying to install macOS Big Sur on Virtual Box..
A few weeks back, the installation went on flawlessly on my first attempt then after 3 days or so I started getting the above error when I tried to boot in...
Bottom line I deleted that instance of the vm and tried reinstalling it but to no avail... I keep getting the above error.
My Tech Specs:
16GD RAM
512 GB SSD
4GB NVIDIA 1650TI Graphics
Intel Core i7 - 10th Generation
user-images.githubusercontent.com/34577844/126802530-143c2209-6214-46e9-9a13-f06c4fa77f96.png
Hi @Nishith P. That’s certainly a frustrating one, having worked for a short time before failing. One of the reasons we mentioned version numbers at some length in the video is that we’re dealing with an interaction between your physical hardware, Windows, VirtualBox, macOS current and the macOS installer. With effectively four “moving parts,” there always exists the possibility that something which worked in the past inexplicably stops because one of the four moving parts has evolved to a new version, breaking the chain which was previously successful. We’re assuming that, between the creation of your first successful virtual machine and your second, a disruptive change of this type may have occurred.
Whilst we’re grateful for the screenshot, and they are almost always useful, in this project there’s always somewhat of a disconnect between the error messages you’ll see on screen, and the potential causes and remedies which are available to you, and, in this instance, there’s nothing in the screenshot which would point us toward a successful resolution.
One thing we did consider was the name of your virtual machine. For example, if your first VM has worked then crashed as you described, then you deleted it and you created a new one, it’s possible that, if you recycled the same VM name, it would presumably inherit some aspects of its configuration from the previous VM with the same name. When starting over, we’d advocate a completely clean slate using a new name, fully recreating the virtual hardware etc and only keeping the installation .iso, which you already know works perfectly having tested it successfully. When starting from scratch with a working .iso, remember that you’ll need to repeat every step of the tutorial from around 11:15 onward. We’ve certainly experienced instances where even a single missed setting or command can cause a project to fail whilst presenting us with no obvious explanation.
Do get back to us if you’re still struggling.
@@TechFixFlix Hey, Thanks for your reply.. I forgot to mention that the above screen remains for a period of time after which the vm restarts due to panic and the same process continues in a loop (please refer ss)
user-images.githubusercontent.com/34577844/126889294-6a8750a4-3c7e-4ed7-a3fc-3032737e9477.jpg
Hi again. There’s nothing quite as reassuring as an error message featuring the word “panic,” and it certainly wouldn’t fill the average user with a great deal of confidence. We’re wondering whether you’ve yet had the opportunity to try recreating your VM a further time beginning with a blank slate, as mentioned in our last reply, and, if so, are the same error messages repeating?
Thanks for a very informative and clear video I just have one small issue, I have been trying to get macOS up and running on my rig for months and to date I haven't found a solution so would like to pose it to you, I have the following hardware:
CPU: AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s)
Motherboard: ROG STRIX B550-E GAMING
RAM: 64.0 GB
GPU: NVIDIA GeForce RTX 3080 Ti
OS: Microsoft Windows 10 Enterprise
Version: 10.0.19044 Build 19044
After following your instructions to the letter and using a self create ISO following your other videos I and presented with the following:
# [EB.WL.DTIt] Err (0xE)
# [EB.LD.LKFS1-?] Ok (0)
# [EB.LD.LKCI-?] Ok (0)
# [EBIFWFM] Ox00000000800003FF
# [EBIFWFT] Ox0000000080000015
# [EBIBST:REV1]
# [EB.CSR.FI!] Err(0xE)
# [EB.LD.OFSIOPEN!] Err (0xE)
# [EB.RH.LRHIP!] Err (0xE)
Hi @Lee Bailey. Glad to hear that you’re strictly following our method, and kudos to you for creating your own .iso. If this is a graphics issue, you’ll definitely want to experiment with the VirtualBox display settings. Right click your virtual machine and select “Settings” from the menu which appears. Then navigate to “Display” and check out your options under the “Graphics Controller” dropdown. We’d advocate trying each of the graphics controller options in turn, running the VM after each change, to see whether changing the specified graphics controller has any impact upon the performance of your virtual machine.
If that fails, the next suggestion is extremely straightforward, but don’t forget to include the command which makes your VM believe that it is running on an Intel platform. We’ve featured this command in the tutorial, but do be sure to include the following amongst the entries at the Windows Command Prompt:
VBoxManage modifyvm "Big Sur" --cpu-profile "Intel Core i7-6700K"
(This assumes that you VM is named “Big Sur.”)
If you’re still having no joy, it might be worth attempting to remake the .iso by repeating the steps from the beginning of the tutorial. We’ve certainly had experiences where an .iso can become corrupted during the creation process, and undertaking exactly the same steps on a second occasion can sometimes yield a more positive outcome.
One other possibility relates to the fact that your last error message specifically references date and time. In our previous macOS projects, we’ve seen the virtual machine fail because its internal clock is set to a date which is rejected by the macOS installer, which appears to be time-sensitive, and will not install if the system clock doesn’t meet its expectations. As Big Sur is quite a recent version of macOS, it’s a reasonable assumption that it will anticipate something close to the current date, and if, for some reason, the virtual machine’s date is set to well before that, it may cause the issue you’re experiencing. Presumably this would only happen where the virtual machine inherits its clock from the host machine, and that host machine is either not synchronised via internet time or has a flat CMOS battery, meaning that the virtual machine thinks that the year is not 2022. We don’t know whether this is at all relevant to you, but we’ll offer it up as another possibility, and one which has genuinely caused issues on some of our previous projects.
If none of this is useful, do get back in touch and we’ll try something else.
If it helps, I just posted my notes from some trials I ran about a month ago at pastebin.com/J5rCYysv.
I think the last line in your post indicates MacOS doesn't like the idea of running on an AMD cpu. Maybe try:
VBoxManage modifyvm "Monterey" --cpu-profile "Intel Xeon X5482 3.20GHz"
You may get it running and find it panics randomly after install for some timeing reason. If so try:
VBoxManage setextradata "Monterey" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
Thanks very much for that @Howard Goff. It’s always rewarding to receive valuable feedback from our community.