Custom Query (16611 matches)

I am running VirtualBox 7.0.12, Win 10 host, Ubuntu guest.

I was listening to audio from my Ubuntu VM when I accidentally powered off my bluetooth headphones. I powered them back on and thanks to the recent patch for #20431, they resumed playing audio within a few seconds (yay!). Less than a minute later, I got an error message from Windows "the instruction at XX tried to access memory at address YY, the memory could not be written". I moved the error dialog out of the way and the VM appeared to operate normally, with audio still playing and programs functioning. After about an hour, though, it got so unstable that I had to click "OK" on the dialog and force-close the VM.

I have experienced this crash multiple times since the patch for the audio switching issue was applied. The sequence of events is always the same: audio device disconnects, then reconnects, wait a few seconds, then error. I originally observed it in the test build that pentagonik posted to ticket #20431, but figured it was just part of the instability of a nightly build. However, this is now the third time that I've experienced this crash with the release version 7.0.12.

A log file is attached. The headphones disconnect on line 1715, reconnect on line 1746, and the exception/crash (with stack trace) starts on line 1805.

there is a problem with the output of the command vboximg-mount, one can read :

The virtual disk is exposed as a device node within a FUSE-based filesystem
that overlays the user-provided mount point. The FUSE filesystem consists of a
directory containing a number of files and possibly other directories:    * vhdd:      Provides access to the raw disk image data as a flat image
    * vol<id>:   Provides access to individual volumes on the accessed disk image
    * fs<id>:    Provides access to a supported filesystem without the need for a                 host filesystem driver

Strange, isn't it ?

Looks like some "\n" are missing in vboximg-mount.cpp :

"The virtual disk is exposed as a device node within a FUSE-based filesystem\n"
"that overlays the user-provided mount point. The FUSE filesystem consists of a\n"
"directory containing a number of files and possibly other directories: HERE"
" * vhdd: Provides access to the raw disk image data as a flat image\n"
" * vol<id>: Provides access to individual volumes on the accessed disk image\n"
" * fs<id>: Provides access to a supported filesystem without the need for a AND THERE"
" host filesystem driver\n"

Regards,

Someone told me, in "​https://forums.virtualbox.org/viewtopic.php?p=542839&sid=236d25143c6b03629e47ed60de15cca9#p542839" You're absolutely right. Please create a ticket in the Bugtracker.

Crash Windows server 2008 R2 64 bit after install additions (2x)