Hello.
Why OpenSUSE not have any Xen Virtualization option when setup? Why it just KVM?
It’s there, but maybe it isn’t on the DVD. After you have completed install, open Yast Software Manager and choose the “Patterns” view. You will see the option.
You’re just looking at patterns, and if I had my druthers the KVM pattern you identified should be hidden to avoid mistakes like what you would have made if you had found a Xen pattern.
In openSUSE,
The proper way to install Xen, KVM and LXC is to use the YaST Virtualization install module.
When you run the module, the patterns will be pulled in automatically, you’ll be given an option to choose any (or maybe more than one) of the three virtualization technologies, install the libvirt management tools, be given an option to allow br0 (enabling bridging networking to the physical network, and set you up with a standard, working configuration.
In other words, you’ll be off to a much better start than if you simply installed the necessary packages.
On the other hand, if you want to do things the hard way, then you can install only a pattern or click on the “details” button in your screenshot and find your Xen packages by either searching for the packages individually or viewing as package groups. And then, you might end up posting to this Forum asking about things that would have been set up automatically by YaST.
TSU
I downloaded the installation DVD.
It is a wrong movement from SUSE. Why its name is not “Xen Virtualization Host and Tools” ?
KVM is not a real hypervisor and it just a type-2 hypervisor. SUSE have discriminated and preferred a type-2 hypervisor or a type-1 hypervisor.
In other words, it mean that SUSE is not an independent open source company and is under Red Hat company control.
It is. I am currently looking at Yast Software Management, the Patterns view.
There’s a “XEN Virtualization Host and tools”
Below that, there’s a “KVM Virtualization Host and tools”.
They are both there.
The image that you posted shows what is available when only using the DVD. If you had enabled online repos during your install, you would have seen the line for XEN. The DVD has limited capacity, so they omitted the XEN stuff from what is on the DVD. You can install that later.
I repeat,
Do NOT
Do not try to install Xen the way you’re trying to do so.
Do not use Software Manager.
Even if you enable Online Repositories which might allow you to access a Xen pattern.
Do not install Xen during the initial installation when you can only use Software Manager (your screenshot) instead of using YaST “Install Hypervisor and Tools”
Do THIS
Install only your base system (can be any choice, ie regular install with Desktop, with only a Window Manager, a text-only “Server” or Transactional Server).
Then when you boot up your system the first time, open YaST and install your virtualization using the YaST module I described… NOT Software Manager.
openSUSE does not prefer any hypervisor type or even isolation (ie containers), all run equally well and are supported on openSUSE.
But you need to install using the procedure I described to be successful for <any> virtualization.
If you tried to install KVM or LXC as you described using Software Manager you would be just as wrong to do so as your attempt to install Xen that way.
Do not do things differently or you will likely have problems.
TSU
I’ll just add that this is very good advice. You might first need to install “yast2-vm”, so that the needed Yast module is there. But once that is there, it is best to install virtualization with that yast module.
Why not omitted KVM ? Why Xen?
Thus, Xen not have a good capacity for install during setup? If “yes” then why SUSE not change the name of “KVM Virtualization Host and tools” to something like “Virtualization Host and tools” and add a note about installing Xen hypervisor?
Are you sure SUSE is an independent company?!!!
Don’t ask me. I’m just a user. I don’t make policy.
It should be pointed out that except for Software Manager, YaST modules are not available during installation, the system has to be fully installed and then boot up to use YaST for everything else.
For very senior, very experienced virtualization administrators who might for some reason not want all the extra things openSUSE does for you, then installing just the pattern or even picking out specific packages might fit a particular setup.
For instance…Reasons for not following recommended procedure might include…
- As a demonstration of manliness and to prove love for the command line, I won’t need graphical tools to manage my virtualization.
- There are no mysteries about how networking and virtualization works, there’s no need for anything to be set up automatically, it’s can-do time!
- Who needs libvirt, I’m going to either use native commands or a different management system like Vagrant.
- I’m just trying to learn and there is nothing like the school of hard knocks.
The above reasons are tongue in cheek, but each could be a truly valid reason.
Bottom line…
Knowing that you should use YaST to install virtualization is not unique in the openSUSE world, there are at least a few other less documentated things that should be known… like the fact codecs are not installed as part of base installs. 15.1 actually includes some additional automatic features that had to be manually installed or configured before. In my presentation slide deck, I describe a number of notable features and enhancements in openSUSE 15.0/15.1 (I’ll post a link immediately below my “TSU” below, I recommend you take a look at it).
If you value the extra benefits of installing on openSUSE, then using YaST to install Xen, KVM or LXC delivers those benefits.
People can choose to install some other way, but unless you’re very experienced, you’ll likely have to overcome a number of common problems as if you’ve installed using some other distro.
TSU
openSUSE presentation slide deck
https://slides.com/tonysu/opensuse/#/
As I said, Why SUSE not added a text about Xen in that section or change that section name?
On Mon, 10 Jun 2019 21:46:03 +0000, hack3rcon wrote:
> Are you sure SUSE is an independent company?!!!
Yes. SUSE and RedHat are two different companies. Actually, RedHat was
just bought by IBM, and SUSE is owned by a VC firm outside the US.
Completely different companies - and the selection of hypervisor has
nothing to do with who owns them.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Mon, 10 Jun 2019 21:36:03 +0000, hack3rcon wrote:
> nrickert;2905148 Wrote:
>> It is. I am currently looking at Yast Software Management, the
>> Patterns view.
>>
>> There’s a “XEN Virtualization Host and tools”
>>
>> Below that, there’s a “KVM Virtualization Host and tools”.
>>
>> They are both there.
>>
>> The image that you posted shows what is available when only using the
>> DVD. If you had enabled online repos during your install, you would
>> have seen the line for XEN. The DVD has limited capacity, so they
>> omitted the XEN stuff from what is on the DVD. You can install that
>> later.
> Why not omitted KVM ? Why Xen?
It’s a project decision. SUSE probably had nothing to do with it.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I know that Red Hat is another company but SUSE using .rpm files and in the old version, the command to install applications was “yum”. Its mean that SUSE just built on Red Hat.
KVM owned by Red Hat and when a company claim that it is an independent company but use and put a popular tool from other company as a default hypervisor then it mean that it is not an independent company.
Look at the Adobe company. Why Adobe never product its applications for GNU/Linux? Because it is under the Microsoft company control.
SUSE not applying any policy on OpenSUSE project? Odd and funny!!!
If you don’t want to use a popular tool from another company, it is simple – DON’T USE LINUX.
That’s what open source is all about – using software from many other sources that was made available for others to use.
Also, don’t use Window – a lot of the Windows software is derived from open source software.
If you just want to gripe about SUSE and openSUSE, then take it to the soapbox forum.
Regarding SUSE/openSUSE use of the rpm package management system, I don’t see that as having any special significance. The other major package management system apt is also used by many different distros with varying relationships. Yum is an archaic tool (Even Fedora now uses its new tool dnf, Fedora users shouldn’t be using yum anymore), and almost everyone universally sings the praises of zypper over yum. And, I am always patiently frustrated going through all the steps necessary when using apt on Debian based systems.
I’ve never seen any relationship between a hypervisor and a specific distro although some companies have invested or contributed greatly to certain technologies. But, today the hypervisor commonly makes use of CPU extensions which mostly ties performance to the hardware and removes from software. Tinkering around the edges is possible through microcode updates, but the core hypervisor can’t be modified… much. And, that goes for both Type 1 and Type 2 hypervisors.
Your comment about Adobe and MSWindows is baseless. And only mostly true about Linux product versions. For example, there is a Linux version of Adobe Acrobat Reader. There are business reasons I won’t go into between Adobe and MS, but one does not own the other.
All of what I described above can be substantiated with simple Internet searches, and I recommend you do the same to correct other misunformation and guesses on your part. Considering how easy it is to do an Internet search today, there are few reasons to create conspiracy theories or guess at cause/effect. It’s good to notice something that catches your eye because a lot of people don’t even notice small things, but it’s a big failure to guess and not to do a quick search to satisfy your curiosity.
The longer you use openSUSE, you will come to appreciate how things “just work” if you follow recommendations and use YaST for practically everything you do to manage and configure your system(non-server applications typically cannot be managed by YaST). You’ll avoid all kinds of difficulties common to Linux that you’d have to deal with in other distros. You may not realize how well things work except in retrospect or try doing the same thing in another distro.
TSU
On Tue, 11 Jun 2019 21:26:03 +0000, hack3rcon wrote:
> SUSE not applying any policy on OpenSUSE project? Odd and funny!!!
Lots of SUSE developers work on the openSUSE project, but the openSUSE
Project is a community project, not a SUSE project. Same as Fedora is
the community project sponsored by RedHat.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C