Linux OS advice for building a SAM-SD
-
2TB minus 4GB is the limit for local storage.
Detached storage doesn't have this limit.
-
If I was building this, I would use KVM on Fedora with a Fedora guest VM, just because I prefer Fedora/RHEL. No other real reason.
-
@dustinb3403 Oh wow, I was not aware of the 2TB virtual HDD limit with XenServer. I will be looking into a new Hypervisor for this. Thanks for the heads up! I like XenServer and ESXi. I personally didn't like working with Hyper-V and it was annoying that it had to be integrated with Active Directory. @JaredBusch I will check out KVM, but with no GUI, it doesn't not seem as easy to work with as others.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
@JaredBusch I will check out KVM, but with no GUI, it doesn't not seem as easy to work with as others.
You mean a GUI like this?
-
@dustinb3403 said in Linux OS advice for building a SAM-SD:
Turnkey isn't an easily supported system, but it's easy to get invested in.
I would avoid Turnkey across the board. Nothing against them individually, just conceptually. They fall into the Jurassic Park trap.
-
@jaredbusch said in Linux OS advice for building a SAM-SD:
I don't use XenServer, but wasn't there some issue with larger disks on the guest machines?
@DustinB3403 should know that answer.
Yes, KVM might be better here.
-
@jaredbusch said in Linux OS advice for building a SAM-SD:
If I was building this, I would use KVM on Fedora with a Fedora guest VM, just because I prefer Fedora/RHEL. No other real reason.
Same here. Fedora on KVM sounds like the way to go.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
@dustinb3403 Oh wow, I was not aware of the 2TB virtual HDD limit with XenServer. I will be looking into a new Hypervisor for this. Thanks for the heads up! I like XenServer and ESXi. I personally didn't like working with Hyper-V and it was annoying that it had to be integrated with Active Directory.
Hyper-V has no dependency on Active Directory. While we could discuss the merits of using or avoiding AD, tons of people believe that Hyper-V should not be connected to AD, so using it that way is extremely popular.
-
@scottalanmiller said in Linux OS advice for building a SAM-SD:
tons of people believe that Hyper-V should not be connected to AD, so using it that way is extremely popular.
We have a thread somewhere stating why that is a silly thing to do if they already have AD. Obviously if there is no AD, that is fine.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
@dustinb3403 Oh wow, I was not aware of the 2TB virtual HDD limit with XenServer. I will be looking into a new Hypervisor for this. Thanks for the heads up! I like XenServer and ESXi. I personally didn't like working with Hyper-V and it was annoying that it had to be integrated with Active Directory. @JaredBusch I will check out KVM, but with no GUI, it doesn't not seem as easy to work with as others.
The issue is with local storage only. When using detatched storage this issue isn't present. Some weird limit that the devs had at the time.
You can have something like 16TB attached to a single VM, just split up 8 times, which could then be spanned in the VM so it looks like a single drive.
-
I think I was confusing KVM with Xen. Maybe it was Xen that has no GUI. So am I just just doing a Fedora minimal install and adding the KVM package? How are you managing the VM's with the GUI? Are you installing a KVM management tool on an other pc? Or are you running Fedora with a desktop and opening up the KVM virtual machine manager app from there? I have a lot to read up on.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I think I was confusing KVM with Xen. Maybe it was Xen that has no GUI.
All hypervisors have a GUI if you add one, none have one if you don't. It's universal. In theory, someone could make a hypervisor with a build in GUI, but that would be crazy and no one has ever done it and we don't anticipate that anyone ever will. But no hypervisor limits you to that and there is no hypervisor on the market for which a GUI has not been built. All hypervisors have multiple GUI options today, in fact. Some are better than others, for sure, but GUI vs no-GUI is not a limitation.
-
@dustinb3403 said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@dustinb3403 Oh wow, I was not aware of the 2TB virtual HDD limit with XenServer. I will be looking into a new Hypervisor for this. Thanks for the heads up! I like XenServer and ESXi. I personally didn't like working with Hyper-V and it was annoying that it had to be integrated with Active Directory. @JaredBusch I will check out KVM, but with no GUI, it doesn't not seem as easy to work with as others.
The issue is with local storage only. When using detatched storage this issue isn't present. Some weird limit that the devs had at the time.
You can have something like 16TB attached to a single VM, just split up 8 times, which could then be spanned in the VM so it looks like a single drive.
I believe the limit is because of ext3.
-
@black3dynamite said in Linux OS advice for building a SAM-SD:
@dustinb3403 said in Linux OS advice for building a SAM-SD:
@magicmarker said in Linux OS advice for building a SAM-SD:
@dustinb3403 Oh wow, I was not aware of the 2TB virtual HDD limit with XenServer. I will be looking into a new Hypervisor for this. Thanks for the heads up! I like XenServer and ESXi. I personally didn't like working with Hyper-V and it was annoying that it had to be integrated with Active Directory. @JaredBusch I will check out KVM, but with no GUI, it doesn't not seem as easy to work with as others.
The issue is with local storage only. When using detatched storage this issue isn't present. Some weird limit that the devs had at the time.
You can have something like 16TB attached to a single VM, just split up 8 times, which could then be spanned in the VM so it looks like a single drive.
I believe the limit is because of ext3.
EXT3 has that limit, but the limit actually exists in this case because of the legacy container type being used.
-
I just want to mention that the KVM Hypervisor does take more than Linux basic knowledge. After @JaredBusch and @scottalanmiller recommended KVM on Fedora for the SAM-SD OS I have been playing with the KVM Hypervisor on a minimal Fedora install. I was able to successfully get a working KVM Hypervisor running. I realize that I've been very spoiled with the ESXi Hypervisor. I will require a more GUI based Hypervisor setup. I played around with the virt-manager which is a nice alternative to the cli for novice Linux users. There is still too much for me to learn with KVM and I never really did find instructions that really spell it out for me. I'm trying not to use VMware ESXi. I'm going to re-visit Hyper-V 2016 standalone with a Fedora Server (with desktop) VM to be my NFS file server. I'm open to any advice or words of encouragement to re-direct my focus back to the KVM Hypervisor.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I just want to mention that the KVM Hypervisor does take more than Linux basic knowledge. After @JaredBusch and @scottalanmiller recommended KVM on Fedora for the SAM-SD OS I have been playing with the KVM Hypervisor on a minimal Fedora install. I was able to successfully get a working KVM Hypervisor running. I realize that I've been very spoiled with the ESXi Hypervisor. I will require a more GUI based Hypervisor setup. I played around with the virt-manager which is a nice alternative to the cli for novice Linux users. There is still too much for me to learn with KVM and I never really did find instructions that really spell it out for me. I'm trying not to use VMware ESXi. I'm going to re-visit Hyper-V 2016 standalone with a Fedora Server (with desktop) VM to be my NFS file server. I'm open to any advice or words of encouragement to re-direct my focus back to the KVM Hypervisor.
You couldn't find any good guides to KVM? We should see about writing one here.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I just want to mention that the KVM Hypervisor does take more than Linux basic knowledge.
Depends on how you get it. You can get KVM from someone like Scale and never see anything of Linux ever.
-
@magicmarker said in Linux OS advice for building a SAM-SD:
I just want to mention that the KVM Hypervisor does take more than Linux basic knowledge. After @JaredBusch and @scottalanmiller recommended KVM on Fedora for the SAM-SD OS I have been playing with the KVM Hypervisor on a minimal Fedora install. I was able to successfully get a working KVM Hypervisor running. I realize that I've been very spoiled with the ESXi Hypervisor. I will require a more GUI based Hypervisor setup. I played around with the virt-manager which is a nice alternative to the cli for novice Linux users. There is still too much for me to learn with KVM and I never really did find instructions that really spell it out for me. I'm trying not to use VMware ESXi. I'm going to re-visit Hyper-V 2016 standalone with a Fedora Server (with desktop) VM to be my NFS file server. I'm open to any advice or words of encouragement to re-direct my focus back to the KVM Hypervisor.
I found KVM to be quite a bit easier than Hyper-V. Did the KVM GUI tools not work for you?
-
@scottalanmiller I only used the Virt-Adapter GUI tool. Where I was having trouble was making KVM see my drive volume on my hardware RAID controller. I then added a network bridge. I was at the point where I was creating a new VM and KMV didn't like my network bridge. Rebooted my KVM host and she wouldn't come out of recovery. I didn't like Hyper-V when I was testing it out a few months ago. Thanks for making me aware of Scale. I will check that out.
-
@scottalanmiller said in Linux OS advice for building a SAM-SD:
words of encouragement to re-direct my focus back to the KVM Hypervisor.
I found KVM to be quite a bit easier than Hyper-V. Did the KVM GUI tools not work for you?
The issue is a bit of the same issue I have with KVM. It's completely build it yourself. (unless you're using Scale). Which means bringing in a gui interface, selecting a dom0 etc etc.
It's a lot to plan and implement from the get-go for someone who is expecting a XenServer or ESXi type solution. Single ISO, install it to the hardware and download a command center of sorts.
If there was a guide on ML of here's a beginners approach to KVM with a full GUI, backups (the whole 9) then I could see more people picking it up to use it.
As it is, it's a , well fedora, or centos or debian or suse, and then you have libvirt or ovirt or the CLI only and then you have . . . .
There needs to be a simple "this is a windows admin (introductory) approach to setting up KVM for production environment, including a GUI and how to get things like ISO repos and backup repo's in place". As I certainly want to test KVM, but I don't want to have to pick every piece and install each.
