VirtualBox problem

Danbor

Active Member
Joined
Aug 1, 2023
Messages
132
Reaction score
57
Credits
1,379
Hello all. I'm hoping to get some pointers on how fix a problem I apparently created when trying to create a virtual machine in VirtualBox.
The host system is Mint 22. I already have virtual machines of Mint 22, Mint 21.3, Mint 21.2, LMDE6, Ubuntu, Fedora and win10. All of these machines are still working fine.
Last week, I thought I'd create a Mac machine, just to check it out having never laid eyes on one. So I found an .iso through Github and started creating one. Ran into some issues and started looking for troubleshooting answers. During this, I learned that Apple doesn't permit this so I deleted the machine and forgot about it.
Two days ago, I tried to create a virtual machine running XFCE and learned that I must have hosed something. First I tried the unattended install, then attended. Both, several times, deleting the machines when it didn't work as it should. Then, thinking it might be a problem with the iso, I tried with a Mint 22 iso I knew was good.Same issues. And here are the issues.

1. When I start the install, it can't find the iso I listed at the start, a popup window pops up asking me to chose an iso and remount it. Once I mount it, installation proceeds as normal.

2. Once the install completes, and I restart the machine, I have to enter my password, even thought I specified otherwise. ( not a big issue, but odd ).

3. In the instances where I used unattended install, this error message pops up - Can't run guest install. Failed to run unattended guest installation. Callee RC: NS_ERROR_FAILURE (0X80004005). When I try an attended install, I get the same error minus the failed to run unattended guest install line.

4. When I open the file manager to the guest editions directory and right click on autorun.sh, there is no "run as program" option. I finally got it to run from terminal with the following command, "sudo /media/dan/VBOX_GAs_7.0.20/VBoxLinuxAdditions.run". After that, the shared folder works and the machine will run full screen. However, shared clipboard and drag and drop do not. And yes, the versions match and those functions are enabled.

5. When the virtual machine starts, I get the following notification message after entering the password, "VBox Client-Fatal Error. Unable to connect to Xserver-running in a terminal?"

6. When the machine starts and I enter the password, the desktop loads normally. However, when I try to open the file manager, the machine immediately closes the desktop and reverts back to the login screen. Afer entering the password again, the desktop loads and I can then open the file manager.

I also purged VirtualBox 7.0 and reinstalled it. Same problems. I can't be sure that my aborted attempt to create a Mac machine caused the problem, but when I search the 'net for that error message, I find a lot of hits from Apple sites.
Oh, in case it matters, in machine settings/system/Acceleration tab, I have tried all options for Paravirtualization Interface. No difference, so I set it back to default.
My next step, if I can't get this fixed, is to reformat / and reinstall Mint 22. I really hope to avoid that if possible.
Feeling a bit disgruntled at the moment. Any pointers would be appreciated!
 


Not sure why your virtualBox got hosed. You don't mention which version of MacOS you are trying to install.

Newer versions ONLY work on M1 or M2 cpus, there is no M1/M2 emulation for VirtualBox.
 
Not sure why your virtualBox got hosed. You don't mention which version of MacOS you are trying to install.

Newer versions ONLY work on M1 or M2 cpus, there is no M1/M2 emulation for VirtualBox.
The version was Sonoma. What's odd, though I'm happy with the oddity, is that the pre existing machines still work just fine. I just can't create any others until I figure this out.
I can move files back and forth, I just can't cut/copy and paste to or from the new machine. All of the answers on the apple sites seem to be talking about disabling or enabling Hyper V. I don't even know what that is. :).
Thought about a timeshift restore, but Timeshift doesn't recognize the snapshot I have stored on a usb thumbdrive. So that option is out. Or even if it would solve the problem.
 

Members online


Top