Custom Query (16363 matches)
Results (2536 - 2538 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2594 | fixed | vboxmanage: make it easier to work with VDI files from different locations than ~/.VirtualBox/VDI | ||
| Description |
I have a local direcotry for VirtualBox images as I don't want to store them via NFS. Now when I want to clone an image I get this: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi Debian-Etch-Template.vdi Debian-Etch-grsec.vdi
VirtualBox Command Line Management Interface Version 1.6.6_OSE
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.
[!] FAILED calling virtualBox->OpenVirtualDiskImage(Bstr(argv[0]), vdi.asOutParam()) at line 3307!
[!] Primary RC = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Full error info present: true , basic error info present: true
[!] Result Code = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Text = Could not access hard disk image '/home/ms/.VirtualBox/VDI/Debian-Etch-Template.vdi' (VERR_FILE_NOT_FOUND)
[!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
I can do: ms@mango:~/lokal/VirtualBox-Images> ln -s /home_lokal/ms/VirtualBox-Images/Debian-Etch-Template.vdi /home/ms/.VirtualBox/Debian-Etch-Template.vdi And then: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-grsec.vdi ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-rsbac.vdi But now vboxmanage creates the images in ~/.VirtualBox/VDI. Thus I have to move them around again: ms@mango:~/lokal/VirtualBox-Images> mv ~/.VirtualBox/VDI/Debian-Etch-{grsec,rsbac}.vdi .
Thus all I ask is that vboxmanage respects the path I give instead of insisting on ~/.VirtualBox/VDI. I know I could symlink VDI completely, but I want to have the option to keep some images via NFS. I tested with VirtualBox 1.6.6 as thats the latest OSE edition I can get via backports.org for Debian Etch. I can try with a newer one in case its needed. The issue is minor, but rather annoying. |
|||
| #2595 | obsolete | Problems with custom keyboard layout Neo 2.0 and Virtualbox 2.0.4 -> fixed post-3.2 | ||
| Description |
I'm using the Neo 2.0 keyboard layout, which can be found at http://www.neo-layout.org When one uses setxkbmap to set the layout to neo (ie setxkbmap de neo, after installing the new xkbmap file) and starts a virtual machine (for example running Windows or Linux, doesn't really matter which guest), several keys don't work, for example the number keys 2, 4, 5 etc. If one starts Vbox with the layout set to QWERTZ (standard german layout), and then changes the layout while Vbox is running, most of the keys work, except for the modifier keys M3 und M4, which still represent their "old" functionality, like Caps-Lock or "< >". I've seen some tickets about other custom keyboard layouts, but most of them don't have those major changes that Neo has, with the modifier keys. |
|||
| #2596 | fixed | virtualbox-ose-2.0.4: host system (gentoo linux) becomes unresponsive on certain vbox operations | ||
| Description |
on certain operations of vbox, such as (formatting, or copying some big files) the host system becomes unresponsive -- due to high load of io operations? -- and has to be rebooted (hard). |
|||

