Custom Query (16363 matches)
Results (2395 - 2397 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7184 | wontfix | vboxdrv does not compile/load on Centos 4 with kernel 2.6.27.45 | ||
| Description |
Environment: Host: Centos 4 with custom kernel 2.6.27.45, dkms 2.1.1.2 VirtualBox 2.3.6 (package VirtualBox-3.2-3.2.6_63112_rhel4-1.i386.rpm) When running vboxdrv setup, the result is: [...] Compilation of the kernel module FAILED! VirtualBox will not start until this problem is fixed. Please consult /var/log/vbox-install.log to find out why the kernel module does not compile. Most probably the kernel sources are not found. Install them and execute /etc/init.d/vboxdrv setup as root. [root@qeynos ~]# tail /var/log/vbox-install.log CC [M] /tmp/vbox.0/linux/SUPDrv-linux.o CC [M] /tmp/vbox.0/SUPDrv.o /tmp/vbox.0/SUPDrv.c: In function `supdrvCleanupSession': /tmp/vbox.0/SUPDrv.c:109: sorry, unimplemented: inlining failed in call to 'supdrvLdrLock': function body not available /tmp/vbox.0/SUPDrv.c:851: sorry, unimplemented: called from here /tmp/vbox.0/SUPDrv.c:110: sorry, unimplemented: inlining failed in call to 'supdrvLdrUnlock': function body not available /tmp/vbox.0/SUPDrv.c:870: sorry, unimplemented: called from here make[2]: *** [/tmp/vbox.0/SUPDrv.o] Error 1 make[1]: *** [_module_/tmp/vbox.0] Error 2 make: *** [vboxdrv] Error 2 This was fixed with the change below on /usr/src/vboxdrv-3.2.6/include/iprt/cdefs.h: [root@qeynos iprt]# diff -u cdefs.h.orig cdefs.h --- cdefs.h.orig 2010-06-25 12:32:20.000000000 -0300 +++ cdefs.h 2010-07-16 16:56:29.000000000 -0300 @@ -736,7 +736,7 @@ * @remarks Don't use this macro on C++ methods. */ #ifdef __GNUC__ -# define DECLINLINE(type) static __inline__ type +# define DECLINLINE(type) static type #elif defined(__cplusplus) # define DECLINLINE(type) inline type #elif defined(_MSC_VER) @@ -755,7 +755,7 @@ * @remarks Use sparsely and with care. Don't use this macro on C++ methods. */ #ifdef __GNUC__ -# define DECL_FORCE_INLINE(type) __attribute__((always_inline)) DECLINLINE(type) +# define DECL_FORCE_INLINE(type) DECLINLINE(type) #elif defined(_MSC_VER) # define DECL_FORCE_INLINE(type) __forceinline type #else After this, the module compiles but when I try to load, I get the following: [root@qeynos ~]# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module [ OK ] Recompiling VirtualBox kernel module [ OK ] Starting VirtualBox kernel module [FAILED] (modprobe vboxdrv failed. Please use 'dmesg' to find out why) [root@qeynos ~]# dmesg vboxdrv: Unknown symbol RTStrPutCpInternal vboxdrv: Unknown symbol RTUtf16GetCpExInternal vboxdrv: Unknown symbol RTStrGetCpInternal vboxdrv: Unknown symbol RTStrGetCpExInternal vboxdrv: Unknown symbol RTStrGetCpNExInternal vboxdrv: Unknown symbol RTUtf16PutCpInternal vboxdrv: Unknown symbol RTUtf16GetCpInternal These functions have only their prototypes defined in string.h but no body anywhere on the sources. The same occurs with 3.2.4. Curiously, these functions are defined on the VBox OSE, on utf-8.cpp. Is there any solution for this? |
|||
| #7388 | fixed | Segfault when passing UTF8 character on VBoxManage controlvm option => Fixed in SVN | ||
| Description |
Minor argument parsing issue. While executing some operations on a stopped VM with my keyboard set to PT-BR on an Ubuntu host (generating dual-byte special characters), VBoxManage returned a segfault when receiving an option which was wrongly written with such character. Attached are:
I did not try to reproduce the event with other options than the used on the sample provided. It's not a show stopper but I hope this information can help VB team to improve the argument parsing to avoid something worst on another place. |
|||
| #7731 | fixed | Impossible to delete "last/single" snapshot => Fixed in SVN | ||
| Description |
While doing some tests for a backup procedure, I was "greeted" with the following message: # VBoxManage snapshot guest-vbox delete backup [...] 0%...FAILED Error: snapshot operation failed. Error message: Snapshot 'backup' of the machine 'guest-vbox' cannot be deleted while a VM is running, as this case is not implemented yet. You can delete the snapshot when the VM is powered off The snapshot was taken with the VM running. Then I tried simply to remove it and got the above message. After some testing, I discovered that the error ocurred only when trying to remove the "last" snapshot on a tree. I.e., after snapshot "backup", I created snapshot "backup2" and was able to remove "backup". However, when I tried to remove "backup2" I got the same error above, as "backup2" was now the "last" or "only" snapshot. Is there any workaround for this? I mean, beside "savestate-ing" the VM before the delete (all this exercise is to avoid losing access to the services provided by the VM). The VBoxLog does not register anything, so I'm not attaching it. Thanks for any help/suggestion. |
|||

