Linux OS advice for building a SAM-SD
-
@magicmarker said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@stacksofplates The way you are describing it, makes it feel more like a Type 2 Hypervisor.
It what sense?
Installing the Linux Server OS with a desktop, then adding the KVM package. It reminds of installing Windows Server OS, and then adding the Hypervisor role. Maybe I'm making this harder on myself. I was doing a Fedora minimal install (no pretty GUI) and installing the KVM packages via the cli to keep the overhead to a minimum. If I were to install Fedora with a desktop package like Gnome I would probably have an easier time working with KVM.
You don't need a desktop unless it's on a workstation. Literally during the install instead of picking minimal pick hypervisor role. It's done, that's it. Then just use Virt-Manager to control it.
-
@kelly said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
That's one theory. I don't believe that CentOS is more stable. I've not seen that. Stability is certainly of concern, but does being "old" really constitute more stability? I think that it used to, long ago when technology was quite different, but I'm not convinced that it does today. CentOS is stable in terms of "package versions", but that's not the same as stable. Fedora gets more updates, more advances, more security, more quickly than CentOS does. All things that you want in your hypervisor.
I was using stability in the context of release cycles, not functionality. On the face of it, I would think you'd want to be running on something less likely to make significant changes. That is my inclination personally. Seeing people post about release changes on Fedora leaves me mistrustful of my ability to rely on it for a subsystem like a VM host.
I saw the same thing about @scottalanmiller as he changes his tune on a solution every month or so. Look at the life of ML and the topic about the different Hypervisors. It was "omg XS is the only reasonable tool" then it went to Scale, and then to Hyper-V and then to KVM.
Stability is based around the support you get, investing in a platform needs to be carefully considered and not abandoned just because something else has a good feature.
-
@stacksofplates said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@stacksofplates The way you are describing it, makes it feel more like a Type 2 Hypervisor. I was attempting to install Fedora as a minimal install and add the KVM role through the cli. I then was able to successfully launch Virt-Manager from a Windows box using Xming and Putty. I was having trouble on the Linux admin side understanding how to add a volumes for VM data storage and how to properly setup the networking within the Virt-Manager which is not documented well. My host has multiple nic's and I'm used to setting up a Virtual Switch.
it's all type 1, there is no type 2 for KVM. Default volume for guests is /var/lib/libvirt/images. You can literally just create a directory and use that as a volume. There is nothing special for ISOs or guest images at all. For multiple NICs you can just pick which one it should be using. So VM1 can use macvtap on em2 and VM2 can use macvtap on em3 (or whatever the NIC is called on your system).
Also Qemu/KVM User session default volume is /home/username/.local/share/libvirt/images
-
@stacksofplates said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@stacksofplates The way you are describing it, makes it feel more like a Type 2 Hypervisor.
It what sense?
Installing the Linux Server OS with a desktop, then adding the KVM package. It reminds of installing Windows Server OS, and then adding the Hypervisor role. Maybe I'm making this harder on myself. I was doing a Fedora minimal install (no pretty GUI) and installing the KVM packages via the cli to keep the overhead to a minimum. If I were to install Fedora with a desktop package like Gnome I would probably have an easier time working with KVM.
You don't need a desktop unless it's on a workstation. Literally during the install instead of picking minimal pick hypervisor role. It's done, that's it. Then just use Virt-Manager to control it.
I don't remember that being an option with Fedora. That sounds like a good deal. What distro gives you that option?
-
@magicmarker said in Linux OS advice for building a SAM-SD:
@stacksofplates said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@stacksofplates The way you are describing it, makes it feel more like a Type 2 Hypervisor.
It what sense?
Installing the Linux Server OS with a desktop, then adding the KVM package. It reminds of installing Windows Server OS, and then adding the Hypervisor role. Maybe I'm making this harder on myself. I was doing a Fedora minimal install (no pretty GUI) and installing the KVM packages via the cli to keep the overhead to a minimum. If I were to install Fedora with a desktop package like Gnome I would probably have an easier time working with KVM.
You don't need a desktop unless it's on a workstation. Literally during the install instead of picking minimal pick hypervisor role. It's done, that's it. Then just use Virt-Manager to control it.
I don't remember that being an option with Fedora. That sounds like a good deal. What distro gives you that option?
It's on CentOS but I was pretty sure Fedora had it also. I'm running CentOS hosts. Only Fedora hosts I have are workstations and it's set up by default on Fedora WS.
-
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
Minimal installs improves stability anyway.
-
@kelly said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
That's one theory. I don't believe that CentOS is more stable. I've not seen that. Stability is certainly of concern, but does being "old" really constitute more stability? I think that it used to, long ago when technology was quite different, but I'm not convinced that it does today. CentOS is stable in terms of "package versions", but that's not the same as stable. Fedora gets more updates, more advances, more security, more quickly than CentOS does. All things that you want in your hypervisor.
I was using stability in the context of release cycles, not functionality. On the face of it, I would think you'd want to be running on something less likely to make significant changes. That is my inclination personally. Seeing people post about release changes on Fedora leaves me mistrustful of my ability to rely on it for a subsystem like a VM host.
I agree, if those changes affect things like the core system. And Fedora has been through some of those changes, but only as a precursor to them happening on CentOS, at least in theory. So while there is potential for more change on Fedora, in reality there is normally just "earlier change" on it. Exceptions will happen, but they are not common. Most of what people talk about is desktop apps and really high level things, not the core OS or hypervisor environments.
-
@scottalanmiller said in Linux OS advice for building a SAM-SD:
Fedora has a better upgrade path as well. Moving from CentOS X to CentOS Y tends to be high risk and relatively painful. Moving from Fedora X to Fedora Y happens many times more often, but tends to be painless and trivial.
That is now changed as starting with CentOS 7 they have added the Fedora style release upgrades as a native function of the OS. Granted we have not seen it happen yet because there is not CentOS 8 yet, but it is designed to do it now.
Also, the CentOS 7 to CentOS 8 will be a larger upgrade than a say Fedora 25 to Fedora 26, but no less intrusive.
-
@kelly said in Linux OS advice for building a SAM-SD:
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
That's one theory. I don't believe that CentOS is more stable. I've not seen that. Stability is certainly of concern, but does being "old" really constitute more stability? I think that it used to, long ago when technology was quite different, but I'm not convinced that it does today. CentOS is stable in terms of "package versions", but that's not the same as stable. Fedora gets more updates, more advances, more security, more quickly than CentOS does. All things that you want in your hypervisor.
I was using stability in the context of release cycles, not functionality. On the face of it, I would think you'd want to be running on something less likely to make significant changes. That is my inclination personally. Seeing people post about release changes on Fedora leaves me mistrustful of my ability to rely on it for a subsystem like a VM host.
Prior to modern, commodity virtualization, I was firmly in the CentOS over Fedora camp.
But now, I don't care because I can snapshot and upgrade then roll back if needed.
When it comes to the hypervisor itself, it is similar. Backup or migrate the guests, then upgrade the host. If it fails, reinstall the host and restore the guests or move them back.
Though honestly, if you have enough capacity to migrate all the hosts, I would jsut nuke it and reinstall for a larger organization. I would upgrade for a smaller one that likely cannot easily reapply permissions, etc.
-
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
After using a lot of different distros, I'm totally hooked on Fedora. Everything about it, to me, makes the most logical sense. It flows the nicest, and imo manages the best.
-
@tim_g said in Linux OS advice for building a SAM-SD:
@kelly said in Linux OS advice for building a SAM-SD:
Why the preference of Fedora over CentOS. It seems like you'd want the more stable release cycle for your dom0.
After using a lot of different distros, I'm totally hooked on Fedora. Everything about it, to me, makes the most logical sense. It flows the nicest, and imo manages the best.
I really like Fedora all around. Especially on servers.
-
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox as the nice GUI wrapper to the Linux KVM hypervisor. For the Linux newbies, and the Windows admins out there getting into Linux, this seems to be a great way to use the KVM hypervisor. Why can't Proxmox be an option for the SAM-SD Hypervisor that runs the Linux VM file server.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox...
We get asked this all the time.
- It's just a GUI on top of KVM and Open-VZ (and now LXC). It's weird and complex and while a GUI is nice, we have GUIs already that work great and don't require completely third party packages.
- The ProxMox company are scammers and rotten people. You don't want to deal with them. This isn't a nice project.
- @StorageNinja can tell you, they actually run a full on spam marketing organization. They are deleted constantly with fake accounts on SW. We've been dealing with them spamming constantly for about five years.
- It's attempting to solve a problem we don't have.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
Why can't Proxmox be an option for the SAM-SD Hypervisor that runs the Linux VM file server.
It can be, but professionally I can't be associated with a company like that. It's not an ethical company, so I won't deal with them in any capacity.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox as the nice GUI wrapper to the Linux KVM hypervisor. For the Linux newbies, and the Windows admins out there getting into Linux, this seems to be a great way to use the KVM hypervisor. Why can't Proxmox be an option for the SAM-SD Hypervisor that runs the Linux VM file server.
#1 It's only a wrapper. You're giving up a lot of control for the convenience.
#2 The Proxmox devs and company obviously don't know a thing about being a sysadmin on UNIX type operating systems. Seriously, removing the mdadm module is the silliest thing I've ever heard anyone doing. Thankfully they can't remove md, as it's a piece of the kernel. Do you really want to trust your environment to a company like that? -
@travisdh1 said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox as the nice GUI wrapper to the Linux KVM hypervisor. For the Linux newbies, and the Windows admins out there getting into Linux, this seems to be a great way to use the KVM hypervisor. Why can't Proxmox be an option for the SAM-SD Hypervisor that runs the Linux VM file server.
#1 It's only a wrapper. You're giving up a lot of control for the convenience.
#2 The Proxmox devs and company obviously don't know a thing about being a sysadmin on UNIX type operating systems. Seriously, removing the mdadm module is the silliest thing I've ever heard anyone doing. Thankfully they can't remove md, as it's a piece of the kernel. Do you really want to trust your environment to a company like that?They remove WHAT?? Are you joking? I wasn't aware of that. My last experience with Proxomox was 5-6 years ago.
-
@francesco-provino said in Linux OS advice for building a SAM-SD:
@travisdh1 said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox as the nice GUI wrapper to the Linux KVM hypervisor. For the Linux newbies, and the Windows admins out there getting into Linux, this seems to be a great way to use the KVM hypervisor. Why can't Proxmox be an option for the SAM-SD Hypervisor that runs the Linux VM file server.
#1 It's only a wrapper. You're giving up a lot of control for the convenience.
#2 The Proxmox devs and company obviously don't know a thing about being a sysadmin on UNIX type operating systems. Seriously, removing the mdadm module is the silliest thing I've ever heard anyone doing. Thankfully they can't remove md, as it's a piece of the kernel. Do you really want to trust your environment to a company like that?They remove WHAT?? Are you joking? I wasn't aware of that. My last experience with Proxomox was 5-6 years ago.
They've always been against using software RAID. Even back then. Of course, if you're at all cognizent of the thing, and the fix is super easy, install mdadm.
-
@scottalanmiller said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
I've still been researching this topic. After digging deeper, I was curious as to why nobody recommended Proxmox...
We get asked this all the time.
- It's just a GUI on top of KVM and Open-VZ (and now LXC). It's weird and complex and while a GUI is nice, we have GUIs already that work great and don't require completely third party packages.
- The ProxMox company are scammers and rotten people. You don't want to deal with them. This isn't a nice project.
- @StorageNinja can tell you, they actually run a full on spam marketing organization. They are deleted constantly with fake accounts on SW. We've been dealing with them spamming constantly for about five years.
- It's attempting to solve a problem we don't have.
Your points are all true. The major selling point is that oVirt is too much a hassle to configure and manage, and the last time I tried it I wasn't able to use it in any productive way. Something like XO for KVM could be a deal breaker for the GUI aficionados. As of today I can do anything without a GUI on plain KVM (virsh console is my friend), so I don't really care/need it, but a lot of people want it of course.
-
@travisdh1 said in Linux OS advice for building a SAM-SD:
They've always been against using software RAID. Even back then. Of course, if you're at all cognizent of the thing, and the fix is super easy, install mdadm.
I'm curious about this statement as Proxmox fully supports ZFS filesystems via GUI and CLI...
-
They'd have a hard time blocking it at the CLI. Possible, but hard. Does ProxMox implement software RAID via ZFS from the GUI? I've never tried it since they added ZFS.
