Hi,
Assertions are printing the file and line number into the VBox.log
when they are triggered. So getting the log of the aborted VM would
help.
Regards,
Alexander Eichner
On 26.01.2011 at 18:00 Hans Petter Selasky, wrote <[email protected]>:
On Wednesday 26 January 2011 17:46:41 Klaus Espenlaub wrote:
On 23.01.2011 17:36, Hans Petter Selasky wrote:
Hi,
During usage of VirtualBOX under FreeBSD 8.2, I've noticed that
the VM
sometimes crashes if the USB string descriptors or other descriptors
cannot be read or the device itself cannot be created, because the
device is not responding.
From what I can understand VirtualBox USB enumeration has two
stages:
1) Identifying devices
2) Probing devices
There is no guarantee that identified devices won't disappear
until they
are probed. Should the FreeBSD USB layer in this case return fake
status
values, to avoid VirtualBOX from asserting.
This is extremely vague, as it we have many thousand assertions
spread
all over the VirtualBox code.
Generally it would be helpful to have a VBox.log with the assertion.
3) Reading any USB descriptor could theoretically fail at any
time. The
USB 1/2 specification specifies the STALL message, and there can
be bus
errors aswell. Who is responsible for hiding these failures, so
that the
VirtualBOX machine does not assert()?
Again - what assertion?
Klaus
Hi,
I will try to get VirtualBOX compiled with debug symbols and get you
the exact
assertion that it triggers on.
--HPS
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
