Custom Query (16363 matches)
Results (1855 - 1857 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8716 | fixed | Cannot recompile VirtualBox kernel module with Debian precompiled kernel 2.6.38-2-686 | ||
| Description |
On Debian Squeeze, when installing and using precompiled kernel 2.6.38-2-686, the VirtualBox kernel module fails to recompile: mini:/home/jors# uname -r 2.6.38-2-686 mini:/home/jors# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules:. Uninstalling old VirtualBox DKMS kernel modules:. Trying to register the VirtualBox kernel modules using DKMS: Failed, trying without DKMS ... failed! Recompiling VirtualBox kernel modules: Look at /var/log/vbox-install.log to find out what went wrong ... failed! mini:/home/jors# The vbox-install.log says the following: mini:/home/jors# cat /var/log/vbox-install.log Makefile:178: *** Error: /usr/src/linux (version 2.6.38) does not match the current kernel (version 2.6.38-2-686). Alto. mini:/home/jors# When showing installed precompiled kernel headers information with dpkg, it seems like some versioning info is wrong. First column version info matches current running kernel, but not second column version info, as you can see here: mini:/home/jors# dpkg -l linux-headers-2.6.38-2-686 Deseado=Desconocido/Instalar/Eliminar/Purgar/Retener | Estado=No/Instalado/Config-files/Desempaquetado/Medio-conf/Medio-inst/espera-disparo/pendiente-disparo |/ Err?=(ninguno)/Requiere-reinst (Estado,Err: mayúsc.=malo) ||/ Nombre Versión Descripción +++-=============================-=============================-========================================================================== ii linux-headers-2.6.38-2-686 2.6.38-3 Header files for Linux 2.6.38-2-686 mini:/home/jors# Could this last tip be the problem's root? Any workaround to bypass this temporally? |
|||
| #1707 | fixed | Cannot remember size and state of window. Starting from ver. 1.6.0 | ||
| Description |
My host system: Kubuntu 8.04 Hardy Virtual Machine: Windows XP When I had innotek 1.5.6 version, my Windows XP was configured to be launched in full screen, and everything worked splendid. Starting from ver. 1.6.0 my sunVM isn't able to remember, what size of window it was when stopped last time. Also it isn't able to launch itself in full screen mode. I thought, that this annoying bug of 1.6.0 must have been repaired with 1.6.2, but it unfortunately resisted. The worse thing on it is, that each time I open my sunVM Windows, I have to rearrange the icons on desktop. What's vasting time, because next all icons will be again gathered in small rentacle of 640x480 pixels ..... I'm starting to think about migration to VmWare, sorry ... |
|||
| #5006 | obsolete | Cannot reopen virtualbox gui after running/closing virtualbox | ||
| Description |
Host: Windows XP Home edition If I close the virtualbox GUI after using a virtual machine then I am unable to open the GUI again. In task manager Virtualbox.exe and VboxSVC.exe are still running, but force ending the processes does nothing to solve the problem. The only way I can get it working again is by logging off & on / restarting, at which point windows tells me that Virtualbox.exe is not responding & do I want to end it now. What's really odd is that this message appears even if I kill the virtualbox.exe process before hitting the logoff button. I've attached some log log files from the virtual machine that I use before closing the GUI. |
|||

