Virtualbox on SuSeLinux 12.3 (latest)
Hi All, I have loaded Virtual Box under Gnome on a SuSe 12.3 64 bit system. On trying to add a VM, I get this error : Could not add the VM. This parameter must be a string or Unicode object. I have added myself to the vboxusers group. Are there any other gotchas? That I need to fix to get this to work? Andrew Greig
Andrew Greig <pushin.linux@gmail.com> wrote:
I have loaded Virtual Box under Gnome on a SuSe 12.3 64 bit system. On trying to add a VM, I get this error : Could not add the VM. This parameter must be a string or Unicode object.
I have added myself to the vboxusers group.
Are there any other gotchas? That I need to fix to get this to work?
Could you try it from the shell prompt? Apparently, the command line interface to VirtualBox is very comprehensive. (I haven't used it; my experience is with KVM/Qemu). This way at least you'll be directly providing the needed parameters.
On Sat, 2013-03-30 at 17:52 +1100, Jason White wrote:
Andrew Greig <pushin.linux@gmail.com> wrote:
I have loaded Virtual Box under Gnome on a SuSe 12.3 64 bit system. On trying to add a VM, I get this error : Could not add the VM. This parameter must be a string or Unicode object.
I have added myself to the vboxusers group.
Are there any other gotchas? That I need to fix to get this to work?
Could you try it from the shell prompt? Apparently, the command line interface to VirtualBox is very comprehensive. (I haven't used it; my experience is with KVM/Qemu).
This way at least you'll be directly providing the needed parameters.
Hi Jason, Thanks for that. I googled for CLI and found this article http://www.linux-mag.com/id/7673/ so I started and this is where I got to, andrewg@linux-wvs7:/usr/bin> /usr/bin/VBoxManage createvm --name Win7 Virtual machine 'Win7' is created. UUID: 8a0c7a74-ef03-49dc-b9eb-1e3ebeb8e512 Settings file: '/home/andrewg/VirtualBox VMs/Win7/Win7.vbox' andrewg@linux-wvs7:/usr/bin> /usr/bin/VBoxManage createhd --filename Win7.vdi --size 20000 --variant Fixed 0%... Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Failed to create hard disk VBoxManage: error: Could not create the medium storage unit '/usr/bin/Win7.vdi'. VBoxManage: error: VDI: cannot create image '/usr/bin/Win7.vdi' (VERR_ACCESS_DENIED) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium VBoxManage: error: Context: "int handleCreateHardDisk(HandlerArg*)" at line 382 of file VBoxManageDisk.cpp andrewg@linux-wvs7:/usr/bin> I understand why a user cannot create a file in /usr. What I don't understand is why vbox is trying to create the hd in /usr instead of in my home dir Thanks Andrew Greig
Andrew Greig <pushin.linux@gmail.com> wrote:
andrewg@linux-wvs7:/usr/bin> /usr/bin/VBoxManage createhd --filename Win7.vdi --size 20000 --variant Fixed 0%... Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Failed to create hard disk VBoxManage: error: Could not create the medium storage unit '/usr/bin/Win7.vdi'. VBoxManage: error: VDI: cannot create image '/usr/bin/Win7.vdi' (VERR_ACCESS_DENIED) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium VBoxManage: error: Context: "int handleCreateHardDisk(HandlerArg*)" at line 382 of file VBoxManageDisk.cpp andrewg@linux-wvs7:/usr/bin>
I understand why a user cannot create a file in /usr. What I don't understand is why vbox is trying to create the hd in /usr instead of in my home dir
The shell prompt (see quote above) suggests that /usr/bin was your current directory when you invoked the command, and it probably just tried to create the file in the current directory. Also, you shouldn't have to specify the path (/usr/bin) as part of the command if your $PATH variable is set correctly.
On Sun, 2013-03-31 at 10:17 +1100, Jason White wrote:
Andrew Greig <pushin.linux@gmail.com> wrote:
andrewg@linux-wvs7:/usr/bin> /usr/bin/VBoxManage createhd --filename Win7.vdi --size 20000 --variant Fixed 0%... Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Failed to create hard disk VBoxManage: error: Could not create the medium storage unit '/usr/bin/Win7.vdi'. VBoxManage: error: VDI: cannot create image '/usr/bin/Win7.vdi' (VERR_ACCESS_DENIED) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium VBoxManage: error: Context: "int handleCreateHardDisk(HandlerArg*)" at line 382 of file VBoxManageDisk.cpp andrewg@linux-wvs7:/usr/bin>
I understand why a user cannot create a file in /usr. What I don't understand is why vbox is trying to create the hd in /usr instead of in my home dir
The shell prompt (see quote above) suggests that /usr/bin was your current directory when you invoked the command, and it probably just tried to create the file in the current directory.
Also, you shouldn't have to specify the path (/usr/bin) as part of the command if your $PATH variable is set correctly.
Hi Jason, Thanks for that tip on invoking a command in a directory. I had success in an unusual way when I loaded the VirtualBox-qt version (although I run under Gnome) everything just worked, straight away. Damn odd really. VirtualBox-gtk was not a happy camper - go figure. Andrew Greig
Andrew Greig <pushin.linux@gmail.com> wrote:
I had success in an unusual way when I loaded the VirtualBox-qt version (although I run under Gnome) everything just worked, straight away. Damn odd really. VirtualBox-gtk was not a happy camper - go figure.
Debian appears to have only virtualbox-qt; I can't find a GTK package - I wonder whether it's unofficial or new. You should be able to run QT applications perfectly well under Gnome unless they're specifically designed for KDE.
participants (2)
-
Andrew Greig -
Jason White