Custom Query (16363 matches)
Results (583 - 585 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #597 | fixed | Cannot take a snapshot when there is a Writethrough hard disk attached | ||
| Description |
Trying to take a snapshot of a VM that has a disk in writethrough mode (even if you have other regular disks) causes the GUI to show an error: Cannot take a snapshot when there is a Writethrough hard disk attached ('/path/to/disk.vdi').
Result Code:
0x80004005
Component:
Machine
Interface:
IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}
Callee:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
This makes it hard to have a "system disk" that you want to snapshot and a "data disk" where you persist documents, settings and other stuff. The workaround today is to manually remove the disk from the VM using the settings window, take the snapshot, then re-add the disk. (And you must remember everytime you restore it). In VMWare, using the "persistent disk" that is the writethrough equivalent, the behaviour is to take the snapshot of regular disks and ignore the persistent ones. So, VBoxManage could have a similar behaviour, and maybe show a simple message like this when taking/restoring snapshots: The following disks are beign ignored because they are in writethrough mode: /path/to/disk1.vdi /path/to/disk2.vdi |
|||
| #598 | invalid | build failure on AMD64 (ubuntu 7.10) incompatable libgcc.a | ||
| Description |
Built this on Ubuntu Gutsy Gibbon Tribe 5 installed all the packages required in the install docs, but the linker fails on the video driver with kBuild: Linking vboxvideo_drv_70
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.1.3/libgcc.a when searching for -lgcc
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.1.3/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
collect2: ld returned 1 exit status
kmk[5]: *** [/home/jdhawk/build/source/vbox-ose-1.3.8/out/linux.amd64/release/obj/src/VBox/Additions/linux/xgraphics/vboxvideo_drv_70/vboxvideo_drv_70.so] Error 1
The failing command:
@gcc -m32 -shared -fPIC -s -o /home/jdhawk/build/source/vbox-ose-1.3.8/out/linux.amd64/release/obj/src/VBox/Additions/linux/xgraphics/vboxvideo_drv_70/vboxvideo_drv_70.so /home/jdhawk/build/source/vbox-ose-1.3.8/out/linux.amd64/release/obj/src/VBox/Additions/linux/xgraphics/vboxvideo_drv_70/vboxvideo.o /home/jdhawk/build/source/vbox-ose-1.3.8/out/linux.amd64/release/obj/src/VBox/Additions/linux/xgraphics/vboxvideo_drv_70/vboxutils.o -Wl,-Map -Wl,/home/jdhawk/build/source/vbox-ose-1.3.8/out/linux.amd64/release/obj/src/VBox/Additions/linux/xgraphics/vboxvideo_drv_70/vboxvideo_drv_70.map -Wl,--cref
kmk[5]: Leaving directory `/home/jdhawk/build/source/vbox-ose-1.3.8/src/VBox/Additions/linux/xgraphics'
kmk[4]: *** [pass_dlls_before] Error 2
Kernel Info: Linux cheetos 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux GCC/G++ Info: jdhawk@cheetos:~/build/source$ g++ -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.3 20070825 (prerelease) (Ubuntu 4.1.2-15ubuntu3) |
|||
| #599 | fixed | VirtualBox 1.5 - keyboard issues with Linux hosts => try again with VirtualBox 2.0.0 | ||
| Description |
I'm Brazilian and have an ABNT2 keyboard. Everything was fine with 1.4.0, but after the upgrade to 1.5.0, the slash/question mark key stopped working. I use Ubuntu 7.04 host and tried Ubuntu and Windows XP guests. Both have the same problem, even after updating the guest additions. I saw that this happened sometime ago but was fixed: http://www.virtualbox.org/ticket/205 Also, I know that VMWare allow to remap keys in the config files. This could also be a way to solve this. |
|||

