Custom Query (16363 matches)
Results (2020 - 2022 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16241 | worksforme | Debian 8.6 "jessie": Install: ERROR: Kernel configuration is invalid. | ||
| Description |
On a new clean installation of Debian 8.6 "jessie" 64-bit i got following error in /var/log/vbox-install.log: ERROR: Kernel configuration is invalid. and i can't start/stop vbox services per service [vboxservice] start/stop" Under /etc/init.d/ doesn't exists any vbox service script. Install command: apt-get install virtualbox-5.1 Content of sources.list: deb http://download.virtualbox.org/virtualbox/debian jessie contrib |
|||
| #16240 | fixed | Fullscreen guest aborted by HP laptop undock | ||
| Description |
I can reliably crash either of my guests by undocking my laptop when running a vbox guest in a fullscreen on an external monitor. I have a patched windows 10 laptop host running V 5.10 2x guests, win7-64 & win10, both patched & running GA. When docked I have 2x external HDMI monitors & a laptop display available. The laptop display resolution is identical to one of the monitors (and the other is the same resolution in portrait format). The guests are configured to use 2x monitors & I can direct fullscreen output to any pair without difficulty. Both guest types will be aborted only if an Undock occurs when they are fullscreen & are using one of the external monitors. The following cases work successfully:
This case does *not* work
When undocking the laptop (separate switch to disconnect the base station, this also cuts ethernet, power & usb devices, although I do not knowingly have any USB passed through. The win64 guest is a p2v machine (with some cruddy HP device drivers I can't uninstall), but the win10 machine is a clean ISO install done on this laptop. Both behave identically when it comes to aborting on undock. It does not seem to make a difference as to whether the disconnected monitor is set as a primary in the guest or which virtual monitor is assigned. The error is always a memory read error & does not appear to show in the log. Any assistance appreciated. |
|||
| #16239 | duplicate | sometimes, only half screen processes mouse events -> duplicate of #14743 | ||
| Description |
After a while, in landscape mode , the graphic display processes only mouse events in half right screen portion. left half screen portion does not answer to mouse events ! the only way to restaure normal behaviour is to stop / restart virtualbox vm |
|||

