Kann .VDI unter VB 6.1. auf Mac Mini 11.5.2 (Big Sur) nicht starten

[Gaston2014]

Hallo zusammen,

ich nutze einen MAC Mini (Late 2014) unter OS X 11.5.2. Ich habe ein Update auf VB 6.1.26 getätigt. Seitdem kann ich mein Windows10.vdi nicht mehr starten. Im Manager kann ich die VDI zuordnen, aber auf dem Startbildschirm sehe ich nichts. Habe die VB 6.1.26 gelöscht und bei installiert, hat aber nichts genützt.Bin komplett ratlos. Ich würde gerne ein LOG-File mitsenden, aber in dem Verzeichnis befinden sich nur alte LOG-Files und kein aktuelles.

Vielleicht hat jemand von euch eine Idee? Auf jeden Fall schon mal vielen Dank- VG Gaston

Zuordnung der VDI im Manager

Bildschirmfoto 2021-09-13 um 17.01.37.png (50.17 KiB) Viewed 18992 times

Danach keine Startmöglichkeit des Guestsystems

Bildschirmfoto 2021-09-13 um 17.02.00.png (121.6 KiB) Viewed 18992 times

[scottgus1]

The .vdi is only the VM's 'hard disk'. There is a whole VM folder with a .vbox file that is the rest of the VM.

I have made an update to VB 6.1.26.

An update of Virtualbox will not erase existing VMs or clear the VM list. We need to know exactly how you updated in such a way to clear your VM off the list.

[Gaston2014]

At first, i make the standard Updateprocess over the VB App and then i start the installation process from my Download folder (.dmg). Then the error occurs.
At last, i delete the VB App with the MAC AppCleaner (see Screenshoot) and then i download and install the actual Version from the VB Website.

Bildschirmfoto 2021-09-13 um 17.33.42.png (91.71 KiB) Viewed 18985 times

[scottgus1]

Interesting, thanks. Something weird definitely happened then.

What are the contents of the folder containing the .vdi file?

[Gaston2014]

Nothing special

This is an extra folder under my User VirtualBox VMs/

Bildschirmfoto 2021-09-13 um 17.43.28.png (18.95 KiB) Viewed 18982 times

[scottgus1]

OK, good. Please zip "Windows...Kopie.vbox" and "Windows...-prev Kopie", and post the zip file, using the forum's Upload Attachment tab.

[Gaston2014]

Here they are... but they are from June

[Gaston2014]

My old log-files

[scottgus1]

Thanks.

Windows 10 Kopie.vbox uses the Windows 10.vdi in the same folder.

Let's reset the Virtualbox environment:
Reboot the Mac so Virtualbox is not running.
Go to "$HOME/Library/VirtualBox" and delete the "Virtualbox.xml" file.
Open Virtualbox. The VM list will be empty.
Click "hinzufügen" (Add) and browse to "Windows 10" folder, and select "Windows 10 Kopie.vbox"
The VM should appear in the VM list and be ready to run.

[Gaston2014]

Sorry, but there is no file "VirtualBox.xml" on my Mac.
There is no folder VirtualBox in the Library directory.

[scottgus1]

Strange. With the Virtualbox Manager open there should have been a Virtualbox.xml made.

Let's proceed with Adding the Windows 10 Kopie.vbox. What happens?

[Gaston2014]

Bildschirmfoto 2021-09-14 um 18.54.56.png (12.3 KiB) Viewed 18914 times

not possible

[mpack]

That shows some VM folder, which is not where the manager's VirtualBox.xml file is stored.

According to the user manual (section 10.1.2), on MacOS the VirtualBox.xml file will typically be located in $HOME/Library/VirtualBox. VirtualBox can't be running if it can't create this file.

Assuming that you know what your $HOME folder is (check it in terminal), the only way the VirtualBox.xml file could be somewhere else would be if you overrode the default using a $VBOX_USER_HOME environment variable (check that in terminal too).

[scottgus1]

Let's proceed with Adding the Windows 10 Kopie.vbox. What happens?

not possible

What's not possible? We need a lot more description, this is not Twitter

By "Adding the Windows 10 Kopie.vbox" I mean this:

Open Virtualbox. The VM list will be empty.
Click "hinzufügen" (Add) and browse to "Windows 10" folder, and select "Windows 10 Kopie.vbox"
The VM should appear in the VM list and be ready to run.

If any errors appear, we ned to see them. "Not possible" is nowhere near enough to help.

[Gaston2014]

I don' know why, but there are the VirtualBox Folder under /User/Library

I Restart the Mac and delete the xml File and start VB and it's only possible to add the Windows10.vdi.
Nothing else happened.

Bildschirmfoto 2021-09-14 um 19.25.16.png (98.72 KiB) Viewed 18910 times

And here is the Logfile VBoxSVC.log:

00:00:00.002045 main VirtualBox XPCOM Server 6.1.26 r145957 darwin.amd64 (Jul 28 2021 18:24:31) release log
00:00:00.002048 main Log opened 2021-09-14T17:23:49.937595000Z
00:00:00.002049 main Build Type: release
00:00:00.002081 main OS Product: Darwin
00:00:00.002087 main OS Release: 20.6.0
00:00:00.002092 main OS Version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64
00:00:00.002225 main DMI Product Name: Macmini7,1
00:00:00.002287 main DMI Product Version: 1.0
00:00:00.002305 main Firmware type: failed - VERR_NOT_SUPPORTED
00:00:00.002337 main Host RAM: 8192MB (8.0GB) total, 4685MB (4.5GB) available
00:00:00.002355 main Executable: /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC
00:00:00.002356 main Process ID: 721
00:00:00.002356 main Package type: DARWIN_64BITS_GENERIC
00:00:00.006282 main IPC socket path: /tmp/.vbox-<#USER#>-ipc/ipcd
00:00:00.109982 nspr-2 VirtualBox: object creation starts
00:00:00.110230 nspr-2 Home directory: '/Users/<#USER#>/Library/VirtualBox'
00:00:00.146301 nspr-2 HostDnsMonitor: initializing
00:00:00.146887 dns-monitor HostDnsMonitor: updating information
00:00:00.148252 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.149799 nspr-2 VirtualBox: object created
00:00:00.149834 dns-monitor HostDnsMonitor: old information
00:00:00.149855 dns-monitor no server entries
00:00:00.149868 dns-monitor no domain set
00:00:00.149895 dns-monitor no search string entries
00:00:00.149917 dns-monitor HostDnsMonitor: new information
00:00:00.149925 dns-monitor server 1: 192.168.178.1
00:00:00.149937 dns-monitor server 2: fd00::eadf:70ff:fe82:331
00:00:00.149945 dns-monitor no domain set
00:00:00.149956 dns-monitor search string 1: <#myRouter#>
00:00:02.497921 nspr-2 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:02.503648 nspr-2 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.799722 nspr-2 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.807538 nspr-2 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.821146 nspr-3 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.827030 nspr-3 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.832024 nspr-2 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:34.837365 nspr-3 Saving settings file "/Users/<#USER#>/Library/VirtualBox/VirtualBox.xml" with version "1.12-macosx"
00:00:40.350041 main VirtualBox: object deletion starts
00:00:40.350655 main HostDnsMonitor: shutting down ...
00:00:40.350739 main HostDnsMonitor: shut down
00:00:40.351549 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:40.351674 main VirtualBox: object deleted