@Fares Bou Najm. We really should have released Part II by now. The audio was recorded back in November 2021, but we felt there was considerable similarity to our Big Sur video (see ruclips.net/video/sV42TRZNmDc/видео.html for details), and the steps which form Parts II and III are essentially identical for both projects. Once you’ve created your ISO, you can drop into that video just before the eighth minute, and follow from there.
Thank you for this very detailed explanation. Quick question, is the downloaded version registered or linked in any way to the Apple account that downloaded it? I don't have a Mac, so I'd have to try to bum around for someone with a Mac, but I don't want it to link back to them if they help me with this.
Great question. What is the role of the host machine, and how can we be certain that its fingerprints don’t transfer to the virtual machine? There is a logical answer to this, and it comes down to checksums. If you’re unfamiliar with checksums, take a look at www.imore.com/checksums-101-how-make-sure-your-downloads-are-real-deal. In short, we’re using the host Mac purely to download a piece of software, and that piece of software is the macOS installer app. That app will have a checksum. If the checksum is the same no matter what host you use to download it, it will be apparent that the software has not been modified as a consequence of contact with the host. If the.checksum varies with each machine, this would be indicative of some form of customisation to match the host. It might take a spot of online research to find the correct checksum for the specific installer version you’re downloading, or, if you’re incredibly fortunate and have access to two Macs you could confirm via experimentation. We strongly suspect that the installer app is not customised to reflect its origins.
@@TechFixFlix Thanks for the reply. Yes, I am familiar with checksums, however I do not know where to find checksums for MacOS and googling it didn't turn up any results. The checksum would also depend on the specific update I'm downloading, not just the primary version so that would make it even harder to find a checksum for the specific version of their MacOS. I'm unlikely to get access to multiple Mac's to compare checksums, I can only think of one person I know that owns a Mac and I wanted to make sure the OS wouldn't be automatically registered to them before I asked. Thanks again.
You are a very responsible friend @Tekkerue, and we admire you for taking sensible precautions where others would potentially dive directly in. We hope you find a solution to this.
Hi there. We suspect that there are very many people in exactly this position. Apple doesn’t make bootable .iso files available for download, and this makes perfect sense from the perspective of their business model, in that every device they sell comes with macOS preinstalled. Therefore, the only reason to obtain an .iso is to run it on non-Apple hardware, which, of course, doesn’t generate revenue for Apple. Whilst this protects Apple’s revenue, it’s harsh for hobbyists like us who simply want to experience macOS on Windows, leaving us without a safe and official path to accessing .iso files. For this reason, we undertook this project to create our own .iso. Of course, we were in the fortunate position to have access to our own Mac, and we fully appreciate that not everyone will have a device as a starting point for this project. As we mention in the video, there are third-party images files available online. We’ve never used them, don’t trust them and wouldn't recommend any of them. We do realise, however, that some people may have no other option and may opt to follow this route at their own risk. Sorry the news isn’t better here.
What if we don't have a device ( = Apple computer) already running MacOS? Is it possible to download somewhere an already created *.ISO image of MacOS? It does not have to be Monterery, but the more recent the better. Thanks.
Hi @ Jerry Suppan. You can essentially take one of two paths with this project, although the first is only open to those people who can access a physical Mac. If you are fortunate enough to be in this position, you can create your own ISO as shown in our tutorial. This method allows us a great deal of control over the creation of the installation media, and reduces the risk of unwanted extras which could theoretically be hidden with ISOs originating from unknown sources. In many respects, there’s an easier path for those who don’t have access to a Mac, and that is simply to Google “macOS installer ISO” or “Monterey ISO” etc. Taking this path, you will be relying upon pot luck, and you simply won’t know how the ISO was created, whether it will work, whether it will be compatible with your virtualisation software or whether it will come with any unexpected surprises. It’s for these reasons that we do not advocate following this route, and that we cannot offer support to people who are not following our method directly. We appreciate that many will follow this route anyway, given that access to a physical Mac presents a high bar to entry for most. Whichever way you go with this, we wish you luck. 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.
Hi, i've created correctly the Mpnterrey.iso file but during the booting of virtual machina on virtualbox it continues to crash. I've followed the video about BigSur virtual machine with .iso file but it' doesn't work, can you help me please?
Hi @Leonardo Persici. You’re absolutely correct to refer to the Big Sur tutorial, as the steps to follow are identical once you’ve created the installation media. Although there are many reasons why this project might crash, the first thing we’d check is the integrity of the installation media. We’re aware from personal experience that, no matter how diligently you create the installation .iso, it can still become corrupted, purely as a consequence of the number of file handling / conversion operations performed upon it. Often the simplest solution is to repeat the opening phase of the video and create a new version of the installation media. Although you might expect the same outcome, experience suggests that creating a fresh .iso can result in a successful outcome. If, having created a second .iso, the project still crashes for you, get back in touch and we’ll explore some other options. These projects are far from straightforward, and require many interdependent variables to successfully align.
On step command two i get - No mountable file systems. when retuning the first command it says file exists? Would i need to start over and how do i purge that file?
Hi @Chirag Gandhi. This happened to us once in testing, and it was a bit of a nightmare. You're right that you need to start over, but purging that file is the difficult part. Given that the temporary file hasn't mounted, you'll either need to delete the temporary file or alternatively, you could leave the temporary file alone, and restart the project using an entirely different name for the temporary file in the first command and any subsequent references. If you do decidec to delete the file, you'll find this summary of hdiutil commands helpful: ss64.com/osx/hdiutil.html
Thanks for the tutorial. I was able to use your Big Sur video to set up the VM part. However, I'm not able to boot into RecoveryOS of the guest machine using cmd-r or even from the terminal command: nvram -d recovery-boot-mode. I get an error: Error setting variable - 'recovery-boot-mode': (iokit/common) not permitted. Do you know anyway to get around this and get into the RecoveryOS?
That’s an interesting question @bob bob, and not one we’ve addressed before. Two options come to mind, although we haven’t tested either. The first would be to attach a recovery boot image as a separate virtual disk, as outlined in this article: www.geekrar.com/get-into-recovery-mode-macos-virtual-machine (scroll down for instructions specific to VirtualBox). The second would be to navigate the EFI shell and access recovery boot by entering commands at the prompt. You’ll find a summary of that process here: github.com/geerlingguy/macos-virtualbox-vm/issues/46 As we haven’t tested these options, we’d welcome any feedback you can offer in respect of their suitability for use with Monterey.
@TechFixFlix Thank you for the links. I have tryed the second method and it doesn't appear to work. For the first one though, they only provide a macOS Recovery Boot Image for macOS Mojave. Is there a way I could possibly create my own boot image, like you did in your video with the .iso
We did have another thought on this topic, which may or may not be useful to you, depending on your specific needs. If you reattach the installation .iso to the virtual optical drive of your virtual Mac and boot from it, you should eventually be taken to macOS Utilities, with options including Restore From Time Machine, Reinstall macOS Monterey, Safari and Disk Utility. If this isn’t what you need, please accept our apologies and get back in touch.
Thank you for the reply. I don't know if this helps, but the reason I'm trying to get into recovery mode in the first place is to download VBoxDarwinAdditions.pkg, the guest additions for MacOS. This I believe improves the performace a bit and provides shared folders between the host and virtual machine. However, once I try to download them, they fail. So I searched online for a solution. I came accross this: github.com/geerlingguy/macos-virtualbox-vm/issues/79 . The solution they provided requires recovery mode. I'm going to see if the new method you provided works over the weekend.
That makes perfect sense, and we can see now why you need to access the recovery environment. The method set out in the linked article has quite a few steps, so we hope you make progress with it. As one of your key objectives was to set up shared folders between the host and the virtual machine, may we suggest taking a look at another of our videos, namely “Networking In VirtualBox - Access Network Devices And Folders From Your Virtual Machine,” which you’ll find at: ruclips.net/video/7CSFbsE-E98/видео.html In this instance, our definition of “Networking” very much includes bi-directional communication between the guest and host, as well as between the guest and the wider network. In the video, we use a Windows guest, but the fundamentals apply equally to a macOS guest, although we’d also point you in the direction of a later video “File Sharing - macOS To Windows” (see ruclips.net/video/xqf9vm07uCQ/видео.html ) in which we specifically address file sharing between the two platforms. Hopefully some of that will help if your Guest Additions project runs into difficulties.
now i need help to install it on virtualbox, it just crashes when im trying to boot it. I try with some commands in the cmd but nothing... i hope yo would continue this serie. Thanks
Hi @Alejandro Vázquez Pan. Rest assured that this series is still very much in production, and we have already recorded vocals and preliminary graphics for Part II. Whilst it’s still in development, you might find its predecessor useful. You’ll find that video (which installs Big Sur) at ruclips.net/video/sV42TRZNmDc/видео.html The commands used at the Windows Command Prompt are essentially identical to those used for Monterey, so you may find the section at ruclips.net/video/sV42TRZNmDc/видео.html useful.
Hi @Will Sells. Our original plan was to publish two further videos, the first detailing the configuration of the virtual machine on Windows, and the other outlining the macOS out-of-box experience. In practice, however, these steps are identical to those we've previously covered in our Big Sur video, which we think you'll find useful. The link to that video is ruclips.net/video/sV42TRZNmDc/видео.html and, if you've already created your .iso file in macOS, you can jump to 7:52 in that video. Also, you can find some of our earlier macOS-on-Windows projects at www.techfixflix.com/p/tutorials-for-macos.html
@@TechFixFlix can I recommend a video for running a different Osx on a virtual box from Osx? Its what I was trying to to to test Monterey compatibility without upgrading. I struggled but got there this morning.
Glad you’ve made progress with this. We haven’t published a video of our own running macOS within macOS, although we did something similar with Windows (see ruclips.net/video/zqbMXXDJEyI/видео.html for info).
I have it running on VirtualBox using the method described in the Big Sur video, but I've had it crash on me twice now. Hoping when you have the install video out that it addresses any minor differences in the process. Also in the Big Sur video, you mentioned that it could find other network devices by bridging the connection, but I haven't been able to do that. Would it be possible to show in the Monterey video how that works?
Hi @Neil, and thanks for all of your feedback on your project, which is very much appreciated. Please be assured that the install video is in the pipeline, and will be appearing in the next few weeks, although we’d confess immediately that there are no significant differences in the installation phase when compared to the Big Sur video. In terms of setting up a bridged network connection, we may not have an answer here as you’ve seen our Big Sur video. Provided you’ve followed the steps shown at ruclips.net/video/sV42TRZNmDc/видео.html and ruclips.net/video/sV42TRZNmDc/видео.html your virtual Mac should hopefully be able to connect both to its host and any devices on your wider network. So we may have more work to do in order to understand why your VM isn’t connecting. We’re pleased to see from your follow-up message that you’ve implemented some stability improvements. We’re fascinated that you’ve been able to run this on a single core, as we’ve repeatedly mentioned that we were entirely unable to do this, and attributed this to the fact that most modern incarnations of macOS require a dual core processor in order to boot. Disabling audio is a sensible position, as, even with it enabled, we haven’t been able to achieve audio input or output on any of the virtual Macs we have created. We believe this to be a VirtualBox issue, as we’ve received feedback from VMWare users who have used our install media yet report full audio functionality in their projects. Using additional R.A.M. will always be helpful. As you’re allocating 16 G.B., we’re assuming that your machine has 32 G.B. or more in order for the remainder of the system to function. Our main machine has 64 G.B., although we appreciate that not everyone will have this much R.A.M. to allocate at the time of this reply. Glad to hear that you’re making progress and experimenting with this. Keep up the good work.
@@TechFixFlix I did double-check today and the connection is bridged and is talking to other devices. I was mistaken in my previous post. Thank you for the helpful walkthroughs and videos. I couldn’t have gotten it up and running without the videos, and this has been a very fun and enlightening experience.
Glad you managed to get networking operational, which certainly makes things easier. This project is definitely more about the journey than the destination, and there’s valuable experience to be gained in experimentation and failure, as well as success. We’re pleased to have offered some help along the way.
We cover this at 02:42 in the video. We do not supply copies of the .iso file which this tutorial creates, as it represents a breach of copyright in respect of intellectual property belonging to Apple. If all you’re looking for is a quick-fix solution to obtain installation media, all you need to do is search for it in Google. There are plenty of options out there. Whether they work and whether they are safe is an entirely different matter, which is why we neither use nor recommend them. The entire concept around which this tutorial series is based is that we create our own installation media, precisely in order to avoid potentially compromising our device integrity and data security through reliance upon the work of a third party. Obtaining an .iso from elsewhere entirely misses the central point of this tutorial.
I try to enter command number 5, hdiutil convert /tmp/Monterey.dmg -format UDTO -o ~/Desktop/Monterey, however it says convert failed - No space left on device, why could this be? I have 120gb left on my Mac
With 120GB free on your Mac, we agree that this is an unexpected error. If you’d have been down to your last 30GB or thereabouts, this could have been understandable, but with over 100GB to play with, you really shouldn’t encounter this error. There’s clearly a precedent for this, and this link details a scenario very similar to yours: superuser.com/questions/1552297/macos-no-space-left-on-device-with-250gb-available-after-catalina-upgrade As reported at discussions.apple.com/thread/253391452 it seems that Safari has generated errors of this type, with a very simple solution also referenced in the same discussion. Even if your error didn’t originate with Safari, it might be worth exploring that solution, as well as those detailed here: macreports.com/safari-says-no-space-left-on-device-how-to-fix This appears to be a bug in macOS which can surface at any time, rather than being an unwanted result of the .iso creation process.
Have the same thing with the same result. So close yet so far! Could this be something to do with being on 12.4 Monterey and trying to use 12.5 version install dmg.?
Hi @Sam Clarke. We haven’t personally experienced this issue, so can’t speak with absolutely certainty, but we wouldn’t rule anything out as these projects are sensitive to many factors, and historically these have included the host system and the installer version. We tend to work out what’s happening when we receive multiple instances of the same feedback from different users. At present, your error remains a mystery, but there’s clearly something to it as you’re the second person reporting it in recent times.
Thank you so much for the easy tutorial, and thank you crazy much for the copy and paste commands 🥳
You are very welcome. Glad you found the video and supporting commands useful.
Thanks for the video, when is part 2 coming out?
@Fares Bou Najm. We really should have released Part II by now. The audio was recorded back in November 2021, but we felt there was considerable similarity to our Big Sur video (see ruclips.net/video/sV42TRZNmDc/видео.html for details), and the steps which form Parts II and III are essentially identical for both projects. Once you’ve created your ISO, you can drop into that video just before the eighth minute, and follow from there.
Thanks for that usefull tutorial. Just needed to remove --nointeraction on the 3rd command to make it work under Mojave.
That’s great. Glad you got this working.
Thank you for this very detailed explanation. Quick question, is the downloaded version registered or linked in any way to the Apple account that downloaded it? I don't have a Mac, so I'd have to try to bum around for someone with a Mac, but I don't want it to link back to them if they help me with this.
Great question. What is the role of the host machine, and how can we be certain that its fingerprints don’t transfer to the virtual machine? There is a logical answer to this, and it comes down to checksums. If you’re unfamiliar with checksums, take a look at www.imore.com/checksums-101-how-make-sure-your-downloads-are-real-deal. In short, we’re using the host Mac purely to download a piece of software, and that piece of software is the macOS installer app. That app will have a checksum. If the checksum is the same no matter what host you use to download it, it will be apparent that the software has not been modified as a consequence of contact with the host. If the.checksum varies with each machine, this would be indicative of some form of customisation to match the host. It might take a spot of online research to find the correct checksum for the specific installer version you’re downloading, or, if you’re incredibly fortunate and have access to two Macs you could confirm via experimentation. We strongly suspect that the installer app is not customised to reflect its origins.
@@TechFixFlix Thanks for the reply. Yes, I am familiar with checksums, however I do not know where to find checksums for MacOS and googling it didn't turn up any results. The checksum would also depend on the specific update I'm downloading, not just the primary version so that would make it even harder to find a checksum for the specific version of their MacOS. I'm unlikely to get access to multiple Mac's to compare checksums, I can only think of one person I know that owns a Mac and I wanted to make sure the OS wouldn't be automatically registered to them before I asked. Thanks again.
You are a very responsible friend @Tekkerue, and we admire you for taking sensible precautions where others would potentially dive directly in. We hope you find a solution to this.
My problem is I want the original iso file and I do not have a mac and I want the mac only in vmware because im using windows 10 please help me...
Hi there. We suspect that there are very many people in exactly this position. Apple doesn’t make bootable .iso files available for download, and this makes perfect sense from the perspective of their business model, in that every device they sell comes with macOS preinstalled. Therefore, the only reason to obtain an .iso is to run it on non-Apple hardware, which, of course, doesn’t generate revenue for Apple.
Whilst this protects Apple’s revenue, it’s harsh for hobbyists like us who simply want to experience macOS on Windows, leaving us without a safe and official path to accessing .iso files. For this reason, we undertook this project to create our own .iso. Of course, we were in the fortunate position to have access to our own Mac, and we fully appreciate that not everyone will have a device as a starting point for this project.
As we mention in the video, there are third-party images files available online. We’ve never used them, don’t trust them and wouldn't recommend any of them. We do realise, however, that some people may have no other option and may opt to follow this route at their own risk.
Sorry the news isn’t better here.
What if we don't have a device ( = Apple computer) already running MacOS? Is it possible to download somewhere an already created *.ISO image of MacOS? It does not have to be Monterery, but the more recent the better. Thanks.
Hi @ Jerry Suppan. You can essentially take one of two paths with this project, although the first is only open to those people who can access a physical Mac. If you are fortunate enough to be in this position, you can create your own ISO as shown in our tutorial. This method allows us a great deal of control over the creation of the installation media, and reduces the risk of unwanted extras which could theoretically be hidden with ISOs originating from unknown sources.
In many respects, there’s an easier path for those who don’t have access to a Mac, and that is simply to Google “macOS installer ISO” or “Monterey ISO” etc. Taking this path, you will be relying upon pot luck, and you simply won’t know how the ISO was created, whether it will work, whether it will be compatible with your virtualisation software or whether it will come with any unexpected surprises. It’s for these reasons that we do not advocate following this route, and that we cannot offer support to people who are not following our method directly. We appreciate that many will follow this route anyway, given that access to a physical Mac presents a high bar to entry for most.
Whichever way you go with this, we wish you luck.
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.
Hi, i've created correctly the Mpnterrey.iso file but during the booting of virtual machina on virtualbox it continues to crash. I've followed the video about BigSur virtual machine with .iso file but it' doesn't work, can you help me please?
Hi @Leonardo Persici. You’re absolutely correct to refer to the Big Sur tutorial, as the steps to follow are identical once you’ve created the installation media. Although there are many reasons why this project might crash, the first thing we’d check is the integrity of the installation media. We’re aware from personal experience that, no matter how diligently you create the installation .iso, it can still become corrupted, purely as a consequence of the number of file handling / conversion operations performed upon it. Often the simplest solution is to repeat the opening phase of the video and create a new version of the installation media. Although you might expect the same outcome, experience suggests that creating a fresh .iso can result in a successful outcome.
If, having created a second .iso, the project still crashes for you, get back in touch and we’ll explore some other options. These projects are far from straightforward, and require many interdependent variables to successfully align.
On step command two i get - No mountable file systems. when retuning the first command it says file exists?
Would i need to start over and how do i purge that file?
Hi @Chirag Gandhi. This happened to us once in testing, and it was a bit of a nightmare. You're right that you need to start over, but purging that file is the difficult part.
Given that the temporary file hasn't mounted, you'll either need to delete the temporary file or alternatively, you could leave the temporary file alone, and restart the project using an entirely different name for the temporary file in the first command and any subsequent references.
If you do decidec to delete the file, you'll find this summary of hdiutil commands helpful: ss64.com/osx/hdiutil.html
Thanks for the tutorial. I was able to use your Big Sur video to set up the VM part. However, I'm not able to boot into RecoveryOS of the guest machine using cmd-r or even from the terminal command: nvram -d recovery-boot-mode. I get an error: Error setting variable - 'recovery-boot-mode': (iokit/common) not permitted. Do you know anyway to get around this and get into the RecoveryOS?
That’s an interesting question @bob bob, and not one we’ve addressed before. Two options come to mind, although we haven’t tested either. The first would be to attach a recovery boot image as a separate virtual disk, as outlined in this article: www.geekrar.com/get-into-recovery-mode-macos-virtual-machine (scroll down for instructions specific to VirtualBox). The second would be to navigate the EFI shell and access recovery boot by entering commands at the prompt. You’ll find a summary of that process here: github.com/geerlingguy/macos-virtualbox-vm/issues/46 As we haven’t tested these options, we’d welcome any feedback you can offer in respect of their suitability for use with Monterey.
@TechFixFlix Thank you for the links. I have tryed the second method and it doesn't appear to work. For the first one though, they only provide a macOS Recovery Boot Image for macOS Mojave. Is there a way I could possibly create my own boot image, like you did in your video with the .iso
We did have another thought on this topic, which may or may not be useful to you, depending on your specific needs. If you reattach the installation .iso to the virtual optical drive of your virtual Mac and boot from it, you should eventually be taken to macOS Utilities, with options including Restore From Time Machine, Reinstall macOS Monterey, Safari and Disk Utility. If this isn’t what you need, please accept our apologies and get back in touch.
Thank you for the reply. I don't know if this helps, but the reason I'm trying to get into recovery mode in the first place is to download VBoxDarwinAdditions.pkg, the guest additions for MacOS. This I believe improves the performace a bit and provides shared folders between the host and virtual machine. However, once I try to download them, they fail. So I searched online for a solution. I came accross this: github.com/geerlingguy/macos-virtualbox-vm/issues/79 . The solution they provided requires recovery mode. I'm going to see if the new method you provided works over the weekend.
That makes perfect sense, and we can see now why you need to access the recovery environment. The method set out in the linked article has quite a few steps, so we hope you make progress with it. As one of your key objectives was to set up shared folders between the host and the virtual machine, may we suggest taking a look at another of our videos, namely “Networking In VirtualBox - Access Network Devices And Folders From Your Virtual Machine,” which you’ll find at: ruclips.net/video/7CSFbsE-E98/видео.html In this instance, our definition of “Networking” very much includes bi-directional communication between the guest and host, as well as between the guest and the wider network. In the video, we use a Windows guest, but the fundamentals apply equally to a macOS guest, although we’d also point you in the direction of a later video “File Sharing - macOS To Windows” (see ruclips.net/video/xqf9vm07uCQ/видео.html ) in which we specifically address file sharing between the two platforms. Hopefully some of that will help if your Guest Additions project runs into difficulties.
now i need help to install it on virtualbox, it just crashes when im trying to boot it. I try with some commands in the cmd but nothing... i hope yo would continue this serie. Thanks
Hi @Alejandro Vázquez Pan. Rest assured that this series is still very much in production, and we have already recorded vocals and preliminary graphics for Part II. Whilst it’s still in development, you might find its predecessor useful. You’ll find that video (which installs Big Sur) at ruclips.net/video/sV42TRZNmDc/видео.html The commands used at the Windows Command Prompt are essentially identical to those used for Monterey, so you may find the section at ruclips.net/video/sV42TRZNmDc/видео.html useful.
do you have a link to the other steps you reference in other videos in this guide?
Hi @Will Sells. Our original plan was to publish two further videos, the first detailing the configuration of the virtual machine on Windows, and the other outlining the macOS out-of-box experience. In practice, however, these steps are identical to those we've previously covered in our Big Sur video, which we think you'll find useful. The link to that video is ruclips.net/video/sV42TRZNmDc/видео.html and, if you've already created your .iso file in macOS, you can jump to 7:52 in that video. Also, you can find some of our earlier macOS-on-Windows projects at www.techfixflix.com/p/tutorials-for-macos.html
@@TechFixFlix can I recommend a video for running a different Osx on a virtual box from Osx?
Its what I was trying to to to test Monterey compatibility without upgrading.
I struggled but got there this morning.
Glad you’ve made progress with this. We haven’t published a video of our own running macOS within macOS, although we did something similar with Windows (see ruclips.net/video/zqbMXXDJEyI/видео.html for info).
I have it running on VirtualBox using the method described in the Big Sur video, but I've had it crash on me twice now. Hoping when you have the install video out that it addresses any minor differences in the process.
Also in the Big Sur video, you mentioned that it could find other network devices by bridging the connection, but I haven't been able to do that. Would it be possible to show in the Monterey video how that works?
I want to report that I moved the COREs to 1, disabled audio, and moved RAM to 16GB. This seems to have made the build significantly more stable.
Hi @Neil, and thanks for all of your feedback on your project, which is very much appreciated. Please be assured that the install video is in the pipeline, and will be appearing in the next few weeks, although we’d confess immediately that there are no significant differences in the installation phase when compared to the Big Sur video.
In terms of setting up a bridged network connection, we may not have an answer here as you’ve seen our Big Sur video. Provided you’ve followed the steps shown at ruclips.net/video/sV42TRZNmDc/видео.html and ruclips.net/video/sV42TRZNmDc/видео.html your virtual Mac should hopefully be able to connect both to its host and any devices on your wider network. So we may have more work to do in order to understand why your VM isn’t connecting.
We’re pleased to see from your follow-up message that you’ve implemented some stability improvements. We’re fascinated that you’ve been able to run this on a single core, as we’ve repeatedly mentioned that we were entirely unable to do this, and attributed this to the fact that most modern incarnations of macOS require a dual core processor in order to boot.
Disabling audio is a sensible position, as, even with it enabled, we haven’t been able to achieve audio input or output on any of the virtual Macs we have created. We believe this to be a VirtualBox issue, as we’ve received feedback from VMWare users who have used our install media yet report full audio functionality in their projects. Using additional R.A.M. will always be helpful. As you’re allocating 16 G.B., we’re assuming that your machine has 32 G.B. or more in order for the remainder of the system to function. Our main machine has 64 G.B., although we appreciate that not everyone will have this much R.A.M. to allocate at the time of this reply.
Glad to hear that you’re making progress and experimenting with this. Keep up the good work.
@@TechFixFlix I did double-check today and the connection is bridged and is talking to other devices. I was mistaken in my previous post.
Thank you for the helpful walkthroughs and videos. I couldn’t have gotten it up and running without the videos, and this has been a very fun and enlightening experience.
Glad you managed to get networking operational, which certainly makes things easier. This project is definitely more about the journey than the destination, and there’s valuable experience to be gained in experimentation and failure, as well as success. We’re pleased to have offered some help along the way.
Can you please add a link to the ISO file
We cover this at 02:42 in the video. We do not supply copies of the .iso file which this tutorial creates, as it represents a breach of copyright in respect of intellectual property belonging to Apple.
If all you’re looking for is a quick-fix solution to obtain installation media, all you need to do is search for it in Google. There are plenty of options out there. Whether they work and whether they are safe is an entirely different matter, which is why we neither use nor recommend them. The entire concept around which this tutorial series is based is that we create our own installation media, precisely in order to avoid potentially compromising our device integrity and data security through reliance upon the work of a third party. Obtaining an .iso from elsewhere entirely misses the central point of this tutorial.
Yo!
Yo! Right back to you.
I try to enter command number 5, hdiutil convert /tmp/Monterey.dmg -format UDTO -o ~/Desktop/Monterey, however it says convert failed - No space left on device, why could this be? I have 120gb left on my Mac
With 120GB free on your Mac, we agree that this is an unexpected error. If you’d have been down to your last 30GB or thereabouts, this could have been understandable, but with over 100GB to play with, you really shouldn’t encounter this error. There’s clearly a precedent for this, and this link details a scenario very similar to yours: superuser.com/questions/1552297/macos-no-space-left-on-device-with-250gb-available-after-catalina-upgrade
As reported at discussions.apple.com/thread/253391452 it seems that Safari has generated errors of this type, with a very simple solution also referenced in the same discussion. Even if your error didn’t originate with Safari, it might be worth exploring that solution, as well as those detailed here: macreports.com/safari-says-no-space-left-on-device-how-to-fix
This appears to be a bug in macOS which can surface at any time, rather than being an unwanted result of the .iso creation process.
Have the same thing with the same result. So close yet so far! Could this be something to do with being on 12.4 Monterey and trying to use 12.5 version install dmg.?
Hi @Sam Clarke. We haven’t personally experienced this issue, so can’t speak with absolutely certainty, but we wouldn’t rule anything out as these projects are sensitive to many factors, and historically these have included the host system and the installer version. We tend to work out what’s happening when we receive multiple instances of the same feedback from different users. At present, your error remains a mystery, but there’s clearly something to it as you’re the second person reporting it in recent times.
same thing is happening to me
i found the solution. Quit safari and run the command again, it worked for me.