“Hardware model data doesn’t exist but a restore image was not provided to create the initial image” #69
-
|
Wanting to run a Monterey VM. Having an issue… I can download/install a Monterey 12.5 VM from the VirtualBuddy “wizard”, but when I try to boot it I get the following error:
I see references to this error in the Swift code (when searching), but am not clear what is throwing this error. Is it possible that VirtualBuddy doesn't know what a "MacBook Pro (13-inch, M1, 2020)" (AKA "MacBookPro17,1") is? I have tested this on both VirtualBuddy 1.2-8 and VirtualBuddy 1.0.3-5 with same results. The host has the 14GB restore file (at ~/Library/Application Support/VirtualBuddy/_Downloads/UniversalMac_12.5_21G72_Restore.ipsw) The vbvm file appears (at ~/Library/Application Support/VirtualBuddy/macOS-Monterey-12.5.vbvm) But it is ess than 1MB in size...? Specs: |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 24 replies
-
|
I think you're facing the issue described in #68. You haven't actually finished the installation due to that UI bug. |
Beta Was this translation helpful? Give feedback.
-
|
Updated to 1.2.1-9 and that appears to have resolved the issue. I'm able to download/install/boot Monterey 12.5 VMs now. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I am still facing this issue on 1.2.1 (9). Any suggestion? |
Beta Was this translation helpful? Give feedback.
-
|
Your VM probably didn't finish its installation properly. Try creating a new one. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed . it worked.Why is the first try failed. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! This also happens when you mistakenly attempt to install a VM with macOS version newer than the one on your host Mac. This has happened to me yesterday, when creating a VM for the first time, then I tried to install one again, at which point others report success, so this message seems to have multiple root causes, but for me it failed telling me I needed to install a system component (something that hasn't happened the first time around) and that installation failed with some vague update service issue error message. That message was I think really about the macOS version of the host being older than the desired guest. |
Beta Was this translation helpful? Give feedback.
-
|
That is right, this error message can appear in multiple circumstances, but the root cause is always the same: that the app is trying to boot up a VM that hasn't been properly installed, either because the installation failed, or because it was interrupted. There are definitely improvements to be made in error reporting so that it's less confusing. The issue with newer OSes is a lack of the latest MobileDevice framework, which has to be installed with Xcode unfortunately. I have a feedback report opened about that ( |
Beta Was this translation helpful? Give feedback.
-
|
I updated my host Mac OS, then downloaded the IPSW and attempted a new install and failed again. |
Beta Was this translation helpful? Give feedback.
-
|
Hitting the same problem here as well. After the download, launching a VM isn't working, instead giving an error about "Hardware model". That's when trying to get macOS 13.x running under macOS 12.x, when using VirtuaBuddy 1.3 on an M1 Mac Mini. @insidegui With your mention of the "MobileDevice framework" being needed, are you able to clarify that a bit. XCode 14.1 is installed on this Mac Mini, though I don't use XCode so am unfamiliar with it. Not seeing anything obviously related to install "MobileDevice" of any form in it. Searching online mostly shows references to an Open Source "MobileDevice" project, but that's probably not what you're meaning? |
Beta Was this translation helpful? Give feedback.
-
|
MobileDevice is a framework that's used by macOS to communicate with iPhones, iPads, etc, and also Apple Silicon Macs under DFU mode. When a macOS VM starts up for the first time under Virtualization's engine, it starts up in DFU mode, and MobileDevice is used by Virtualization in order to perform a restore of the virtual machine, just as if you were restoring actual Mac hardware. MobileDevice.framework ships with macOS, but it can be updated independently of the operating system because new devices require updates to the framework. Xcode will install an updated version of MobileDevice when you install it on your Mac the first time you launch it (the "installing additional components" part that happens when you launch a new Xcode version). The bottomline with the issue described in this discussion is that VirtualBuddy is attempting to boot up a VM that hasn't been installed. It's ultimately a UX problem because the app doesn't handle that case well, it just tries to boot up the VM, but then fails with that error message because it can't find the hardware model file (which is created upon initial installation), and since the boot up is being attempted outside of the installation process, it can't find the corresponding restore image that's required in order to create the VM. The steps folks can try to fix it for now are:1 - Download the latest version of Xcode from the App Store* or Apple's Developer Portal (a paid developer account is no longer needed, just a free Apple ID will be enough) It looks like Apple will soon be offering a separate download of the MobileDevice framework outside of Xcode, which will be a lot better since it's a smaller download, but for now the only solution to run more recent versions of macOS in Virtualization is to download and install Xcode. Of course there's a lot in VirtualBuddy we can do to make this failure mode more clear and actionable, and that will be coming in future releases. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I tried those exact steps (co-incidentally) last night with no difference in result. eg fails in the same way. The only thing that eventually worked (using UTM though) was upgrading the host OS to Ventura first. Once I'd done that, then upgraded Xcode again (slightly newer Xcode is available for Ventura onwards), then installing Ventura as a guest OS worked. Note that I didn't try installing Ventura guest OS with using VirtualBuddy after upgrading the host OS, as by that stage I was very much over the whole thing and UTM got tried first and worked. Fairly sure VirtualBuddy wouldn't have have problems after the host OS upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately I cannot make this work with 13.3 or above. It finally succeeded with 13.0
|
Beta Was this translation helpful? Give feedback.
-
|
I had this error the first time I set up a VM. I did not encounter the button to install. When I deleted that first VM and created a second, the prompts were different because I had already downloaded the image. In that case, the button to install was there, and I could successfully get the VM running. |
Beta Was this translation helpful? Give feedback.
-
|
I had this exact same experience! Added it once, went through prompts, didn't work after installation. Deleted it, went to add it again, this time "Install" was an option, I selected this, and everything worked great. For additional context, I am on macOS Ventura 13.2.1 and was installing a VM for macOS Monterey 12.6.1. @insidegui just want you to be aware this issue is still occurring! Thanks for the amazing tool! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I am aware. This will be addressed in the next update, which will include several changes to the installation process. |
Beta Was this translation helpful? Give feedback.
-
I had the same issue with a similar case (virtualising 12.x on 13.x) and could not get anything to work due to this bug. But trying the 1.3 beta fixed the issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing this problem as well, on MacOS 12.6.6, trying to install a VM for Ventura 13.3.1 or 13.4 I have Xcode and the Developer Tools installed. I previously had no problems with multiple OS versions on this exact hardware and OS, but reset my machine and am setting everything back up again. Have tried the 1.3 beta as well as 1.2.2 |
Beta Was this translation helpful? Give feedback.
-
|
You probably need to re-create your VM: #69 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
So installing 12.6.1 did work for me, but anything higher than my host OS seems to fail - despite multiple re-creation attempts. I had this working before in this exact same configuration before :-( |
Beta Was this translation helpful? Give feedback.
-
|
So I was able to get 13.0 to install on my Monterey host - it looks like it is newer versions of Ventura that have the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have Xcode installed? Installing newer OS versions requires the device support package that's included in Xcode (with Xcode 15 and Sonoma, Apple made that a separate download, but I think for Monterey to run Ventura you'll still have to install Xcode itself unfortunately). |
Beta Was this translation helpful? Give feedback.
-
|
So I do have Xcode installed - Xcode 14.2, which is the highest version that will run on Monterey. I only have the macOS and iOS installations though, and no simulators - I wonder if I might be missing something. Having managed to finally get a macOS 13.0 VM up and running, I can't seem to upgrade it, either via Software Update to 13.4.1, or manually via Trying to see if I can create a 13.2.1 VM from scratch now. |
Beta Was this translation helpful? Give feedback.
-
|
I just updated my computer to Ventura 13.4.1 and when downloading the IPWS for 13.4.1 I get this error. |
Beta Was this translation helpful? Give feedback.
-
|
The error discussed in this thread doesn't happen during a download operation, but when starting a VM. If you're seeing an error when downloading, that could be something else. If you're seeing an error when attempting to run the VM, see: #69 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'm using Virtual Buddy 1.22 My host machine is running on macOS 13.4.1 (c) with Xcode 14.3.1 installed, and I'm trying to install a guest machine running macOS 13.4.1 When I installed the machine, VB tells me that installation failed. I also can't start the machine and gets the error: The machine has stopped due to an error: Failure (errorDescription: Optional("Hardware model data doesn't exist, but a restore image was not provided to create the initial data.")) I tried the proposed workarounds above like configuring a new one, but they're not working. 
|
Beta Was this translation helpful? Give feedback.
-
|
That fixed it for me and my M1, many thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, looks like we'll have to start offering different options depending on the host 😬 |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime, I've added both builds to the download options, noting that |
Beta Was this translation helpful? Give feedback.
-
|
I was overjoyed to hear we might have a fix for this, but |
Beta Was this translation helpful? Give feedback.
-
|
Thx @Jerry23011. |
Beta Was this translation helpful? Give feedback.
MobileDevice is a framework that's used by macOS to communicate with iPhones, iPads, etc, and also Apple Silicon Macs under DFU mode. When a macOS VM starts up for the first time under Virtualization's engine, it starts up in DFU mode, and MobileDevice is used by Virtualization in order to perform a restore of the virtual machine, just as if you were restoring actual Mac hardware.
MobileDevice.framework ships with macOS, but it can be updated independently of the operating system because new devices require updates to the framework. Xcode will install an updated version of MobileDevice when you install it on your Mac the first time you launch it (the "installing additional components" par…