VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1879 - 1881 of 16363)

Ticket Resolution Summary Owner Reporter
#9726 obsolete BSOD when Online Armor installed pcguy
Description

Virtualbox 4.1.4 causes BSOD in Online Armor software firewall for Windows 5.1.0.1370 http://support.emsisoft.com/topic/6048-online-armor-5101370/page__view__findpost__p__35369

"It is an interaction we can't fix though. So please report it to the VirtualBox guys. The crash is caused by the VBoxNetFlt.sys driver that is always running even when VirtualBox is closed. To be more precise it crashes when freeing a chunk of memory. Most likely a case of bad error handling or parameter verification. "

#9728 obsolete Oracle VM VirtualBox 4.1.4 r74291 Manager version (Win64) crash after checkpoint restore a disabled PC Codename
Description

Oracle VM VirtualBox 4.1.4 r74291 Manager version (Win64) crashes when I wanted to restore a backup point of a powered off machine. At the same time, another machine was on.

Windows showed the crash of a dialogue with the following message:

Problemsignatur:
  Problemereignisname:	APPCRASH
  Anwendungsname:	VirtualBox.exe
  Anwendungsversion:	4.1.4.0
  Anwendungszeitstempel:	4e89c9d4
  Fehlermodulname:	ntdll.dll
  Fehlermodulversion:	6.1.7601.17514
  Fehlermodulzeitstempel:	4ce7c8f9
  Ausnahmecode:	c0000005
  Ausnahmeoffset:	00000000000532d0
  Betriebsystemversion:	6.1.7601.2.1.0.256.4
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	e0d1
  Zusatzinformation 2:	e0d15ac2f29137f01c0ce55eef570951
  Zusatzinformation 3:	8d59
  Zusatzinformation 4:	8d59443770b792fe21cbaa900b1ef127

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

Host: Windows 7 Enterprise x64 SP1 Deutsch (ISO/CRC: 83FC73C0)

Attached is the latest sign that after the crash of the Oracle VM VirtualBox Manager, was available.

#9730 obsolete Host hang on pci-attach'ed device initialization in guest dimaqq
Description

I tries to pci-attach a PCIe graphics card (I know I shouldn't, but...), attachment succeeded, guest OS booted, but when guest OS tried to use the card with native drivers, guest OS bluescreened and soon/immediately after host hung.

host: dq67sw, i7-2600, all vt-x, vt-d settings enabled in bios, kernel 3.0.4-1 (arch), 64-bit, all proper extensions enabled: intel iommu, dmar, pci-dma. virtual machine config all important enabled:ich9, io-apic, pae/nx, 2 cpus, vt-x, nested paging pci-passthrough: 01:00.0@04:00.0, 01:00.1@04:00.1. (.0 is gfx hd 6870, .1 is audio on same card, guest wouldn't boot with 01@01, thus 01@04) guest: xp 32-bit, driver in question catalyst 11.6 (considered good version for xen)

guest boots up enough to install gfx drivers, ask to reboot, next time boots up and and bluescreens in ati2drav.

immediately or very soon after (enough to show virtualized blue screen in host virtualbox window), host hangs too.

I was under the impression that VT-d should have protected me from this, so perhaps it's a bug or limitation in virtualbox pci passthrough?

Sorry I can't get any linux crash backtrace :(

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

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