-
|
With the current Version 1.2.2 (10) I can create VM's fine, just installed DP 8 from the menu and completed without errors. Changing the VM settings did not help. How can I launch a VM on 13.0 Beta (22A5321d), XCode Beta 14.0 installed on 6.8.2022, XCode and VirtualBuddy run on external SSD? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 14 replies
-
|
No suggestions? I have this same problem. Potential reason is that I'm also trying to run the VM on an external HDD. I'm running VB 1.2.2 on host running MacOS 13.2.1 with Xcode 14.2. I've setup three different VMs using both local IPSW downloaded via script that grabs latest compatible version and also using VB's OS selection menu and choosing 13.2. All fail with this same error message when booted regularly or in safe mode.
|
Beta Was this translation helpful? Give feedback.
-
|
I'm stuck on this issue as well - parallels runs fine for me but I can't get a single vb vm to run regardless of host OS, vb version, guest OS version, or vm settings. |
Beta Was this translation helpful? Give feedback.
-
|
@brokosz did your VMs happen to be saved to an external drive? That appears to have been the problem for @cerkut and me and the problem when away when I moved them to the internal drive ... although that's not a long-term fix because I can't fit the VMs I need on the baked-in SSD. |
Beta Was this translation helpful? Give feedback.
-
|
Ahhh - yes! They are on an external, but so are my parallels vms that do work |
Beta Was this translation helpful? Give feedback.
-
|
My VMs are also on an external SSD ... all of them and it's only the first start who is causing an issue. |
Beta Was this translation helpful? Give feedback.
-
|
This sounds like something internal to Virtualization is failing and not giving us a good error message. For anyone who's running into this, it would be very helpful if you could send console logs captured while reproducing the issue. It's unlikely to be something we can fix, but at least this would help us understand what's going on and report it as a bug to Apple with more information. |
Beta Was this translation helpful? Give feedback.
-
|
I got console logs and will send you by email @insidegui Usually if you retry it's working at the end ... can be up to 5 times... |
Beta Was this translation helpful? Give feedback.
-
|
Thanks to logs sent by @mcnahum, we were able to determine that this issue is caused by a crash in the As you might imagine, given this is a crash in a macOS system component, it's not something we can address directly. The best thing anyone who's able to reproduce this issue can do is to file feedback to Apple including a full sysdiagnose, right after reproducing the issue. You may include links to VirtualBuddy and this thread in your feedback reports. Anyone who files such a feedback report may also file a public version here so that others can duplicate. If I manage to reproduce this issue, I'll file it myself and get a DTS incident to try to expedite a fix or get a workaround. However, I've run thousands of VMs on my Macs and never encountered this crash, and it wouldn't be productive to try to get DTS to help on an issue I can't reproduce. Anyone who's willing to send me details about their hardware configuration, as well as the virtual machine that's reproducing this issue, feel free to send that information to me privately on The current workaround that works for most people is to keep retrying to start the VM until it works. We may consider retrying automatically in the app as a workaround. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @insidegui! I've reported feedback to Apple and also submitted a public report as suggested. I just did some more testing on my system (Macbook Air M2 2022, MacOS 13.3.1) and I'm always able to launch VMs normally when they're saved on internal SSD and they crash on startup 100% of the time when they're saved on my external HDD (LaCie 2Big Thunderbolt3). @cerkut mentioned using an external SDD as well so this looks like an incompatibility between com.apple.Virtualization.VirtualMachine and external drives from my limited perspective. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for taking the time to report it to Apple and file the public report. That's an interesting observation about the external SSD. I used to store my VirtualBuddy library in an external SSD as well until recently when I got a new Mac with a larger internal SSD. However, I often run my Mac with SIP disabled, so I wonder if that could be a factor in not having the problem (not recommending anyone disable SIP, please don't). Looking into how the VirtualMachine process works, it looks like the host app sends it a scoped URL bookmark for the VM files so that it can access them on behalf of the app. I wonder if there's a bug in that mechanism that only manifests itself when working with files on external storage, perhaps a race condition 🤔 For others who are experiencing this issue, if you're running from external storage, try running a VM from internal storage and see if that makes a difference in how often it occurs (if at all). |
Beta Was this translation helpful? Give feedback.
-
|
Just as a data point, I've noticed that the two most recent VMs I have tried to build have encountered this same problem. They are both on the internal SSD storage. However, after I manually gave VirtualBuddy Full Disk Access, the most recent VM has been able to boot. I don't know if that's coincidence, but perhaps worth trying for those having the problem. |
Beta Was this translation helpful? Give feedback.
-
|
All my VMs are on an SSD too ... a fast Thunderbolt case with a fast M2 inside and it's 95% dedicated for VMS... 1-I tried to set "full disk access" --> New VMs on SSD are not booting |
Beta Was this translation helpful? Give feedback.
-
|
This workaround works, but the sparse disk balloons to its full size when moving it between the internal and external disk. I tried |
Beta Was this translation helpful? Give feedback.
-
|
@insidegui could you consider to have 2 Libraries Path? that will allow an easy move to fix that issue? |
Beta Was this translation helpful? Give feedback.
-
|
I finally received a reply from Apple on this Feedback Assistant report. It said they're unable to reproduce this error using external drive and latest MacOS 14 Beta. Their response was silent about whether they reproduced on MacOS 13 but guessing they did since they followed-up. I've updated and it works. I'm now able to launch VMs from my external drive for the first time! Details: I updated Virtual Buddy to latest package release that resolves the Sonoma launch bug and upgraded host to Sonoma Beta 14.0 (23A5286i). Launching my pre-existing VMs (13.2 & 13.3) from external drive still didn't work but the problem changed from original framework error message to a silent black screen. Retrying a few times and booting in recovery mode didn't help. Maybe more patience would have. Then I installed a fresh 13.4 VM from official image and that failed with a hardware recognition error. Chalking this up to bad luck. Then I installed a fresh Sonoma Beta 14.0 (23A5286i) VM on my host running the same and it finally launched successfully from the external HDD. I lunched in recovery mode and after selecting "Macintosh HD" waited through more than 10 minutes of unresponsive black screen (host is Macbook Air M2 2022), then eventually pointer and pinwheel, then normal VM responsiveness. @insidegui I noticed a new boot option during final successful boot that read "boot on install drive" above the "boot in recovery mode" option. I didn't use it. I can't find documentation about this new feature. Was this something you added? From title, I'm wondering if it was part of a test to address external drive problems? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting.
No, that's something unrelated, it's for Linux VMs, but it's incorrectly showing up for macOS VMs as well for now, that will be addressed before this new version gets out of beta. |
Beta Was this translation helpful? Give feedback.
-
|
I think I have new information on when this happens and when it doesn't. To cut to the chase, it's probably an issue with APFS formatted drives. APFS has been giving me all kinds of problems, so this is no surprise. First, my 6 external HDD's, and 1 external SSD were taking longer and longer to mount at startup. As APFS external drives fill up, this issue gets worse. It eventually hit the 10 minute mark before they would all mount, and then eventually not mounting at all. Did the Google thing, formatted the HDD's to HFS+, and mount time dropped to 17 seconds! So I still had the SSD as APFS, where VB runs, among other things. Decided to take advantage of VM Duplicate feature of APFS. Had 24 backups, 1 every hr, rotating backup going. That's fine until they actually start to use actual space and fill up your SSD. And what happens when an APFS drive runs out of space? It stops working. I had 82K free space. You cannot delete files to free up space. You will only get "No space left on device" or "the operation can't be completed because the disk is full". When this happens on your INTERNAL drive, you can reboot, or use SafeMode, and recover space. Not so if the drive is external. sudo rm -rf will not work, DiskUtility will not help, and cannot delete Snapshots to make space. The only option is to Erase the drive and start over. I have yet to try that, so even that could give me issues. We shall see. DU could NOT remove a snapshot on this drive, so who knows if it will even Erase it. Probably will, but .... yeah. Connecting it to a different Mac, a Mac with Windows VM, a PC, a PC with Paragon APFS program, will not help, although in some cases that might still work for some, maybe... None of those allowed me to delete files. I ordered another external SSD and rsync'd from the bad one to the new one. Reading files is the only thing that works. You can't even delete 0 bytes files, or empty directories. By mistake, I formatted the new SSD as HFS+. Again, this is where VirtualBuddy VM's live. I've only started the VM maybe 10 times, but it has started up every time with no issue. With my old APFS SSD, it would always take 10 or so tries to launch a VM. Now, the old drive was a 1 TB Samsung 970 EVO NVME.2 in a Thunderbolt enclosure, and the new drive is a 2 TB SAMSUNG T7 external drive. But, I doubt that's the difference here, and the issue is most likely APFS. I hate to lose the Duplicate feature, but my automated system really likes it when stuff just works, and it doesn't have to keep looking and checking if things are running or not. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if you already tried with Sonoma and the Sonoma version of VirtualBuddy ... but I switched since beta 1 and never had any issues since. |
Beta Was this translation helpful? Give feedback.
-
|
That's good news. I've only used Ventura so far. Let me know what happens when you fill up your SDD, the real/host SSD, not the Virtual one used by the VM. To the point of not even being able to 'touch' a new empty file. See if you can delete anything and recover. |
Beta Was this translation helpful? Give feedback.
-
|
I Will probably not fill the disk soon .. it is a 2TB and as create and delete the VMs often the usage is quite stable ... even if I also store the Ipsw files on it |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure it's directly related to APFS, since I've been using an external SSD formatted with APFS which is always close to being full, but never had any problems. It may have something to do with the specific hardware. It's definitely worth filing this as feedback to Apple, including a sysdiagnose taken right after the issue occurred and your detailed description. Thanks for sharing your experience. |
Beta Was this translation helpful? Give feedback.
-
|
This message from our friend here also suggests some issue with APFS (maybe also on Ventura) , and the way it's handling these files that do not take up their full size. Once expanded, and then back to the APFS SSD, they seem fine. Unless I am not interpreting this correctly. mcnahum 1-I tried to set "full disk access" --> New VMs on SSD are not booting |
Beta Was this translation helpful? Give feedback.
Thanks to logs sent by @mcnahum, we were able to determine that this issue is caused by a crash in the
com.apple.Virtualization.VirtualMachineprocess, which is the one that actually runs the virtual machines.As you might imagine, given this is a crash in a macOS system component, it's not something we can address directly.
The best thing anyone who's able to reproduce this issue can do is to file feedback to Apple including a full sysdiagnose, right after reproducing the issue. You may include links to VirtualBuddy and this thread in your feedback reports.
Anyone who files such a feedback report may also file a public version here so that others can duplicate.
If I manage to reproduce t…