Custom Query (16611 matches)
Results (40 - 42 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21957 | wontfix | Virtualbox 7.0.12 doesn't run on Ubuntu 22:04:03 running kernel 6.5.0-14 | ||
| Description |
A VM in Virtualbox 7.0.12 created on Ubuntu kernel 6.2.0-39 and running ok but after upgrading to latest released Ubuntu kernel 6.5.0-14 doesn't start. There are no drivers in the /lib/modules/6.5.0-14-generic/misc directory of the kernel. In fact the misc directory has not been created. Reviewing the logs in /var/log, shows: Building the main VirtualBox module. Error building the module: make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/6.5.0-14-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j8 modules make[1]: warning: -j8 forced in submake: resetting jobserver mode. warning: the compiler differs from the one used to build the kernel
and later /bin/sh: 1: gcc-12: not found There is no gcc-12 installed on the system with the latest being gcc-11, which is a link from /usr/bin/gcc It appears the drivers are not being built because the kernel was built with gcc-12 so virtualbox goes looking for gcc-12. Is gcc-12 a prerequisite for virtualbox modules to work with the 6.5.0-14 kernel and has it been tested? Full log file attached |
|||
| #21950 | obsolete | vboxadd.service fails to start in the guest after an kernel update of Ubuntu 22.04 | ||
| Description |
A guest machine with Ubuntu 22.04 has been updated. The update is from kernel version 6.2.0-39 to version 6.5.0-14. During the update a hint has been displayed in the terminal: look at log file /var/log/vboxadd-setup.log what's wrong [file is attached]. After re-starting the guest machine (Ubuntu 22.04) booting last 5 minutes, because vboxadd.service fails to start (see syslog). |
|||
| #21947 | invalid | When using 'tcpserver' uart mode, data is not received until cr/lf | ||
| Description |
For example: install terminal emulator software in a guest, and connect it to a serial port that is a tcp server on the host side. Connect to that port with telnet or putty. As you press keys on the telnet side, one would expect them to appear in the guest. They do not, until ENTER (or return) is pressed. Install BBS software in a guest, associated with a serial port configured similarly. If the software provides a prompt and is awaiting a single keypress, that keypress cannot be received until enter is also pressed. |
|||
