Ideapad 5 Pro R7-7840HS VM virtualization issue

[garciax1671]

Hello,


I have the Ideapad 5 Pro with the AMD Ryzen 7 7840HS processor with W11, with the Virtualbox 7 program and I tried to install a VM (Virtual Machine) of an Ubuntu 23.10 OS, at the time of installing there comes a point where a message appears message "Freeing initrd memory: 105798K" and it stays blocked, I have tried everything. AMD-V is enabled in the BIOS, I updated the BIOS, I have tried other Linux distributions and there is no way, I have tried all the configurations in Virtualbox, several versions, I have searched for information everywhere and I have not found a solution.


I need to fix this problem, please.

[scottgus1]

The only thing I have seen, mentioned several places on the forum, is that the 7840HS needed a BIOS update, which you have done. What version of "Virtualbox 7" are you trying?

[garciax1671]

Yes, I have installed the latest BIOS update and I am using VIrtualbox 7.0.14-161095, and the problem still exists. I have also seen that the problem was fixed with the BIOS update, but I still have the problem, the update is v31. I attach an image of what happens, also the logs.

[fth0]

Please try the workaround I posted in Re: Unable to install CentOS and report back.

[garciax1671]

So do I have to wait for them to release the next version of Virtualbox with the problems already fixed?
In my case, with everything updated: BIOS, drivers, latest version of Virtualbox, my updated W11 and the version of Ubuntu to virtualize, I don't know what to do.

[scottgus1]

Garcia, it is expected that you'll read other responders' posts on your topic before posting again. There was a suggestion to try above your last post that you've apparently missed.

[garciax1671]

Of course it works, but logically it is not a solution if every time I have to create a virtual machine I have to go into the command prompt and enter those commands, because all the other computers that are not like mine do not have to do this, Therefore, it is a problem that must be corrected. That solution works to get by, but it is not satisfactory.

[scottgus1]

Of course it works

Thanks for reporting back. Nice to see you saw and tried the suggestion.

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

logically it is not a solution

Quite logically. That's why it is not called a "solution":

Please try the workaround I posted

"Workaround" != "Solution". A workaround is something done to get a project working when the project is stopped because of a problem. The devs have not reached "solution" stage on this yet, although they may by the time the next version of Virtualbox comes out. The solution may already be in the test builds, or may be there soon.

So for now, until the devs figure this out, you:

have to go into the command prompt and enter those commands

Unless you want to not use Virtualbox until the official new version comes out, probably in some months.

When you've been around Virtualbox long enough, you'll see various times when Virtualbox works swimmingly, and other times when things are rough because of various new changes in host hardware, CPU's, OS's, and Virtualbox development goals. When the rough patches come, some go predicting the end of the world because Virtualbox needs a temporary workaround. Get a grip, folks.... Life happens, and life isn't always 100% smooth. Time and work smooth the problems.

[garciax1671]

Thank you very much, at least it will be fixed in the next versions and that is quite reassuring, that is, the problem is reported, which is what I wanted to get to, thank you very much again for your time.

[fth0]

FWIW, the issue should be fixed in the VirtualBox test builds 7.0.15r161357 and newer. Please undo the workaround and give it a try.