There’s a problem with the VBox from the Oracle repo.
#### YaST2 conflicts list - generated 2014-12-05 06:20:59 ####
nothing provides libdevmapper.so.1.02()(64bit) needed by VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
] do not install VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
] break VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64 by ignoring some of its dependencies
#### YaST2 conflicts list END ###
You could try to “break VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64 by ignoring some of its dependencies”. You might have to create a symlink from /lib64/libdevmapper.so.1.02 to /lib64/libdevmapper.so.1.03 though (which is actually 1.02.90 at the moment…).
Or just install the virtualbox packages included in Tumbleweed instead.
On Thu, 04 Dec 2014 20:36:02 +0000, swerdna wrote:
> Hi
>
> There’s a problem with the VBox from the Oracle repo.
>
>
> Code:
> --------------------
> #### YaST2 conflicts list - generated 2014-12-05 06:20:59 ####
>
> nothing provides libdevmapper.so.1.02()(64bit) needed by
> VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
>
> ] do not install VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
>
> ] break VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64 by ignoring
> some of its dependencies
>
>
> #### YaST2 conflicts list END ###
> --------------------
>
>
> Any thoughts how to resolve this?
Install from the Virtualization repo instead - I’ve been using that for
years, and have never had a problem with it.
DKMS is not needed in this case and not even used. Those packages contain the kernel module in pre-compiled, binary, form.
And IMHO there’s no need to add that repo on Tumbleweed at all for virtualbox alone. The virtualbox packages in there are submitted to Tumbleweed anyway (you’ll get updates a bit later though, after the openQA testing), the exact same packages are included in Tumbleweed.
On 12/04/2014 04:35 PM, Jim Henderson wrote:
> On Thu, 04 Dec 2014 20:36:02 +0000, swerdna wrote:
>
>> Hi
>>
>> There’s a problem with the VBox from the Oracle repo.
>>
>>
>> Code:
>> --------------------
>> #### YaST2 conflicts list - generated 2014-12-05 06:20:59 ####
>>
>> nothing provides libdevmapper.so.1.02()(64bit) needed by
>> VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
>>
>> ] do not install VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
>>
>> ] break VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64 by ignoring
>> some of its dependencies
>>
>>
>> #### YaST2 conflicts list END ###
>> --------------------
>>
>>
>> Any thoughts how to resolve this?
>
> Install from the Virtualization repo instead - I’ve been using that for
> years, and have never had a problem with it.
>
> Jim
>
>
>
On 12/05/2014 08:26 AM, wolfi323 wrote:
>
> swerdna;2680824 Wrote:
>> I replaced this repo: >
> Code:
> --------------------
> > > http://download.virtualbox.org/virtualbox/rpm/opensuse/12.3/
> --------------------
>>>
>>
>>
>> With this repo:>
> Code:
> --------------------
> > > http://download.opensuse.org/repositories/Virtualization:/VirtualBox_Tumbleweed/openSUSE_Tumbleweed/
> --------------------
>>>
>>
>> and added DKMS – And problem solved.
>>
> DKMS is not needed in this case and not even used. Those packages
> contain the kernel module in pre-compiled, binary, form.
>
> And IMHO there’s no need to add that repo on Tumbleweed at all for
> virtualbox alone. The virtualbox packages in there are submitted to
> Tumbleweed anyway (you’ll get updates a bit later though, after the
> openQA testing), the exact same packages are included in Tumbleweed.
>
>
But USB pass-through is disabled by default for security reasons, you have to enable it first by copying /usr/lib/udev/rules.d/60-vboxdrv.rules to /etc/udev/rules.d/ and uncommenting some lines as instructed in the file.
And automatically mounting of shared folders doesn’t seem to work either according to some posts here in the forums (nobody filed a bug report about that yet though), but mounting via “mount” or /etc/fstab should work fine at least.
Well we can take that as a “No” then, since most “normal” users would expect those features to work “out of the box” without further fiddling about. lol!
I got a message to install DKMS when I ran the VM Control Panel. Must be a feature of the CP that doesn’t know about the openSUSE versioning. Or maybe I ended up with a blend of softwares. Anyway, it’s working fine.
I made these adjustments for usb. I have a windows 7 VM within my TW system. I tried three different USB storage drives. All were recognised and attached but could not be initialised with drivers by windows auto-driver process (guest additions have been installed).
Now, after some investigating, I get this preventing me from starting the VM:
Failed to open a session for the virtual machine Win7Ult.
Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings (VERR_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
So I downloaded from Oracle Vbox site, the 4.3.18 extension pack to match the virtualbox release 4.3.18. When I go to install it, as usual I just click it, I get something like this: no device installed to open file of this type. It’s a compressed file and I can drag out the contents but that doesn’t help.
open Virtualbox Main Menue, go to the Tab File----Global Settings-----additional Packages and than install your Extensions-Pack by clicking on the Triangle on the right Side.
Im here in German, it might be other Names in Englisch…