On Fri, 19.06.15 11:13, Igor Bukanov ([email protected]) wrote: > Hello, > > forthcoming VirtualBox 5.0 hypervisor (currently at RC1) supports > paravirtualization using Hyper-V or KVM interfaces. When the latter is > used with a linux guest then systemd-detect-virt prints kvm. I suppose > at least the manual page for systemd-detect-virt should be updated to > indicate that the command output does not reflect a particular > implementation but names hupervisor technology. > > However, the issue then is what to do with ConditionVirtualization= > testing for oracle in unit files. Under kvm mode that gives false > preventing in my case mounting a host directory with config files > using vboxsf module. I suppose I should just deal with that and try to > mount vboxsf share both under kvm and oracle, but perhaps > systemd-detect-virt should be updated to still print oracle even when > VirtualBox uses paravirtualization?
Yeah, I am pretty sure we should update src/shared/virt.c then and ensure we detect the new version correctly. I am pretty sure there's a way how to discern kvm and vbox5 even then, it's just a matter of figuring out how. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
