My setup: OpenSuSE 12.3 x86_64 KDE and Others all latest upgrades.
I was testing a remote RDP connection on my lan to VirtualBox (VB) VM guests installed on a the above mentioned host and … it did not work.
VB version was 4.2 something …
I made an upgrade to the version OpenSuSE has on the repos … no luck. The update destroyed the previously working version.
Also I usually don’t install from the repos as it is always a problem on my late installs.
after the prompt starts yast install one has to go to the cli and make the usual /etc/init.d vboxdrv setup
and … still no luck … RDP did not work.
I made some web searches and finally found one that mentioned it was because it VB alone does not allow for RDP to work … one need to install the VirtualBox Extension Pack !!
On Thu, 13 Feb 2014 16:26:06 +0000, keyb user wrote:
> I was testing a remote RDP connection on my lan to VirtualBox (VB) VM
> guests installed on a the above mentioned host and … it did not work.
Did you open the port in the firewall? Or are you tunnelling over ssh?
> VB version was 4.2 something …
>
> I made an upgrade to the version OpenSuSE has on the repos … no luck.
> The update destroyed the previously working version.
> Also I usually don’t install from the repos as it is always a problem on
> my late installs.
Install from the Virtualization repository, that version works, and is
recommended.
Obviously the Firewall was all ok … the problem was the VirtualBox Extension Pack, it must be installed.
Also remember folks … the IP to connect on the KRDP client is the HOST IP, Not the VM guest. … in order to have multiple rdp sessions each VM must define a different rdp port.
Install from the Virtualization repository, that version works, and is
recommended.
The Virtualization repo updates always Kill my VB installs … and this time it was not different. I only use now the official Oracle version that works very very good.
On Thu, 13 Feb 2014 19:16:01 +0000, keyb user wrote:
> Hi Hendersj,
>
> hendersj;2624527 Wrote:
>> On Thu, 13 Feb 2014 16:26:06 +0000, keyb user wrote:
>>
>> Did you open the port in the firewall? Or are you tunnelling over ssh?
>>
>>
>>
> Obviously the Firewall was all ok … the problem was the VirtualBox
> Extension Pack, it must be installed.
> Also remember folks … the IP to connect on the KRDP client is the HOST
> IP, Not the VM guest. … in order to have multiple rdp sessions each
> VM must define a different rdp port.
Ah, yes, I always forget the extension package provides this as well - I
install it for USB 2.0 support.
>> Install from the Virtualization repository, that version works, and is
>> recommended.
> The Virtualization repo updates always Kill my VB installs … and this
> time it was not different. I only use now the official Oracle version
> that works very very good.
That’s very strange, it works wonderfully here on 13.1. There’s a
specific repo for virtualization that’s not the standard OSS repo (which
is the one that broke for me). It might be useful to ask about the
breaking you see (or get bugs entered) so it can be dealt with.
The reason to use the repo vs. the Oracle builds is that you’ll get
updates in the update channel when they’re released. The Oracle install
will work well, but you won’t get any automatic updates.
The reason to use the repo vs. the Oracle builds is that you’ll get
updates in the update channel when they’re released. The Oracle install
will work well, but you won’t get any automatic updates.
I have the repos installed, all of them, the VIrtualization (Virtualbox) repo is installed.
I did not take note this time of the exact bug and error message and right now I have no time to sort it otherwise I would have get back at it and send you all the info necessary. But the previous times the bug was always the same, and the error was related with wrong VirtualBox (VB) Kernel modules. Some of my threads on this fora for sure have this issue on previous OS versions.
Meaning once starting a VM the same error message would show up saying one must make a new /etc/init.d/vboxdrv setup, that is compile the VB Kernel modules.
The problem is the installed modules simply don’t compile correctly.
They always give errors.
I suspect, and I can be wrong on this one, this is due to mismatch between the Compiled version on the VB repos and the OS Kernel. This happened after Kernel up-dates …
At least this happened to me before.
About the VB updates … I will try to sort the repos version later on , I really simply must deal with this install right now.
But this problem did already occurred to me before, its recurrent …
I’m using VirtualBox from the Virtualization repo as well (for years now), and had absolutely no problem after the kernel update (or ever before).
The packages in the Virtualization repo are actually built against the update repo, so whenever a kernel update is released, the KMP packages in the repo are available for the new kernel automatically.
You have to install the updated packages of course, with the updater applet, YaST->Software Management, or “zypper up”. (YaST->Online Updates and “zypper patch” WILL NOT work, as those packages are not part of the update repo)
And you must have enabled the repo and set Auto-Refresh to yes, otherwise the updated packages will not be seen.
That’s good to know, but I think I’ll stick with the openSUSE
Virtualization repo - since it comes from the build service, there’s less
of a chance of compatibility problems, it would seem.
where “$version” is the suse version ie 13.1 , now one thing to remember that vbox.org repo does not coincide with the suse version/release so for example the 12.3 version of vbox should work for 13.1 after you have added that repo you can search for using zypper: zypper se virtualbox | grep -i oracle ;)[/FONT]
