Description of problem: systemd-detect-virt uses vendor names such as microsoft and oracle which is really problematic as these vendors have more than one virtualization technology. For example, Oracle has Oracle VM (xen) and Oracle VirtualBox. I could send in patches to change the names to be more specific (ie) hyperv and virtualbox with legacy compatibility for vendor names. Let me know if this makes sense.
Currently, there's qemu, kvm, vmware, microsoft, oracle, xen, bochs, chroot, uml, openvz, lxc, lxc-libvirt, systemd-nspawn, docker. So the only problematic ones would be microsoft and oracle. I think that so far this is not confusing, and e.g. oracle is understood to be virtualbox. If they introduce another proprietary technology, we can always use a more specific name for it, 'xxxxxx' or 'oracle-xxxxxx'. I *think* that the trouble of providing compatiblity handling and documentation updates is not worth the (small) additional clarity in this case. I'm inclined to let things be for now and close this. I think that those kinds of proposals are better handled on the ML, where there's more eyes. Please post there if you think it requires further discussion.
http://cgit.freedesktop.org/systemd/systemd/commit/?id=b3a2a7ceb7b0db3003c205bc49853fd62df155dc
initscripts-9.56.1-1.fc21, systemd-216-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/initscripts-9.56.1-1.fc21,systemd-216-3.fc21
initscripts-9.56.1-2.fc21, systemd-216-5.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.