Custom Query (16363 matches)
Results (1843 - 1845 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3284 | fixed | _init() driver entry point in vboxdrv kernel module returns bogus error value => Fixed in SVN | ||
| Description |
In this forum thread http://forums.virtualbox.org/viewtopic.php?t=13950 we found out that failures during an attempt to load the Solaris vboxdrv kernel module result in bogus error messages, like this: bash-3.2# modload -p drv/vboxdrv can't load module: Unknown error I can reproduce this issue by deliberately messing with the /etc/name_to_major file, changing vboxdrv 297 vboxflt 298 to xvboxdrv 297 xvboxflt 298 (added 'x' in front of the module names), followed by a reboot. After that change, modload -p drv/vboxdrv returns an error with errno == -1 (an unknown error code). The bug is in src/VBox/HostDrivers/Support/solaris/SUPDrv-solaris.c in function _init(). An _init(9e) function is supposed to return a positive error code from <sys/errno.h>, not -1: 192 /**
193 * Kernel entry points
194 */
195 int _init(void)
196 {
197 LogFlow((DEVICE_NAME ":_init\n"));
198
...
254
255 return -1; <<<<<<<
256 }
In my test case, the mod_install() call inside vboxdrv's _init() function failed with errrno == ENXIO; in this case ENXIO is the expected return code for the _init() function - and not -1. |
|||
| #3285 | fixed | Usability problem with "interfaces list" in configure Network panel | ||
| Description |
First, thanks for the great tool! Second, I'd like to point some usability problem: 1)
If instead usual list there were items with radio buttons it will be easier to understand that selection is so important. + when you wifi connected it's preferable to have wifi interface "selected" by default, when wired connection => select bge (or other) by default 2) I have wired connection at work and wifi at home (both DHCP) when I shutdown VM at work and start it again at home => I have to remember to change used network interface. It would be great to see, that now wired interface is down on general page in Network section (i.e. red text color) Thanks! Vladimir Less errors and no need to restart VM. |
|||
| #3286 | fixed | Windows XP Host, Full screen and Direct Network connection | ||
| Description |
Hi, it seems that there is a bug when Network is directly attached to the physical adapter of the host: the full screen mode of the guest is only possible in low resolution : eg my desktop can display in 1400x900 but when using host interface for network config,I can only display in 1200x800 mode inside the host. Reverting back to NAT fix the issue. Cheers, David LIMA |
|||

