@eleceng The setting that you want is called "AutoProtect"

@scottalanmiller said in Multiple Virtual Disks and Application Performance:

Remember.... just because you are virtual does not imply that your storage is virtual, nor does virtual storage imply that the storage will be shared between workloads or VMs. None of that is implied or suggested in going virtual. You still maintain all proper storage management decision making when virtual as you did physical. You don't get to give any of that up.

In restrospect, I probably ought not have included the System Center Dude stuff in the discussion, since it seemed to just cause confusion about what I was curious.

You still maintain all proper storage management decision making when virtual as you did physical.

I believe this is the greatest takeaway from the discussion. Regardless if the environment is like the one I'm in where ultimately one physical storage device is hosting all of the virtual storage within the VMs.

@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!