It’s my first post here in OpenSUSE forum. I’ve been testing OpenSUSE Leap for a time in VirtualBox (I intend to install OpenSUSE in my machine) but I guess OpenSUSE Tumbleweed is best for me.
I’ve tried a lot of times install OT in Virtualbox and I just can’t. I just updated my VirtualBox and the installer stop in the middle of installation process leading me to a terminal page with options to install.
Well, I don’t know if anyone here has experienced it or may have a clue.
Information:
VirtualBox 5.1.16 r113841 (Qt5.5.1)
Host SO: Ubuntu 16.04
Kernel: Linux MalibU 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
That’s not the first time I tried to install it, I’ve tried months ago but I gave up so I tried LEAP, but I really want to use OpenSUSE Tumbleweed.
Hi and welcome to the openSUSE Forums! Glad to see that you plan on using openSUSE (Leap or Tumbleweed).
To help you, the volunteers here may need further details about the errors you encounter.
To test out Tumbleweed you don’t really need to install it on VirtualBox: just use one of the LiveDVD versions available that should have no problems booting in a recent VirtualBox.
If you really want to check the installer, please note that currently the installer included in the Live versions is a network installer, i.e. it downloads everything from the repositories, so you must have a working net access in VirtualBox.
If you tried the full Install DVD, please tell us and tell what do you mean by “the middle of installation process” and what terminal with what options you see.
Please be aware that the VirtualBox default for openSUSE installs is a 8GB disk, of which more that 1GB is then devoted to swap, while if you accept the openSUSE default install options (i.e. BTRFS filesystem and a full desktop environment) you need some 40GB of disk space for the install to complete.
A basic test install with EXT4 filesystem and no separate /home should be possible within the 8GB disk size of the default setup though.
If the errors you see are related to your (*buntu) host, maybe this is not the best place to get help…
I was trying to install it using just 25GB disk, but I tried using 41GB and I finally got it to work. There were two errors during instalation (kipi-pluggin and LibreOffice) but I just clicked “ignore” button and I now have my OT installed.
About qemu/kvm, I don’t know how it works. I heard that somebody who uses VirtualBox shouldn’t use Tumbleweed due to constante kernel upgrades.
Well, now my problem is solved, I guess I’ll have to read more and test OT to know how it works.
Tumbleweed is not recommended as a HOST for VirtualBox, but in general using it as a guest is OK; when a bleeding edge kernel becomes available maybe you have to wait for a VirtualBox update, but keeping the former kernel installed allows booting in the meantime.
Nice to know you are up and running now.
We don’t use that practice here, your statement says it all.
On 03/10/2017 04:36 PM, OrsoBruno wrote:
>
> Sorg;2815764 Wrote:
>> I heard that somebody who uses VirtualBox shouldn’t use Tumbleweed due
>> to constante kernel upgrades.
>>
>> Well, now my problem is solved, I guess I’ll have to read more and test
>> OT to know how it works.
>
> Tumbleweed is not recommended as a HOST for VirtualBox,
Not recommended by whom? I have been running VBoz on TW for years with
little to no problem. I need only run “/sbin/rcvboxdrv setup” when I do
have a problem.
> but in general
> using it as a guest is OK; when a bleeding edge kernel becomes available
> maybe you have to wait for a VirtualBox update,
I’ve not had that experience.
> but keeping the former
> kernel installed allows booting in the meantime.
> Nice to know you are up and running now.
>
> Sorg;2815764 Wrote:
>>
>> Edit: How do I make this thread as a solved one?
>
> We don’t use that practice here, your statement says it all.
>
>
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
> Tumbleweed is not recommended as a HOST for VirtualBox
**OrsoBruno] **do you have evidence or reasoning to support this claim? I have been using the default vbox for 6 months on TW host without the slightest issue, why would updating the kernel have anything to do with it?
“Not recommended” does not mean that you cannot do that and experience no hiccups in 6 months, or be prepared to rebuild modules or tweak configs or wait a week or so for an update to VBox and/or the Extension Packs.
The reasoning is simple.
Tumbleweed uses (almost) a bleeding edge kernel.
VBox needs to build kernel modules (or install KMPs) on the host to work.
KMPs are usually published with a slight delay compared to major kernel updates (maybe a day, maybe a few weeks).
Building kernel modules yourself occasionally breaks after a major kernel update; I saw this with kernel 4.5 IIRC.
If that happens, you have to (wait and) install an update to VBox: 5.1.16 apparently has been patched to build up to kernel 4.11, but the (current on openSUSE) 5.1.14 might have problems running on TW when kernel 4.11 will show up.
With a newer VBox comes a new Extension Pack, needed by guests to enable optional features (shared folders, USB3, video features).
With a newer VBox you might need to install the newer Extension Pack to the guest OSs and rebuild guest kernel modules for best performance.
If you just have a couple of Virtual Machines running on your desktop and can occasionally tolerate downtime, TW as a host may be OK, the choice is up to you.
If you have dozens of VMs in a production environment needing 24/7 operation, TW as a host is not recommended, since it is better to choose when (and if) to update the whole setup during planned downtime rather than being forced to do so just because TW got a newer kernel.
That said, I am not going to start a flame war about it. Take it as personal opinion if you prefer so.
On 03/11/2017 01:46 PM, OrsoBruno wrote:
>
> ndc33;2815888 Wrote:
>>> Tumbleweed is not recommended as a HOST for VirtualBox
>> *‘OrsoBruno’ (https://forums.opensuse.org/member.php/87885-OrsoBruno)]
>> *do you have evidence or reasoning to support this claim? I have been
>> using the default vbox for 6 months on TW host without the slightest
>> issue, why would updating the kernel have anything to do with it?
>
> “Not recommended” does not mean that you cannot do that and experience
> no hiccups in 6 months, or be prepared to rebuild modules or tweak
> configs or wait a week or so for an update to VBox and/or the Extension
> Packs.
> The reasoning is simple.
> - Tumbleweed uses (almost) a bleeding edge kernel.
> - VBox needs to build kernel modules (or install KMPs) on the host to
> work.
> - KMPs are usually published with a slight delay compared to major
> kernel updates (maybe a day, maybe a few weeks).
> - Building kernel modules yourself occasionally breaks after a major
> kernel update; I saw this with kernel 4.5 IIRC.
> - If that happens, you have to (wait and) install an update to VBox:
> 5.1.16 apparently has been patched to build up to kernel 4.11, but the
> (current on openSUSE) 5.1.14 might have problems running on TW when
> kernel 4.11 will show up.
> - With a newer VBox comes a new Extension Pack, needed by guests to
> enable optional features (shared folders, USB3, video features).
> - With a newer VBox you might need to install the newer Extension Pack
> to the guest OSs and rebuild guest kernel modules for best performance.
>
> If you just have a couple of Virtual Machines running on your desktop
> and can occasionally tolerate downtime, TW as a host may be OK, the
> choice is up to you.
> If you have dozens of VMs in a production environment needing 24/7
> operation, -TW as a host is not recommended-, since it is better to
> choose when (and if) to update the whole setup during planned downtime
> rather than being forced to do so just because TW got a newer kernel.
>
> That said, I am not going to start a flame war about it. Take it as
> personal opinion if you prefer so.
>
>
Thank you for clearing that up. Yes, it is mere personal opinion with no
actual facts to back up the “could/might” claim. As I stated, I have
been using TW for years and always use the “Oracle” provided RPM’s and
never have downtime other then the few minutes it takes to rebuild the
drivers and install the extensions. I’m currently running on the latest
version of TW with Vbox 5.1.16 without issue.
If an admin running is business critical software on TW he needs/
deserves to be fired.
Don’t ever be afraid to express your opinion here, just expect it to
always be accepted as fact.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
On 03/12/2017 01:08 PM, Ken Schneider wrote:
> On 03/11/2017 01:46 PM, OrsoBruno wrote:
>>
>> ndc33;2815888 Wrote:
>>>> Tumbleweed is not recommended as a HOST for VirtualBox
>>> *‘OrsoBruno’ (https://forums.opensuse.org/member.php/87885-OrsoBruno)]
>>> *do you have evidence or reasoning to support this claim? I have been
>>> using the default vbox for 6 months on TW host without the slightest
>>> issue, why would updating the kernel have anything to do with it?
>>
>> “Not recommended” does not mean that you cannot do that and experience
>> no hiccups in 6 months, or be prepared to rebuild modules or tweak
>> configs or wait a week or so for an update to VBox and/or the Extension
>> Packs.
>> The reasoning is simple.
>> - Tumbleweed uses (almost) a bleeding edge kernel.
>> - VBox needs to build kernel modules (or install KMPs) on the host to
>> work.
>> - KMPs are usually published with a slight delay compared to major
>> kernel updates (maybe a day, maybe a few weeks).
>> - Building kernel modules yourself occasionally breaks after a major
>> kernel update; I saw this with kernel 4.5 IIRC.
>> - If that happens, you have to (wait and) install an update to VBox:
>> 5.1.16 apparently has been patched to build up to kernel 4.11, but the
>> (current on openSUSE) 5.1.14 might have problems running on TW when
>> kernel 4.11 will show up.
>> - With a newer VBox comes a new Extension Pack, needed by guests to
>> enable optional features (shared folders, USB3, video features).
>> - With a newer VBox you might need to install the newer Extension Pack
>> to the guest OSs and rebuild guest kernel modules for best performance.
>>
>> If you just have a couple of Virtual Machines running on your desktop
>> and can occasionally tolerate downtime, TW as a host may be OK, the
>> choice is up to you.
>> If you have dozens of VMs in a production environment needing 24/7
>> operation, -TW as a host is not recommended-, since it is better to
>> choose when (and if) to update the whole setup during planned downtime
>> rather than being forced to do so just because TW got a newer kernel.
>>
>> That said, I am not going to start a flame war about it. Take it as
>> personal opinion if you prefer so.
>>
>>
>
> Thank you for clearing that up. Yes, it is mere personal opinion with no
> actual facts to back up the “could/might” claim. As I stated, I have
> been using TW for years and always use the “Oracle” provided RPM’s and
> never have downtime other then the few minutes it takes to rebuild the
> drivers and install the extensions. I’m currently running on the latest
> version of TW with Vbox 5.1.16 without issue.
>
Fixing/correcting the following:
If an admin is running business critical software for a company on TW he
needs/
deserves to be fired.
Don’t ever be afraid to express your opinion here, just don’t expect it to
be accepted as fact.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
not running TW on a high availability, professional basis (and not expecting other TW users to) i can say from using the default vbox provided by TW repos that - there is no messing with kernel modules, that the repo tracks upstream reasonably closely and that i have never had a single problem.
Who should use openSUSE Leap instead of Tumbleweed?
While every effort is made to build them, at this point there is no guarantee to have all additional modules available in openSUSE Leap like for example, Vmware or Virtualbox. And while the Packman Tumbleweed Essential repository attempts to deliver them there is no guarantee they will always succeed due to the incompatibilities with the quickly advancing Linux Kernel.