I have installed opensuse leap 15.2 64 bit on virtualbox 6.1.10 virtual machine (ram 4096 MB, hd 40gb, 2 processors) . It seems that each time the virtual machine is restarted the system crashes with the following message :
The instruction at 0x00007FF9550AF43C referenced memory at 0x000000000000000000. The memory could not be read.
The error occurs already during the installation (when the installation process is nearly completed and the machine gets restarted), and at each new execution of the machine. (I’ve tested it with KDE and xfce). It seems to occur before the completion of the start (i.e., not when the machine is already restarting and reloading the OS).
I have also tested, always with virtualbox 6.1.10, the old leap 15.1 and it doesn’t have the problem, it restarts smoothly.
Can this thing be investigated or solved ? If you need further information, please let me know.
Just done an update of 15.2 on virtualbox 6.1.10 virtual machine (ram 4096 MB, hd 8gb, 4 processors) on a 15.2 host and reboot at the end went smooth. We need more info about what you actually did, e.g.:
My guess is the update was not done in one of the virtual consoles and the GUI was running…
You need to get into a virtual console with right-ctrl+insert+f1 (or f2 or f3 ) and login there and do an init 3 to stop the gui so the install will go problem free.
It sometime takes a few seconds before you can login to the virtual console in VirtualBox or try another console - there are 6 of the f1 - f6.
First,
Although this problem was observed during an installation,
It’s almost certain this problem has nothing to do with bare metal installs so should have been posted in the Virtualization Forum.
A general observation,
This almost certainly has nothing to do with the Guest,
Memory mapping happens on the HostOS, and likely the Virtualbox app and hypervisor.
So,
Will need to know…
HostOS (another openSUSE? Something else?)
Virtualbox installed from Oracle or from openSUSE repos?
Regardless of the HostOS, has the HostOS been fully updated, and has the Virtualbox application been fully updated?
host system : windows 10 (sorry, I had forgotten to write it).
video adapter int the VM : (taken from “display” section in the settings of the virtualbox VM) video memory 16MB, monitor count = 1, graphics controller VMSVGA, 3D acceleration enabled (my pc’s graphics card is a geforce gtx970 with nvidia game ready driver v 451.67)
installer used : DVD - I have downloaded and mounted the ISO
VM EFI booting : I’m not sure; at this url : Check if Computer Uses UEFI or Legacy BIOS [Linux & Windows]
it tells me that to check if I have EFI booting I do have to search for a sys/firmare/efi folder on the linux os; I’ve checked and I don’t have that folder, so I suppose I don’t have EFI booting.
I was not doing an update : I was doing a fresh install on a new virtual machine.
Do I have to do that when the installation is running ? if so, at what point ?
This https://www.virtualbox.org/ticket/19708 looks very similar to what you witness.
Apparently a VirtualBox problem, not specific to openSUSE since it seems reproducible with many different distros as guests.
ok; anyway, on the same virtualbox installation I have also an old virtual machine with leap 15.1 which doesn’t have the problem (it can currently restart smoothly).
Your setup seems sound and you filed a bug report on bugzilla, so let’s see if anybody can reproduce what you are experiencing.
My guess is that there are not so many members here on the Forums running a Win10 host though.