LXD
LXD is a manager/hypervisor by Canonical for containers (via LXC) and virtual-machines (via QEMU).nutanix
proxmox
xcp-ng
Hyper-V
OpenVZ
chroot
LXC
Do you have a great relationship between the SQL Server, storage, and network teams?
Do all of the teams have read-only access to each others’ tools to speed up troubleshooting?
Do all of the teams have access to the on-call list for all other teams, and feel comfortable calling them?
Do you have a well-practiced, well-documented troubleshooting checklist for SQL Server outages?
Does your company have a good change control process to avoid surprises?
Do you have an identical environment to test configuration changes and patches before going live?
If the answer to any of those questions is no, consider honing your processes before adding complexity.
Anything with a dongle or physical hardware requirements (e.g. ASICS/GBICs).
Systems that stress RAM, I/O or CPU (e.g. heavily used databases).
Applications/Operating Systems where license/support agreements don't permit virtualisation (e.g. arguably Oracle on VMWare).
Anything mission critical that hasn't been properly tested in a virtual environment.
Anything on which your physical environment depends (e.g. door access control).
Anything on which your virtual environment depends (e.g. domain controller). If the virtual environment crashes and you can't logon to fix it because AD is hosted in that virtual environment, then you have a big issue.
Anything that must be secure (i.e. not accessible by the hypervisor admins).
Anything on which time sync is critical. Mitigate using NTP on all physical hosts.