VirtualBox

Opened 9 years ago

Last modified 9 years ago

#14180 new defect

when trying to open sagemath in oracle vm virtual box in windows 8.1 64 bit Blue screen of death happening

Reported by: amritendu Owned by:
Component: other Version: VirtualBox 4.3.28
Keywords: BSOD Cc:
Guest type: Linux Host type: Windows

Description

Installation of Oracle VM Virtual Box and importing the sage ova file in it was not a problem. But when I started the sage machine Blue Screen of Death (DRIVER_VERIFIER_DETECTED_VIOLATION) happened. Otherwise my machine works fine. I was using Sage-6.7 ova file and Virtual Box 4.3.28.100309-win in a windows 8.1 64 bit machine. The problem persists for 4.3.12.93733-Win version also. For my machine OS, drivers BIOS everything is up to date. Hard disk health is good. No issue of Virus or malware. I have not installed the guest additions.More than 100 GB space is available in machine. Any help will be appreciated.

Attachments (1)

Sage-6.7-2015-06-07-23-00-52.log (25.0 KB ) - added by amritendu 9 years ago.
guest log file

Download all attachments as: .zip

Change History (4)

by amritendu, 9 years ago

guest log file

comment:1 by Perry G, 9 years ago

Perhaps this should be tended to first.

00:00:01.387811 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization. 

Reference forum for additional assistance.

https://forums.virtualbox.org/viewtopic.php?f=1&t=62339

comment:2 by Frank Mehnert, 9 years ago

That warning might be a problem but I'm not sure if this is really related. First I would like to know some more information about the BSOD which happens on your host. There should be several parameters available.

Second, did you disable VT-x for this VM by intention? Also I doubt that 512 MB guest RAM is enough for such a guest.

comment:3 by Frank Mehnert, 9 years ago

Actually I just tried the OVA myself and it runs fine here with VBox 4.3.28. However, I saw that the OVA comes with VT-x/AMD-V disabled. I strongly suggest to enable this setting. I still don't understand where the actual BSOD comes from.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy