@EddieJennings said in MacVTap Modes: One option I didn't see in the redhat doc was openvswitch. Don't they support it? The link I posted was for RHEL 6. I just now saw that RHEL 8's documentation is online. I glanced through it and didn't see that mentioned. I'll read it more closely tomorrow. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/configuring-virtual-machine-network-connections_configuring-and-managing-virtualization There's no mention of openvswitch anywhere in that document. I am aware of XenServer and XCP-ng uses it by default. So its possible RHEL just prefers using macvlan/macvtap instead of openvswitch.

@wrx7m said in VMware Host Cannot Connect from vSphere Client: Could also be an issue if a vendor-specific ISO was used to initially install ESXi. I ran into a similar problem with Dell; I had to get the Dell ISO from their downloads for the specific server model/service tag. For 6.0 this is fine (you'll use this to get ASNC drivers). You can also add the dell VIB depot to get them this way also. For 6.7 Dell has (thankfully) stopped shipping ASYNC drivers and moved 100% to inbox. It's all for 3rd party management VIBs. Honestly I've seen 3rd party VIBs be a culprit for updates before. I'd make sure you are updating the BIOS/FIrmware also when updating ESXi (People forget this sometimes).

@black3dynamite said in Converting VMware VMs to KVM: I haven't been keeping up with Windows Admin Center for awhile. Was that an option to manage Hyper-V? It will be, but I'm not sure that it is yet. We've tried and not been able to get it working even internally anywhere, let alone externally. Once they figure out stability and authentication, I assume that it will be great for that. Being that this is 2016, it's going to suck hard. And if there is a Hyper-V issue, WAC would be down which is a problem in a small environment like this.

@WrCombs Also remember once you have vm's setup and running they are just files. So that also makes it real easy to backup with robocopy, veeam, rsync or borg. Its one of the many great advantages of virtualizing, your expanding your options alot.

WSL2 tells us a lot. First, Microsoft is really making it more known that WSL has no Linux and is just Ubuntu (or whatever) on the Windows kernel. Second, Microsoft is making it clearer that there was no virtualization going on in WSL. Third, now there is Hyper-V and a Linux kernel involved. So now it is just virtualizating a Linux instance on top of Windows. Fourth, now it is much faster. That means that Linux on Hyper-V is faster than Windows on bare metal!

@Dashrender said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @wrx7m said in Planning for New ESXi Hosts - Which CPU Metrics Should I Use?: @Pete-S They list both the 61xx and 62xx as options for the R740XD. Good! What CPUs do you have in the R720 today? 1 or 2 CPUs? Do you want the new ones to be faster or just capable of running more VMs? I have 2 x E5-2609 CPUs in each server. I would like faster, but more VMs would be the priority. The E5-2609 CPUs are at the low end of what was available at the time so no problem there. Actually, are you looking to keep the old servers around for testing and such? In that case you could just drop in refurbished CPUs that are faster and/or has more cores for very little money. If the server can take E5-2600 V2 you can get up to 12 core CPUs. yeah, but Windows licensing is an issue, assuming multiple CPUs... for a test server, not likely worth going over the 16 cores. Not to mention the test server might require licensing (if needed beyond the 90 day test period for something). Two 8-cores would be an option. For instance two E5-2690. They are 2.9 GHz base frequency and have 8 cores. About $100 each when buying refurbished. About 50% faster per core (2609 have no turbo) and about 3 times faster multicore performance. Has more cache and faster memory transfer speed. Was a very high end CPU at the time. Was listed at $2000 while the E5-2609 was $300. The fastest 8-core E5-2600 V2 CPU is the E5-2667 V2. 8 cores and base frequency of 3.3 GHz. It will likely also be an option for the R720XD. V2 uses 22nm technology so uses less power with the same clock speed and can fit more cores or run higher frequencies.

@scottalanmiller said in P2V Windows 2000 on KVM: So this is ridiculous, but we just found out that it is actually 2003 R2, not 2000. So I assume that this will be way better. I had a ton of issues getting mine to work - I had to run chkdsk like 15 times before it finally booted... I don't recall what migration tool I used.

For Fedora you can just do sudo dnf install vagrant-libvirt

1 .So can ovirt be run with only 2 nodes? 2. With those 2 nodes, do you need a separate shared storage device for live migrations, etc, or can you have local storage (Like "vsan")?

@FATeknollogee said in oVirt Host Choices for Production: @EddieJennings I would start by using oVirt Node (it's based on CentOS), it's the simplest, least hassled way of setting up. Yeah, they have their own Node deployer, I'd generally just use that.

Very Interesting!