Custom Query (16363 matches)
Results (388 - 390 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20435 | duplicate | Guestcontrol --wait-exit is back in the manual | ||
| Description |
Seems the "--wait-exit" argument is still shown in the manual as an example option for 'vboxmanage guestcontrol', even though it is not a valid command as shown in the syntax error message when trying the command: VBoxManage.exe: error: Unknown option: --wait-exit See https://download.virtualbox.org/virtualbox/6.1.22/UserManual.pdf, page 191, also https://www.virtualbox.org/manual/ch08.html#vboxmanage-guestcontrol Searching the Bugtracker for "--wait-exit guestcontrol" shows this gets fixed, but it crops back in. Maybe someone has a branch with old data that gets re-implemented? |
|||
| #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 |
|||
| #20424 | invalid | Virtualbox session not working macos monterey | ||
| Description |
Virtual box session not loading on macos Monterey. Any virtual machine like windows 10n macOS bigger or anything won't load on macOS Monterey. |
|||

