Soldier Soul and Black Screen

[Virulix]

Hello,

I've just installed Steam in my VM.
When I install the play "SAint-Seya Soldier Soul", I can launch the Play but at the moment the Play tries to synchronise to the Cloud, I got a black screen and come back to the Play Icon again. So I cannot play at all !

(to be noted, with another Play of Chess, the images are also choppy and intermittent)

I have a Laptop : ASUS TUF GAMING.


I will send you my personal Settings of the VM within 1 day, I'm not allowed to do so because I must wait a day before to allowed to !)

$ dkms status
virtualbox, 6.1.34, 5.15.0-41-generic, x86_64: installed

I'm under Ubuntu :
Ubuntu 20.04.4

The Disk :
Disk nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors

I've upgrade the number of vCPU : don't take into account the print-screen when you will be able to see them, I upgraded the number of vCPU to 4 (4 vCPU) currently.

Thanks in advance !!

[Virulix]

Here are the links as promised :

https://pix.cyber-nux.fr/?img=1658855659.png
https://pix.cyber-nux.fr/?img=1658855678.png
https://pix.cyber-nux.fr/?img=1658855694.png
https://pix.cyber-nux.fr/?img=1658855709.png
https://pix.cyber-nux.fr/?img=1658855730.png

another info : I changed the process as a Real Time, but nothing has changed unfortunately...

Help !

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

And be aware, VMs are often unsuitable for gaming. You will rarely if ever get low latency from simulated hardware. VMs are best when the application and hardware requirements are generic.

And p.s. unless apps have been specially designed (i.e. are a member of a vanishingly small subset) then adding more CPU cores does not make things go faster, all it does is it allows more apps to run at the same time. But those that run do so at the same speed they always did.

[Virulix]

OK Go get it then !

==> see underneath the attached file,

Thanks a lot

[mpack]

00:00:01.045102 VirtualBox VM 6.1.34_Ubuntu r150636 linux.amd64 (May 13 2022 07:34:48) release log

Unsupported third party build (not VirtualBox).

00:00:01.116917 File system of '/home/tux/Téléchargements/Win10_21H2_French_x64.iso' (DVD) is ext4
...
00:00:04.073916 VMMDev: Guest Log: BIOS: Booting from CD-ROM...

If the OS is installed then eject the install DVD.

00:00:01.154358 NumCPUs <integer> = 0x0000000000000004 (4)
...
00:00:01.359749 CPUM: Physical host cores: 4

I always struggle to understand why people think that starving the host of CPU will make things go faster. The VM is a simulation running on the host. It will not be improved by allocating more cores to guest code (not the simulation). And since your host has 4 cores total, you should not be assigning more than 2 cores to the guest.

[Virulix]

maybe it is due to CPU stitching ?
(increase of CPU Cores)

Ok so it won't never run due to compatiblity problem between my ubuntu release and the virtualbox. Is that correct ?

[multiOS]

NO! That's not what mpack said/recommended at all.

1. The point was made that you are using a 'fork' of VirtualBox provided through the Ubuntu repositories rather than the official version only found via the Oracle Downloads Page. As your version is compiled by Ubuntu, using the open source VirtualBox Source Code as a base, it is not known what, if any, changes may have been made during that process, so this forum doesn't support that version, though general advice may be available from other users based only on how the official version works.

2. The Log shows you still have the Windows installation disk loaded in the Virtual CD/DVD Drive and which should have been ejected when the installation process was completed. The log includes:

00:00:04.073916 VMMDev: Guest Log: BIOS: Booting from CD-ROM...

shortly before the the Virtual Machine starts shutting down, so the presence of the OS installation iso may be causing a problem.

The log also shows:

00:00:01.101021 Guest OS type: 'Windows7_64'

But the iso present in the drive is

00:00:01.154495 Path <string> = "/home/tux/Téléchargements/Win10_21H2_French_x64.iso"

So, if the VM installation is Windows 10, you should change the VM Template to match the installation.

3. mpack recommended reducing the cpu allocation from 4 to 2 because your Host PC only has 4 physical cores. The Host PC should continue to work with 1/2 of its brainpower, but may not survive very long with no brain at all.