@phlipelder said in Hyper-V Server 2016 guest licensing question:

The guests on an OEM licensed host can be moved to another host whether it's licensed OEM, VL, or Retail so long as the destination host is licensed to receive those guests.

That makes no sense. That's not moving it, that's buying it twice. Very different things.

That's like "can I move my house from here to there"? People mean take the same house and shift its location. Not buy a second house in the new location and give up the old one.

@oksana

I doubt you will find the audience you are looking for at reddit, but good luck.

Go figure...CentOS-7 UEFI vm on Windows Server 2019 "Preview" w Hyper-V installs no problem!!!

@vhinzsanchez Containers are lighter and faster. And they are a type of virtual machine, Type-C virtualization. So things like performance and density alone are reasons that containers are popular.

You can restart the Hyper-V Virtual Machine Management service or the Windows Remote Management service and it should work.

@scottalanmiller said in KVM & Networking:

I have currently maybe 65 VMs on my KVM host, they each have their own IPs and are bridged. But there is a firewall and NAT sitting in front of all of it.

This is really how it is most cases regardless of hypervisor.

The only exception is in non-production when dealing with KVM + Wireless NIC... I haven't had time to see if I could get it to bridge somehow, so I'm stuck with NAT on my laptop. But, this is not an issue with servers, as they don't use wireless and this seems to be specific to wireless.

@travisdh1 said in Storage Setup for KVM:

@emad-r said in Storage Setup for KVM:

@eddiejennings

keep your images and ISOs in the default location of /var/lib/libvirt/images/?

Yes I do, but I create 2 new folders there, iso and vm.

Fedora will be presented a 4 TB block device ?
Why dont you separe that a little, and have more fun. Block device I assume DAS, if no why dont you make the storage reliable and robust, and make it its own server, like another fedora or centos install, with RAID 10 and the simplest option to share is NFS, and this way you can have many KVMs and the migration feature will actually work, and you can do RAID on just /var, and you scan scale easily with KVM nodes + KVM nodes can be state file, think salt stack, and you can treat them as pure compute nodes.

Because @EddieJennings is talking about his home lab, which will consist of a single 1U server. That hadn't been mentioned in this thread.

Bah! Folks should be able to read my mind ;). There were some good ideas in this thread though.

What I decided on was giving enough space to / live comfortably, and gave everything else to /var.

@eddiejennings said in Determining resources for hypervisor:

@black3dynamite said in Determining resources for hypervisor:

Instead of using Fedora as a firewall VM, how about using VyOS?
https://wiki.vyos.net/wiki/User_Guide

I was thinking of that as well, since the OS for the ERLs.

EdgeOS and VyOS are cousins, both descended from Vyatta.

@tim_g said in Networking and 1U Colocation:

fail2ban

Fail2ban does nothing with key based access. It's denied before fail2ban even sees it.

@krisleslie said in Adding additional Drive to XenServer host, get error:

@black3dynamite i use 1 hdd 😞

I meant virtual disks. VM1 with virtual disk 1 = OS and virtual disk 2 = data

@dustinb3403 said in Virtualizing Your Cudatel Appliance:

@scottalanmiller said in Virtualizing Your Cudatel Appliance:

Go ahead, download FreePBX and start playing with it. You could have installed it while reading this article!

Any good installation guides here on ML?

@JaredBusch has a great series of posts for FreePBX here.

https://mangolassi.it/topic/11805/freepbx-13-setup-guide

Also we could achieve hyperconvergence "the other way" (unlike having a global shared filesystem like Gluster or Ceph) but use fine grained replication (per VM/VM disk). That's really interesting (data locality, tiering, thin pro etc.). Obviously, we'll collaborate to see how to integrate this in our stack 🙂

Hi Kelsey,

First of all, as previously mentioned in the thread, the IPOD scenario is absolutely atrocious no matter how you look at it. You pay more to get more hardware to manage to get lower resiliency. Here is a very short paper on why it's particularly important to have HA or FT in a virtual inrastructure:
https://www.starwindsoftware.com/fault-tolerance-and-high-availability-page

A way to play around IPOD is replicating local storage across the hypervisor hosts. Here is a doc describing how it's done:
https://www.starwindsoftware.com/whitepapers/starwind-virtual-san-whitepaper.pdf

Also, our forums are pretty helpful and you can ask different virtualization, storage, HA questions there:
https://forums.starwindsoftware.com

@storageninja said in VMware vSphere Update Manager Client - Is there a version 6.5?:

@wrx7m A 6.5 vCenter can manage a 6.0 host just fine.

Right. That is why I upgraded vCenter server to 6.5 🙂