VirtualBox

Changes between Initial Version and Version 1 of Ticket #15090


Ignore:
Timestamp:
Jan 29, 2016 1:08:14 PM (8 years ago)
Author:
Frank Mehnert
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15090

    • Property Summary Linux host running "perf top" kills Virtualbox vm'sLinux host running "perf top" kills Virtualbox vm's (VERR_PGM_INVALID_CR3_ADDR)
  • Ticket #15090 – Description

    initial v1  
    11If I run Linux tool "perf top" on host and Virtualbox VM at the same time, VM crashes. It doesn't matter which is started first.
    22
    3 
    43Host versions tested:
    5 Linux 4.3.3-3-ARCH #1 SMP PREEMPT x86_64
    6 perf version 4.4.gafd2ff
    7 VirtualBox 5.0.14_OSE r105127
    8 
     4 * Linux 4.3.3-3-ARCH #1 SMP PREEMPT x86_64
     5 * perf version 4.4.gafd2ff
     6 * !VirtualBox 5.0.14_OSE !r105127
    97
    108Guest versions tested:
    11 Linux 4.4.0-4-ARCH #1 SMP PREEMPT x86_64
    12 Linux 2.6.18-164el5PAE #1 SMP i686
    13 Windows10 64-bit modern.ie without guest additions
    14 
     9 * Linux 4.4.0-4-ARCH #1 SMP PREEMPT x86_64
     10 * Linux 2.6.18-164el5PAE #1 SMP i686
     11 * Windows10 64-bit modern.ie without guest additions
    1512
    1613Host dmesg:
     14{{{
    1715[  313.192046] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
    1816[  371.880286] SUPR0GipMap: fGetGipCpu=0x3
     
    3634[  389.380249] device eth0 left promiscuous mode
    3735[  390.099756] vboxnetflt: 0 out of 4 packets were not sent (directed to host)
    38 
    39 
     36}}}
    4037Attaching VBox.log's in a second.

© 2023 Oracle
ContactPrivacy policyTerms of Use