After upgrading to a new version I get an error

[Docfxit]

After upgrading to Ver. 7.0.14
This is the error I get:

VboxError.jpg (72.82 KiB) Viewed 1354 times

I did install:
Oracle_VM_VirtualBox_Extension_Pack-7.0.14.vbox-extpack
The host is Windows 10
The guest is Windows 10
This is the Log:

Win10_64bit-2024-02-14-22-00-13.zip

(31.24 KiB) Downloaded 30 times

Please let me know what I can do to fix this.

Thank you,

[granada29]

You have allocated more RAM to your VM than you actually have available.

Code: Select all

00:00:07.196594 Host RAM: 11983MB (11.7GB) total, 5973MB (5.8GB) available
00:00:07.808041   RamSize           <integer> = 0x0000000200000000 (8 589 934 592, 8.0 GiB)

Try reducing RAM to 4 GB and see if that helps. If it still fails please post the new log.

[scottgus1]

In addition to Granada29's diagnosis above:

What version of Virtualbox were you running before the upgrade? If you downgrade back, does the VM OS start running again?

Why did you post the VM's Display settings screenshot?

[Docfxit]

I have changed the memory to 4meg.

VboxMemory.jpg (67.3 KiB) Viewed 1282 times

When I start Vbox I get an error:

VboxMemoryError.jpg (45.81 KiB) Viewed 1282 times

I was running:
VirtualBox-7.0.10-158379-Win.exe
I just remember I got an error during the install so I tried to install VirtualBox-7.0.14-161095-Win.exe again.
It wouldn't let me so I removed it.
When I tried installing it again I got this error:

VboxPython (.jpg (52.25 KiB) Viewed 1282 times

I figured out how to get Python installed.
I have Python installed now.
I re-installed VirtualBox-7.0.14-161095-Win.exe
It installed clean this time.
When I start Vbox I get the same error

[Docfxit]

I added the VM's Display settings screenshot by mistake.
I do have a problem with the Display setting but I wanted to solve the Start problem first.
After it does start the Display needs the setting changed because the screen is too large.
Right now I can't Start, but when I can it looks like this:

VboxDisplay (.jpg (42.82 KiB) Viewed 1280 times

[scottgus1]

Try reducing RAM to 4 GB

I have changed the memory to 4meg.

That's gigabytes not megabytes. It's been a really long time since Windows could run in a few MB of RAM. Try 4 GB. That should clear up the text error.

************************

When I tried installing it again I got this error

The Python screenshot is not an error. It's a mild warning that Python isn't installed on the host, so you won't be able to control Virtualbox with Python scripts on this host. It's not a problem, just press OK and move on.

*************************

I was running:
VirtualBox-7.0.10-158379-Win.exe

Good, thanks. Now:

If you downgrade back, does the VM OS start running again?

*************************
The display problem should be fixable if Guest Additions are installed, and the VM window's View menu is set corectly. Let's get the VM booting first.

[Docfxit]

I installed VirtualBox-7.0.10-158379-Win.exe
as you suggested.
I get the same error.

VboxError.jpg (72.82 KiB) Viewed 1255 times

[scottgus1]

OK, thanks.

The log above did not show any VM "hardware" trouble for the time between boot and the VM being turned off. It could be a coincidence that this happened just when you updated Virtualbox.

Try troubleshooting this inside the VM as if it were a real PC. This means to figure out what the error code means on Windows websites and support channels, and find out what required device isn't connected or can't be accessed.

Alternative, restore the VM from the backups you took before you updated the host Virtualbox.

[Docfxit]

I ended up restoring a backup. It's working good now.
Except I still need to reduce the size of the display.

Any suggestions?

[scottgus1]

Let's see if Guest Additions are installed:

Please start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Attachments tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

[Docfxit]

Here is the log:

VBoxLog.zip

(33.93 KiB) Downloaded 31 times

I see Guest Additions 7.0.10 is installed

DevicesMenu.jpg (27.62 KiB) Viewed 1176 times

I don't see how I can add Guest Additions 7.0.14

I'm now getting an error when I start Vbox:
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID:BLKCACHE_IOERR
Severity:Non-Fatal Error

[scottgus1]

RE the error, the message explains itself:

VERR_DISK_FULL

Either the physical host disk or the VM disk... This one should be easy to figure out.

You do have Guest Additions 7.0.10 installed in the VM.

Once your get the error handled, and the VM is booting to the desktop again, check the VM window's View menu. "Auto Resize Guest Display" should be checked. Then resize the VM window. The screen size of the VM should change to match the VM window.

[Docfxit]

I found the PC drive was full. I fixed it.

I finally got Guest Additions 7.0.14 installed.

VBox.zip

(39.37 KiB) Downloaded 28 times

Does this mean "Auto Resize Guest Display" is checked?

VboxView (.jpg (52.22 KiB) Viewed 1131 times

As you can see turning on "Auto Resize Guest Display" didn't solve the display problem.

[granada29]

In the screenshot of your Display Settings (one of your earlier posts), you have set a scale factor of 200%. Try reducing this to 100% and see if that helps.

[Docfxit]

Changing it to 100% helped. Now it's too small. It's not filling the screen.

VboxWindowsScreen (.jpg (51.28 KiB) Viewed 1040 times