Custom Query (16363 matches)
Results (859 - 861 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12584 | obsolete | VB crashes when logging into host via LogMeIn.com | ||
| Description |
Host: Win7/64bit, 16GB RAM, 9GB free Guest: WinXP_SP3/32bit, 2GB RAM, 1.4GB free I run the guest in Seamless mode. VB: Version 4.3.6, Guest Additions installed I use an online service called LogMeIn.com to connect to my host machine from work. This had been working until about two VB updates back (about two months ago), but now when I connect to the host, although everything appears to be running properly at the time, when I get home I find that VirtualBox has crashed, leaving just a blank screen with a Windows error window. Once I close the error box, my host system is still running fine, and the VB Manager is still running, but the Guest OS and VB window for it are gone. I am enclosing the VB log file for today's event with this message. There are no available minidump files on the host machine, I will check for a minidump on the guest after I file this report (I didn't want to confuse the log file contents). |
|||
| #20425 | fixed | VBox guest fails to run on Linux host with host-kernel built with clang. | ||
| Description |
For one of my hosts, I'm recently trying out llvm/clang built linux kernel. After installing the kernel in the host and restarting it; the VBox Manager works but VM guests won't start. Checking the vbox-setup.log shows that dkms is trying to build the vboxdrv modules using "gcc" explicitly and failing. Typical errors are gcc: error: unrecognized command-line option ‘-Qunused-arguments’ gcc: error: unrecognized command-line option ‘-Qunused-arguments’ gcc: error: unrecognized command-line option ‘-mno-global-merge’ cc: error: unrecognized command-line option ‘-Qunused-arguments’ cc: error: unrecognized command-line option ‘-mno-global-merge’ cc: error: unrecognized command-line option ‘-mno-global-merge’ cc: error: unrecognized command-line option ‘-mno-global-merge’ cc: error: unrecognized command-line option ‘-mno-global-merge’g c: error: unrecognized command-line option ‘-mno-global-merge’g c: error: unrecognized command-line option ‘-fsplit-lto-unit’ I tried again using "update-alternatives" command to set "cc" to point to clang as a work around $ cc --version; c++ --version Ubuntu clang version 12.0.0-3ubuntu1~20.04.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin Ubuntu clang version 12.0.0-3ubuntu1~20.04.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin But it still didn't work and produced the exact same errors in the vbox-setup.log. I suspect because somehow dkms is explicitly trying to build the modules using "gcc" instead of "cc". Here is part of one line example from the log: gcc -Wp,-MMD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/11/include ... I'm not sure what to do next. For now I have reverted to a Linux kernel host built using gcc which works perfectly. Please advice or fix the dkms setup so that it isn't hardcoded to use gcc. Perhaps figure out whether to use gcc or clang based off the host kernel somehow; or perhaps change the dkms setup to use "cc/c++" instead which is configured by "update-alternatives". I am running Ubuntu 20.04 and the llvm/clang built kernel is 5.12.10 |
|||
| #9698 | fixed | Guru Meditation (VERR_PGM_PHYS_PAGE_RESERVED) trying to boot the Windows 2008 R2 64 bit ISO in 4.1.4 | ||
| Description |
Team, I am the Windows Server admin, i had installed windows 2008 R2 iso in Virtualbox ver 4.0.2 it worked well, due to some misconfiguration in that windows server i had deleted that server from my VM pool. yesterday i have updated the new Vbox 4.1.4 then i used the same win server 2008 R2 Iso 64 bit it is not booting, i have configured the boot options and IDE settings properly and i know that ISO file worked many times i have installed before in virtual box and physical servers too. Team please check this. it is booting properly with windows server 2003 R2 32 bit properly i think its issue with 64 bit. Thanks in advance, Daniel |
|||

