Comment 5 for bug 1567622

Revision history for this message
Thomas Orozco (torozco) wrote :

Good news: upgrading to latest VirtualBox seems to resolve the issue!