virtualbox.org

Hello,
So this has been a persistant issue. If I run virtualbox and then later try running a java application, the application will run, but any window that's supposed to pop up will not. The best example I have of this is minecraft. If I run virtualbox and then later try to run minecraft it will run, but there will be no icon in the taskbar and no window to interact with. This problem happens exclusively when I have ran virtualbox and then try to run minecraft without restarting, so virtualbox must be changing something that java needs to display the window properly. Any ideas?

I am not certain how to troubleshoot this one.

After running a VM, shutting down, then trying to run a Java program, please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.

Also, please go to C:\Users\{youraccount}\.Virtualbox, and zip & post the VboxSVC.log, using the forum's Upload Attachment tab.

Here is the logfile.

Jaclyn wrote:Here is the logfile.

There were actually supposed to be three logs:

scottgus1 wrote:After running a VM, shutting down, then trying to run a Java program, please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.

Also, please go to C:\Users\{youraccount}\.Virtualbox, and zip & post the VboxSVC.log

Sorry, my bad.

OK, there are some problems in the setup of your Virtualbox and the VM.

00:00:02.645207 Executable: E:\VB install\VirtualBoxVM.exe

Virtualbox was installed out of the default "C:\Program Files". This has caused problems in the past. Uninstall then reinstall in "C:\Program Files". Then try the Virtualbox vs Java again. (Note that if Virtualbox was installed in a non-default location, so may other apps, and this conflict may be deeper than we can troubleshoot. In several years of reading the forum I haven't heard of a conflict between Virtualbox and Java.)

Other things to consider:

Host CPU status:
00:00:03.538088 CPUM: Logical host processors: 16 present, 16 max, 16 online, online mask: 000000000000ffff
00:00:03.538089 CPUM: Physical host cores: 8
Guest CPU settings:
00:00:02.764145 NumCPUs <integer> = 0x0000000000000008 (8)

All the host's physical cores are available for the VM. If the VM goes 105% on the reactor, the host stability may suffer. Reduce cores to 2 until the software installed in the VM maxes out the 2 cores all the time. (More cores in a VM slow down the VM due to extra scheduling in the host OS.)

Guest OS:
00:00:02.741820 Guest OS type: 'Windows2019_64'
Paravirtualization:
00:00:02.801257 GIM: Using provider 'KVM' (Implementation version: 0)

The "KVM" should be "Hyper-V" for a Windows OS in the VM. See the VM's System settings, Acceleration, Paravirtualization Interface. (This "Hyper-V" is not the Virtualbox-killing Hyper-V. It is OK to set this as recommended.)
The 2019 template may have bugs in it. Set the General settings, Basic, Version to "Windows 2016 (64-bit)". 2019 will run fine in the 2016 template.

Alright. I followed /most/ of your suggestions. I changed to the 2016 template and pushed my CPU down to four cores rather than two. I switched to hyper-v. It was on KVM because the last time I installed a machine hyper-v was not working with my AMD processor, so an update must have been pushed with windows or virtualbox. Virtualbox is still on E since I put it there for a reason and it turned out to not be the issue. Either switching to hyper-v or the 2016 template solved the problem, thanks.

Nevermind. It's doing it again.

Nevermind again. I forgot to kill the java process. Turns out if I let it just sit for like five minutes, the window will pop up.

Are your Virtualbox and Java cooperating now or are there still problems?

Yes because I found out that if I just let java run for like five minutes when the behavior exhibits, the window will pop up. No clue what is getting changed that makes it take so long after I've ran virtualbox, but you know what, it works and I'll take it.

Great, thanks for letting us know. Sorry we couldn't pin this one down more firmly.