You can do that, but they're not really replacements for one another, and there are lots of things that can pull one way or another for that use case.
- You generally don't want to run storage servers virtualized.
- Tooling matters. There are multiple reasons I generally do things the same way at home as I do at work (within reason).
- Probably a niche concern, but I have some hardware that is only configurable during early boot.
- Virtualization costs performance. Not a huge issue at home, granted, and you have to quantify it for your specific workload. (It is usually going to be IO.) But it certainly can matter with home workloads; home theater video processing is probably the most common.
I use both for what they're good at. IMPI is for managing hardware. Virtualization is for not needing more of it.
- You generally don't want to run storage servers virtualized.
- Tooling matters. There are multiple reasons I generally do things the same way at home as I do at work (within reason).
- Probably a niche concern, but I have some hardware that is only configurable during early boot.
- Virtualization costs performance. Not a huge issue at home, granted, and you have to quantify it for your specific workload. (It is usually going to be IO.) But it certainly can matter with home workloads; home theater video processing is probably the most common.
I use both for what they're good at. IMPI is for managing hardware. Virtualization is for not needing more of it.