Problems Full Screen --- La instrucción en 0x00000000 ....

[pabusa99]

Hello, when I try to set my mahicnes to full screen I always receive a message like that:

"La instrucción en 0x00000000 hace referencia ala memoria en 0x00000000. La memoria no se pudo written."

I use virtualbox 5.0.38

Why can't I ?????

Thank you

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[pabusa99]

Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

here it is.

I tell you how I generated it.

1 - I start the VM normally.
2 - When it has started I try to go to full screen... and de message appears... and the VM goes to state "Aborted"
3 - I start again normally. (You told me to get the machine off)
4 - I turn off the VM
5 - I get the vm.log

Thanks.

[mpack]

Topic moved to "Windows Hosts".

Something peculiar is happening here.

00:00:00.988489 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:00.988502 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:00.988504 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX

What are these? Where are the memory addresses normally found in those fields?

00:00:00.999270 File system of 'I:\Software\Desarrollo\vs2015.1.com_esn.iso' (DVD) is ntfs
00:00:01.000579 File system of 'E:\Virtual\VirtualBox VMs\W764_VS_202\Snapshots' (snapshots) is unknown
00:00:01.000584 File system of 'E:\Virtual\VirtualBox VMs\W764_VS_202\W764_Base clonar-disk1.vdi' is ntfs

Strange paths.

00:00:01.403393 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0

Again with the strange memory addresses.

Have you missed out any part of your story? Are you using a completely standard install from the offical distribution of VirtualBox?

If so I suggest that you download a more recent version (e.g. 5.1.22) and try with that.

[Perryg]

Don,
I have been seeing those weird addresses for some time now. I suspect it is fault diagnostic code in the 5.1.* version that has not been fixed yet, but that is just a guess at this point. Do you not see this in your own guests?

[mpack]

I suspect it is fault diagnostic code in the 5.1.* version that has not been fixed yet

The OPs log is from 5.0.38, hence my suggestion that he try something recent.

[Perryg]

I honestly don't remember when I first saw this but 4.0.38 is still getting some updates with regards to 5.1.* work which includes some of the new diagnostic code. If I find the time ( and remember ) Monday I may ask the DEVs what is going on with this.

[pabusa99]

More information could be that I updated to 5.1 versión however VMs didn't start, I can't remember because of... so I "downgraded" again to 4.0... however I could tell you if the problem was before or after....

[pabusa99]

Another fact to point out could be that some machines where cloned from others created before...

Anothers created in differents folders...

But, even if I créate a new one... the problem comes as far as I try to set it to full screen. I don`t try full screen everything goes perfectly.

Thanks.

[mpack]

As mentioned, try updating to a current version of VirtualBox. Update the Guest Additions at the same time.

Speaking of the Guest Additions, I see no evidence that they have been installed in this VM, and fullscreen mode certainly won't work without them - though I would not have expected a crash.

[pabusa99]

As mentioned, try updating to a current version of VirtualBox. Update the Guest Additions at the same time.

Speaking of the Guest Additions, I see no evidence that they have been installed in this VM, and fullscreen mode certainly won't work without them - though I would not have expected a crash.

If I go to the last versión... I mean 5.1 --> VMs don't start .... I keep 5.0 because of that...

I run 5.0.40, I have tried to installa guest additions in one of my VMs... and I have the same problema with full screen

[socratis]

Again with the strange memory addresses.

Don,
I have been seeing those weird addresses for some time now. I suspect it is fault diagnostic code in the 5.1.* version that has not been fixed yet, but that is just a guess at this point. Do you not see this in your own guests?

The OPs log is from 5.0.38, hence my suggestion that he try something recent.

I stumbled in the answer. From ticket #15167: Kernel Address Info Leak, you can see what's going on in CVE-2017-3513:

Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.0.38 and Prior to 5.1.20. Difficult to exploit vulnerability ...

Bottom line, you're going to be seeing a lot of XXXXX addresses from now on...